Discovery sprint for a pet-care marketplace
User interviews, a tested clickable prototype and a phased MVP plan with budget, ready to build or show investors.
- Typical timeline
- 3 weeks typical
- Team
- 2 people
Clarify the problem, validate the solution and plan your product before investing in development.
Before spending your budget on building, you want to know what to build, for whom and what it will cost. You get a tested plan, a prototype and a realistic estimate you can take to any team.
Most failed products don't fail because of bad code — they fail because they solved the wrong problem or tried to do too much at once.
Our discovery phase brings product, design and engineering together to define what to build, why and how — so development starts with clarity and a reliable estimate.
This is for you if you…
Every project is different, but these are the pieces we combine most often.
Align stakeholders on goals, users and success metrics.
Understand customers, competitors and opportunities.
A clear, prioritised backlog ordered by value.
Visualise the product and test it with users.
Stack, integrations and infrastructure planned upfront.
A phased plan with timeline and budget.
Typical budgets by scope, so you can plan before we talk. After a free 30-minute call you get an exact quote in writing, before any work starts.
$2,000 – $4,000
1–2 weeks
Best for: Turning an idea into a buildable plan
$5,000 – $10,000
3–4 weeks
Best for: Founders seeking evidence before building
from $10,000
4–6 weeks
Best for: Complex or regulated products
Prices in USD, excluding taxes. They're typical ranges, not offers: your price depends on scope and is agreed in writing. Not sure which fits? See how we price.
Get your exact quoteThese choices shape the cost, the timeline and how the product works for years. We talk them through with you in plain English before any code is written.
If scope is unclear, yes: a few weeks of discovery usually saves far more in rework. If you already have tested designs and a clear spec, skip it and we'll start building.
The person who owns the budget, someone who knows your customers and anyone who'll use the product. Two focused workshops beat weeks of email.
A scope you can build from, a realistic budget and timeline, a prototype if included, and the list of risks we found. It's yours, with or without us.
Everyone agrees on what's being built and why.
A detailed scope means fewer surprises later.
Assumptions tested with real users early.
A ready backlog lets engineering start at full speed.
Clear steps, a demo every week, and no surprises on the invoice.
1–2 weeks
Clarify the problem, the users and the smallest product that proves value.
1–3 weeks
A clickable prototype to test with users and show investors.
6–12 weeks
A production-ready first version on a scalable foundation.
Ongoing
Analytics, feedback loops and fast iterations after launch.
Proven tools chosen for your product, team and budget, not whatever is trending this month. Here's what each one does for you.


From the first call to launch day, you talk directly to the designers and engineers building your product. Same faces, same team. No hand-offs to strangers halfway through.
“If something isn't worth building, we'll tell you. If something goes wrong, you'll hear it from us first.”
— the VavenSoft team
Projects we've designed and built, and what changed for the people using them.
User interviews, a tested clickable prototype and a phased MVP plan with budget, ready to build or show investors.
Twenty AI ideas scored on value and effort, two of them prototyped, and a costed 12-month plan for the board.
Straight answers to what people ask us first: cost, time, ownership and the details that matter. Anything else? Just ask.
It depends on scope. Typical budgets: Discovery sprint, $2,000 – $4,000; Discovery + prototype, $5,000 – $10,000; Full discovery, from $10,000. After a free 30-minute call you get an exact quote in writing, before any work starts.
You do. You own the research, prototype, scope and estimate once invoices are paid, so you're never locked in to us.
Typically 2–4 weeks, depending on product complexity and the amount of research needed.
A product vision, user personas and flows, a clickable prototype, a technical architecture outline and a prioritised roadmap with estimates.
No. The discovery deliverables are yours and can be used with any team — though continuing with the same team saves ramp-up time.
Yes. You own everything from discovery. We hope you'll build with us, but the plan works with any capable team.
Yes. Workshops run well over video with a shared whiteboard, and user interviews can happen wherever your users are.