“I very much respect the knowledge that you have. You have a lot of things, just in our few communications, that no one else has mentioned. No one else has even made me think about them.”
Discovery Sprint
A scoped spec and cost before you commit
A 1 to 2 week co-creation engagement that produces a scoped roadmap, architecture overview, risk register, and a fixed-price quote. The right starting point before any significant build: no commitment beyond the Sprint itself.
Why choose us for discovery sprints?
The sprint only earns its place if what comes out of it holds up in front of any engineering team, investor or vendor you show it to.
Scoped roadmap
You leave with a prioritised roadmap you can put in front of stakeholders, investors or any engineering team: user flows, feature scope and the MVP-vs-full-build decisions written down.
Fixed-price quote
The Project Build that follows is quoted as a binding fixed price rather than an estimate or a range, so there is a number you can plan against and no surprise change orders.
Architecture + risk register
An architecture overview, integration scoping and a register of technical risks catalogued by severity mean you know exactly what you are committing to before you commit.
Wireframes for the critical paths
The critical user flows are drawn as Figma wireframes during the sprint, so the scope is something you can look at rather than a list of feature names.
The number comes with its assumptions
Milestone definitions and the assumptions behind the quote arrive in writing alongside it, so you can see what the price rests on and challenge any of it before you sign.
Yours to keep, whatever you decide next
The roadmap, wireframes, architecture docs and risk register are yours to use with any vendor or internal team, whether or not the build that follows is with us.
What we build in discovery sprints
Everything a sprint produces is a document or a drawing you can hand to someone else, which is the point of it.
Scoped backlog
Feature scope with the MVP-vs-full-build line drawn, prioritised for a build team.
- Every feature written as a user story
- Each story tagged MVP or a later phase
- Ordered by the value it unlocks first
Critical-path wireframes
Figma wireframes for the user flows that matter most, before any code exists.
- Every screen on the critical user paths
- States for empty, loading and error cases
- Annotated with the rules behind each screen
Architecture note
The existing stack assessed and an architecture recommended, with integrations mapped.
- What to keep from the current stack
- Recommended services, data model and hosting
- Each integration listed with its dependencies
Fixed-price estimate
A binding quote for the Project Build that follows, not a range.
- One fixed number for the whole build
- Team composition and milestones behind the price
- The assumptions the quote rests on, in writing
Risk register
Technical risks catalogued by severity, known before the build starts.
- Each risk rated by likelihood and impact
- A mitigation or fallback beside every entry
- The ones that could sink the build flagged first
Roadmap
The full roadmap as PDF and Notion, ready for stakeholders or investors.
- Sprint plan with what ships in each phase
- The recommended team and who does what
- Yours to hand to any vendor or team
Recent products we shipped
Our most recent case studies. Each result is the one its own case study reports, in its own words.
30+ SKUs scanned into one Shopify draft order; the old version choked on large ones.
Draft Deputy
Shopify · Micro-SaaS
1,000+ skincare formulas resolved from a 60-second phone scan in 55+ San Pablo pharmacies, before the customer leaves the store.
2250
A.I · Custom Web App

3.5K students stayed online while a Lovable-built front end was mapped onto the live LMS.
Squid Academy LMS
SaaS · Custom Web App

Non-marketers launch Meta and TikTok campaigns from one plain form, and read both platforms’ results in one view instead of two ad managers.
AI Agent for Meta and TikTok Ads
MVP · SaaS
How we build discovery sprints
Ten days in overlapping stages, from stakeholder interviews to a roadmap and a binding quote.
Days 1 to 3: Kickoff & stakeholder interviews
Founder and stakeholder interviews, product requirements gathering, and technical constraints discovery. We align on what success looks like before we scope.
Days 3 to 5: Architecture review & integration scoping
Existing-stack assessment, architecture recommendation, third-party integration mapping, and dependency audit.
Days 5 to 8: User flows & feature scoping
User flow mapping, feature scope definition, MVP-vs-full-build boundary decisions, and Figma wireframes for the critical paths.
Days 8 to 10: Estimate, roadmap & handoff
Sprint plan, team composition recommendation, a binding fixed-price quote for the Project Build, and the full roadmap document delivered as PDF + Notion.
- See our full process
What clients say after the build
Real client reviews, every one checkable at source.
Discovery Sprint questions
Straight answers about how the Sprint works, what it costs, and what happens after.
Scoped on our initial call based on product complexity and the team size needed. We give you the number before any work starts: no open-ended meters, no surprise invoices.

