What is the value of a single auto dealer software integration?
The answer to this questions is complex. It is also crucial to understand due to the fact that the answer feeds return on investment discussions. Integrations that are one sided in value for the auto manufacturer or auto dealer tend to struggle and/or fail. Due to the complexity of the topic, I'll focus on a small piece of it; creating a business case based on actual vs perceived value. Data sharing between auto manufacturers and auto dealerships has become essential in the retail automotive industry. Successful integrated solutions have lead to more efficient business processes, improved customer satisfaction, increased revenue and more. To be successful, the integration must offer actual, as opposed to perceived, value to all companies involved. I will use a common integration scenario to in an attempt to explain what I mean by creating a business case from actual vs. perceived value. Integration Scenario: An auto manufacturer develops an integration that will eliminate a manual processes by receiving data electronically from a dealership directly to their back-end systems. The integration project will require auto software providers to add new screens to current application and the ability to automatically send the data. The new screens will eliminate the need for the dealer to rekey data into an auto manufacturer web site. Value to the auto manufacturer: I think the value for the auto manufacturer is pretty clear. Value to the dealer: The opportunity to automate a manual process. The value will depend on a cost analysis of the two processes, but has the potential to have a high value. Value to the auto software provider: The ability to earn revenue. How/what revenue can be earned is determines by considering actual vs. perceived value. The following are just a couple examples of actual vs. perceived values:
Join The Blog! Subscribe & Comment and Contribute! (use the subscribe form on this page) |
|