Your business has outgrown the systems holding it together
The site your enquiries come through, the servers under it, and the data moving between them. Built here, or taken on as it stands, then run here from that point on.
Twenty-five minutes, and nothing to prepare. The call settles whether the paid audit is worth doing, and I do not diagnose anything on it.
The people who built it were never asked to run it afterwards
The site falls over on the Monday of a campaign and you hear about it from a customer rather than from a monitor. Somebody in the office retypes every enquiry by hand, because the two systems were never connected. The hosting comes off a card each month and nobody could name the provider.
Every piece was bought separately, and nothing anybody sold you covers the joins between them. Closing that gap does not have to begin with a rebuild.
Three pieces of Ampy's platform, all still in service
Ampy started as one town site in April 2025. It is now a multi-site electrical services, battery storage and EV charging business, running on dedicated infrastructure with structured content and automated workflows behind it. I built the system, and I am still the person operating it.
Zero-downtime platform migration
The live multi-site network moved onto dedicated infrastructure with no downtime, and the origin is now closed to everything except Cloudflare.
Still getting faster after launch
The same person who built it kept tuning it after launch, rather than handing it over. Desktop Lighthouse now runs 98 to 99, measured by Cloudflare Observatory from three European regions in August 2026.
31 services migrated, zero failures
The automation platform and the content pipeline moved to self-hosted infrastructure, with the full workflow history and every credential intact.
What happens between today and somebody being answerable for it
Four steps, and nothing obliges you to stay past the one you have paid for.
What usually arrives first is not a specification, it is a description of what keeps going wrong, and that is the right way round.
The call
A conversation before anything is written down or invoiced. It costs nothing and produces nothing on paper, which is exactly what makes the next step worth paying for.
25 minutesThe audit
€450, fixed, and it comes off a build or a retainer if one follows. I write down everything you are running, including the parts that are fine and should be left alone. That last list is usually the longest.
The work
The work happens against what the audit wrote down, not against a conversation somebody half remembers. Where it departs from the document, I change the document that week and tell you why.
Running it
From then on I watch it, update it and keep it in working order.
OngoingWhat happened after the build, on every one of these
Three things that hold on every engagement
These are conditions for the work being worth doing, not a service level agreement.
You do not find out from a customer
Anything I run is monitored, and I would rather be the one telling you a thing has broken.
Care is matched to the system
I do not charge a site with a contact form as though it were a platform with moving parts.
The price is agreed before the work
I quote build work at a fixed price, agreed in writing before anything starts.
What the work covers
Infrastructure underneath, the site sitting on top of it, the data moving through both, and the automations tying them together. They are held to one standard here, and there is one number to ring when any of them misbehaves. Not every system needs all four, and nothing here assumes yours does until somebody has looked.
Build, Optimize and Operate are the three shapes the work takes. The audit decides which of them applies, so you are not choosing between them today.
Questions this usually comes down to
There is probably a simpler way to own this
Tell me what you are running and what keeps going wrong with it, and the call ends with you knowing two things: whether this is a problem I can solve, and whether the audit is worth paying for.
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.