What customers want to see in a repair estimate

The estimate is where the customer decides. Most are written as a record of what the tech found, which is a different document entirely.

An estimate is a decision document

Internally, the estimate is a record: what was inspected, what was found, what it takes to fix. That version is necessary and it's the one most systems produce by default.

The customer is doing something else with it. They're deciding how to spend money they probably hadn't planned to spend, on a machine they depend on, using information they can't verify. A document that's organized around what the tech found doesn't help much with that.

The fix isn't more detail. It's usually less detail, better sorted.

Plain language, not part numbers

"Replace front pads and rotors" is fine. A part number and a labor op code is not. It reads as deliberately opaque even when it's just how the system prints.

The test is simple: could the customer repeat this to somebody else and have it make sense? They often need to. The person who dropped the car off is regularly not the person who decides, and whatever you wrote has to survive being relayed over the phone by someone who doesn't know cars.

Sort it into three buckets

This is the single highest-value change to how most estimates are presented. A flat list of five items with five prices asks the customer to do the prioritizing, and they have no basis for it. So they either approve everything, which is rare, or they freeze and approve nothing, which is common.

Sort it for them.

• Safety now. Don't drive it far like this. Say plainly what could happen.
• Needed soon. It's going to fail, it isn't dangerous today, here's roughly the window.
• Keep an eye on it. Noted, measured, not urgent, we'll check it next time.

The third bucket earns more trust than the first two

It's tempting to leave the minor stuff off, or to promote it upward so it sells. Don't.

A customer who sees you write down something and explicitly say it can wait learns something important: that you'll tell them when they don't need to spend. That's the thing that makes them believe the safety-now bucket. If everything you ever write is urgent, then nothing you write is.

It also sets up the next visit honestly. When that item does come due in six months, you've already flagged it once and it doesn't land as a surprise.

Show the evidence

A photo of the actual part on their actual car, with a measurement where one applies, does more work than any amount of description. Worn against new, side by side, is instantly readable by someone who knows nothing about brakes.

Where a photo isn't possible, a number helps: the reading, the spec, and where theirs sits between them. "Measured 3mm, spec is 8mm new, we recommend replacing under 3mm" is a fact a customer can check and reason about. "Brakes worn" is an opinion they have to take on faith.

Price the whole line

Each line should carry its own all-in number. Parts, labor, shop supplies, tax, everything. Not a parts figure the customer has to combine with a labor figure and a percentage they don't understand.

This matters because it's the unit they're deciding on. If they can only see the total at the bottom, the only decision available is all or nothing, and all-or-nothing decisions on unexpected spending default to nothing.

Say what happens if they wait

For every item, one line on the consequence of not doing it. Sometimes it's serious: the pads are down to the backing and the rotors go next, so the bill roughly doubles. Sometimes it's genuinely minor.

Say the minor ones too. It costs you a small amount of revenue now and buys a customer who believes the next thing you tell them.

Make declining easy

This feels backwards and it isn't. A customer who can decline two lines cleanly, without a phone call where they have to justify themselves to a professional, approves the other three and comes back next time.

One who feels cornered approves nothing and takes the car somewhere else, and you never find out why. The decline you make easy is the one that tells you something. The decline you make awkward just leaves.

What good looks like

One page. Three buckets. Plain words. A photo per item where there's something to see. An all-in price on every line, each approvable on its own. One sentence per item on what waiting costs.

Nothing in that list is about the software you use to produce it. It's about what the customer is being asked to decide, and giving them enough to decide it without a phone call.