Technical review
Understand the application, hosting and current dependencies.
What are you working on?
A sentence is enough — we will work out the rest together.
Keep an existing website or system in working order. We review the setup and agree what should be maintained, how requests are handled and which improvements belong in the ongoing work.
The core of this engagement. We agree the exact scope in your project plan.
Understand the application, hosting and current dependencies.
Plan the updates and technical upkeep the setup needs.
Agree where requests go and how they are prioritized.
Plan content changes and product improvements within the agreed scope.
Every engagement runs through the same moves, and you always know which one we are on.
We read what exists, write down how it runs, and get the access sorted.
Updates, backups, certificates and monitoring, on a schedule rather than in a panic.
An agreed amount of change each month, so it does not quietly stand still.
Work this has already carried. All of it is live, and all of it is still ours to keep running.

Deadlines were the main thing for us. We needed a site almost at once and assumed two weeks could only buy something basic or templated. We got a complete project — design, brand, site, domain, hosting and every setting — and hardly had to deal with the technical side.

We came for a new website. At the first meeting the team asked not about button colours but what happens after a guest presses Book. Now a guest writes wherever they like, and for us it is one queue — we see the free room before we answer, and we never promise one suite to two people.
Nothing here was chosen because it is fashionable. Each one is on the list for something it does that the alternative does not.
Privacy-first analytics by default, because a cookie banner nobody agrees to produces data nobody can use. Anything deeper sits behind consent, and it is documented.
05 toolsSEO here is the technical and editorial work that makes a page findable. No link buying. We report on the queries that end in an enquiry, because impressions do not pay anyone.
04 toolsThe unglamorous half, and the reason nothing rots. Patches, certificates, backups and monitoring run on a schedule whether or not anything is in flight that month.
04 toolsUsing something we have not listed? Say so on the call — half of what we know arrived because a client was already on it.
What we learn is shipped into the product that month. You are not handed a slide deck and an invoice for it.
Around half of all tests lose. You hear about those in the same detail as the wins, in the same monthly read.
Your analytics, domains and accounts stay in your name. Monthly, with one month's notice, indefinitely.
Still deciding? Half an hour on a call is usually enough to know either way.
“Changes shipped predictably, and critical alerts arrived before a user noticed a problem. Months after launch, support still knows the history of every technical decision.”
The questions that arrive by email anyway. If yours is not here, ask it on the call.
Yes. We start by reading what is there and telling you honestly what state it is in.
Hosting, updates, backups, certificates, monitoring, and an agreed amount of change each month.
The same working day for anything that is down. Everything else is scheduled.
Yes. You get the code, the content and the credentials, and nothing is locked to us.
Start with a 30-minute call. The scope, the fee and the dates go into a project plan before any work begins.
Tell us what you are building. If it is a fit you will have an offer — and if not, we’ll tell you upfront.