One engineer, and why that is the point rather than the limit
There is nobody between you and the work, for the plain reason that there is nobody else: no account manager relaying messages, no junior learning on your budget, and nobody different on it next quarter. More often than not the work ends up embedded, closer to a member of staff than a supplier waiting to be briefed. When something needs a specialist I do not keep on permanent call, I bring one in, and I stay answerable for the whole of it either way.
What the work actually looks like
I started in custom WordPress and ended up in the layer most studios either outsource or avoid: the hosting, the routing, the performance, the indexing, the uptime. Nobody notices any of it until it breaks, which is roughly why that is where most of the real failures live.
Two from the last month. A set of scheduled jobs on a client platform that had never once run, because WordPress fires its cron from page loads and the site was simply too quiet to trigger one. And a hero image in the newest and smallest format that was making phones slower than the older format it replaced, because decoding it cost more than downloading it saved. Neither produced an error message anywhere, and neither would have appeared in a redesign brief.
If it needs a name, it is a fractional engineering department.
What being one person commits me to
The question underneath all of that is what happens the week I am ill, or away, or nowhere near a desk. It is a fair question, and it takes for granted a system that needs daily attention from somebody. An ordinary week on one of these needs no intervention from anyone, by design rather than by luck. When something does need attention, I can usually see it and act on it from a phone.
One person doing the work only holds up if the client can carry on without that person. That is not a sentiment, it is three specific arrangements, and they are in place from the first week rather than the last.
"Carrying on without me should never need my cooperation. That is the test everything here is built to pass."
The server, the domain, the DNS and the repository sit in accounts you own before the work starts. Not at handover, at the start.
It describes how the thing actually works, including the parts that are ugly, so another engineer could pick it up cold.
There is no plan to grow into an agency, and no target that would make the first client matter less than the third.
Who this is for, and who it is not
Both of these lists are real, and the second is the reason some enquiries end in a no.
Three things that are still running
Two of these are client work and one is my own. Each is listed by the year it went live.
Questions this usually comes down to
Start with a conversation.
You would be hiring one engineer, not a company that has one.
Twenty-five minutes on Google Meet, and a straight answer either way.
- 01
You describe what you are running, in whatever words you use for it internally.
- 02
You get a straight answer on whether the audit is worth doing at all, including when it is not.