What a website actually is
A website isn't a poster you swap out when the offer changes. It's a living system: templates, stylesheets, databases, plugins, third-party integrations, all depending on each other in ways that aren't obvious from the outside. It was built in a particular order, by particular people, making particular decisions.
Change one piece and you're pulling a thread - that's not a complaint, in case you were wondering. It's just the nature of how websites work.
The update that isn't just an update
Say you want to change your services page - it's a reasonable enough thing to be done, and it might seem simple on its surface.
But your services page might share a template with six other pages. The new content is longer than the old content, and as a result, the layout breaks.
Or the layout relies on a particular plugin to do something funky - the plugin hasn't been touched in eighteen months and is flagging a compatibility warning with the current version of WordPress.
Or, whilst someone's in there getting ready to make the changes, they notice the site is running on PHP 7.4, which the host is about to stop providing.
None of this was visible from the outside. From the outside it was just a simple change to a services page. But from the inside, it's not an unusual scenario. If anything, it's a pretty typical Tuesday.
The cost of not understanding this
Businesses sometimes hand small updates to someone cheap and fast, which is understandable. Time is short, budgets are tight, and it really does sound like a simple job.
But someone who doesn't know the site well enough tends to make the change, check that the one thing they changed looks right, and move on. The thing that broke somewhere else gets discovered later, by someone else, at a less convenient moment. It might be a contact form that stops working, a page that renders oddly on mobile or a step at the checkout that throws an error. Small things that erode trust with customers before anyone on the inside has noticed.
Why familiarity is worth paying for
There's a reason a mechanic who's worked on your car for years is faster and more reliable than one encountering it for the first time. They know its quirks, they know what was done last time and why, and they know where not to poke around.
Websites are the same. An agency or developer who built your site and has maintained it since can make changes confidently, quickly, and with a clear picture of the consequences, whereas someone briefed cold has to reverse-engineer all of that first. Sometimes they do it well, but oftentimes they don't have time to.
What this means practically
It means that budgeting for website work should account for the full job, not just the visible bit. It means timelines that look generous often aren't. And it means the question isn't really "can you just update the website" but "can you update the website properly, without breaking anything, and make sure it still works the way it should afterwards."
The answer to that question is yes. It just takes a bit longer than "just."
How we can help
Status 218 builds websites. And we then look after them long-term.
When something needs changing, we already know where everything lives and what everything does. No reverse-engineering, no surprises. If you've let someone else "just" do a quick update on your site and it's left bits not working, or left you with a large bill you weren't expecting, feel free to get in touch, with no obligation, to see how we can help with your on-going support.