A founder with an idea
You know the market and the problem. You need a first version good enough to charge for, built without wasting runway on features nobody asked for.
New projects
From idea to launched product, without the usual surprises
Whether it is a first product, an internal tool or a new line of business, we help you decide what to build — then build it in the open, in short cycles, with working software every two weeks.
Who it's for
Three common starting points
A business outgrowing its tools
Spreadsheets, email and an off-the-shelf package held together by one person's memory. You need a system that fits how you actually work.
A company adding a product
An established business launching a customer portal, an app or a digital service, without an in-house team to build it.
The path
How a new build runs
The most expensive mistakes in software are made before any code is written: building the wrong thing, or far too much of the right thing. So we spend a little time at the start making sure the plan is sound.
Discovery
Workshops with the people who will use it. We map the workflows, agree what the first release must do, and write down what it deliberately won't.
1–3 weeks · fixed priceDesign & prototype
Clickable designs of the key screens, tested with real users, plus a technical plan: architecture, hosting, integrations and risks.
2–4 weeksBuild
Two-week cycles, each ending in a demo of working software on a staging site you can use yourself. Priorities can change between cycles.
8–20 weeks, typicallyLaunch
Production infrastructure, monitoring, backups, security review, app-store submission where relevant — and a rehearsed release.
1–2 weeksHandover or support
Complete documentation and a clean handover to your team, or an ongoing support arrangement with ours.
Ongoing, optional
What you get
Deliverables that outlast the project
Code in your repository
From the first commit, the code lives in an account you own. No lock-in and no hostage situations — ever.
Documentation that works
Setup guide, architecture overview and runbook, tested by having someone follow them from scratch.
Tests and automated releases
An automated test suite and a deployment pipeline, so changes in year two are as safe as changes in month two.
A running statement
Every two weeks: what was done, what it cost, what is next, and how the budget looks against the plan.
Infrastructure you control
Hosting in your own cloud account, described in code, with backups that have actually been restored once.
A direct line
You talk to the engineers doing the work — not an account manager relaying messages.
Examples
What new builds look like
Customer portal for a field-services business
A self-service portal where customers book visits, approve quotes and pay invoices — replacing phone calls and emailed PDFs.
- React
- TypeScript
- Node.js
- PostgreSQL
Booking and scheduling platform
Online booking with real availability, deposits, reminders and calendar sync, built around one business's actual rules.
- Next.js
- TypeScript
- PostgreSQL
- Stripe
Internal operations tool replacing shared spreadsheets
One system of record for orders, stock and approvals, in place of a dozen spreadsheets only two people understand.
- Python
- Django
- PostgreSQL
- Docker
Questions
New-project questions
I only have an idea. Is that enough to start?
Yes. Discovery exists for exactly this. You will finish it with a written scope, designs for the key screens and a realistic budget — useful whether or not you build with us.
Can you give me a fixed price?
For discovery and for well-defined scopes, yes. For products that will evolve as you learn from users, a monthly budget with two-week checkpoints is usually cheaper and safer than a fixed price padded for uncertainty.
How small can a first version be?
Smaller than most people expect. The best first releases do one valuable thing well. We will push you to cut scope, because shipping sooner and learning is worth more than launching later with everything.
What happens after launch?
Your choice: we hand over to your team with full documentation, stay on for further development, or move to a lighter support arrangement.
Have something you want to build?
Tell us about it. You will get a straight answer on feasibility, rough cost and the sensible first step.