Home / Services / 05 · Micro Products
Small products, shipped whole.
Not every idea needs a six-month build and a product team. Internal tools, MVPs, SaaS utilities, dashboards — the value is in shipping something small that works, owned entirely by you, with an honest written list of what was deliberately left out.
What we usually find
A product idea that has lived in slide decks for a year.
An internal process held together by a heroic spreadsheet.
An agency quote for an MVP that reads like a full enterprise build.
A tool a contractor built that nobody can maintain or even deploy.
If two or more of these are familiar, this is the practice to start with.
What we build
MVP development
The smallest version of your product that a real user can pay for — built to validate the idea, not to impress a demo audience.
Internal tools
Replacing the spreadsheet-and-email workflows your team has outgrown with small web apps that do one job well.
SaaS utilities and APIs
Focused services — a calculator, a converter, an integration bridge — built to run cheaply and unattended.
Dashboards
Data from your existing systems in one place, live, without a business-intelligence platform migration.
Automation bots and extensions
Chrome extensions, chat bots and scheduled jobs that remove a specific, named piece of friction.
Tooling is chosen per engagement. This is what we reach for most often, not a fixed stack.
What you get
Deliverables, written into scope.
Every item here is an acceptance criterion, not an aspiration. If it is not delivered, the engagement is not complete.
- A working product deployed in your accounts, not a prototype in ours
- The complete source repository with CI, tests and deployment documented
- A written cut-list: what we left out of version one, and why
- Running costs estimated in writing before we build, measured after
- One hundred percent ownership — code, data, infrastructure and IP
A shipped version one beats another quarter of slide decks.
— Micro Products, in one line
What we will not do
- Build a 'quick MVP' with enterprise scope — we will show you the cut-list conversation instead.
- Keep any part of your product on infrastructure or licences that we control.
- Ship something we would not be able to hand over with a straight face.
Questions
What does 'micro' actually mean?
A scope one or two people can build in weeks, not months — typically one core workflow done properly, with authentication, deployment and documentation included. If your idea genuinely is not micro, we will say so before quoting rather than discovering it together at week nine.
What happens after launch?
You own everything, so the honest answer is: whatever you choose. Thirty days of defect support is included. After that we can quote for iterations, or your own developers can take it — the handover is designed so that both options are real.
Start with an audit of this area.
One week, fixed fee, credited against the build. You keep the written map and the ranked build list either way, with no obligation to continue.