The quote was $2.5K. The project was $6.5K. Here's how I knew.

A client forwarded me a helpdesk implementation quote and asked one question: "Is this fair?" The number was $2,500. Twenty minutes later, I knew the honest answer was no — it was fair to nobody, including the vendor.

The quote covered "Zendesk setup and configuration." What it didn't cover was everything the client actually needed: migrating four years of ticket history out of a shared inbox, SLA policies for three client tiers, an escalation path that crossed two time zones, and integrations with an invoicing system the vendor had never heard of.

Underscoped quotes aren't cheap — they're deferred invoices

An underscoped project doesn't cost less. It costs the same or more, just later, delivered as change orders, blown timelines, and a team that stops trusting the system before it launches. The $2.5K quote was really a $6.5K project wearing a smaller price tag to win the signature.

So we did the unpopular thing: we repriced it upward before anyone signed. The new scope was written line by line — migration included, SLA design included, two rounds of workflow revision included, and a named list of things explicitly not included.

A scope document is a pricing document. If it can't tell you what's excluded, it can't tell you what it costs.

The client signed at $6.5K. Not because they enjoyed a bigger number, but because it was the first quote in the process that survived their questions. The project shipped on the revised scope with one change order — a small one, and it was theirs, not ours.

Three questions that would have caught it

If you're holding a quote right now, ask: Where does the data live today, and who is moving it? What happens to a ticket that breaches SLA at 2 a.m.? And which of my current workflows is this price assuming I'll abandon? If the quote can't answer all three, the number on it is fiction.