It happens on almost every first call. Ten minutes in, after a good description of the idea, comes the question: “So — ballpark, what would this cost?” And we give the answer nobody loves: we don’t know yet, and neither does anyone else.

An estimate without discovery is a guess with a signature. Here’s what actually happens when a vendor quotes a custom software project from a phone call — and what a real scoping process looks like instead.

The first-call quote is a trap for both sides

A number given on day one can only be built from assumptions. To protect themselves, vendors pad it — or worse, they lowball it to win the work and make up the difference in change orders. Either way, the number you anchored your budget to was fiction. The project doesn’t get cheaper because the guess was optimistic; it just gets tense.

What discovery replaces the guess with

Our discovery phase is a short, fixed-price engagement with concrete deliverables: workshops with the people who do the work, a requirement document in plain language, wireframes of every screen, and a feature set ranked by business value. By the end, three things exist that didn’t before:

The blueprint is yours either way

Here’s the part that surprises people: everything discovery produces belongs to you. Take the wireframes and requirement document to another firm, put it out to bid, build it in-house — the blueprint stands on its own. Clients rarely do, but knowing they could keeps our recommendations honest.