01
The support horizon is a decade
Vehicles outlive frameworks. Versioning and backwards compatibility are architectural decisions, not release-time ones.
ThinkDebug
Practical deep dives on software architecture, AI systems, and scaling digital products - drawn from the work we ship.
Dealer platforms, connected-vehicle services and aftermarket commerce.
We build automotive software above the vehicle: dealer and retail platforms, connected-vehicle services and companion apps, aftersales and service booking, and the data platforms that make telematics useful to the business.
Automotive has a longer memory than most sectors. A vehicle sold today will be receiving software and data services for a decade or more, across owners, markets and regulatory changes. That makes versioning, backwards compatibility and update strategy architectural concerns from the first sprint.
It is also a distributed retail business. Manufacturer, importer, dealer group and individual dealership each hold part of the customer relationship and part of the data, and the software usually has to serve all of them without pretending they are one organisation.
The constraints that shape every build in this sector, and the ones teams usually meet too late.
Vehicles outlive frameworks. Versioning and backwards compatibility are architectural decisions, not release-time ones.
Manufacturer, importer, dealer group and dealership each hold part of the relationship and part of the data.
Dealer management systems are often proprietary, batch-oriented and slow to change, yet they hold the operational truth.
Continuous vehicle data is expensive to store and mostly uninteresting until something specific is being investigated.
Location and driving behaviour are regulated, and consent has to survive a change of owner.
Connectivity varies, and an over-the-air update that half-applies is worse than one that never started.
Swipe to read all 6
Each one is a system we have built before, not a capability we are willing to try.
Configurators, stock, finance quotes and lead handling across a dealer network.
Owner apps for status, remote functions and service history that work across model years.
Service booking, parts and workshop scheduling wired to the systems dealers run.
Ingestion, aggregation and retention that keeps vehicle data affordable and useful.
Consent, entitlement and data handling that survive a vehicle changing hands.
Fault and usage data turned into service actions rather than dashboards.
Engagements across sectors - the same team, the same standards.
Partnering with Thinkdebug to develop the Forever 52 mobile app has been a game-changer for us. They were always open to feedback, and it was clear they were as invested in our success as we were. What really sets them apart, though, is the amazing support we've received since the app launched. They’ve made sure the app continues to run smoothly and are always ready to fix any issues that come up.DMDhruv MehtaBusiness Head, Forever 52
Chosen for fit and long-term maintainability, never for novelty.
Send us the scope and we come back with an itemised estimate - no discovery fee, no obligation.
What we design and document against, from the first commit rather than the week before an audit.
Certification itself belongs to your entity and its assessor. What we provide is software built and documented so the assessment is about evidence rather than remediation.
Most of our work comes from clients we already shipped for. These are the reasons they give.
APIs are versioned and deprecation is planned, because a car sold today will still be calling these services long after the current framework is unfashionable.
Over-the-air delivery is designed to resume, roll back and never half-apply, since a partial update is worse than none.
Dealer systems are proprietary and slow to change. We build around their batch interfaces rather than assuming they will modernise.
Sampling, aggregation and retention are decided at design time, because raw vehicle data becomes the dominant cost quickly.
Entitlement and consent are tied to the vehicle and the current owner, so a change of hands does not leak the previous owner's history.
Manufacturer, importer and dealer each get the access their role needs without one system pretending they are the same organisation.
Let's start with you.
Your information stays private. We reply within 24 hours.
Still have a question we have not answered?
Ask an engineerWhat we build for automotive, the work we have shipped, and what we have written about it.
