Almost every client, when ordering a website, says the same sentence: "we need to be able to edit the content ourselves." We hear it every week. Then the site launches, and the content doesn't change for a year. Sometimes two.
That's not a complaint. That's how it should be: a business has better things to do, and the website isn't its main job. The problem is something else. That sentence gets paid for every single time, because "edit our own content" means a content management system (CMS), an editor, training, and then monthly maintenance. For a tool nobody ever opens.
What agencies themselves say about it
We looked for anyone admitting this in public. They do.
One agency used to record a video walkthrough for every client, showing how to edit pages. Professional, narrated, step by step. A year later they'd still get the call: "how do I log in again?" Their conclusion sounds blunt, but it's right: "Just hard code it. If they ever actually start using it, then you can set up a new contract."
Another studio, working with WordPress, admitted on its own blog: "we make content changes regularly only for a few clients." And in the same post they explained what "website maintenance" actually means now: the WordPress core gets updated 2 to 3 times a year, plugins and themes more often than that. Read that again. The monthly fee isn't paying for content. It's paying for a system that was sold so you could change content nobody changes.
And the story we like best. A developer built a client a site with an editor, exactly as requested. The client, handed a system they'd just paid for, replied: "We don't want to make the change, that's what we hired you for." The developer's conclusion, years later: with modern tools, fixing the code himself is faster than clicking through the editor nine times out of ten. The editor was slowing down the one person who ever actually touched the site.
Why everyone still asks for an editor
Not because they plan to write every week. Because they're afraid of dependency. "If I don't have an editor, I'll have to ask you every single time." That's a rational fear, and it's justified if the agency bills for every comma or answers two weeks later.
But the fix for that fear isn't an editor. The fix is a person who answers the same day, and a clear price for small changes. Or, and this is new, no longer a person at all.
What to do instead
The model "client writes an email, the developer fixes the HTML and uploads it" isn't some embarrassing relic. It's a normal, named architecture, recommended when changes happen less than once a month and are small. That model works as long as someone answers. With us, someone does.
Now the same model, minus us. When a site is plain HTML rather than a system, an AI can change it. You send a link to the page, write "change the opening hours to 9 to 6 and add the new phone number," and a minute later the site is updated. No login, no editor, no training. One American maintains a 41-page site for a local services company exactly this way: the AI pushes the change, the site rebuilds, and the owner "never touches a terminal again."
Yes, this has a limit. If the person editing isn't you but a colleague who gets nervous at the word "link," a visual editor with buttons is the better fit. We cover that boundary separately. But for a one-person business, a freelancer, a café, or a law office with a single website, that limit is still far off.
One question before you order
Before paying for an editor, answer honestly: how many times in the last twelve months did you actually change your current website. Not "wanted to change." Changed.
If the answer is zero, one, or two, you don't need an editor. You need a simple site and a person (or an AI) who'll make those two changes in a day. If the answer is twenty, then we're talking about a content system, and we'll point you to webflow.lt, where the same team builds sites like that.
Most of the time, that number is the decision.