MotorAdvisor — the question becomes a repair order.

A service writer standing at a counter has one question — what’s wrong with this car, what will it cost, and should we even do the work? — and answering it today means crossing four systems and a phone call. MotorAdvisor turns that question into a priced, bookable, payable repair order, in the conversation where it was asked.

The bet isn’t that shops want another database. It’s that the repair decision is a single continuous act— diagnose, price, decide, approve, pay — and that every product in this market breaks it into pieces and hands the seams to the shop.

The part nobody does: it gates the repair against the car. A vehicle valuation sits alongside the estimate, so a $3,400 repair on a car worth $2,900is a conversation the system starts rather than one the writer has to remember to have. That verdict is advisor-facing by default — telling a customer their car isn’t worth fixing is the shop’s call to make, in the shop’s voice.

Same operating model as TopHand, at a different scale: specs first, epics and stories, one story per pull request, every merge reviewed. Where it differs is the shape of the risk — two licensed upstream data providers that must stay strictly separate in the code, enforced as build rules with negative controls rather than as conventions anyone has to remember.