16. Roadmap and Risks
eBattery’s roadmap describes its evolution from an app that meets the daily needs of electric vehicle owners to a platform that connects digital services with physical charging infrastructure. At the center of this evolution is preserving the benefit offered to users at every stage and adding new services to the existing experience in a reliable way.
Discovering a station on the map, planning a suitable trip to that station, using the charging service and paying are consecutive actions. However, each of these actions relies on different data sources, technical connections and service responsibilities. Similarly, financing a station project digitally, building it physically and operating it on a regular basis are interrelated processes that require separate expertise.
eBattery manages these relationships with a phased development model. In the first phase, the experience that forms the basis of daily use is strengthened. Then transaction and service capacity is expanded. In the platformization phase, the aim is for partners, charging infrastructure and the Web3 layer to grow together within a shared system.
The basic principle of the roadmap is that every new feature becomes a service that is understandable to the user, technically verified and operationally supportable.
The dates given refer to development and launch targets. The opening of services proceeds with product readiness, platform approvals, completion of integrations and fulfillment of the conditions required by the relevant activities.
16.1 Phases — MVP, Expansion, Platformization
eBattery’s development plan consists of three main phases. These phases do not represent completely disconnected versions of the product. Each phase builds on the user experience and technical know-how gained in the previous stage while adding a new capability to the platform.
Phase One: MVP and Global Launch — Building the Foundation of Daily Use
eBattery’s launch date targeting global reach on iOS and Android 1 November 2026 has been set. Türkiye is one of the local implementation and growth areas of this global strategy.
At this stage, the MVP refers to the first product scope that can meet a meaningful need in the user's electric vehicle life from start to finish. The main goal is that when a driver opens the app, they reach a concrete benefit related to their location, vehicle or trip plan.
The launch core consists of the following areas:
Charging station discovery, filtering and station details on the map.
Favorites, map layers and Emergency Charge access.
Real-time availability information at stations within the integration scope.
Vehicle- and trip-focused support through eBattery AI.
Route planning, trip planning and efficiency analysis.
Community, topic structures and messaging between users.
Social map visibility under the user's control.
Short-term road alerts.
Game Zone, quests, and Web2 loyalty mechanics.
The first-use experience is approached with an understanding that it does not have to introduce all of these modules at once. A user looking for a station nearby can use the map directly. A user who wants to prepare for a trip can move to the planning flow. A user looking for information about a vehicle experience can reach the relevant conversation through the community.
The success of this phase is assessed not only by the number of downloads but by whether users can benefit from the core functions and come back to use them again. A station search that returns results, a generated route being reviewed, the AI recommendation being found usable, and useful interactions forming in the community are behaviors that show the product's value.
At this stage, global reach and local service depth are managed together. The app being available in different countries does not mean that the same operator connections or the same data coverage exist in every country. The functions shown to the user reflect the actual service and data access in their region.
Second Phase: Expansion — From Discovery to Transactions and Service Use
The expansion phase aims to let the user obtain the relevant service based on the information they gain within the app.
At this stage, charging and unified payment, EV Market, mobile charging support, insurance and comprehensive coverage, and home charging services are introduced gradually. Each service is developed together with its own partnership and operating structure.
Charging and unified paymentensures that the process, which starts with station selection at supported operators, is completed with the session start, monitoring, ending and payment steps. Users can clearly see in the app which actions they can take at which station.
EV Market, supports product and service discovery based on vehicle compatibility. Chargers, cables, accessories and related products are presented together with seller information, technical specifications and after-sales processes.
Mobile charging support, aims to let users who run out of charge or cannot reach a suitable station with their current energy level create a service request. Opening this service for use is planned together with regional field capacity, service area, vehicle compatibility and support processes. While the Emergency Charge feature on the map guides users to a suitable station, mobile charging support is being developed as a physical assistance service.
Insurance and comprehensive vehicle insurance, covers processes such as quotes, coverage review, purchase and policy tracking through authorized partners.
Home charging, starting with access to device and installation services, moves toward connected and shared use of suitable points.
Pro membership is also positioned as a subscription tier that supports the product's sustainable service structure. The rights offered to the user, the terms of use and the fees are shown clearly in the membership flow.
In this phase, the main measure of growth is the quality of service completion. Successful charging sessions, accurate payment records, completed orders and resolved support requests show that expansion is progressing in a healthy way.
Third Phase: Becoming a Platform — Partners, Physical Infrastructure and Web3
In the platformization phase, eBattery’s individual user experience is supported by a broader structure in which partners can offer services and physical charging infrastructure can be managed.
The main development areas of this phase are B2B solutions, white-label services, charging operations, connected station data and RWA-based project participation.
For eBattery's transition to licensed charging operations and the activation of Web3/RWA work 2027 is targeted. In this scope, operation, project development and investor access are addressed together with their own preparation processes.
The RWA model aims to provide digital representation of participation rights in station projects, presentation of project information through Launchpad, participation by eligible users, and supported secondary transactions. Stations’ digital identities, IoT data and oracle connections support the link between physical operations and digital records.
An important part of this phase is being able to track financial and operational records together. Energy consumption, collections, operating expenses, maintenance and renewal reserves, and the calculation of distributable net profit are handled in a structure that can be explained at the project level.
The white-label approach, in turn, lets partners in different markets benefit from these technological capabilities. The permits, service responsibilities and operating conditions required by local operations are met together with the operating model in the market concerned.
| Phase | Main focus | Value delivered to the user and the ecosystem | Progress measure |
|---|---|---|---|
| MVP and global launch | Map, AI, planning, community and game zone | Access to daily EV needs and decision support | Reliable operation of core flows and repeat use |
| Expansion | Charging–payment, commerce, assistance and vehicle ownership services | From information to completing the transaction | Integration quality and successful service delivery |
| Becoming a platform | B2B, operations, connected infrastructure and RWA | Linking digital services with physical projects | Operational readiness, regulatory compliance and traceable records |
16.2 Integration-Dependent and Planned Features
The scope of eBattery's service rests on the app's own functions working together with capabilities provided by external systems. For this reason, whether a feature is available is determined by the transactions the relevant connection supports.
For example, a station being on the map does not mean charging can be started at that station through the app. Similarly, access to tariff information and access to real-time availability data may require different connections.
This distinction is made directly visible in the user experience. In station details, accessible information, the actions that can be taken and the freshness of the data are presented clearly.
Managing information and transaction authorities separately
Station services are evaluated at four basic levels:
| Proficiency level | Scope offered to the user | Core dependency |
|---|---|---|
| Discovery | Location, operator, connector and power information | Station record and data usage right |
| Current status | Availability, operating status and current rates | Operator or authorized data source connection |
| Session management | Starting, monitoring and ending a charge | Operator integration that supports the transaction |
| Payment and record | Collections, transaction history and related financial records | Payment infrastructure, reconciliation and service processes |
This structure ensures that the real service scope is shown for each station. An unsupported operation is prevented from being presented as available; accessible alternatives are explained to the user.
Conditions for putting the service into operation
Opening a new connection for use is assessed beyond establishing a successful technical connection. In addition to normal transaction flows, scenarios of delay, connection interruption, incomplete response and failed transaction are also verified.
For example, if no response is received from the operator after a charging start request, it is not appropriate to resend the same request without checking the session status. On the payment side as well, cases where the outcome of a collection remains uncertain must be resolvable without making the user pay a second time.
For this reason, the rollout approach includes technical verification, controlled use, support readiness and monitoring processes together. As the service scope is expanded, the quality of the earlier user experience is preserved.
Regional service coverage
Commercial and physical services are matched with the real capacity of service providers. For mobile charging support, the service area is taken into account; for home charging, installation access; for EV Market, delivery coverage; and for insurance services, the markets where the product can be offered.
The user sees the services available at their location and the terms that apply to them. This approach ensures that the global product experience is supported by locally applicable services.
Version and scope communication
When new features are released, their scope is communicated through in-app explanations and release announcements. The communication states which users, regions or operators the feature applies to.
The distinction is maintained between a roadmap service presented as a development goal and one that is actively available. This keeps product communication consistent with the real experience the user meets in the app.
16.3 Regulatory, Technical, Adoption and Competition Risks
eBattery’s approach to risk management is based on understanding the conditions under which the service may be affected, reducing those effects, and preparing the processes to be applied when problems occur.
Risks are handled as part of product development and operating decisions. Along with the benefit a feature provides to the user, its impact on data security, service continuity, cost and operations is evaluated.
Regulation and Operating Authorizations
eBattery’s different service areas give rise to different operating responsibilities. Charging operations, payment, insurance, commerce and investment participation are each assessed separately within the service model of the relevant country.
In Türkiye, charging network operation and commercial charging services are subject to the licensing and operating framework regulated by EPDK. eBattery's operator plan targeted for 2027 rests on the completion of the required permits and operational preparations.
On the Web3 side, the rights a digital asset represents, along with its technical standard, matter. In the European Union, whether a crypto-asset has the nature of a financial instrument affects the applicable regulatory framework. ESMA’s approach provides that assets called NFTs are also assessed on the rights and characteristics they carry.
For this reason, in eBattery's RWA preparation, project contracts, the investor's right to participate in net profit, transfer terms, investor eligibility and the required operating authorizations are addressed together. The authority to operate a station and the authority to offer an investment product or provide secondary trading services are separate areas of assessment.
Fiat on-ramp and crypto-asset-related payment functions are also activated per country, together with suitable service providers, terms of use and tax obligations. The goal of global access does not mean these services will be offered with the same scope in every country.
Technical Continuity and Data Reliability
External dependencies in map, route, operator, payment and AI services may cause delays, outages or data inconsistencies. eBattery's technical design aims to limit the effect of these situations on the user.
Checking data freshness, recording critical transactions, safely handling repeated requests and separating services from one another to a sufficient degree are parts of this approach.
When current availability information cannot be obtained from a source, an old record should not be presented as if it were current. Similarly, the AI layer should not produce a station status or price it cannot access as definite information. Separating source information from forecasts preserves the reliability of decision support.
The security approach covers limiting access permissions, monitoring critical administrative actions, protecting sensitive data and preparing incident response processes. Verifying backup and restore processes is also part of service continuity.
In the Web3 layer, smart contract security, key management and verification of oracle data are addressed separately. Recording data on-chain does not by itself remove an error at its source. For this reason, the aim is to establish reconciliation between device records, collections and expense documents.
User Adoption and Product Complexity
A broad app can make the first-use experience harder while offering the user many options. eBattery manages this risk with flows that bring forward the user's need at that moment.
A person who wants to use the map does not need to learn all the modules, a person who wants to join the community does not need to open an investment account, and a person who wants to plan a route does not need to use commercial services. Each module offers a clearly understandable benefit on its own, while working together through a shared account and vehicle profile.
Notifications, quests and loyalty mechanics are also assessed according to this principle. The aim is to offer useful information at the relevant time instead of needlessly distracting the user.
Adoption performance is tracked through activation, repeat use and users completing core tasks. User feedback, support requests and drop-off points help set product development priorities.
Competition and Economic Sustainability
EV apps, operator services and vehicle manufacturers' digital solutions continue to evolve. Competitors expanding their coverage, price changes or new partnerships may affect user expectations.
eBattery’s approach in this area focuses on measurable benefit for the user and a healthy service economy. The development priority of a new module is assessed on the basis of usage need, expected value, operating cost and contribution to the existing experience.
AI, map, payment, support and reward costs are tracked as the business grows. Pro membership and other revenue channels are managed together with service costs and the value offered to the user.
Especially in reward and referral programs, the difference between activity gained through a campaign and lasting use is taken into account. User acquisition is not scaled up in a way that would weaken service quality or unit economics.
Continuity of Physical Stations and RWA Projects
In physical charging projects, situations such as device failure, changes in energy cost, low usage, loss of site access or the end of the site agreement may affect operating results.
In eBattery’s RWA model, these effects are addressed together with project-level budgeting, the maintenance plan, insurance coverage and renewal reserves. The investor’s share in monthly distributable net profit is calculated from actual revenue and expenses. The monthly calculation and distribution arrangement does not mean that a positive or fixed return will arise every month.
The goal of operating the station over the long term is supported, where necessary, by device renewal and, under suitable conditions, relocation plans. The rights and obligations that apply in cases of forced closure or where continuity cannot be ensured are explained in the project agreements.
The secondary market aims to allow participation rights to be transferred under suitable conditions. The ability to transact arises together with finding a buyer, eligibility checks and market conditions. Immediate sale, a fixed price or recovery of the invested amount is not guaranteed.
Monitoring of risk management
| Risk area | Management approach | Key element to track |
|---|---|---|
| Regulation and authorization | Eligibility assessment by country and service | Operating conditions and required permits |
| Integration and data | Source checking, freshness tracking, and error handling | Data consistency and service continuity |
| Security | Access control, security reviews and incident response readiness | Incident detection and resolution capacity |
| User adoption | Clear flows and features offered according to need | Quest completion and reuse |
| Economic sustainability | Evaluating service costs and revenues together | Contribution by user and transaction |
| Physical operation and RWA | Maintenance, reserve, record reconciliation and clear project terms | Station availability and accuracy of financial records |
This governance framework ensures that each new service is put into operation together with its own responsibilities. Development decisions are assessed not only by the benefit offered to the user but also by whether the service can be sustained reliably.
