How I work
I am not a day-rate contractor and not an agency. I take a long-term position inside a small number of businesses, build the software they operate on, and tie my own economics to how well it performs.
Engagement models
A long-term technical seat inside one business
I work as the technical side of the business — designing, building and running the software it depends on. Not a day-rate contractor and not an agency: one person accountable for the whole thing, from the database to the day it goes live.
Any business with real operational complexity and no technical lead of its own, that wants someone permanently on the hook rather than a project team that leaves.
I build it, then we grow it together
Where the software is the growth engine — a store, a membership, a booking system, a product launch — I build it as a marketing partner and take my return from the revenue it generates, not from the build invoice.
Founders and owners with a commercial idea and no technical partner, where the software is the revenue engine rather than a cost centre.
Priced per customer live, not per hour or per user
For work that repeats — onboarding a customer, launching another branded instance, wiring up another integration — the build is productised. A fixed price per unit delivered, plus ongoing economics where volume flows through what I built. Not seat licences: one price per live customer or instance.
Resellers, partners and platform businesses whose growth is measured in customers brought live rather than features shipped.
I host it, run it and keep it healthy
The system lives in your accounts, but I handle the infrastructure, monitoring, backups, updates and the small fixes that keep it moving. You get a working product without hiring an ops person or learning how to keep a server alive.
Businesses that need a live, reliable system but do not want to manage hosting, security patches, uptime or the day-to-day care themselves.
Capability areas
The business runs on spreadsheets, inboxes and a few tools that disagree with each other, and nobody can answer a straight question quickly.
One system your team logs into, covering the people, the work, the customers, the money and the reporting — with the right access per role and a record of every change. For example: a full recruitment, training and governance platform replacing years of manual process.
Code, database, migrations and hosting in your accounts.
Taking money is manual, inconsistent, or reliant on someone remembering to check that the right amount was charged.
Card payments, subscriptions and in-person terminals wired in properly, with card details never touching your systems and every amount confirmed on the server before it is taken. For example: a gateway that onboards new merchants with a hosted embed or a self-contained code pack.
The payment flow, the customer records and the reporting on top.
The website is slow, out of date, or disconnected from the system that holds the real numbers — and your reporting no longer tells you what is working.
A fast, well-built site or storefront kept in sync with your stock and systems, with consent-respecting tracking that still measures accurately when browsers block it. For example: a headless Shopify storefront with live product sync and server-side conversion reporting.
The site, the tracking setup and the data flowing through it.
You hold information about people — customers, patients, learners, staff — and your controls exist as a policy document rather than something the software enforces.
Access rules enforced in the database, personal data classified, hidden by default and encrypted where it matters, consent captured, and evidence you can produce on request. For example: safeguarding and clinical records with review gating and a one-click evidence pack.
The controls themselves — written into the system you keep.
Work that repeats every week is done by hand, and output is capped by how many hours your team can give it.
A pipeline that does the repetitive part automatically and reliably, with people reviewing the result rather than producing it. For example: course material taken from structured content through to narrated video, published at volume without a studio.
The source material, the pipeline and everything it produces.
Next step
No pitch deck, no discovery fee. If something off the shelf would genuinely serve you better, I will say so before either of us spends money.
Prefer to write it down? Send a full enquiry with what you are trying to build.
