How we work
AI writes it. A human owns it.
This page explains exactly what that means, how the work is delivered, what happens after launch, and how we handle security. No part of it is a secret.
The method
AI-led engineering, with an owner.
Nearly all of the code in our products is written by AI coding agents. The direction, the judgement and the accountability belong to a human product owner who runs businesses on the result.
In practice: the owner describes what the software has to do, in the words of the person who will use it. Agents plan the change, write the code, write the tests, review each other's work against a written set of conventions, and deploy. The owner reads every change, uses the feature the next morning, and sends back what is wrong.
This is faster and cheaper than a team of engineers, and it only works because of three things we hold to.
Written conventions
Every production bug we have ever had became a rule in a conventions document the agents read before writing code. Scoping, SQL, security, UI patterns, throttle safeguards. The list only grows.
A real user on the team
The owner does not approve from a screenshot. The feature is used in a live business, with real money and real customers, before it is called done.
Small, daily, reversible changes
Dozens of deploys a day, each small enough to read and roll back. Over 11,000 commits across our products so far.
Delivery
From first call to launch.
First conversation
Free. You tell us what you are trying to do and we tell you honestly whether we are the right people for it. Usually 30 minutes.
Discovery week
Paid. We work with the people who will use the software, read what you have today, and write a scope with a price. You keep the document either way.
Build
You get a staging site on day one and see it change every day. Weekly written updates. Scope changes are written down and priced, never absorbed silently.
Launch and run
Cut over without downtime, with a rollback ready. Then monitoring, support and improvements under whichever engagement model you chose.
Operations
We run what we build.
Most software fails after launch, slowly, when nobody is watching. We treat operations as part of the product.
- Zero-downtime deploys. Web workers roll one at a time; the new one must report healthy before the old one retires.
- Monitoring that ships with the change. A new service, job or log file is not done until our Watchdog covers it: process, heartbeat, log path, rotation.
- Backups and certificates handled automatically and checked, not assumed.
- Throttle safeguards on every external API: rate limiting, backoff, circuit breakers, terminal states for retries. Learned the hard way.
- A named human who answers when something breaks.
Security and data
Habits, not a checklist.
Our flagship holds data governed by franchise agreements. One of our products holds medical bills. These are the practices that came out of that.
Tenant isolation at the query
Every read and write of customer data carries the account's identifier. Cross-tenant combination is forbidden by rule and checked in review.
Sensitive data encrypted at rest
Health and financial documents are encrypted in the database and in object storage; files are private with short-lived signed links.
Strict browser policies
Content security policy, no inline scripts where it matters, HTML stripped from user input, sessions invalidated on password change.
Least privilege for integrations
Dedicated API users per tenant, scoped tokens, secrets outside the repository, writes to external systems claimed atomically so nothing posts twice.
AI with a gate
Personal data does not go into a language-model prompt unless the tenant has turned that on. We aggregate before the prompt, not after.
Deletion that works
Per-account and per-individual deletion with a dated record, because a right to erasure that cannot be verified is not one.
Engagement model
Build, Build and run, or Partner.
We publish the model rather than a price list, because the price comes out of discovery. Every engagement starts with a paid discovery week that ends in a written scope.
| Build | Build and run | Partner | |
|---|---|---|---|
| Commercial basis | Fixed scope, fixed price | Monthly retainer | Revenue share |
| Best for | A defined product or feature set you will host yourself | A product you want to keep improving without hiring a team | A product we want to co-own, after discovery |
| Discovery week | Included | Included | Included |
| Hosting, monitoring, deploys | Handover | Included | Included |
| Support | 30 days of fixes | Ongoing, named owner | Ongoing, named owner |
| Improvements | Priced per change | Monthly budget | Product roadmap shared |
| Code ownership | Yours | Yours | Agreed in the partnership |
Have something that needs building, or running?
Tell us what you are trying to do. We reply within one business day, and the first conversation is free.