The Estimate That Was Never an Estimate

Summary: A scoping conversation produces a number. Both sides treat it as a price. Neither side treated it as one when it was said. The number becomes load-bearing without ever being chosen, and the relationship begins on a foundation that nobody actually agreed to.

Pattern

A potential client asks roughly what something will cost. The seller, mid-conversation, gives a rough number to keep the conversation moving. The client hears the number as a quote. The seller hears their own answer as a starting point for a real conversation. From that moment, the two parties are working from different documents.

What tends to happen

The conversation continues. Scope is discussed in vague strokes. Everyone is friendly. A version of “let’s make it work” is exchanged.

Days later, a more formal scoping happens. The work, once examined, is meaningfully larger than the rough number suggested. The seller writes up a proper estimate. The client reads it and feels overcharged — not because the new number is wrong, but because they are now anchored to the first one.

The relationship arrives at its first real moment of friction before any work has begun.

Why it fails

Nobody acted in bad faith. The seller answered a casual question casually. The client treated the answer with the seriousness that any number deserves once it leaves a professional’s mouth.

The asymmetry is built into the conversation. The seller knows the difference between a guess and a quote. The client cannot reliably distinguish them, especially when the guess is delivered with confidence. The label “rough estimate” or “ballpark” does not survive the trip from the seller’s mouth to the client’s notebook. What survives is the number.

Human layer

Most rough numbers are a form of conversational lubricant. They keep a discovery conversation from stalling out on the awkwardness of “I cannot give you a price yet.” They are produced under social pressure, not commercial pressure.

The cost of this becomes visible later, when the same number has to do commercial work it was never designed for. It has to defend itself against a client who has now built a budget around it.

System layer

Most solo and indie operations do not have a structured intake. There is no form, no triage, no separation between “exploration call” and “scoping engagement.” The same conversation is doing both jobs, and the number leaks out somewhere in the middle.

A more structured operation would have intake stages where pricing simply cannot be discussed, and gates beyond which it must be discussed in writing. Most independent operators do not have those gates because they did not need them when the practice was smaller.

What it costs

The cost is not always the deal. Sometimes the deal closes at the higher number, after a conversation that leaves both sides slightly bruised. Sometimes the deal closes at the original number, and the seller absorbs the gap by working uncompensated hours.

The deeper cost is in the relationship’s calibration. It begins with one party feeling that the other moved the goalposts. That perception lingers through the engagement and shapes how every subsequent question is interpreted.

Reduction path

The first intervention is to refuse to give numbers verbally during exploration. Not in a stiff way — a sentence is enough: “I do not want to give you a number that we will both have to defend later. Let me write something up.” This trades a small amount of conversational warmth for a large amount of later clarity.

The second intervention is to send a written scoping document before any number appears anywhere. The number, when it arrives, arrives next to the assumptions it depends on. This makes it harder for the number to detach from those assumptions and travel on its own.

The third is to recognize that the question “roughly what would this cost?” is rarely a question about cost. It is a question about whether the relationship is worth continuing. A scoping document answers that question better than a number does.