You have a product idea. We build the first real version.
Most of what we do is bringing an existing business into one system. This is the other half: when there's no operation to untangle yet — just an idea that needs to become something real people can use.
Which one are you?
You already have a business running
Real operations, staff, customers and tools — spread across a CRM, spreadsheets, a booking tool and email. The work is bringing them together into one system built around how you already run.
One app for your whole businessYou have an idea for a new product
Nothing to consolidate yet. The work is deciding what the first version actually needs to include, building it properly, and getting it in front of real users before the budget is gone.
Book a scoping callWhat a first version means here
Not a clickable mockup, and not a twelve-month roadmap either. A working product with real accounts, real data and the parts that genuinely matter — deployed where people can use it.
The point of a first version is to learn something true about whether the idea works. That means cutting scope hard, and building the remainder properly rather than building everything badly.
How it runs
Scope
A call to work out what the product has to do to be worth putting in front of anyone — and what can wait. You get an honest view of what's realistic, including when the answer is "that's bigger than you think".
Build
Built in stages with real progress weekly. You see it working as it comes together rather than waiting for one reveal at the end.
Launch
Deployed and live, with accounts, permissions and payments working properly — so that if it does find traction, it can be extended rather than rebuilt.
Built to be extended, not thrown away
Plenty of first versions are built to be disposable, then quietly become the thing the business runs on. We build on foundations that hold up: a real database, proper accounts and permissions, and deployment that scales — the same engineering behind every business system we build.
Ownership, hosting, access and ongoing support are agreed clearly before we start, so you know where you stand from the beginning.
Products we've built
A gamified workout app that secured funding after launch, a personal finance and net worth planner, and a GAMSAT prep platform with separate student and tutor dashboards — each one a first version that shipped and got used.
Common questions
What is an MVP in software development?
A minimum viable product is the smallest version of a product that real users can genuinely use, rather than a clickable prototype. The point is to learn what version two should be by putting something real in front of people, which means the parts it does have need to actually work: accounts, payments if you are charging, and a database designed so version two is not a rebuild.
How much does an MVP cost to build?
Scope drives it more than anything else. The most common cause of an expensive MVP is building too much for version one — most of the value in the work is deciding what to leave out, and being honest that some of those cuts will hurt.
Who owns the code and the accounts?
You do. The repository is in your organisation’s name, hosting and third-party accounts are registered to your business, and the handover includes documentation another developer can pick up without calling us.
Tell us what you're trying to build.
A 30-minute call to pressure-test the idea and work out what a first version actually needs.