3. The eBattery Thesis

eBattery's core thesis is that the value created in electric vehicle ownership grows with the quality of the relationship between the vehicle, energy, information and services. Being able to find a suitable station, plan a trip, understand costs and reach the services they need makes it easier for electric mobility to settle into daily life.

In this approach, the user experience is treated as a set of consecutive decisions. Discovering a station may influence the route decision; the route decision, the energy need; the charging experience, the next station choice; and information gained from the community, behavior related to vehicle ownership. Preserving these relationships between services can improve the benefit each module offers on its own.

For this reason, eBattery is designed as a platform that organizes electric vehicle ownership around a shared digital experience. The Web2 layer focuses on the driver’s daily needs, while the Web3 layer focuses on developing physical charging infrastructure and the traceable economic structure of station projects.

The platform’s long-term value proposition is to build a meaningful relationship between these two areas: understanding user needs better, making access to services easier, and supporting the development of infrastructure with measurable demand and operating data.

3.1 Core Hypothesis: EV Life in a Single App

3.1.1 The Integrity of Electric Vehicle Ownership

eBattery’s core hypothesis is expressed as follows:

When the interrelated needs of electric vehicle ownership are brought together in a single app through a shared user context and reliable service data, users' decision and transaction burden decreases, and the benefit the platform provides in daily life and its potential for repeat use increase.

At the center of this hypothesis is the relationship between services. Map, route planning, community, shopping and payment serve the same user while producing information that complements one another. Vehicle model, trip purpose and user preferences form a shared context that can be reused across different modules.

For example, a vehicle's socket compatibility matters in choosing charging equipment as much as in discovering stations. A trip plan the user prepares carries the route and the charging need together. Sharing the same plan in the community makes it easier for other drivers to contribute their experience of that trip.

This integrity also fits the ongoing nature of electric vehicle ownership over time. One day a user may look for a nearby station, another day plan a long trip, answer a community question or look at a product suited to their vehicle. The relationship with the platform builds continuity across these different needs.

eBattery's super app approach is based on a product architecture that organizes this continuity. The need for users to redefine the same vehicle ownership experience across different services is reduced.

3.1.2 The Value Shared Context Provides to the User

For a digital service to become suitable for the user, the need must be understood correctly. In the electric vehicle ecosystem, this need is shaped by vehicle characteristics, energy status, location, time budget and personal preferences.

Linking this information within the scope of the appropriate permissions helps the app offer more meaningful options. The user does not have to reselect their vehicle for every action, re-enter the same journey preferences or carry previously saved information over to another service.

Shared context also affects how the options presented to the user are ranked. A station being nearby, being compatible with the vehicle and being well located for the planned trip can be assessed together. This ties the information to the user’s actual need.

However, forming a shared context does not mean every piece of data must be used in the same detail across all modules. Vehicle compatibility may be meaningful for product discovery, while detailed trip history may not be needed for the same transaction. eBattery’s design approach is that each function works with information suited to its purpose.

Within this structure, personalization is a tool that helps the user evaluate options more easily. The user should be able to understand the main reason behind a recommendation and change their preferences.

3.1.3 Turning a User Need into a Service Flow

At eBattery, modules are tied to the needs an electric vehicle owner encounters. A feature's place in the platform is judged by which user decision or action it makes easier.

User need Related product area Benefit intended to be created
Finding a suitable charging point Map, filters and vehicle profile Evaluating options quickly and clearly
Planning the trip around energy needs AI, route and trip planning Feasible stops and time management
Sharing and learning from experiences Community and messaging Access to relevant information and other drivers
Managing the charging session and spending Charging and payment integrations Transaction continuity and traceability of history
Finding a product or service suited to the vehicle EV Market and service network Understanding compliance and service terms
Getting support in an unexpected energy need Access to Emergency Charge and mobile charging services Finding the solution that fits the situation
Building a regular relationship with the app Game Zone and loyalty Additional user experience that supports participation

The current product foundation of this scope consists of the map, AI, route and trip planning, community and Game Zone. Charging and payment, EV Market, mobile charging support, insurance and Home Charging services are treated as areas of expansion after launch.

The purpose of moving between modules is to make it easier for the user to complete what they started. A station selected on the map can be transferred to the route plan; a prepared trip can be shared within the community; and for supported operators, station selection can be linked to the charging session.

In this approach, each link is presented in a way that is consistent with the technical and operational scope of the relevant service.

3.1.4 Evaluating the Hypothesis with Measurable Results

eBattery’s integrated experience hypothesis is evaluated through user behavior and service outcomes. Having multiple modules in the same app is not, in itself, proof that it creates user value. Value is measured by how easily and reliably the app meets the user’s need.

