Six weeks after launch, an agency forwards you an email from their client: “How do I add a fourth team member?” The answer takes four messages, a screen recording, and eventually a developer logging in to do it manually, because the team section was built as a single hand-coded block.
That cost was not created by the support request. It was created during the build, by someone choosing the fastest way to make three cards appear on screen. The support tail of a website is designed, not discovered.
The support tail is a design decision
Every site hands its owner a set of things they can change and a set of things they must ask about. Where that line sits is decided by whoever models the content. A site can look identical in two builds and differ completely in how much of your team’s time it consumes over the following year.
For an agency reselling the work, this is a margin question. Care plans are priced on expected effort. If the build pushes ordinary edits back to you, the plan loses money quietly for as long as the client stays.
Anything the client will plausibly change more than twice a year should be a field, not markup.
Fields, not free-form
The temptation is to give clients a rich text editor and let them do anything. It feels generous and it is the fastest thing to build. It also guarantees that within a year the site looks nothing like the design that was approved, because someone pasted styled text from a Word document into a hero.
The better model constrains. A team member is a repeatable item with a name, role, photo and bio, in that order, with an image ratio enforced on upload. The client cannot break the layout because the layout is not something they are editing. They are editing content, and the template decides how it looks.
Three rules we follow
Anything that appears more than once becomes a repeatable field group, even if the design shows only three of them.
Any image the client will replace gets a defined crop and an automatic fallback, so a bad upload degrades instead of breaking.
Any section the client might want to hide gets a toggle, rather than requiring a developer to comment it out.
None of these take long during the build. All of them are expensive to retrofit, because retrofitting means migrating content that is already live.
What to hand over
Not a manual. A short screen recording, five to eight minutes, showing the three or four things this specific client will actually do: add a post, change the hero, swap a team member, update the contact details. Recorded with no branding, so an agency can forward it as their own.
Alongside it, one page of written notes covering logins, where the site is hosted, and what to do if something looks wrong. Two pages get read. Thirty pages get filed and the questions come anyway.