BYD Owner Services

Update time: May 26, 2026 14:29 (Beijing time)

Project status card

Field	Content
Current stage	Pending project confirmation / preliminary research
Topic initiator	TranFu Team
Current owner	TranFu Team
Last updated	2026-06-01
Current assessment	The BYD ecosystem opportunity has a complete research report and a clear hypothesis, but it is still only a candidate for conversion from research into an active project. Before adding it to the long-term project archive, the team must confirm that it intends to keep pursuing charging, trip planning, and energy services for BYD owners.
Next step	Assess project readiness first: confirm the target users, real pain points, feasibility of ecosystem access, existing alternatives, and available validation samples. Only then should it move into formal assessment and ongoing maintenance.

Latest developments

• 2026-06-01: Completed the project-record maintenance structure while retaining the manual-update policy. The project remains marked "Pending project confirmation / preliminary research"; its priority will not be raised automatically, nor will it be added to daily project maintenance automatically.

• 2026-05-22: The topic was created with a BYD ecosystem business opportunity research report. Its core hypothesis is to use charging-station discovery and trip planning as a frequent-use entry point, intelligent charging coordination as a data flywheel, and V2V, V2G, and emergency energy services as potential extensions.

Executive Summary

This project draws on discussions and attachments collected in a Lark topic to explore opportunities around the BYD open platform and its D++/DiLink ecosystem. The goal is not to pursue generic “automotive AI,” but to find a commercially viable, testable, and extensible entry point in the frequent travel and charging scenarios faced by BYD owners.

The clearest one-sentence definition currently is:

Use charging-station discovery and trip planning as the frequent entry point, intelligent charging coordination as the data flywheel, and then evaluate commercial extensions such as V2V, V2G, and emergency energy dispatch.

This positions the project as a vehicle-owner service and new-energy ecosystem opportunity, not merely a standalone software feature.

2. Internal Evidence from the Lark Topic

1. Topic Identification

• Topic title: BYD Ecosystem Business Opportunity Research Report

2. Evidence Captured in the Topic

The local Lark topic snapshot currently shows:

• Total messages: 4

• Human messages: 3

• AI/App messages: 1

• Current status: discussing

• Status recommendation: Proceed with preliminary research

3. Key discussion points extracted

The topic currently contains the following useful evidence:

• The user clearly requested: "Do some market research on this basis"

• The topic includes an attachment: BYD Ecosystem Business Opportunity Research Report.docx

• Preliminary directions have been described:

• Find charging stations + trip planning

• Intelligent charging scheduling

• High-ARPU extensions such as V2V, V2G, and emergency energy services

4. Current internal consensus

The discussion establishes at least three points:

1. The team is not pursuing an abstract "BYD-related project"; it is looking for an entry point into a frequent-use owner scenario.

2. The idea is no longer just a working title; it already has the outline of a layered product.

3. The most important business-validation evidence is still missing:

• Who is the specific user?

• Are high-frequency pain points strong enough?

• What are the existing alternatives?

• Are users willing to pay?

The conclusion therefore should not be "start the project," but rather:

The direction merits further research, but it must first be reframed around specific users, scenarios, and a concrete validation plan.

3. Opportunity Definition: What Are We Evaluating?

The opportunity can currently be defined as follows:

Core Opportunity Hypothesis

Build a product path around key moments in BYD owners' new-energy journeys: information entry point → decision support → coordination capabilities → high-value extension services.

Three-Tier Opportunity Structure

Layer One: Frequent-Use Entry Point

• Charging-station discovery

• Route planning

• Charging decisions

• Support for range anxiety

These needs occur most often in daily use and offer the most accessible entry point.

Layer Two: Intelligent Coordination

• Make charging recommendations based on route, time, battery, destination, and queue status

• Recommend a better charging plan

• Help users reduce waiting, detours, and decision-making costs

If this layer works, it can demonstrate genuine AI value rather than simply aggregating information.

Layer Three: High-ARPU Extensions

• V2V (emergency energy supply between vehicles)

• V2G (vehicle-to-grid interaction)

• Emergency energy dispatch

• Extended energy services for vehicle owners

This layer has the greatest long-term potential, but it is also the furthest from validation. It should remain a future extension rather than part of the initial product.

4. Market Assessment

1. Why is this direction attractive?

(1) BYD Has a Large Owner Base

BYD has one of China’s largest new-energy vehicle owner bases. If the team finds the right entry point, the addressable market could be substantial.

(2) Charging and Trip Planning Address Real Needs