For this reason, in evaluating the product, alongside the number of downloads, what matters is the user reaching their first meaningful result and returning to the platform for later needs.

For example, a user finding a suitable station, creating a workable route, or getting a relevant answer to a question in the community are different moments of value. Each of these is measured according to the purpose of the relevant module.

Size of the hypothesis Assessment approach
Reduced decision burden Time required and number of repeated actions to reach a suitable result
Continuity across modules Successfully passing a need on to the relevant service
Usefulness of recommendations Selecting a recommendation, applying it and user feedback
Service reliability Successful completion of supported transactions
Lasting user value The user returning to the app at their next real need
Economic sustainability Assessing the revenue, cost and support load the service creates together

The interpretation of measurements also depends on the context of use. Someone planning a long trip may not be expected to open the app every day. For such a user, the meaningful indicator is choosing eBattery again on their next trip.

Interaction in the Game Zone and the use of core mobility services are also tracked separately. This allows the platform to assess which feature produces entertainment and engagement and which produces direct journey and vehicle ownership benefit.

3.1.5 The Relationship Between Driver, Service Provider and Infrastructure

eBattery's thesis links the benefit provided to the user with the economic participation of the service provider.

Drivers want to reach the service that fits their needs. Charging operators, sellers and service providers, for their part, aim for the relevant user to find and use the solution they offer. The platform supports matching these two needs under suitable conditions.

The quality of this match is important. Whether a service with a high number of impressions actually reaches the right user, whether discovery turns into a successful transaction, and whether the user is satisfied with the experience are assessed together.

The RWA model on the Web3 side adds an infrastructure development dimension to this relationship. The technical characteristics and operating results of physical station projects make the asset on which economic participation rests understandable.

In this structure, the driver's daily use of the service and the investor's participation in the project have different purposes. Using Web2 services is not made conditional on investing or using crypto-assets. The relevant users access Web3 services according to their own choice and eligibility conditions.

3.2 Platform Philosophy

3.2.1 Respecting the User’s Time and Attention

In eBattery's product philosophy, time and attention are user resources that must be protected. An electric vehicle owner uses the app to continue their trip, reach a service or find an answer to a specific question.

For this reason, the product's success is judged by how clearly and easily the user can complete what they want to do. Presenting information in the right place, reducing unnecessary steps and organizing options in an understandable way are the core design principles.

For example, the priority of a user looking for a station with a low battery level is to quickly find an option that is suitable and reachable. A user preparing a trip may want to examine the alternatives in detail. The same platform must take into account the different attention and time conditions of these two needs.

This approach also shapes the design of notifications and recommendations. The aim is for the information sent to the user to be relevant, timely and manageable. Notification preferences let the user adjust their relationship with the platform.

The main measure of the convenience eBattery offers is how meaningful a task the app takes on in the user's life.

3.2.2 Openness of Information as the Foundation of Trust

A trustworthy platform makes the nature of the information it provides clear. Users should be able to tell whether the value they see is a current measurement, an estimate, a historical record or a personal experience.

The availability status of a charging station received from the operator, a comment left by a user and the estimated arrival energy calculated by the route engine are different types of information. Each is valuable; however, their roles in the decision process are different.

eBattery's approach to information is based on maintaining this distinction. Estimates are presented according to the inputs used and the data available. Integration scope is shown together with whether the relevant transaction is possible. User experiences are assessed within their own dates and context.

This principle continues on the Web3 side as well. The existence of a record on-chain does not mean that the physical event the record is based on is verified automatically. The relationship between IoT measurements, financial records, verification processes and oracle transfer must be established clearly.

eBattery's approach to transparency covers understanding what the data represents, as well as access to the data.

3.2.3 AI That Supports Human Decisions

eBattery AI is treated as an interaction layer that connects the user’s need with the app’s relevant services. The user can express their goal in natural language without defining technical parameters one by one.

Phrases such as “I want to arrive at a certain time in the evening”, “I am traveling with children” or “I want to take a short trip along the way” contain different planning preferences. The assistant’s task is to connect these preferences to the relevant calculation and service flows.

In this approach, the responsibilities of the language model and the calculation systems are separated. Route suitability, energy need and vehicle compatibility are assessed using specific data and rules. The language model interprets the user’s request, asks for missing information when needed and explains the result.

User control remains at the center of the experience. The main rationale for a recommendation should be visible; the user should be able to change their preferences and review alternatives. Transactions with consequences, such as payment or investment, are carried out within the relevant authorization and approval flows.

