Your website, properly kept fresh

The Content Support Package: ticket-based design and content updates for your live site — briefed in plain English, designed and built by professionals, shipped through proper QA and staging. No CMS training. No plugin chase. No more “we’ll get to it next sprint.”

Book a 20-minute call See how it works

If this looks familiar…

Your website was supposed to be an asset. It’s started behaving like a liability.

You don’t need another CMS. You don’t need to hire another marketer to wrangle plugins. You need the change to actually happen, on brand, on time, without it landing on your desk every Friday afternoon.

  • Three weeks for a copy change

    A two-line tweak goes into a backlog, then a sprint, then a retainer review. By the time it ships, the campaign is over.

  • CMS training that nobody remembers

    You paid to onboard editors a year ago. Half have left. The other half can’t remember which field controls which page.

  • Plugin updates that break the homepage

    Security patches, theme updates, third-party widgets. Every month something silently breaks — and someone has to notice before a customer does.

  • Brand drift, page by page

    Each new editor makes a “sensible” choice. Six months later your site looks like five different companies in one tab.

  • Two agencies, three freelancers, no owner

    When something goes wrong, the first hour is spent working out who should fix it. The second hour is spent waiting for them to reply.

  • Surprise quotes for tiny changes

    “That’ll be a half-day SOW.” You stop asking. The site stops evolving. Your competitors do not.

If you nodded at three or more of those, you don’t have a content problem — you have an operating model problem. The good news: it’s a solved one.

Now imagine instead…

A Tuesday morning where your website just… gets better.

  • You drop a one-line ticket: “New testimonial on the homepage by Friday, here’s the quote and the headshot.” By Wednesday it’s on staging, designed properly. Friday it’s live.

  • Your seasonal banner refresh hits four pages, two layouts, and the email header — without anyone in your team logging into a CMS.

  • A new product page is briefed on Monday with a paragraph and three rough notes. By Thursday there’s a designed draft on staging waiting for your sign-off.

  • Someone joins your marketing team on a Monday and is “productive” on day one — because the workflow is “send a ticket”, not “sit through three days of CMS training.”

What if every change to your website passed through professional designers and developers — and that process was fast, predictable, and didn’t need anyone in your team to learn a thing?

That’s the Content Support Package. It’s the way modern teams keep their site alive.

Introducing

The Content Support Package

A monthly subscription that turns “we should update that” into “it’s done.” You brief in plain English. We handle design, build, QA, staging, and the production release. Your team stays focused on the business; your website keeps moving forward.

  • Brief in plain English

    Tell us what you want, why, and by when. No content models. No field mappings. No CMS jargon. A short ticket is enough — we’ll come back if anything is missing.

  • Designed and built by humans, accelerated by AI

    A real designer takes the brief, working inside your design system. A real developer builds it. AI takes the donkey work out of the middle so we can move at the speed your business actually needs.

  • Shipped through proper QA and staging

    Every change is tested and pushed to a staging URL with release notes. You can review, we can ship. No more “please don’t edit live.”

Built for the person whose name is on the domain

Delegate the website. Don’t abdicate it.

If you’re the founder, the MD, or the marketing lead with too many hats, this package is built for you. You stay in control of what happens. We take ownership of how it happens.

  • Delegation, with a clear seam

    You write a sentence or two of intent. We turn that into a designed, built, and tested change ready to review. The handoff is the ticket; the accountability stays with us until you sign off at staging.

  • Workflows and approvals, built in

    Triage on day one. Design with included revisions. Staging with release notes. An optional review window before production. Audit trail end-to-end. The governance you should have, without the governance theatre.

  • Zero training. Zero onboarding for new joiners.

    A new starter doesn’t need to learn your CMS, your design system, or your release process. They learn one thing: how to send a ticket. That’s their day-one productivity, not their day-thirty.

  • No key-person dependency

    You don’t depend on the one person who knows where the homepage hero lives. The site is operated by a team that documents what it does — so when people change, your website doesn’t go dark.

What’s in the box

Everything you need for ongoing change. Nothing you don’t.

Work is structured as tickets: a short description, acceptance criteria, your copy, your assets. We do the rest. Two rounds of design revision are included per ticket; further rounds use overage or a fresh ticket.

  • Copy and text changes — pages, metadata, translations (you supply the final text)
  • Imagery work — swap, crop, optimise, format for performance
  • Design assets — web banners, header images, simple infographics, social-ready exports
  • Layout adjustments within your existing design system
  • CMS / database-driven content updates — if you’ve got one, we drive it; if you don’t, we don’t miss it
  • Brand-consistent styling tweaks that don’t require a redesign
  • End-to-end release flow — our QA, staging deploy, optional review window, then production
  • A monthly allowance set in your schedule (Annex B), so you know what’s in scope before you commit

And, importantly

What you’re not signing up for

A lot of the value here is in what we don’t ask of you.

  • No CMS to learn, no admin UI to babysit, no “please don’t click that” areas
  • No plugin updates, theme upgrades, or weekly “why is the site broken” firefighting on the editorial side
  • No three-day onboarding for every new marketer or assistant
  • No surprise “that’s out of scope” quotes for tiny changes — the allowance is the contract
  • No chasing freelancers across three Slack workspaces and four invoices

