Why we start every project with a two-week discovery.
What a product discovery engagement is, what you walk away with (a brief, a prototype and a priced plan) and why it saves money even if you build elsewhere.
By the Wovekit team · · 5 min read
Most software projects that go wrong went wrong before anyone wrote code. The brief was a wish list, the price was a guess, and the first time anyone saw a screen was the week before launch. Discovery exists to stop that, and it is why we will not quote a build on a first call.
What discovery is
Two to three weeks of structured work with the people who do the job today. We watch the process as it really runs, including the workarounds, then shape options on a page, choose a direction, prototype the core journey and test it with real users. It ends with three things you own.
- A brief in plain English: who it is for, what it does, what it deliberately does not do, and the order to build it in.
- A clickable prototype of the core journey on real phones and screens, so people can react before any code exists.
- A plan with numbers: phases, a fixed price for the first one, running costs and the honest list of risks.
Why it saves money
Changing a prototype costs minutes. Changing a built screen costs days. Changing a launched system costs weeks and a confused team. Every decision moved from the third column to the first is money kept. Discovery also makes quotes comparable: with a written brief, three studios price the same thing, and you can see who has understood it.
What happens in the three weeks
- 1.Listen (days one to five). Sit with the people who do the work. Screens, spreadsheets, inboxes, the lot. Write down what breaks and how often.
- 2.Shape (days six to twelve). Options on a page, then one direction. Prototype the core journey and put it in front of the people who will use it.
- 3.Price (days thirteen to fifteen). Phases, a fixed price for phase one, running costs, risks. A walkthrough you can show a partner or a board.
When you can skip it
If you arrive with a clear specification, the exceptions written down and a sense of budget, discovery would be a tax. We will say so and go straight to a build plan. Discovery is for the far more common case where the problem is clear and the product is not.
Discovery is a fixed fee agreed up front and scoped on a free thirty-minute call. If you want to arrive with something in hand, the planner at /plan produces a short brief from four questions, and we read it before the call.
Short answers.
Is discovery just a sales exercise?
No. It is paid, fixed-price work with deliverables you own. About half of our discovery clients go on to build with us; the rest brief someone else or decide not to build. All three are good outcomes.
What if we already know exactly what we want?
Then we skip it. If you arrive with a clear spec and the exceptions written down, we go straight to a build plan.
How much of our time does it take?
Two or three sessions a week for the first fortnight, usually an hour each, with the person who owns the problem in the room.