Verbal Estimates vs Written Estimates. What Actually Works for Trades

Why trades use both

Most trades use both verbal and written estimates. Not because it’s a strategy, but because that’s how work actually happens. Sometimes you’re on site and a number gets discussed there and then. Other times you sit down later and send something in writing. Both are normal. Both are useful. The problem isn’t using both. The problem is treating them like they’re the same thing.

When verbal estimates work best

Verbal estimates work best when the job is fairly straightforward and speed matters more than paperwork. You’re already there, the customer wants an idea of cost, and everyone understands it’s a conversation rather than a contract. In those moments, a verbal estimate does exactly what it needs to do. It answers the real question the customer is asking, which is whether the job is roughly in the right range for them.

Where verbal estimates fall down

Where verbal estimates tend to fall down isn’t in the conversation itself, but in what happens afterwards. Once a price has been discussed verbally, there’s nothing written to come back to and no clear record of where things landed. If the customer says they need to think about it, that isn’t silence and it isn’t a rejection. It’s a decision that just hasn’t been made yet. Many systems still treat that as if nothing happened, and that’s where jobs quietly disappear.

When written estimates matter

Written estimates matter in different situations. They’re useful when the job is bigger, when details need to be clear, or when more than one person is involved in the decision. A written estimate gives everyone something concrete to look at. It shows what’s included, what isn’t, and what the price actually covers. Crucially, it also creates a clear point where the customer can accept or decline.

The problem written estimates introduce

Written estimates introduce a different kind of problem, and that problem is silence. An estimate gets sent, it’s opened, and then nothing happens. That silence doesn’t usually mean the customer has decided against the job. More often it means they’re busy, distracted, or planning to come back to it later. This is one of the few situations where follow-up genuinely helps, not as pressure, but as a reminder.

Why most systems get this wrong

Most systems get this wrong by treating verbal and written estimates exactly the same. They use the same stages, the same reminders, and the same follow-ups regardless of how the price was given. In practice, that means verbal estimates get chased when they shouldn’t, and written estimates don’t always get followed up properly. Both feel off to the trade because they don’t reflect what actually happened.

What actually works in practice

What works better is a simpler, more realistic approach. Verbal estimates should be recorded as conversations, with an outcome noted clearly. Was it accepted, declined, or is the customer still thinking about it? Once that’s known, there’s no need for automated follow-up. Written estimates, on the other hand, benefit from being tracked once they’re sent. If nothing happens, a calm follow-up or two makes sense. Different situations need different handling.

The difference most people miss

The difference most people miss is that a verbal estimate already includes a response, even if that response is hesitation. A written estimate often doesn’t. That single difference should change what happens next. When systems respect it, they feel helpful. When they don’t, they feel annoying and out of touch.


How Siteyard approaches it

At Siteyard, we treat verbal and written estimates as different tools, not competing ones. The goal isn’t to force everything into paperwork. It’s to support how trades already work in the real world.