Company· 5 min read
What a good discovery phase actually produces
Discovery is not a sales exercise. Done properly, it ends with documents you own and a decision you can make with confidence.
NNAFATECHS AdminAdministrator
Discovery has a reputation problem. In many agencies it is a free-looking preamble that quietly commits you to the build. We run it differently: it is a short, paid engagement with a defined output, and you keep that output whether or not we build the rest.
What you receive
- An architecture document describing the system, its main components, data model and integrations in plain language.
- A prioritised scope separating what must be in the first release from what can wait.
- A fixed estimate with every assumption written down, so you can see exactly what the number depends on.
- A risk register listing what we do not yet know and how we plan to find out.
How we get there
The first week is listening. We talk to the people who will use the system, not just the person buying it, and we ask them to show us the work rather than describe it. The second week turns what we heard into models and options. The third presents trade-offs honestly, including the option of not building anything.
Why we charge for it
Because the work is real and the result is valuable on its own. A free discovery is a sales process, and it is built to end in a yes. A paid one is built to end in the right answer — which occasionally is “do something smaller”, or “do not do this at all”. We would rather tell you that in week three than in month six.
What it is not
It is not a vague workshop with sticky notes and no output, and it is not a commitment. If you take the documents to another supplier, they will make that supplier faster and more accurate, and that is a fine outcome.
