Software built around your process, not the other way round.
Web applications, internal tools, integration layers, workflow automation, mobile apps, AI agents — and migrations off systems that stopped paying for themselves.
start a project→Who this is for
You have a process that works and software that doesn’t fit it.
A spreadsheet doing a job it was never designed for. Three systems that don’t talk to each other, joined by somebody’s morning of copy-paste. A platform bought in 2016 that now costs more in workarounds than it ever saved.
Or you have work that a person is doing only because nobody has automated it. Four hours a week retyping order details from an inbox into a spreadsheet. Invoices read by eye and entered by hand. Enquiries that sit unsorted until someone gets to them. Reports assembled every Monday from the same six places.
Off-the-shelf software is cheaper than custom right up until your business has to reshape itself around it.
What you get
- Technical discovery and an architecture proposal before anything is built — including an honest answer if the right move is to buy something rather than build it
- A deployed system, monitored, with the deployment pipeline set up and documented
- Reviewable increments — working software at intervals, not a reveal at the end
- A mobile app where the work happens away from a desk — built, submitted and released by us, not handed to you as a zip file
- Your code, in your repository, written so that another developer could pick it up without calling us
Automation and AI, specifically
Automation is the boring, reliable half: the manual steps between two systems, done by software on a schedule or a trigger. Most of the hours a business wants back are here, and most of it needs no AI at all.
An AI agent is for the part that used to need judgment — reading an unstructured email and working out what it is, extracting fields from a document that never has the same layout twice, drafting the first version of a reply, deciding where something should be routed.
We build both, and we scope them the same way: what happens today, what it costs in hours, and what it costs when it goes wrong. Where being wrong is expensive, a person stays in the loop and the agent prepares the work rather than finishing it.
The honest part: most problems that arrive described as "we need AI" are better solved by a deterministic script that costs less, never surprises you, and can be explained to an auditor. We will say so, and quote it that way.
No branding, no photography, no campaigns.
Platform is the system and nothing else. If you also need the brand and the launch around it, you’re looking at Launch — say so early, because it changes the shape of the work.
Months, not weeks. Scoped after discovery, not from a form.
Discovery is a paid piece of work in its own right. You finish it holding an architecture proposal and an estimate that belong to you — and no obligation to build any of it with us.
Questions
six answers
01Do we own the code?
+
Do we own the code?
+Yes. All of it, in your repository, from the first commit. No licence, no lock-in, nothing to keep paying for the right to use what you paid to have built.
02Can you take over something already built?
+
Can you take over something already built?
+Often. It starts with a paid technical audit — the codebase, the dependencies, the deployment, the risks — and a written answer on whether it should be continued, refactored or replaced. Sometimes that answer is "replaced," and sometimes it’s "this is fine, spend your money elsewhere."
03We already have a developer.
+
We already have a developer.
+Then you may need review, architecture, or a second pair of hands rather than a build. Those are real engagements and we’ll scope them as such.
04Should we just buy something off the shelf?
+
Should we just buy something off the shelf?
+Frequently, yes, and we’ll say so. Custom software earns its cost when your process is the thing that makes you money and no product fits it. If you’re doing something thousands of businesses also do, buy the product — you’ll be live in a week for a fraction of the money.
05How do we know you can build it?
+
How do we know you can build it?
+You don’t, and no portfolio page would settle it either — anyone can show screenshots of work they project-managed. So the first step is small and separable: buy the discovery. You get the architecture, the risks and the estimate as a document you own, and you can take it to any developer, including one who isn’t us. If we’re not good, that’s where you’ll find out, and it will have cost you a discovery rather than a build.
06Can this be a mobile app?
+
Can this be a mobile app?
+Yes — where the work genuinely happens away from a desk: a technician on site, a driver, a warehouse floor. We build it, submit it and release it, including the store accounts and the review cycle. If the app is the thing you sell rather than the thing your staff use, that is Product instead.
07What happens after launch?
+
What happens after launch?
+A maintenance plan — security updates, dependency upgrades, monitoring, backups, and a defined response time. Agreed as part of the proposal.
Tell us what you’re trying to do.
start a project→