The quote you're used to getting
When you ask a technology firm to quote a project, you're usually expecting a number back within a few days. Maybe a week. A PDF with line items, a timeline, a total.
What you're actually getting is a guess dressed up as a plan.
The firm hasn't spent time in your operation. They haven't talked to the people who actually run the system day to day. They haven't seen where the workarounds live, or why that particular process works the way it does, or what happens when something breaks at 6pm on a Friday.
They've taken your brief, made some assumptions, added a contingency margin, and called it a quote.
That number isn't something you can trust. And here's the uncomfortable part — most of the time, neither can they.
What that quote is actually telling you
When a fixed price lands before anyone has spent real time in your operation, something is off.
Either there's so much hidden contingency in the number that you're paying for their uncertainty without knowing it. Or the quote is optimistic — written to win the work, with the real cost to emerge later when you're already committed. Or the firm has done this specific problem so many times they genuinely don't need to look closely — but that situation is rarer than they'd have you believe. Most operations are more particular than they appear from the outside.
What goes wrong when you skip straight to build
There's usually a gap between what someone thinks they need and what their operation actually needs. That gap is where most projects quietly fail — not during the build, but after it.
The system gets delivered. It works. The firm moves on. And then it starts not working — because it was built to a brief, not to the reality of how things actually run. Processes that existed informally never made it into the design. Constraints nobody thought to mention surface halfway through. The documentation describes the system as it was imagined, not as it ended up.
None of that is inevitable. It's what happens when the work starts before anyone really understands the operation.
What a Discovery Sprint is
Before we design anything, we spend time in your operation. We talk to the people who actually run it — not just whoever wrote the brief. We map the workflow as it actually works, including the workarounds. We look at what already exists and what it can and can't do.
Then we tell you what we found — including the things that are uncomfortable to hear.
If technology isn't the right answer to your problem, we say so before any money goes into building. A Sprint that ends with "don't build" is still a useful Sprint. You're paying for an honest read, not a proposal dressed up as one.
If building does make sense, you walk away with your operation properly on paper — how it works, where the problems are, what the constraints are — and a plan for the next phase that's based on that understanding rather than a set of assumptions made at a distance.
The Sprint is fixed fee. If we scope it wrong, we absorb the extra time. You won't get an invoice for our misjudgement.
What this looked like for one client
The knowledge that ran a critical operation belonged to one person. Not written down anywhere. No handover plan. Everyone knew it was a problem; nobody had been able to fix it.
We went in, spent time in the operation, and turned what we found into something the whole team could read — a breakdown of how the system actually worked, a workflow map, the dependencies nobody had ever made explicit. That alone had value before anything was built. And it meant that when we did scope a build, we were working from something real.
The pushback
"Other firms don't charge for this."
They do, though. They just hide it in the build quote, or they skip the work and hope the gaps don't show until after handover.
We'd rather be upfront about what the investigation costs than bury it somewhere you can't see it or, worse, not do it at all.
One question worth bringing to your next project
Before you accept a quote, ask the firm — what did you learn about our operation before you put this number together?
If the answer is "we worked from your brief," you already know what you're dealing with.