Do I need written requirements?
No. We can start with an idea, a workflow to improve or a recurring problem. Concrete examples, known constraints and an initial goal help.
SERVICE
Product Discovery: from idea to technical plan
You have a product idea or a business problem, but requirements and technical choices are still unclear. Product Discovery is a structured engagement to decide what to build, in what order and on what technical foundation. You leave with a concrete plan for assessing the development investment.
Let’s talk about your projectWhen to start with Discovery
- You are a founder turning an idea into a first product to test.
- Your business has an operational problem, but it is unclear whether custom software, integrations or automation will help.
- There are many possible features: you need to decide what belongs in the MVP and what can wait.
- You need to assess feasibility, dependencies and risks before committing to development.
The handover: a plan you can use
- Product scope: problem, users, goals, requirements and first-release boundaries.
- Reference architecture: components, data, stack, integrations and key technical decisions.
- A phased roadmap and an initial feature backlog ordered by priority.
- Development effort estimate with explicit assumptions, dependencies and uncertainty.
- Technical risks and recommendations: checks to make, alternatives and relevant AI or automation opportunities.
PROCESS
How we work on your idea
- 01
Clarify the problem
We gather context, users, goals and constraints. We first agree the Discovery scope and the materials to review.
- 02
Define the first product
We translate needs into requirements and journeys. We select core features and separate the first release from later improvements.
- 03
Assess technical choices
I compare architecture, stack and integrations, assess automation opportunities and identify risks that need technical validation.
- 04
Deliver and discuss the plan
We review scope, architecture, backlog, estimate and roadmap together. You decide how to proceed, with me or with your team.
FAQ
Before we start
How long does it take and what does it cost?
It depends on complexity, integrations and available materials. The first conversation defines the scope; activities, timeline, deliverables and fee are agreed before work begins.
Does Discovery include development?
No. It is a standalone engagement with a defined handover. Any technical prototype must be agreed in the scope; product development is assessed and agreed separately.
Can my own team use the plan?
Yes. The handover makes the decisions usable. There is no requirement to hire me for subsequent development.