How long does it take?

A first working version is usually live within weeks, because the scope is settled in days and the price is fixed before anything is built. It does the one job that hurts most first, then grows from what people actually do with it. That is how a build stays on budget instead of becoming the six-month project nobody wanted.

Yes, outright. The repository, the hosting, the domain and every account are opened in your name from day one, and you can hand the whole thing to any developer you like. No licence back to us, no runtime only we can host.

Can you build on what we already have?

Yes, and it is usually the better route. A portal over the data your accounting system already holds, or an interface onto a database someone built years ago, beats replacing systems that work. We connect to what you run and build the layer that is missing.

Who looks after it once it is live?

We do, if you want us to: monitoring, maintenance and the next round of improvements are part of the engagement. If you would rather run it yourselves, it is built in mainstream technology with the reasoning written down, so a competent developer picks it up in a week.

What do you need from us?

The brief, the brand and the access: what the tool has to do, how it should look, and the systems it needs to reach. Everything after that is us.

Bespoke software development: internal tools, portals and apps

The internal tool, client portal or app that nothing off the shelf does the way you need. Scoped at a fixed price, live in weeks, and yours outright. You bring the brief and the brand. Everything after that is us.

What we build

Six kinds of build, each one live in weeks and running in your own accounts. We start with the one that hurts most.

Internal toolsThe spreadsheet three people edit at once, replaced by a screen a stray keystroke cannot break.
Client portalsCustomers check their own status, documents and invoices instead of ringing you.
Quoting and configurationYour pricing rules, out of one person's head and into a tool that produces a correct quote every time.
Dashboards and reportingOne screen over every system you run, refreshed on its own, readable on a phone.
Integrations and APIsSystems that only talk through a spreadsheet, joined properly so data moves without a person copying it.
Web and mobile appsThe product your customers use, or the app your field team opens on site, built and shipped.

How a build runs

ScopeWhat it does, in writing, with a fixed price. Days, not weeks.
BuildThe first working version does the one job that hurts most.
LaunchLive in weeks, in your accounts, under your name.
RunMonitored, maintained and improved from what people actually do with it.
Hand overThe repository is yours from day one. Any competent developer can take it on.

A fixed price in writing before anything starts.

The build is a fixed price quoted first, and the repository, the hosting and every account are in your name from the first day. Nothing is licensed back to you and nothing switches off if we part ways.

Book twenty minutes →Send us the brief

What we build it with

Best in class for each job and nothing exotic. Claude and Codex do the heavy lifting on the code, on the stack the rest of the industry already runs.

Claude
Codex
GitHub
Vercel
Supabase
Stripe
PostHog
Twilio
n8n
MCP
Figma
Slack

Every account is opened in your name, so the code, the data and the bills are yours from the first commit.

Weighing a build against a subscription? Run the numbers with the free tool →

The day-to-day, all of it automated

Fourteen jobs a specialist does by hand. The run does every one, on a schedule, inside the tools you already use. You see the results, not the work.

Custom portal, illustrated with example figures: Custom portal: internal job management portal showing job table, engineer assignments and checklist drawer. — Custom portal: internal job management portal showing job table, engineer assignments and checklist drawer.

Software screens updated using staff feedback
Database queries tuned for fast responses
User permissions checked to safeguard internal data
Reporting dashboards updated with live business numbers
Daily tests run to catch system errors
Client portal checked for smooth document sharing
Data backups checked to prevent record loss
System connections monitored to prevent downtime
Security updates applied the day they land
Workflows adjusted when business rules change
Screen layouts tested on phones and tablets
Audit logs checked to track key actions
System logs checked daily to fix glitches
New software features tested before release

GitHub, illustrated with example figures: GitHub: repository overview page displaying source files, commit history, README document and passing check badge. — GitHub: repository overview page displaying source files, commit history, README document and passing check badge.

Vercel, illustrated with example figures: Vercel: project deployment overview showing active production status and attached custom domain name. — Vercel: project deployment overview showing active production status and attached custom domain name.

Illustrations of the tools in use, drawn for this page for an example business, Marlow & Finch. Every figure in them is an example, not a client's data, and any person in them is generated. Tap a picture to open it full size.

GitHubThe code, owned by you
VercelLive in your account
SupabaseYour data, in your database
ClaudeBuilt and maintained with it
PostmanEvery connection tested

The night shift

Nobody in the building. This is the job doing itself at eleven at night, and what you see in the morning.

The tool on one screen, the code that makes it on the other, the sketch that started it on the desk.

A phone floating over a deep green gradient showing a booking app: a Book a slot header, a highlighted Tuesday 10:30 row, a Confirmed pill. — What a client's app looks like when it ships: the screen, not the slide deck.

Questions we get asked about this

How long does it take?: A first working version is usually live within weeks, because the scope is settled in days and the price is fixed before anything is built. It does the one job that hurts most first, then grows from what people actually do with it. That is how a build stays on budget instead of becoming the six-month project nobody wanted.
Do we own it?: Yes, outright. The repository, the hosting, the domain and every account are opened in your name from day one, and you can hand the whole thing to any developer you like. No licence back to us, no runtime only we can host.
Can you build on what we already have?: Yes, and it is usually the better route. A portal over the data your accounting system already holds, or an interface onto a database someone built years ago, beats replacing systems that work. We connect to what you run and build the layer that is missing.
Who looks after it once it is live?: We do, if you want us to: monitoring, maintenance and the next round of improvements are part of the engagement. If you would rather run it yourselves, it is built in mainstream technology with the reasoning written down, so a competent developer picks it up in a week.
What do you need from us?: The brief, the brand and the access: what the tool has to do, how it should look, and the systems it needs to reach. Everything after that is us.

Got a question the list did not answer? Ask it on a call, or send us the brief and we will come back with a fixed price.

Book twenty minutes →Send us the brief