Ship the smallest product people will pay for.
Founders rarely fail for lack of features. They fail because the first version took a year and answered the wrong question. We help you cut the idea down to what proves it, build that properly on web and mobile, and put it in front of real users while you still have runway.
- Our own products: Cargonio and our Console, built and launched by us
- Web + iOS + Android: one backend behind every app
- Weeks, not years: a first release scoped to fit your runway
- Your code: repositories and accounts in your name
§ 01Overview
Built by people who launch their own products
We have been on the founder's side of the table: scoping our own products, choosing what to leave out and supporting real customers after launch.
Our own Console, which runs our leads, outreach and hiring, went live in six stages, each one in daily use before the next began. Cargonio, our freight ERP, grew the same way: from freight operations into finance, HR and reporting as real users asked for them. That is the habit we bring to your MVP: launch narrow, learn fast, then grow.
An MVP still has to be built properly. Cutting scope is good; cutting corners on security, payments or data is how a promising product becomes a rewrite six months later. We build the smallest version on foundations you can keep building on, with analytics in place so you know what users actually do.
Where it fits
- Turning an idea into a clickable prototype for investors or early users
- Launching a first version of a SaaS or marketplace
- Building the web and mobile apps behind a new business
- Rescuing an MVP that stalled with another team
- Cut to the core. We help you decide what not to build.
- Built to last. Small scope, solid foundations.
- Measure from launch. Analytics to see what users really do.
- Yours from day one. Code, repos and accounts in your name.
§ 02What you get
Six deliverables.
Product scoping
A short, structured workshop to agree who the first users are, the one problem the MVP solves, and the features that can wait. You leave with a scope, a plan and a price.
Clickable prototypes
A designed, clickable prototype in Figma you can show investors and test with users before any code is written, so the expensive decisions are made with feedback rather than guesses.
Web & mobile MVPs
A production-ready first version on web, iOS and Android from one backend, with sign-up, payments and an admin panel included, because every real product needs them on day one.
SaaS foundations
Accounts, roles, subscriptions and multi-tenant data separation done properly from the start. We learned the awkward parts running Cargonio for real customers.
Launch & analytics
Store submissions, hosting, monitoring and product analytics set up before launch, so the first weeks of real usage tell you something useful.
After launch
We stay on to fix, measure and build the next most valuable feature, or hand over cleanly to your own team when you hire one.
§ 03How it runs
Four steps, in the open.
- Step 01
Scope the bet
We agree the riskiest assumption in your idea and the smallest product that tests it, and write the scope down with a fixed price for the first release.
- Step 02
Prototype and test
A clickable prototype in front of a handful of target users in the first weeks, so the build starts from what they actually responded to.
- Step 03
Build the first release
Short cycles with a working build you can use every week, and a firm line between what is in this release and what waits for the next.
- Step 04
Launch and learn
We launch, watch the analytics with you and plan the next release around what users did, not what was in the original plan.
Stack we use for this
- Figma
- Laravel
- Node.js
- NestJS
- Python
- React
- Next.js
- TypeScript
- React Native
- Flutter
- PostgreSQL
- MySQL
- MongoDB
- Stripe
- Firebase
- AWS
- Vercel
- Docker
- PostHog
- Google Analytics
§ 04FAQ