For new-energy vehicle owners:

• Find the right charging station

• Decide when to charge

• Plan long-distance routes

• Reduce queuing and time loss

These are genuine user problems, not manufactured demand.

(3) AI Can Power the Decision Layer, Not Just the Information Layer

Conventional apps can display maps and charging stations. AI could go further by:

• Making recommendations based on vehicle conditions, routes, time, and preferences

• Dynamically recalculating charging plans

• Providing decision support that users can trust

That offers more room for differentiation than a simple charging-station directory.

2. Why This Opportunity Does Not Yet Justify Optimism

(1) The current scope is still too broad

The label "BYD Ecosystem Business Opportunity" is too broad and could encompass:

• Vehicle-owner services

• Automotive aftermarket services

• Owner communities

• Local services

• Charging services

• In-vehicle systems and applications

• Energy services

If it is not narrowed down, the project will remain in the research stage.

(2) There are many existing alternatives

Even without considering AI, there are already:

• Map services

• Charging-station platforms

• Information shared in owner communities

• Automakers' official services

• General-purpose navigation tools

So we must answer:

Why would users adopt a new product instead of continuing to combine existing tools?

(3) The necessity of AI has not yet been proven

It is clear so far that AI might be useful, but the team has not shown that AI delivers core value rather than merely adding a nice-to-have feature.

(4) Ecosystem access has practical barriers

Delivering a sufficiently capable product would likely require:

• Access to in-vehicle systems or open-platform capabilities

• Charging-data APIs

• Maps and navigation data

• A path to ecosystem partnerships

This means:

• A front-end application alone will not solve the problem.

• Validation must address the practical question of whether the required platform and data access are actually available.

Based on the existing Opportunity Radar assessment, the project's current baseline should be:

• Internal assessment: 80

• Formal conclusion: Narrow and reframe the direction

• Project stage: pending preliminary research

• Priority: Internal ranking

• Base score: 65

• Evidence factor / completeness: 0.9

• Final score: 59

• Key dimensions:

• Demand validity: 72

• AI fit: 62

• Validation feasibility: 70

• Commercial value: 68

Why not a higher score?

Because what is lacking right now is not imagination, but:

• Specific user profile

• Validation of the frequent-use entry point

• Gaps in existing alternatives

• A credible payment scenario

• Distribution/ecosystem access path

A more reasonable conclusion is not "greenlight the project," but rather:

First narrow the project definition, then validate whether it deserves to become a formal product direction.

6. The Most Valuable Part of the Opportunity

If this direction is retained, the most valuable part is not the broad ecosystem narrative but this specific proposition:

Intelligent charging and trip-planning support for new-energy vehicle owners.

Reasons:

1. It is more specific than the broad "BYD ecosystem";

2. It is easier to validate than generic vehicle-owner services;

3. It can deliver measurable value:

• Save time

• Reduce detours

• Improve charging efficiency

• Reduce decision-making costs

1. It has a better chance of proving that AI is not a gimmick but a core layer of the product.

7. The Most Critical Questions

1. Who is the first user?

The team must determine whether the first users are:

• Daily commuters?

• Long-distance travelers?

• Ride-hailing drivers or other commercial operators?

• Charging-service operators?

The pain points of these types of users are very different.

2. What Is the True Frequent-Use Entry Point?

Are charging-station discovery and trip planning really the most frequent entry point, or would the following be more valuable?

• Determining the timing of charging

• Route replanning

• Emergency energy dispatch

Which of these would offer more value?

3. Where Do Current Alternatives Fall Short?

If existing maps, charging apps, and official in-vehicle systems already work well enough, a new product will struggle to gain traction.

4. Can AI be better than a rule-based system?

For static recommendations, AI may offer no advantage over a rules-based system. The team must identify the situations in which AI can materially improve the experience and decision quality.

8. Recommended Reframing

Rather than developing a product under the broad heading "BYD Ecosystem Business Opportunity Research Report," narrow the concept to:

Recommended Concept

BYD Charging and Trip-Planning Assistant

Clearer Definition

Help new-energy vehicle owners make the following decisions more efficiently while traveling:

• Driving-range estimation

• Charging-stop selection

• Route and time decisions

• Alternative charging plans when disruptions occur

This reframes the opportunity from an industry report into a concrete user problem, making it more suitable for further evaluation in Opportunity Radar.

9. Recommended Next Research Plan

Step 1: Define Users and Scenarios

Prioritize interviews with 3-5 target users, covering at least:

• Daily commuter new-energy vehicle owners

• Medium- and long-distance travelers

• Users who are sensitive to charging experience

Interview topics:

• What charging decisions do they struggle with most often?

• How do they solve those problems today?

• Which situations cause the most frustration?

• Would they pay for a solution that saves time or gives them greater confidence?

Step 2: Map the Alternatives

Document the current mix of alternatives:

• Map and navigation apps

• Charging-station platforms

• Official in-vehicle systems and apps

• Advice from owner communities

• Manual planning

Then identify where meaningful gaps remain.

Step 3: Validate AI's Role

Answer these questions as quickly as possible:

• Should AI explain recommendations?

• Should it recommend charging decisions?

• Should it coordinate charging dynamically?

• Should it personalize recommendations?

Avoid the vague claim that the product is simply "AI-powered."

Step 4: Assess Ecosystem Access

Even if the first version avoids deep integration, assess early:

• Open-platform capabilities that will be needed later

• Availability of the required data

• Risk of overdependence on a single platform

10. Current Conclusion and Recommendations

Current Conclusion

The direction is not ready for an immediate project launch, but it is worth retaining for preliminary research.

Reasons

• It addresses real user scenarios

• It has commercial potential

• AI may add meaningful value

• The current definition, however, is too broad and lacks critical validation evidence

Best Next Step

Rather than expanding the broad ecosystem story, the team should:

Reframe the project as a BYD Charging and Trip-Planning Assistant, then fill the four critical evidence gaps: users, scenarios, alternatives, and ecosystem access.

Recommended Actions

• Identify the most frequent owner use case;

• Research BYD's open-platform capabilities, competitors, and potential partnership and distribution paths;

• Re-evaluate after completing a round of preliminary research.

11. Recommended Fields to Sync to Lark

Project Record

• Formal assessment: 59

• Formal conclusion: Narrow and reframe the direction

• Current stage: Pending preliminary research

• Next step: identify the most frequent owner use case; research BYD's open-platform capabilities, competitors, and potential partnership and distribution paths

Score History

• Retain the medium-confidence note

• Note the need for user interviews and research into alternatives

Opportunities

• Retain the internal assessment: 80

• Sync the current formal conclusion as "Narrow and reframe the direction"

• Clarify the core focus as "vehicle-owner services / new-energy ecosystem"

Daily Briefs / Daily Updates

• Only record which part of the research was completed today

• Do not duplicate the role of the long-term source of truth

Data Links

Field	Content
Current dataset	4 messages / 3 human messages / 1 AI/App message / 16 resources; one AI reply appears to belong to another topic and must not be used as evidence for the BYD opportunity.

Expanded Project Analysis (2026-06-02)

Methodology note: This analysis uses the latest maintenance report, the actual Lark topic data, and reviewable public information. Because web_search was unavailable, market claims without secondary verification are treated conservatively as trends or assumptions.

Opportunity in One Sentence

Explore focused business opportunities in charging, travel, owner services, smart-cockpit content, and developer tools around BYD's large owner base and new-energy mobility ecosystem. First confirm whether this research should become an active project so that a one-off study is not mistaken for a long-term initiative.

Target Users

• BYD new-energy vehicle owners, especially frequent commuters, long-distance drivers, and families traveling by car.

• Service providers around the BYD ecosystem, including charging, repair and maintenance, customization, insurance, used vehicles, automotive accessories, content, and navigation.

• Developers or local service providers seeking access to in-vehicle systems, smart cockpits, or owner communities.

Core pain points

• New-energy vehicle owners still face charging anxiety around station availability, queues, pricing, route planning, and the reliability of cross-city travel.

• Owner services are fragmented across in-vehicle systems, apps, maps, charging platforms, communities, and local businesses.

• BYD has a large owner base, but third parties need a clear distribution channel, appropriate data access, and a viable partnership model to participate in the ecosystem.

• Smart-cockpit applications may appear to have a clear distribution channel, but actual usage frequency and commercial conversion remain uncertain.

Current Evidence

Internal topic data

• Topic owner: Internal member.

• Messages/resources: 4/16.

• A recent internal summary includes BYD Ecosystem Business Opportunity Research Report.docx, followed by a request to "do some more market research on this basis." The maintenance report also contains an output summary from the "Team API Key Management" project, indicating possible cross-project contamination or a write-path mismatch in the archive.

• The maintenance report explicitly specifies a manual update policy: do not write updates automatically without human approval.

External data and trends