The model-agnostic approach also supports this philosophy. AI components are evaluated for accuracy, response time, cost, language support and reliability according to the product’s needs.

3.2.4 Privacy and User Control

Personalized service and privacy are addressed in the same design process. The benefit provided to the user depends on it being understandable for what purpose the necessary data is used.

Location data is one of the clearest examples of this relationship. Finding nearby stations, planning an active trip and being visible on the social map are different purposes of use. Users should be able to manage these functions according to their own preferences.

eBattery's approach is to organize data access by function and purpose. A user joining the community does not need to turn on social location sharing. Product recommendations based on vehicle compatibility do not depend on sharing a detailed movement history.

In infrastructure analyses too, personal records are separated from aggregated indicators. The data used to assess a service need arising in a particular area is not presented in a way that would make people's daily movements publicly visible.

Station performance and financial records shown to the investor in the Web3 layer are subject to the same principle. Accountability rests on the verifiability of the relevant project data, not on exposing users' personal lives.

3.2.5 Balanced Value Creation Among Stakeholders

A platform's sustainability depends on its participants being able to get repeated benefit. The driver must be able to reach a suitable service, the service provider must be able to reach the relevant demand, and the platform must build the economic structure that sustains this relationship.

This balance is also important in recommendation and ranking systems. The options presented to the user should be explainable through technical compatibility, access, relationship to the route, cost and current service information. Commercial promotions must be distinguishable from organic recommendations by the user.

eBattery’s goal of operating its own stations increases the importance of this principle. The discovery and comparison experience the platform offers users, alongside its role as an operator, is designed together with clear evaluation criteria.

The same approach applies to EV Market and other service areas. Product compatibility, service terms and the fees shown to the user should be clear. The user should be able to assess what benefit an option offers them.

The platform’s economic success is supported by the continuation of reliable service relationships. For this reason, short-term growth in transactions and long-term user trust are considered together.

3.2.6 The Physical Counterpart of Digital Convenience

In eBattery’s philosophy, the value of digital systems is tied to the results they create in real life. A point shown on the map corresponds to a physical service, a calculated route to a real trip, and a station’s digital identity to an operated asset.

This relationship requires attention to how design decisions play out in the field. The station’s entrance location, operating hours or user support are as important as the information in the app interface.

On the Web3 side too, the clarity of economic rights rests on the transparency of the physical project and the operating arrangement. Digital units represent the economic participation defined in the relevant project documents. The station's revenues, expenses, maintenance needs and renewal arrangement are the core components of this structure.

The account abstraction approach helps reduce the technical complexity of Web3 transactions in the user experience. The convenience offered to the user is addressed together with how clearly it can be understood which transaction is being made, which permission is being granted and what economic outcome results.

In this way, eBattery brings together responsibility for the digital experience and for the physical service within the same product approach.

3.3 Network Effect and Growth Flywheel

3.3.1 Where Growth Begins: A Completed User Need

eBattery’s growth approach starts with meeting a real user need. A user who finds a suitable station, plans a trip more easily or reaches useful information in the community gains a reason to return to the platform for their next need.

Reuse makes it possible to understand how the product performs under different conditions. User feedback and transaction results, evaluated appropriately, contribute to improving the services.

As service quality and the relevant user base grow, the value of joining the platform may increase for partners. New integrations and services may also widen the needs of existing users that can be met.

This relationship forms the basis of eBattery's growth flywheel:

Stage Value generated Contribution to the next stage
Meeting the initial need The user gets a concrete benefit A reason for repeat use is created
Repeat use The product is preferred for different needs Feedback and service requests become clearer
Improvement in product and data quality Recommendations and flows are improved The user experience gets stronger
Participation of relevant business partners Service scope expands More needs can be met
Trust and recommendation Passes the user experience on to those around them Discovery by new users is supported
New usage and contribution The ecosystem becomes more effective The cycle continues with new needs

The operation of this flywheel depends on preserving the value delivered at each stage. For growth in the number of users to translate into service quality, operations, support and data management are also developed.

3.3.2 Separating Network Effect, Economies of Scale and Learning

When assessing platform growth, different mechanisms need to be kept separate from one another.

Network effect, that new participants also create value for existing ones. A community member sharing relevant experience can improve other users' access to information. A new service provider can increase the options in a given region.

Economies of scaleis about shared infrastructure being used by more usage. Being able to use the same software components and operational processes across different services may spread some costs over a broader activity base. The result is measured against the actual cost structure.

Learning effect arises when usage results improve product decisions. Understanding why a route suggestion was changed, or which step in a transaction was difficult, can help improve the product.

