Who would I actually be dealing with?

A senior engineer, named at the start, who leads the project from the first conversation through to launch.

That is the whole answer, and it is worth spelling out because of what it rules out. The person working out your search strategy is the person writing the copy, building the pages, and replying when you ask about a decision a year later. The thinking and the doing stay with the same person.

Why it is built that way

Every time work moves between people, the reason for a decision has to be explained again, and some of it does not survive the retelling. By the third move nobody left in the conversation was in the first one.

Keeping direction and delivery together removes that. It is also why the answer to “why was it built this way” still exists in a year. You can ask, and get a reason rather than a guess about what somebody intended.

What that looks like in practice

You are not introduced to a senior person and then passed to somebody else. The lead on your project is the lead throughout.

There is no standing status call held to make up for nobody knowing where things are, because the person who knows is the person you are already talking to. When something needs deciding, it gets decided in the conversation rather than taken away and brought back.

Decisions, scope and changes are agreed in writing as they happen, so the project has a record rather than a memory.

Tool-assisted, human-led

We use modern automation and development tools to gather raw search data, scaffold components, and run automated performance audits in seconds. That eliminates administrative drag and repetitive setup.

What those tools never do is make decisions. Every line of strategy, copy and code is directed, reviewed, and signed off by the senior engineer leading your project. You work with a practitioner with professional judgment, not an agency relay team or an unmonitored script.

Capacity, and what we do about it

Senior-led work sets a limit on how much can run at once, and we would rather say so than take a booking we cannot serve properly.

We take on a small number of projects at a time. When we are full, we say we are full and give you a realistic date, rather than accepting the work and quietly queueing it. If your deadline is fixed, say so at the start and you will get a straight answer about whether it is achievable.

What you own, whatever happens

The site is yours on settlement: the code, the copy and the design. It is built on open standards with no proprietary platform underneath it, so any competent developer can pick it up and carry on.

That matters more than any promise about continuity. It means your business does not depend on the relationship lasting.