• BYD continues to expand in new-energy vehicle sales, vertical integration, batteries, and vehicle intelligence, creating a large owner ecosystem and substantial aftermarket-service potential.

• Automakers' software strategies focus on smart cockpits, driver assistance, in-vehicle applications, charging networks, and OTA services.

• Chinese new-energy vehicle owners' frequent needs are generally not for "generic in-vehicle apps," but for charging, ownership costs, routing, maintenance, insurance, resale value, and community services.

Competitors/Alternatives

• Official ecosystem: BYD App, DiLink and the smart cockpit, official services, the official store, and OTA capabilities.

• Maps and charging: Amap, Baidu Maps, Tencent Maps, TELD, Star Charge, YKC, and State Grid e-Charging.

• Owner services: Tuhu, JD Auto, insurance platforms, used-car platforms, and owner communities/KOCs.

• Smart-cockpit content: in-vehicle app stores, audio, video, games, navigation, and local services.

MVP Entry Point

Start with use cases that require little privileged access, address strong needs, and can be validated independently:

1. Long-Distance Charging Planner for BYD Owners: Enter the vehicle model, origin, destination, and departure time; receive a route, charging stops, backup plans, pricing, and queue-risk estimates.

2. Savings Assistant for BYD Owners: Combine charging prices, maintenance, insurance, tires, automotive-accessory discounts, and recurring-service reminders.

3. Owner Community Service Radar: Help local owner groups discover events, service providers, group-buying offers, and reputation rankings.

Recommended MVP: the long-distance charging planner. It avoids the need for deep access to official systems, addresses a clear pain point, and can be validated early with public map and charging-station information plus owner feedback.

Validation Approach

• Interview 20 BYD owners across commuter, ride-hailing, families taking long trips, and road-trip segments.

• Collect 10 real long-distance routes, manually prepare charging plans, and compare them with Amap, Baidu Maps, and BYD’s official recommendations.

• Test whether owner groups save or share plans that include a route, backup charging stations, and risk alerts.

• Metrics: plan adoption rate, willingness to consult the service a day before travel, and willingness to pay for advanced planning or membership-based savings.

Risks and counter-evidence

• Official apps and map platforms may quickly cover charging planning, leaving third parties without a data advantage.

• Real-time station availability, queue, and fault data can be difficult to obtain; inaccurate data would directly undermine trust.

• Opportunities for smart-cockpit developers depend on official platform policies and are therefore highly uncertain.

• The internal record shows signs of cross-project contamination. If the original BYD report cannot be verified, postpone formal assessment.

Next step

• Clean the record first: verify BYD Ecosystem Business Opportunity Research Report.docx and remove the suspected "Team API Key Management" cross-project summary from the maintenance report.

• Keep the status as "Pending project confirmation / manual" and do not write to the Wiki automatically.

• Interview 20 owners to prioritize among charging planning, owner savings, smart-cockpit applications, and owner community services.

Reference Links

• BYD global website: https://www.bydglobal.com/

• BYD China website: https://www.byd.com/cn

• Amap new-energy charging service: https://ditu.amap.com/

• TELD: https://www.teld.cn/

• Star Charge: https://www.starcharge.com/

---

Maintenance boundary: This section is the controlled expanded-analysis block dated 2026-06-02. It may be replaced when new customer validation, competitor changes, or Lark topic updates emerge, without overwriting the original record.

Project Quality Upgrade (2026-06-03)

Methodology note: This section replaces the previous template-driven analysis. It uses the actual Lark discussion, project mapping, existing maintenance reports, and the public competitive landscape to focus on the assessment, scope, validation plan, and counterevidence. It does not overwrite the other sections.

Current Assessment

This opportunity may be promising, but the record itself must be repaired first. Internal evidence does include a BYD research document and a request to conduct further market research. However, the latest maintenance summary also contains market-research content from the "Team API Key Management" project, indicating possible cross-project contamination or a broken archival write path.

It should not receive a high priority yet or be written automatically into the Wiki. The safest assessment is: keep the project pending confirmation with manual updates, clean the archive first, and then decide whether to validate charging, owner services, or smart-cockpit opportunities.

If the original BYD report is valid, the first concept to test should not be a generic “BYD ecosystem” product but a long-distance charging planner for BYD owners. It requires little privileged access, addresses a concrete pain point, and can be validated through owner interviews and public information.

Real Internal Data

• Title: BYD Ecosystem Business Opportunity

• Lark thread: [redacted]

• Update strategy: manual

• Owner: internal member

• Data source: snapshot

