Product scoping
Deciding the first version, which mostly means deciding what to leave out.
Services
SaaS and Product Development
We can also help determine what belongs in the first version and what should wait.
Have a software product you want to build? We help with product scoping, technical architecture, database design, frontend and backend development, APIs, infrastructure, testing, deployment, analytics, and launch.
We can also help determine what should be in the first version and what should wait, which is usually the decision with the largest effect on whether the product reaches anyone.
We build and operate our own products, so the parts that are easy to underestimate are the parts we plan for first: billing, support, churn, infrastructure cost, and the second year of a codebase.
Problems this solves
You may recognise some of these.
- The roadmap covers eighteen months and nothing is in front of a user
- You have a prototype and no idea what it takes to make it real
- The product works and the business model has never been tested
- Infrastructure costs scale faster than revenue
- Every new customer requires a custom change
What we do
The work itself
Architecture and data design
Decisions that are cheap now and expensive in eighteen months.
Frontend and backend build
The product itself, built to be extended by people who did not write it.
Infrastructure and deployment
Environments, pipelines, monitoring and cost control.
Launch and measurement
Analytics, funnels and the instrumentation to tell whether it is working.
Process
How an engagement runs
Define the smallest sellable version
Not a demo. Something a customer can actually use.
Design the data model early
It is the decision that is hardest to reverse later.
Build, deploy, and get it used
Real usage answers questions a roadmap cannot.
Instrument the business, not just the app
Activation, retention and cost per customer.
Decide what comes next from evidence
Rather than from the original plan.
Technology
What we typically build this on
The technology is chosen around the project. The business problem comes first.
- TypeScript
- React
- Node.js
- Python
- Django
- PostgreSQL
- DigitalOcean
- Cloudflare
Related work
Software we have built
Nutrition and Meal Planning Application
easyChef Pro
A consumer health and nutrition platform combining meal planning, pantry management, grocery workflows, nutrition data and personalised recommendations.
Read the case study →B2B Nutrition Platform and API
NutriSync
The business arm of easyChef Pro. The same scoring engine sold white label, brown label, or as an API, to sports teams, healthcare providers and enterprises.
Read the case study →Questions
Things people ask before starting
- Can you help decide what goes in version one?
- Yes, and it is often the most valuable part of the engagement. A first version that ships beats a complete one that does not.
- Do you work with founders who are not technical?
- Yes. You do not need to know which framework, database, AI model or cloud service you need. Tell us about the business and the problem and we will work out the technical approach.
- What if the product does not work commercially?
- That is a real outcome and worth finding out cheaply. Building the smallest useful version first is how you find out before the money is gone.
Related services
Often part of the same engagement
Tell us what you are trying to build
Tell us about the business, the problem, what you have today, and what you want to accomplish. If we are not the right team, we will tell you.