eBattery assesses these three areas with separate indicators. Having more data does not by itself show that better recommendations are produced. Having more users also does not mean the same service value arises in every region.

This distinction makes the nature of growth visible. It becomes clearer in which part of the platform community contribution creates value, in which part operational efficiency does, and in which part product learning does.

3.3.3 Local Density and Global Spread

In electric mobility, many needs arise in a specific geography. The suitable station near the user, the alternatives in the corridor they are traveling, and the providers serving the area they are in directly affect the experience.

For this reason, eBattery's global growth is considered together with local service capability. A high number of users in one country does not by itself improve station or service coverage in another country.

Local density creates value when enough relevant users, up-to-date information and service options come together in the same region. On the community side, language and vehicle model, as well as geography, are what connect users to one another.

For example, people in different countries who own the same vehicle model can benefit together from some technical experiences. By contrast, regional knowledge is needed for station access or local service conditions. The platform organizes these contexts together.

In eBattery's approach, language support is one of the starting conditions of access for the user. Local service quality is built through data coverage, integrations and operational processes. In this way, the global product experience is backed by the capacity to deliver meaningful service in the market where it operates.

3.3.4 Community, Recommendation and Loyalty Reinforcing Each Other

Users passing information to one another can help the platform's benefit reach new people. A driver sharing a useful route, or giving the right directions in a vehicle group, can improve another user's experience.

At the center of this relationship is the quality of contributions. Current, relevant and clear information increases community value. As the amount of content grows, search, topic organization and moderation need to be improved.

Recommendation and referral mechanisms support passing the resulting user satisfaction on to others. The quality of participation is evaluated by whether the invited person can meet a real need and keeps using the platform.

The Game Zone and loyalty program are also a separate dimension of this relationship. They offer experiences that strengthen the user’s participation and connection to the app. Reward mechanics are managed within the program’s defined budget and usage rules.

For this reason, at eBattery, activity generated by incentives is tracked separately from lasting service use. A user performing an action only for a reward and a user returning to the platform because of a regular need are different behaviors.

The strength of the growth model depends on a healthy relationship between incentives and the core product benefit.

3.3.5 The Loop from Demand Information to Infrastructure Development

The growth relationship designed between eBattery's Web2 and Web3 layers begins with a better understanding of infrastructure needs.

Map searches, deviations along routes, user preferences and accessible transaction data may point to needs that should be examined in certain regions. These indicators are assessed taking data scope and representativeness into account.

For example, a frequently searched area can form a potential review area. However, the extent to which search density in the app turns into real charging demand is assessed together with vehicle use in the area, existing stations, private charging access and user behavior.

After this stage, the station investment assessment continues with physical and economic analysis. Electrical connection, site access, site agreement, equipment selection and operating costs are included in the project assessment.

Commissioning a station developed under the RWA model creates a new service point. The station’s actual usage and operating results provide additional information for later assessments. In this way, a feedback relationship can be established between demand analysis and physical service performance.

The purpose of this cycle is to support a better match between capital and need. Digital interest indicators, site conditions and actual operating results are evaluated together, each keeping its own meaning.

3.3.6 Measurement Framework Showing the Quality of Growth

eBattery's growth wheel relies on an evaluation structure that tracks user and service outcomes together. Each indicator is handled so that it is clear which benefit it represents.

Field Key question being tracked
User acquisition What real need are the incoming users joining the platform for?
Initial value How easily does the user reach their first meaningful result?
Repeat use Do they choose the platform again for their next need?
Switching between modules Does the new service help the user complete what they started?
Community Do contributions improve access to the relevant information and finding solutions?
Partners Does the access provided turn into successful and sustained use of the service?
Operations Can growing usage be met with support and service quality?
Economy Does the value created support the costs and the continuity of the service?

These measurements are assessed in contexts such as country, user group, service type and participation period. The behavior over time of users who joined in the same period helps separate initial interest from lasting benefit.

The effect of product changes is also examined with the usage context in mind. A seasonal increase in journeys or a new operator integration can influence behavior. For this reason, not every increase is attributed directly to the same product decision.

This approach ties eBattery's growth to measurable user benefit and sustainable service capacity.

3.4 Why Now?

3.4.1 The Expanding User Base Growing the Need for Services

The scale that electric mobility has reached makes it important to design vehicle ownership services for broader groups of users. IEA’s Global EV Outlook 2026 report, global electric car sales exceeded 20 million units in 2025 and made up roughly a quarter of new car sales. This scope includes fully electric cars and plug-in hybrids together. IEA

The strategic conclusion eBattery draws from this data is that user needs are diversifying. The person the platform serves may be an experienced driver closely interested in technical details, someone driving their first electric vehicle, or a user who wants to manage daily transport easily.

