09Care · Service

Support Packages.

A retained channel for bugs, small changes and engineering advice — with defined response windows.

Book a callSee pricing
Team collaborating at a desk over a product brief

01The problem

Launch day is not the end of the product.

Dependencies age. Browsers change. A small content request turns into a half-day archaeology dig because nobody remembers the repo. Ticket portals promise “support” and deliver silence.

Without a retained channel, every change becomes a mini procurement exercise — or an unpaid favour that burns goodwill.

02How it runs

How care works month to month.

  1. 01

    Onboard.

    Access, priorities, severity definitions and what sits inside vs outside the retainer.

  2. 02

    Triage.

    Every request scored against agreed severity, so urgent work jumps the queue and nice-to-haves stay visible.

  3. 03

    Respond.

    Bugs and requests handled against agreed windows — not a bottomless backlog with no owner.

  4. 04

    Maintain.

    Dependency updates, small features, and optional hosting, SSL and email under the same roof.

  5. 05

    Review.

    A light cadence to rebalance allowance, priorities and whether a larger sprint is needed.

03Our approach

Retained response with engineers who already know the stack.

Support packages give you a defined allowance for bugs, small changes and advice — with response windows you can plan around.

We prefer to support what we built, or inherit with a short audit. The point is continuity: the same scrutiny as a build, applied to keep the product healthy.

04What you get

A retained channel that answers.

  • 01

    Defined response windows

  • 02

    Bugfix and dependency updates

  • 03

    Small change allowance each month

  • 04

    Architecture and tooling advice

  • 05

    Optional hosting, SSL and email included

—Signals

The bar we hold on every engagement — velocity from the platforms, assurance from the engineers.

100%

Engineer-reviewed merges

99.9%

Hosting uptime target

24/7

Emergency cover on hosting

05Proof

Who it fits. What good looks like.

Teams who have shipped and need a partner on call — without hiring a full-time engineer for intermittent work.

Who this is for

  • 01Products we built or maintain
  • 02SMEs without standing DevOps
  • 03Marketing sites that still need changes
  • 04Bundles with hosting and email care
01

A known channel.

You know who to ping — and when to expect a reply.

02

Healthy software.

Patches and small improvements before they become incidents.

03

Honest scope.

Clear boundaries so “quick favour” does not become unpaid debt.

06Pricing

What this costs.

A retained channel with response windows in writing.

01

Care.

From £950

per month

Keep what you shipped healthy — updates, monitoring and small changes.

  • Next-working-day first response
  • Bugfix and dependency updates
  • Small change allowance each month
  • Monitoring and uptime checks
  • No out-of-hours surcharge, ever
Set up care
02Most chosen

Priority partner.

From £1,950

per month

Faster windows and a larger change allowance for business-critical products.

  • Same-business-day first response
  • Larger monthly change allowance
  • Architecture and tooling advice
  • Quarterly security and dependency review
  • Named engineer who knows your stack
Talk priority

Rolling monthly, cancel with 30 days’ notice. Support runs Monday to Friday, 9am–5pm. Out-of-hours work is charged at 1.5× on weekday evenings and 2× at weekends — never for clients on a care plan, whose work is covered whenever it happens. Excludes VAT.

Next step

Care is how velocity survives contact with reality. Pick a package and we stay.

Ask a questionBook a call

—Resources

Read this before you brief us.

Guides, workshops and field notes from shipping AI-accelerated work for UK teams.

Browse all resources →
← All servicesSee our work →