Solutions
For multi-shop operators
The MSO question is not whether the estimate is good. It is whether it is the same estimate in every building.
What holds up across locations
The estimating logic, the comp grounding and the rate profiles are identical wherever they run, so the same damage on the same vehicle produces the same first write in every location. That is the part of consistency software can actually deliver.
What is not built yet
Central multi-location administration, cross-location reporting, role hierarchies and consolidated billing do not exist today. Plans are single-seat with paid additional seats. An MSO evaluating this should know that before a demo rather than after.
Volume economics
Published plans top out at 30 estimates a month. A multi-location operator will exceed that. Volume beyond the published tiers is a direct conversation rather than a hidden page, and the pricing is not quietly different for people who ask.
Before you ask
Can we roll this out to ten locations?
Not as a self-service product today. The estimating is ready; the multi-location management layer is not, and pretending otherwise would waste your time.
Do you have an API?
There is an internal API the applications use. It is not published or supported as a customer integration surface yet.
What would a pilot look like?
One location, real jobs, compared against estimates that location has already written.
Run it on damage you have already written
Accounts are created by hand, usually within a business day. Bring your own photographs and a repair order you have already closed, so you can see how close it lands before you decide. No card, no trial timer.