At Edmunds, we aspire to fully empower the automotive consumer. We've done a good job so far in achieving that, but I think more could be done. Here are my thoughts on how we can do that. I'd love to hear what you think about it (whether you think it's nuts or actually achievable.) Thank you in advance :-)
Here is the automotive experience life cycle as I see it:
- Research: the consumer is looking around for his/her next vehicle
- Negotiations: the consumer is negotiating (or not) pricing/features with dealer or private seller
- Acquisition: the consumer buys or leases or rents the vehicle
- Operation: the consumer owns the vehicle
- Maintenance: everything the vehicle experiences while owned by the consumer (i.e. accidents, service, ...etc)
- Sale: the consumer wants to sell the vehicle
I believe we have done well in some stages (1, 2 and 6) and hardly scratched the surface in the rest. There is tremendous opportunities here to give the automotive consumer support and information in every single stage of that life cycle.
But we cannot do it alone.
In order to truly empower the consumer in every step of the automotive experience, I feel that we need to allow the community at large to use our data and systems to create value for our consumers through applications--both mobile and wired--and services. The way to do that is to build an open platform.
What is a "Platform"?
At a high level, a platform is an ecosystem that provides the following:
- Data Accessibility: providing our data in an easy and standard format ready for consumption by the larger community.
- Code Extensibility: Our software should be open and extensible. The community can contribute and build upon our readily available codebase.
- Service Oriented Approach: Be visible throughout the life cycle.
Goals
My goal is to ultimately reach æ¶
æ§, or Nirvana, in automotive consumer empowerment. But in order to do so, we need to lay down a solid foundation that will help us get there. That foundation is illustrated in the Edmunds Platform Pyramid below (Figure 1.0)

Near Future Milestones
In the near future, the goals are:
- Technical Brand and Community Presence: The very first step is to get out there and create our technical brand through frequent technical blogs posts, technical speaking engagements, community gatherings, hosting tech mini conferences, be active on Twitter as an "Edmunds" network of techies. This blog is a manifestation of this goal :-)
- Complete Documentation: This is the linchpin of all our efforts. In the end, the developer is our consumer and if the developer doesn't know how to use or find our platform, then we've failed.
- Internal Open APIs: Getting our developers to use our APIs as if they were 3rd party APIs.
- Public Open APIs: Building on the success of the Internal Open APIs, we open it to the public.
Far Future Milestones
Our future accomplishments should build on the ones mentioned above.
- API Virtualization: Without changing our underlying API layer, we'll add a layer to customize the APIs for the devices and partnerships they're serving.
- Edmunds Labs: A dedicated team of code and product evangelists and enthusiasts that works on bringing Edmunds and the technical community closer together through mutual collaboration.
- Open Sourcing: Taking our tried and tested products and open sourcing them through Edmunds Labs
- Tech Partnerships: Through Edmunds Labs, foster relationships with software and hardware technical partners that will help us expand our business and product scope.
- Edmunds OS: Build on top of an open source mobile platform (Android?) to deliver web-based operating system for cars--the ultimate mobile devices.
What do you think? Is there value in such approach? You can comment below or tweet your thoughts with #edmundsapi . Looking forward to hearing from you.