Ongoing care versus build and forget — choosing a web partner.

Most studios have the same pitch: discovery, design, build, launch, done. You get a project manager for 12 weeks and then an invoice. What happens in month 13 isn't their problem. For a lot of clients, this is fine — the site is solid, the CMS is simple, and the work is self-contained. For some clients, it's where the investment starts to deteriorate. The question is which category you're in.

What deteriorates on a website over time

Four things, specifically:

Performance

As dependencies update, as third-party scripts add weight, as the JavaScript ecosystem evolves, Lighthouse scores drift. A site that scored 95 on mobile at launch may score 78 eighteen months later — not because anything broke, but because the environment changed around it. This drift affects search ranking, user experience, and ad conversion rates if you're running paid traffic.

Content

Treatment pages go stale. Team members change. Pricing updates don't happen. A page that says “Dr Sarah” when Dr Sarah left six months ago isn't just inaccurate — it erodes trust for the patient who researched her before booking. Content maintenance is often overlooked because it doesn't feel like a technical problem. It is, in its effects, a business problem.

Security and dependencies

Next.js, headless CMS plugins, Shopify apps, and third-party integrations release updates on their own schedules. Unmaintained sites accumulate technical debt — outdated packages, deprecated APIs, unpatched vulnerabilities. Most of these don't cause immediate problems. Some do, unexpectedly, at the worst possible time.

Core Web Vitals

Google's algorithm incorporates Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift — and these thresholds have changed over time. A site that passed field data assessments at launch may not be passing them now if the target has moved or if third-party scripts have affected the scores.

What a retainer actually covers

A care retainer should include: monthly dependency updates and security checks; a quota of content updates so you're not writing a brief and waiting three weeks to change a phone number; quarterly performance reviews covering Lighthouse and Core Web Vitals with notes on any movement; and priority response for anything that breaks unexpectedly.

It should be priced based on what it actually takes to do these things properly. A “$99/month maintenance plan” from a studio that built your site is not a care retainer — it's a commitment to look at the site if something goes catastrophically wrong. A genuine retainer involves someone with their name on it spending real time each month.

Ask for a scope before you agree to anything. What's included, specifically? How many content updates per month? What's the response time SLA for a broken booking form on a Friday afternoon? What happens if something needs a developer to fix — is that included or quoted separately? These questions separate a real offering from a vague commitment.

Who actually needs a retainer

Clinics that update their services, practitioners, or pricing on any kind of regular basis. Ecommerce brands with active product catalogues where the site is the primary revenue channel. Any business running paid advertising to a landing page — because ad costs make a broken or degraded page very expensive, and the feedback loop between site performance and campaign ROI is tight.

Small static sites with no CMS and no external integrations can often go without. A five-page brochure site built on a stable framework, with no third-party booking widget, no active content updates, and no paid media spend, is less likely to need ongoing attention. It can still benefit from a quarterly check-in, but a formal retainer may not be justified.

Red flags when choosing a studio

Watch for: no post-launch period quoted at all in the project scope; no care offering or SLA mentioned; a studio that has never explained what happens if something breaks in month 6. These aren't edge cases — they're common, and they indicate a studio whose model ends at handover.

Ask the question before you sign: “If our booking form stops working on a Saturday morning, what happens?” The answer will tell you a great deal about whether this is a partner or a contractor. A partner has a process. A contractor has an email address.

The best web partner is one that thinks about your site's performance after the invoice is paid — because they understand that the site's job didn't end at launch. Our care tiers are structured around what sites actually need over time, not around what's easiest to package and sell. See our services page for how we structure ongoing work, or get in touch to talk through what makes sense for your site.