For things that are bigger — net-new features, full rebrand, video production, applications not in your schedule — we handle those as a change request or new statement of work under the Master Services Agreement. So nothing falls between the cracks; it just goes in the right lane.

How a ticket flows

Brief on Monday. On staging by mid-week. Live by Friday.

Every ticket follows the same five-step path. You always know exactly where your change is.

  1. Triage

    We review your ticket within one working day. If it’s complete, we start. If anything’s missing, we tell you exactly what — the delivery clock starts when the ticket is complete.

  2. Design (if required)

    A designer takes the brief and produces a draft inside your design system. Two rounds of revision are included on every ticket where design is in scope.

  3. Build

    A developer implements the change against the acceptance criteria in your ticket. Tested, version-controlled, ready for review.

  4. Staging and QA

    We run our own checks, deploy to a staging URL, and send you a link with brief release notes. No surprises.

  5. Review (optional) and production

    Opt in to a review window (typically five working days) and approve or request corrections against the criteria. Or skip review and we ship straight to production. Production deploys respect any change windows or incident freezes from your Support Agreement.

Why this is even possible now

The reason your team had to learn a CMS doesn’t exist anymore.

CMS platforms were a rational answer to a 2008 problem: deployments were slow and risky, developers were scarce, and there were three channels to publish to. So we accepted the trade-off: a giant admin UI everyone has to learn, plus a plugin ecosystem to maintain forever.

Three things changed:

  • Deploys are safe. Git workflows, CI/CD, preview environments and feature flags now make shipping a small change safer than letting people poke at production via an admin UI.
  • Brand lives in design systems. Layout, components, typography — encoded once, applied everywhere. Updating a card now updates everywhere it’s used.
  • AI does the donkey work. A small, professional team can handle the volume of change a 2018 in-house team used to need. Faster, more consistent, and without the editor-training tax.

Net effect: a tight team plus modern tooling delivers more, better content than a CMS-plus-editors model — for less ongoing cost. That’s exactly what this package productises.

Want the long version? Read Ditch the CMS, it’s killing your business — the article that started this product.

Pace, not promises about uptime

Delivery targets you can plan around

Unless we agree a hard deadline in writing, every ticket has a target turnaround from the moment it’s complete:

  • High 3–5 working days — campaign-critical, time-boxed
  • Medium 5–10 working days — the everyday default
  • Low 10–15 working days — nice to have, not urgent

These are change-delivery targets, not uptime SLAs. Uptime, incident response, monitoring, and patching are governed by the Support and Maintenance Agreement when you have operational support in place — the two products work together, but they make different promises.

A sensible monthly

One predictable fee. A clear allowance. No surprises.

You pay a monthly content fee that includes a defined allowance of content services — tickets, hours, or points, set out in Annex B of your schedule. Overage is billed at the rate in your schedule; unused allowance does not roll over unless your annex says otherwise.

We size the allowance to your real-world rhythm in a 20-minute scoping call before you commit. There’s no public checkout for this product because the right answer for a SaaS launching weekly campaigns is not the right answer for a B2B services site shipping a release a month.

Three-month initial term, then monthly. Auto-renews until either side gives 30 days’ notice. You’re committing to try the workflow, not to a year you can’t exit.

Common questions

The things business owners actually ask us

We already have a WordPress / Webflow / Shopify site. Does that work?
Yes. We work with what you have today. Where your platform is the source of friction we’ll say so — but the package itself doesn’t require you to migrate anything.
Do my team still get to make their own quick edits?
Absolutely, where it makes sense. If your team has a flow that works for blog posts or product copy, we leave that alone and pick up everything else. The package isn’t about taking control away — it’s about making sure the changes you don’t want to do yourself actually happen.
How is this different from hiring a contractor?
A contractor is one person. This is a workflow with documented hand-offs, governance, design quality, and no key-person risk. When the contractor goes on holiday, your website goes on holiday too. With this, it doesn’t.
Is design genuinely included, or is everything “extra”?
Genuinely included. Two rounds of revision per ticket on any work that needs design, inside your existing design system. Beyond that, additional rounds use overage or a fresh ticket — we’ll always tell you in advance.
What about approvals and audit trail — my legal / compliance team will ask.
Every ticket has a status, an owner, a staged preview, optional review window, and an auditable production release. If you have specific approval gates (legal, regulatory, brand), we wire them into the workflow.
Do we have to use your support service too?
For the Content Support Package to make sense, yes — we deploy to your production environment, so we need to be the team operating it. That alignment is also what lets us make change-delivery targets stick. See the Support and Maintenance Agreement for what operational support covers.
What happens if we don’t use our allowance one month?
By default, allowance doesn’t roll over — it’s priced as standing capacity, not banked hours. If your business is genuinely lumpy (e.g. quarterly campaigns), tell us in scoping and we’ll structure the annex around that.

Built on real contracts

Sample agreements you can read before you talk to us

This isn’t a handshake retainer. The Content Support Package is a schedule under our Master Services Agreement, with the workflow, scope, IP, and allowance defined in writing. Read the samples below in advance — the executed version with your specific annexes is provided individually.

Stop chasing your own website. Start shipping it.

A 20-minute call is enough to size an allowance, see if we’re a fit, and get you a written proposal. No deck, no sales pitch — just whether this solves the problem you actually have.

Book a 20-minute call Send us a message instead

Questions first? Get in touch or read why we built this product.

Discovery call Our packages