Every conversation adds another feature. The launch date moves. And the most important question stays unanswered: will people actually use this?
I help founders turn a product idea into a focused first release. We define the core experience, design it, and build a working product you can put in front of real users.
The goal is to give people enough value to come back, and give you enough evidence to decide what deserves building next.
Who this is for
Founders with a clear problem to solve who need a partner to shape and ship the first version. You might have a rough brief, early customer feedback, a Figma prototype, or an unfinished build.
A good fit for SaaS tools, customer portals, booking platforms, marketplaces, and products that turn a manual service into a digital experience.
You should be ready to make scope decisions, share feedback, and involve early users.
What we build
A complete core journey, with the supporting functionality needed to make it usable:
First-use experience: clear onboarding that helps users reach the product’s value quickly.
Core workflow: the main task your product helps someone complete, from beginning to end.
Accounts and access: sign-in, profiles, and user roles where required.
Data and integrations: the database, APIs, payments, or external services the agreed workflow depends on.
Essential admin tools: enough visibility and control to manage the first release.
Learning after launch: agreed analytics events or feedback points to understand how people use the product.
We decide what belongs in the first release by asking what it helps us learn and whether the core experience works without it.
How the project works
Define the first release. We identify the target user, the problem, and the key assumption the product needs to test. You get a clear scope, launch criteria, and a separate backlog for later ideas.
Design the core journey. I map the flow and create the key screens in Figma. We review the experience before committing to the build.
Build in milestones. I develop the approved product with regular demos, so you can review working progress and make informed decisions.
Prepare for launch. We test the main journeys, access rules, and failure states, then deploy the agreed release and walk through how to operate it.
What you receive
A defined MVP scope and prioritized future backlog.
Figma designs for the agreed product flows.
A working product with the agreed backend and integrations.
Reusable components to support future iterations.
Source code, setup documentation, and a handover walkthrough.
Deployment to the agreed hosting environment.
How scope is defined
Pricing and timing depend on the core workflow, platform, user roles, integrations, and technical complexity.
We agree on the launch scope before work starts. New ideas are assessed against that scope and either scheduled for a later release or quoted as a change. Hosting, paid services, and ongoing support are scoped separately.
Let’s Talk Shop
Tell me who the product is for, what they struggle with today, and what the first version needs to help them do. Bring the rough notes. We will turn them into a clear starting point.
Every conversation adds another feature. The launch date moves. And the most important question stays unanswered: will people actually use this?
I help founders turn a product idea into a focused first release. We define the core experience, design it, and build a working product you can put in front of real users.
The goal is to give people enough value to come back, and give you enough evidence to decide what deserves building next.
Who this is for
Founders with a clear problem to solve who need a partner to shape and ship the first version. You might have a rough brief, early customer feedback, a Figma prototype, or an unfinished build.
A good fit for SaaS tools, customer portals, booking platforms, marketplaces, and products that turn a manual service into a digital experience.
You should be ready to make scope decisions, share feedback, and involve early users.
What we build
A complete core journey, with the supporting functionality needed to make it usable:
First-use experience: clear onboarding that helps users reach the product’s value quickly.
Core workflow: the main task your product helps someone complete, from beginning to end.
Accounts and access: sign-in, profiles, and user roles where required.
Data and integrations: the database, APIs, payments, or external services the agreed workflow depends on.
Essential admin tools: enough visibility and control to manage the first release.
Learning after launch: agreed analytics events or feedback points to understand how people use the product.
We decide what belongs in the first release by asking what it helps us learn and whether the core experience works without it.
How the project works
Define the first release. We identify the target user, the problem, and the key assumption the product needs to test. You get a clear scope, launch criteria, and a separate backlog for later ideas.
Design the core journey. I map the flow and create the key screens in Figma. We review the experience before committing to the build.
Build in milestones. I develop the approved product with regular demos, so you can review working progress and make informed decisions.
Prepare for launch. We test the main journeys, access rules, and failure states, then deploy the agreed release and walk through how to operate it.
What you receive
A defined MVP scope and prioritized future backlog.
Figma designs for the agreed product flows.
A working product with the agreed backend and integrations.
Reusable components to support future iterations.
Source code, setup documentation, and a handover walkthrough.
Deployment to the agreed hosting environment.
How scope is defined
Pricing and timing depend on the core workflow, platform, user roles, integrations, and technical complexity.
We agree on the launch scope before work starts. New ideas are assessed against that scope and either scheduled for a later release or quoted as a change. Hosting, paid services, and ongoing support are scoped separately.
Let’s Talk Shop
Tell me who the product is for, what they struggle with today, and what the first version needs to help them do. Bring the rough notes. We will turn them into a clear starting point.