User journeys and product flows
Who the product is for, what they are trying to finish, and where the current path breaks down.
Product discovery and UX/UI sprints: find out what to build before you pay to build it.
A short, fixed-price sprint that turns an uncertain idea into a plan you could hand to any competent team, including one that is not us.
- User journeys and product flows
- Solution outline and risk map
- Prototype and design-system foundation
- Delivery options and evidence-based estimate
Most software that fails does not fail because it was built badly. It fails because the wrong thing was built carefully. By the time that becomes obvious, the budget is gone and the team is defending decisions nobody can remember making.
Discovery is the cheapest place to be wrong. It is a small, bounded purchase that ends in a written recommendation, including the recommendation to stop, which we will give you if the evidence points that way.
You keep everything it produces. If you take the plan to another firm, or build it in house, that is a legitimate outcome and the work still paid for itself.
What the engagement includes
Solution outline
The shape of what to build, in enough detail to estimate and to disagree with.
Risk map
What could sink this, ranked, with the cheapest way to test each risk early.
Prototype
A clickable version of the core flow. Far cheaper to argue about than a built feature.
Design system foundation
The type scale, colour, and components the build will reuse, so the first sprint is not also a design exercise.
Evidence-based estimate
Delivery options with costs and trade-offs, based on the plan rather than on optimism.
Whether this is the right fit
We would rather tell you now than three weeks in. If the right column describes you, say so on the call and we will point you somewhere better.
Best when
- The idea is real but the scope is still argued about internally
- You need a number you can take to a board or an investor
- Two or more approaches are on the table and nobody can settle it
- A previous attempt produced code nobody wanted to use
- You want to test how we work before committing to a build
Not the right fit when
- The scope is genuinely settled and you just need it built
- You want a proposal and an estimate for free, which is a different conversation
- Nobody available can answer questions about the business
- The decision has already been made and discovery is wanted as cover for it
How it runs
Frame the question
Agree what the sprint must answer, so it ends in a decision rather than a document.
Learn
Talk to the people who will use it and the people who will support it. Read whatever exists already.
Shape
Flows, a prototype, and the technical direction, reviewed with you as they form rather than revealed at the end.
Cost and risk
Options with estimates, and an honest map of what could go wrong.
Recommend
A written recommendation to proceed, reshape, or stop, with the reasoning attached.
How this is priced
Discovery is fixed price. The scope is knowable, the duration is short, and you should be able to buy it without a negotiation. Founding clients get the same sprint at a 25% reduction with no obligation to continue.
Where the work happens
Discovery runs on GMT+7. Sessions are scheduled inside your working hours, early or late where the overlap is tight, and the written output is built to travel: it has to be useful to someone who was never in the room, including a team that is not us. The firm is a registered business, and the registration is published with the contact details if you would rather check before paying for a sprint.
Before you ask on the call
How long does it take?
Short enough that momentum survives it. The exact length depends on the size of the question, and we agree it in writing before starting rather than billing by discovery.
What if the recommendation is to stop?
Then that is the answer, and it is the most valuable one we can give. It costs a fraction of finding out after the build.
Do we have to build with you afterwards?
No. Every stage is separately scoped and approved. You keep the artifacts and may take them anywhere.
Is the prototype throwaway?
The prototype is for deciding, not for shipping. The design system foundation underneath it is not throwaway and carries into the build.
If this is not quite the shape of it
The engagements next to this one, and the reason you might want them instead. All five are in the Services menu at the top of the page.
Bring the question you cannot settle.
Thirty minutes by video with Tai. Describe the idea and where the disagreement is. You will leave knowing whether a discovery sprint would actually help.
If you cannot yet say what you are building, you are exactly on time.