• Messages/resources: 4 messages / 16 resources

• Key internal evidence: The record includes BYD Ecosystem Business Opportunity Research Report.docx, followed by a request to "do some more market research on this basis."

• Important anomaly: The latest maintenance summary includes content about "Team API Key Management and LLM Subscription Access Distribution," which appears to be cross-project contamination.

• Evidence level: L2- (documents and resources exist, but the original report has not been reviewed and the record is contaminated)

Competitors and Alternatives

• Official ecosystem: BYD App, DiLink, official store, service locations, OTA services, and owner community.

• Maps and charging platforms: Amap, Baidu Maps, Tencent Maps, TELD, Star Charge, YKC, and State Grid e-Charging.

• Owner-service platforms: Tuhu, JD Auto, insurance platforms, used-car platforms, and local repair and maintenance providers.

• Owner communities/KOCs: WeChat groups, owner content on Douyin and Xiaohongshu, local clubs, and communities focused on modifications and ownership experience.

• Smart-cockpit content alternatives: In-vehicle app stores, audio and video apps, navigation, and local services.

MVP Scope

Recommended MVP: Long-Distance Charging Planner for BYD Owners.

In scope:

1. Collect the vehicle model, origin, destination, departure time, whether older adults or children are traveling, and the acceptable detour range.

2. Provide one primary route and two backup charging plans.

3. Show charging-stop locations, estimated state of charge on arrival, nearby rest and dining options, queue risk, and fallback stations.

4. Accept user feedback on charger availability, queues, pricing, and the overall experience.

Explicitly out of scope:

• Do not build an in-vehicle application or rely on privileged DiLink access.

• Do not promise perfectly accurate real-time charging-station status; clearly label data sources and uncertainty in the early stages.

• Do not build a multi-brand new-energy owner platform; validate with BYD models only.

• Do not assume an official ecosystem partnership unless a concrete channel exists.

• Do not build a general owner marketplace or automotive-accessory shopping guide; keep the scope focused.

Validation plan

Step One: Record Cleanup (Must Come First)

• Find and read BYD Ecosystem Business Opportunity Research Report.docx.

• Label which content comes from the original BYD research, which was generated later by AI, and which appears to have been imported from the API Key project.

• After cleanup, decide whether to update the controlled enhancement block.

Step Two: Interview 20 Vehicle Owners

• Segments: commuters, families taking long trips, road-trip users, ride-hailing or other high-mileage drivers, and first-time new-energy vehicle owners.

• Key questions: What went wrong during their most recent charging experience? Which app did they use? Did they plan ahead? Would they consider a third-party plan?

Step Three: Manually Plan 10 Routes

• Collect real routes and use Amap/Baidu/charging platform information to manually generate plans.

• Compare the results with users' current approaches: Are they more reassuring, less expensive, or less circuitous?

Success threshold: At least 8 of 20 owners report a recent charging concern or failure; at least 5 of 10 routes produce backup plans that are more useful than existing tools; and at least 3 owners say they would proactively consult the service before their next trip.

Counterevidence and Kill Criteria

• If the original BYD research report cannot be reviewed, the project should remain manual without evaluation.

• If Amap, Baidu Maps, or BYD's official app already meets 80% of the need, third-party planning does not add enough value.

• If trustworthy real-time charging-station data is unavailable, users will treat the product only as a reference guide, not a decision tool.

• If owners care more about maintenance, insurance, or resale value than charging, the project should pivot accordingly.

• If the opportunity depends on official BYD APIs or smart-cockpit distribution, postpone it unless a partnership channel is available.

Next step

1. Clean the record first and remove the API Key cross-project contamination.

2. Keep the status "Pending project confirmation / manual" and do not publish updates automatically.

3. If the BYD report is valid, interview 20 owners and prioritize validation of the long-distance charging use case.

4. If the charging use case fails validation, compare the Owner Savings Assistant with the Local Owner Community Service Radar.

---

Maintenance boundary: This section is the controlled quality-upgrade block dated 2026-06-03. It may be replaced in full when new evidence emerges.

Maintenance Notes

• This record is currently treated as a candidate for conversion from research into an active project and is excluded from automatic daily maintenance by default.

• The owner defaults to the sender of the Lark topic's root message; this project's topic initiator is listed as an "internal member."

• One AI/App message appears to contain content from the “Team API Key Management” project and must not be used as evidence for the BYD assessment.

• Automatic maintenance may update only the project status card, latest developments, data links, and maintenance notes; it must not overwrite the original research by default.