The most expensive mistake in software is building the wrong thing well. Product discovery is how you avoid it. Before anyone writes code, we work with you to validate the actual problem, talk to the people who will use the product, and define the smallest version worth building. The result is a plan grounded in evidence, not assumptions, and a budget you can defend.
Strategy & Product Discovery
Get the Plan Right Before You Write a Line of Code
Most failed software fails in planning, not coding. Product discovery validates the problem, scopes the smallest version worth building, and hands you a plan any team can execute.
Discovery with Larkwell runs one to four weeks depending on scope. You get a senior product strategist and a senior engineer looking at your idea from both sides: what the market needs and what is realistic to build. At the end you own every deliverable, whether you build with us or take the plan elsewhere. That is the point. Good plans stand on their own.
What you get
The discovery wall
Four columns of work, one wall. Each card below is a piece of the plan you walk away with.
Hover or tap a card to see it work
Product Discovery Workshops
Structured working sessions that turn a rough idea into a tested concept. We map user problems, challenge assumptions, and pressure-test the business case with you in the room. You leave with a clear problem statement and evidence for what to build first.
MVP Planning & Roadmapping
We scope the smallest version of your product that delivers real value, then sequence everything else into a realistic roadmap. Features are prioritized by business impact, not wish lists, so your first release earns its budget.
Technology & Architecture Consulting
Senior engineers recommend a stack and architecture that fit your budget, team, and five-year plan, not just the current sprint. The goal is a foundation that scales without a rewrite. We document every decision and the reasoning behind it.
Business Process Analysis & Automation
We map how work actually moves through your business, find the bottlenecks and manual steps that drain hours, and identify which processes are worth automating. You get a prioritized automation plan with realistic effort estimates for each fix.
How we work
From first workshop to handoff
One to four weeks depending on scope — and a plan any team can execute at the end of it.
- 01 · Discovery
Discovery workshop
Structured sessions that surface the real problem, the real users, and the real constraints.
- 02 · Validation
Validate & prioritize
Assumptions tested cheaply before budget is committed to any of them.
- 03 · Roadmap
Roadmap & architecture
A scoped MVP, a sequenced roadmap, and a stack that won't need a rewrite.
- 04 · Handoff
Handoff or build
Deliverables any team can execute — ours or anyone else's. No lock-in.
Book the first workshop
Start with a free consultation. Straight answers, a written scope, no obligation.
Outcomes
What you can expect
- Validate the problem before you commit a development budget to solving it
- Scope an MVP that reaches users sooner instead of a bloated first release
- Choose architecture that grows with your business instead of forcing a rewrite
- Own every deliverable outright, with no obligation to build with us
- Reduce project risk with plans written by senior engineers, not salespeople
Tools
The workshop sticker sheet
Figma FigJam Miro Notion Jira Confluence Lucidchart Mixpanel Hotjar Maze UserTesting Airtable
FAQ
Questions from the wall
Honest answers — including the ones about price.
01 What is a product discovery phase and do I need one?
Product discovery is a short, structured phase before development where we validate the problem, define the smallest useful version of your product, and plan the architecture. You need one if the project involves meaningful budget, unproven assumptions, or multiple stakeholders. For small, well-defined builds, a lighter scoping call is often enough, and we will tell you if that is the case.
02 How much does discovery cost and how long does it take?
Typical US-market discovery engagements run from around $5,000 for a focused one-week sprint to $25,000 or more for complex, multi-stakeholder products, over one to four weeks. Scope drives price: the number of user groups, integrations, and unknowns matters more than anything else. We quote a fixed price after a free initial call, so there are no surprises.
03 What deliverables do we get at the end of discovery?
You receive a written problem and solution definition, a prioritized MVP feature scope, user flows and wireframes for key screens, a recommended architecture with the reasoning documented, a delivery roadmap, and a development cost estimate. Everything is written in plain business language with enough technical detail for any competent team to execute. All files and documents are yours to keep.
04 Can you audit software that another team built?
Yes. We review the codebase, architecture, security posture, and infrastructure, then give you a plain-English report on what is solid, what is risky, and what it would cost to fix. This kind of audit is most useful after an agency handoff, before an acquisition, or when a project has stalled.
05 Are we locked in to building with Larkwell afterward?
No. Every deliverable is written so any competent development team can build from it, and you own all of it outright. Many clients do continue with Larkwell because the same senior engineers who planned the product can build it, which saves ramp-up time. But the plan stands on its own, and there is no obligation to continue.