An auto repair estimator app is a record-keeping app wearing a calculator.
The arithmetic in an auto repair estimator app takes an afternoon: hours, rate, parts, tax. The part that matters takes longer, because an estimate is a statement a customer relies on, and in several places the rules about changing it are written down. Getting the number right is easy. Being able to show what you told the customer, and when they agreed to more, is the actual product.
This page covers what a written estimate has to hold, how approval for additional work should be recorded, where the labour times come from, and why the whole thing has to work standing next to a car rather than at a desk. The wider shop side sits in an auto repair shop app.
See what an estimate has to containThe short version
Write the estimate down, and record every conversation that changed it.
Two things carry an estimator app. A written estimate that separates parts from labour and is given to the customer before work starts, and a log of every authorisation to exceed it, with who said yes, when, and what they were told the extra would cost.
That second record is the one shops lose. It usually happened, over the phone, and nobody wrote it down. An app that makes writing it down faster than not writing it down is worth more than any pricing feature.
What a written estimate has to contain
California is a useful reference point because the rule is explicit and other places converge on the same shape. Under the state's Business and Professions Code, an automotive repair dealer must give the customer a written estimated price for labour and parts necessary for a specific job, and no charge may be made for work done or parts supplied in excess of the estimated price without the customer's consent.
That gives you the minimum fields, and they are worth treating as required rather than optional. The vehicle, the specific job, parts, labour, and a total. An estimate that says only a total is not really an estimate, because the customer cannot tell which half moved when the invoice arrives.
The rule on exceeding it is where the app earns its money. California requires that where a customer authorises additional work orally, the dealer records the date, the time, the name of the person authorising, the telephone number called if any, and a specification of the additional parts and labour with the total additional cost. Read that as a form: five fields, on a phone, thirty seconds, while the conversation is still happening.
California Business and Professions Code section 9884.9
Try it
The number the customer is going to hold you to
An estimate is three inputs and one promise. The promise is the part that has rules attached.
670 estimated
Labour 350 plus parts 320. If the job runs to 737, that overage is not yours to charge without going back to the customer and recording that you did.
Approval, and whether a tap counts
Phone authorisation is the traditional route and it is fragile, because the record is a note somebody meant to make. Sending the revised estimate to the customer's phone and having them approve it is better in every respect: the customer sees the number rather than hearing it, and the record writes itself.
It also holds up. The United States E-SIGN Act provides that a signature, contract or other record relating to a transaction in interstate commerce may not be denied legal effect, validity or enforceability solely because it is in electronic form, and that a contract may not be denied effect solely because an electronic signature or record was used in its formation. A tap that approves an itemised estimate is a real approval.
What matters is what you store around it. The exact version of the estimate they approved, not the current one. Shops that store a link to the live estimate discover the problem the first time there is a dispute, because the document now says something different from what was approved.
15 U.S. Code 7001, general rule of validity for electronic signatures
Where the labour times come from
The hours in an estimate are not invented, they come from a labour time guide: a database of how long a given operation takes on a given vehicle. This is the part of an estimator app people assume they can look up and cannot.
The major labour time guides are commercial products sold under licence rather than open data, and access is priced per shop. We have not verified the terms of any specific provider, so if your plan depends on looking times up inside your own app, confirm licensing and redistribution rights with that provider directly before you build around it. Treat any claim otherwise, including a confident one from an AI, as something to check.
The alternative most independent shops take is simpler and works: your own times. Record what each job actually took, per operation and per vehicle, and after a few months you are quoting from your own history rather than someone's national average. It is more accurate for your shop, it costs nothing, and it is the same idea that makes an estimate app for contractors useful once it has a year of jobs in it.
Written in the bay, not at the desk
An estimate written from memory at the counter is worse than one written at the car, and the gap is where the second phone call comes from. So the app has to be usable while someone is holding a torch, which is a narrower requirement than it sounds.
That means large touch targets, a parts list you can search rather than scroll, photographs attached to a line rather than to the job, and text entry kept to a minimum. It also means the estimate has to survive the workshop having no signal, which many do, especially in a basement or a steel building.
Photographs deserve a mention of their own. An estimate line that says the rear pads are worn is an opinion. The same line with a photograph attached is an explanation, and shops that attach them approve more additional work, because the customer can see the thing they are paying for.
What each way of writing estimates gives you
| Option | Itemised parts and labour | Approval recorded | Photos on the line | Own labour times |
|---|---|---|---|---|
| Handwritten pad | Yes | only the signature at the end | No | in someone's head |
| Spreadsheet template | Yes | No | No | if somebody maintains it |
| Licensed estimating platform | Yes | Yes | Yes | theirs, not yours |
| An estimator app you build | Yes | Yes | Yes | yours, from your own jobs |
Building one around your own shop
Estimating platforms are built around a national labour guide and a workflow that assumes insurance work. Plenty of independent shops do neither. A classic specialist, a mobile mechanic, a fleet workshop billing internally, all end up fighting a product designed for a body shop settling with an insurer.
Newly is an AI app builder. You describe the app you want, including how your estimates are actually approved, and it builds and ships a real mobile app you own. Plans start at $25 a month, there is no free plan, and iOS builds ship through App Store Connect. It does not come with a labour time database and it does not process payments. It is what you use when the platform you tried is shaped around somebody else's business.
Decide the offline behaviour before anything else, because retrofitting it is painful. Estimates get written where the cars are, and a lot of workshops are steel boxes. It is worth reading about writing an estimate in the bay before you design the first screen, along with the wider question of what a car dealership app has to do differently.
Questions people ask about auto repair estimator apps
It is the tool a shop uses to produce a written estimate at the vehicle: the job, the parts, the labour hours and the total, given to the customer before work starts. The more important half is the record it keeps afterwards, including any authorisation to go beyond the estimate and what the customer was told at the time.
Describe how your shop writes an estimate
Write down what goes on the estimate and how a customer approves extra work, including the call you always mean to log, and build the app around that.
Start building