A website should not depend on its developer

We built a website for a hospitality brand around five years ago. It is still live. It has grown as the business grew. New pages, new sections, new content — none of it done by us.

They are not a client any more. That is the point.

Lock-in is usually accidental

Very few agencies set out to trap a client. Dependency is normally a side effect of decisions that seemed reasonable at the time:

• Page layouts hard-coded rather than composed from content the client controls, so a new section means a developer.
• A CMS configured for the launch content, with no thought given to what the third year looks like.
• Documentation written as a handover formality, describing the system rather than the tasks someone actually needs to do.
• Training delivered once, to whoever happened to be available that week.

Each is defensible in isolation. Together they mean a phone call to the agency every time the business changes.

What we do differently

Build components, not pages. If the client can assemble a new page from parts that already exist, they do not need us to make one. This is more work up front and dramatically less work forever after.

Model the content, not the design. A "tenant profile" or a "case study" is a thing with fields. When the content model matches how the organisation actually thinks, editing feels obvious. When it matches the visual design instead, editors end up reverse-engineering a layout.

Make the accessible, correct path the easy one. Required alternative text. Sensible field limits. Preview that reflects reality. If the system permits a mess, there will eventually be a mess.

Treat handover as a deliverable. Documentation written for the tasks people do, training for more than one person, and every credential and access route transferred in writing.

The test

Here is the question worth asking any developer before you appoint them: what happens if we stop working with you?

If the honest answer involves difficulty, you are buying a dependency along with the website. The answer we want to be able to give is the one above — the client took full control, kept building, and did not need us.

We stay available when technical support is genuinely needed. That is different from being needed to change a paragraph.

If you are weighing up a build and want a straight answer about what it would take, get in touch.