Introduction
The site launched well and everyone was pleased. Eighteen months later the pages have drifted apart, three of them contradict each other, and every small correction goes back to the agency with a quote attached. Nothing went wrong, exactly. A set of decisions was simply never made, and the cost of not making them arrives slowly enough that nobody connects it to the build. This piece names those decisions, when they have to be taken, and what to ask for so you are not funding a second site far too early.
Key Takeaways
- Decide The System, Not The Pages: Agree reusable styles and components before the first page.
- One Change, Every Page: Variables and components mean a brand tweak is one edit.
- Name Things Plainly: Clear naming is what lets someone else maintain the build.
- Redirect Imports Overwrite Everything: Export your current redirects before uploading any new file.
- Give Retirement An Owner: Someone must review the site quarterly and remove what is stale.
- Accessibility Is Ongoing: A UK site has to stay accessible, not launch accessible.
Why Does a Site That Launched Well Get Harder to Live With?
Because launch quality and maintainability are different things, and only one of them is visible on launch day. A site is judged at handover on how it looks. It is judged for the next two years on how easily it changes. Nothing in the launch review tests the second one, so it is usually nobody’s job.
Six signs your site is drifting, all visible without any technical knowledge.
- Two pages of the same type no longer look like each other.
- A brand tweak means a list of pages rather than a single change.
- Links inside the site lead to pages that no longer exist.
- Nobody can tell you how many pages the site currently has.
- Old campaign pages are still live because deleting them feels risky.
- Every correction, however small, becomes an email to your supplier.
Count how many are true. Three or more and the drift has already started, and the cost is not the corrections you pay for, it is the improvements nobody bothers to propose any more.
A concrete example makes the difference obvious. A company decides to change its brand blue. In a systemised build that is one value updated once. In a bespoke build it is somebody opening forty pages and hoping they found them all.
Which Decisions Made Before Launch Decide Your Maintenance Cost?
Six, and every one of them is cheap at brief stage and expensive afterwards. They are also invisible in a pitch, which is why almost nobody asks about them.
Webflow’s design system documentation explains the mechanism plainly: variables store reusable values such as colour and spacing, and if you change the variable once, every instance updates automatically, while components are reusable blocks that stay in sync across the site. In business terms, that is the difference between rebranding in an afternoon and rebranding across forty pages by hand, and it is decided by how the build was set up rather than by who does the work later.
- A design system agreed before pages are built, not extracted from them afterwards.
- Components for anything that appears more than twice.
- Naming a non-technical person can read without a glossary.
- A content model matching the page types you will actually publish.
- Roles agreed so the people who spot problems can fix them.
- A named owner for the site inside your company, not only inside the agency.
Get these right and maintenance is a small standing task. Get them wrong and you are funding a rebuild eighteen months early, which is the most common way UK companies pay for the same website twice. Webflow web design UK buyers rarely raise any of this at pitch stage, which is exactly why raising it tells you so much about who you are talking to.
Two Mistakes That Cost You Later
One of these is a decision you make, the other is one you allow.
- Buying a site rather than a system. A quote for pages produces pages; a quote that includes the design system, naming and handover produces something your team can run.
- Letting the site grow without anyone owning what comes off it. Pages accumulate, nobody deletes, and within a year the site says three different things about the same service.
What Happens to the Pages You Stop Using?
They keep earning traffic and then quietly break it. Retiring a page is a decision with a technical consequence, and it is the part of maintenance that most teams discover only after something has gone wrong.
The mechanism to know about is bulk redirect management, because it carries a trap. Webflow’s documentation on importing redirects explains that you can upload a spreadsheet of old and new paths for a migration, and warns that a new import overwrites all existing redirects, removing any already on the site. The practical consequence for you is simple: whoever manages redirects must export the current list before uploading anything, or a routine tidy-up can silently break every link people have to your old pages.
Three habits that keep this under control:
- Keep the redirect list as a file your company holds, not only inside the platform.
- Decide what happens to a page before you unpublish it, not afterwards.
- Review the site once a quarter and retire what no longer earns its place.
Accessibility belongs in the same routine. The Equality Act 2010 makes reasonable adjustments an ongoing duty for UK businesses rather than a launch-day checkbox, so contrast, focus states and keyboard access need rechecking whenever templates change. Left to drift, that becomes a compliance problem you discover through a complaint rather than a review.
What Should You Ask a Webflow Web Design UK Team Before You Sign?
Ask about the two years after launch, because that is what you are actually buying. Every studio can describe the build. Far fewer will tell you unprompted what your team will and will not be able to do afterwards.
- What is included in the design system, and will we own it?
- Which changes can my team make without you, and which will always need you?
- How will the naming be documented, so a future supplier can pick it up?
- Who holds the redirect list, and how is it backed up?
- Who reviews the site after launch, on what schedule, and at what cost?
A studio that has supported sites for years answers all five without hesitation, because they have lived with the consequences. One that treats them as unusual questions is planning to hand over and move on, which is fine if that is what you want, as long as you know that is what you are buying.
A pro tip for the shortlist: ask each studio to send you the naming convention from their last build. The ones who have thought about handover will have one ready; the ones who have not will explain why it is not needed.
Spoke’s UK Webflow work shows the kind of build these questions apply to.
Conclusion
Maintenance is not a phase that starts after launch. It is a set of decisions taken before it, and their cost arrives slowly enough that most teams never trace it back. Agree the design system, insist on plain naming, decide who can change what, protect the redirect list, and put someone’s name against reviewing the site each quarter. Webflow web design UK projects that do this stay useful for years; the ones that do not get replaced early and expensively. If you want a second opinion on a brief or an existing build, Spoke works as a Webflow web design agency for UK teams, across design, development and web UI/UX.
FAQs
Q. What actually makes a website hard to maintain?
Ans. Usually the absence of a system rather than the presence of complexity. When styles and blocks are reused, one change updates everywhere; when each page is bespoke, every change is manual. The second kind looks identical on launch day and costs steadily more from then on.
Q. Is it too late if our site was already built this way?
Ans. Often not. A design system can be introduced retrospectively, starting with the components that repeat most, and pages migrated onto it gradually. It is slower than doing it first, but far cheaper than a rebuild. Ask a supplier to price that path alongside a full rebuild.
Q. Who should own the redirect list?
Ans. Your company. Webflow lets you export existing redirects to a file, and a new import overwrites everything already there, so keeping your own backup outside the platform protects you from a single mistaken upload and from losing the list when a supplier changes.
