For founders and product teams
I have a product idea and need a first version people can actually use.
You do not need a full specification. You need a sharp question, a small scope and a build that can be extended once you know the answer.
Where you probably are right now
A long feature list and a short budget
Everything feels essential, but you cannot afford to build all of it before knowing what matters.
Unsure what to build first
You are choosing between web, mobile, integrations and admin tools without evidence to rank them.
Worried about a throwaway prototype
You want speed, but not a codebase you have to discard after the first users arrive.
What you walk away with
A written scope
What is in the first release, what is explicitly out, and the question the release is meant to answer.
A working product
Deployed software with accounts, the core workflow and monitoring, ready for real users.
Data to decide with
Analytics events and a feedback channel so the next step is a decision, not a guess.
How we get from idea to launch
Frame the question
We agree who the product is for, what must be true for it to succeed, and what to test first.
Cut the scope
Features are ranked against that question. Anything that does not help answer it waits.
Design and prototype
A clickable prototype is shown to target users before development starts.
Build in weekly slices
You use working software each week and redirect while changes are still inexpensive.
Launch and read the signals
We release to a first group of users and review usage together.
Typical path for an MVP
Typical durations for this kind of work. Real timing depends on scope, integrations and how quickly decisions are made.
Scope and prototype
3 to 6 weeks
Question, scope, flows and a tested prototype.
First build
6 to 12 weeks
Core workflow, accounts, any payments and admin basics.
Launch and review
2 to 4 weeks
Release to early users, monitoring and a prioritised next step.
Questions from founders
Do I need a full specification before contacting you?
No. A clear description of the problem and the user is enough. Producing the specification is part of the first phase.
Can I keep building on it afterwards?
That is the intention. We keep features few but structure code, data and deployment so that you extend the product. Some parts will change as you learn, which is normal.
How do you decide what goes in?
By asking what is needed to test your riskiest assumption with real users. We document the reasoning, so scope discussions have a reference point.
Services that deliver this
- MVP developmentScope, design, build and launch a minimum viable product with analytics in place, so the next decision is based on what real users do.
- Product designUX research, interface design, design systems and prototypes for web apps, mobile products and dense admin tools, delivered with engineers in the loop.
- SaaS developmentFrom MVP to scalable SaaS: multi-tenancy, subscription billing, teams and roles, usage analytics and the architecture to grow without a rewrite.
- Mobile app developmentReact Native, iOS and Android apps with offline workflows, Bluetooth and hardware integration, push notifications, payments and scalable backends.
Bring the idea, even if it is rough.
We will help you decide what the first version should and should not contain.
Tell us about your product idea
Who is it for, what problem does it solve and what have you tried so far? Rough notes are fine.