How we build.
We will work in whatever language and on whatever platform the job needs — that part is not precious. What does not change is how we decide, test and hand over, and it comes from running our own software in production rather than from a methodology deck.
Built for the conditions, not the demo
A demo runs on a fast laptop with a good connection. Your software will not. We build for the machine, the network and the hands it will actually meet — a mid-range Android, an unreliable connection, somebody in a hurry with a customer waiting.
Sometimes that means a connected, cloud-backed system, because that is what the job is. Sometimes it means a genuinely offline-capable architecture, where the local database is the source of truth and sync is allowed to fail — the harder build, and one we have run in production. We decide that per project. We do not have a favourite we sell to everyone.
The simplest thing that will hold
A marketing site does not need a server, a database or a CMS to patch. Built as static pages on a CDN it loads in under a second on a mid-range phone, there is no admin panel to compromise, and hosting costs nothing worth putting on an invoice.
When a project genuinely needs a database, an API and real accounts, we build that properly — and we have. What we will not do is reach for the complicated version by default, then bill you to maintain it.
Automated where it repeats
If a person has to do it every morning, it should be a scheduled job with a quality gate in front of it. We build pipelines that generate, check and publish on their own — and that hold anything failing a check for a human instead of shipping it.
The gate matters more than the automation. Anything that can publish unattended must be able to refuse to.
Built to be handed over
Source in your GitHub organisation. Deploys on your Cloudflare account. Third-party keys billed to you directly, at cost. Architecture documented well enough that another team could pick it up.
Nothing we build should need us in order to keep running. A studio that makes itself load-bearing has sold you a subscription, not a system.
What every project gets, whatever it costs.
- Every project ships with automated checks that run before anything deploys
- Reproducible builds — a release can be rebuilt from a tag, months later
- No secrets in the repository, ever, on any project
- Accessible by default: real contrast, keyboard paths, working focus states
- Mobile-first, because your customers are on a mid-range Android phone
- Written handover notes, not a call where we tell you how it works once
We build and run our own software products, not only other people’s. Everything on this page is how we treat them — the applications, the sites, the automated publishing, the payment and reminder plumbing. We were the ones on call for it first.
That is the whole difference between us and a studio that bills hours. We have had to live with our own decisions — which is also why we have no stack to push. The right answer changes with the project.
Want something built this way?
Tell us what you are building and what is in the way of it.