This diversity increases the importance of explanatory design and personalization. The same product must be able to meet the needs of users with different levels of knowledge.

The existing vehicle fleet also creates a continuous need for services. Vehicles that remain in use continue to need charging, travel, equipment, community and support services at different frequencies.

eBattery’s timing approach is built on creating a relationship that provides daily benefit to this usage base.

3.4.2 Growing Infrastructure Increases Coordination Value

As charging infrastructure expands, the number of options a user can compare also grows. Choosing between stations by location, power, price and access conditions calls for a richer assessment of information.

At this stage, the value of digital coordination becomes clear. When users understand which option suits their situation, it becomes easier for them to make use of the physical infrastructure.

The development of infrastructure also allows service quality to be measured in more detail. The assessment that starts with a station being found on the map extends to outcomes such as availability, transaction success, waiting and user satisfaction.

eBattery treats this development as an opportunity in terms of the map, planning and user experience. The platform's aim is to connect existing options with the user's needs and to expand the accessible service coverage.

The same information discipline can also contribute to the review of future station projects. Understanding which need the existing infrastructure meets, and how, is one of the basic inputs for new capacity decisions.

3.4.3 Interoperability as the Technical Foundation for Integrated Services

For different organizations to contribute to the same user experience, data and transaction systems must be able to communicate with each other.

Open protocols such as OCPI support communication between charge point operators and e-mobility service providers on functions such as tariffs, locations, real-time status, sessions, and remote start or stop. EVRoaming Foundation

This technical foundation supports the development of shared app experiences. The actual scope of service is shaped by the functions implemented, the quality of integration and the agreements between the parties.

eBattery's architectural approach is based on keeping connections with different service providers manageable. Being able to carry the experience gained in one integration over to other connections is important for the product's capacity to expand.

Under these conditions, the platform’s competitive value comes from developing the user interface, data quality, transaction continuity and partnership structure together.

3.4.4 Expressing Complex Needs More Clearly with AI

Electric vehicle planning requires evaluating a user’s different preferences together. Entering all of these preferences through many filters and settings can be demanding for some users.

Conversation-based interaction allows users to express their needs in their own language. For eBattery, its value is that the stated intent can be connected to the relevant tools and calculation processes.

For example, a request to arrive at a certain time, a break preference and the current battery level can be handled in the same conversation. While the app passes this information into the planning process, the user can review the result through clear cards and options.

This approach increases the importance of the technical infrastructure. The quality of language interaction gains meaning together with the accuracy of station data, the vehicle profile and calculation methods.

eBattery’s timing thesis is to place artificial intelligence within this service ecosystem. AI is designed as a component that makes it easier to access existing product functions and improves the understandability of decisions.

3.4.5 Designing Physical Infrastructure and Digital Accountability Together

Developing charging infrastructure covers site selection, investment, installation, operation and renewal processes. For these processes to be economically understandable, the relationship between the capital used and the service provided must be traceable.

eBattery's RWA approach is based on representing station projects within this wholeness. The digital identity, technical specifications, project rights and operating records are tied to the economic structure of the physical asset.

IoT and oracle systems support transferring appropriate operating data to digital record processes. Financial transparency, in turn, covers the ability to evaluate items such as energy, maintenance, space use, taxes, operating services and reserves, alongside revenues, together with their relevant periods.

In this approach, the information presented to the investor serves to explain how the project is operated and how the distributable result arises. Designing technology, operations and the record-keeping arrangement together forms the foundation of the model.

eBattery’s licensed operations and Web3 development within its 2027 target are therefore addressed together with physical service responsibility.

3.4.6 Phased Implementation and Cumulative Capability

eBattery's timing approach is based on adding new services on top of existing product capabilities.

The map, AI, route and trip planning, community and Game Zone form the core that meets user needs and starts product learning. After launch, payment, EV Market, insurance, mobile charging support and home charging areas are expanded together with the relevant operations and integrations.

This progression means each stage gives the next one information and capability. The map experience contributes to managing data quality, route use to understanding trip needs, and the community to making user questions and experiences visible.

The Web3 and physical station development side progresses in connection with this accumulation. Assessing demand, site feasibility and operating capacity are addressed together.

eBattery’s answer to the question “why now?” is to bring growing electric vehicle use, maturing service infrastructure and digital coordination capabilities together in the same product approach. Implementing this approach depends on developing, at every stage, the benefit offered to the user and the real-world counterpart of the service.

Search eBattery

Search for a feature, guide or topic.

Starting pointsFinding a charging station →Sample RWA project →Guides and news →