Service
We hand it over. We don't drop it.
The training, written runbooks, and ongoing support that turn a shipped build into a build the team actually uses. Plus open enquiries for anything else you need an extra pair of hands on - a tool we didn't build, a fix we didn't break, a question that doesn't have an obvious service page.
Scoped per engagement, agreed in writing - whether that's a half-day workshop, a three-month handover overlap, a small monthly retainer for the questions a team keeps asking, or a single afternoon on a tool that isn't ours.
Build's shipped. Now what?
The second month is when the questions start.
Every build we ship comes with a handover - documentation, an operator walkthrough, the test the team has to pass to call it done. That covers the first day. The second month is when the team starts asking the questions nobody anticipated, hitting the edges nobody specified, and wishing the new tool had the one thing the old tool did.
We stay reachable for that second month - and the twelfth, if you want us to. And we're open to enquiries for anything else: a tool you bought, a build somebody else shipped, a process you're trying to roll out. If we can help, we will; if we can't, we'll tell you who probably can.
What we do
Six shapes of training and support engagement. Every one is scoped to your team - no support tiers off a shelf, no per-seat metering. Pick the closest, or describe yours in the enquiry form and we'll work it out.
Half-day workshop, written runbook, recorded video walkthroughs the team can replay. A baseline handover is included on every build we ship; deeper handovers - multi-team rollouts, regulated workflows, change-management heavy - sit on top as their own engagement.
A new tool, a new process, a new playbook. Half-day session on-site or remote, with a written follow-up the team can refer back to. Works for builds we shipped, playbooks we wrote, or tools you bought elsewhere - we don't have to have built the thing to train you on it.
The thing every shipped build needs but nobody scopes for at the start - the small changes, the questions, the 'can you just...' requests, the wording tweak that's a 20-minute job and a fortnight wait without a retainer. Fixed monthly cost, response window agreed at scope.
Something we shipped is broken; we fix it. Something we didn't ship is broken; we'll usually take a look and tell you what we'd do - or who'd be better-placed. Live channel for reports, triage within the response window agreed at scope.
You bought a CRM, a Zapier, a ChatGPT, a Notion, a Tradify, a ServiceM8 - and nobody on the team knows what to do with it. Half-day workshop tailored to your tool, your team, and the actual job you bought it for. Includes the bits the vendor's docs skip.
One owner learning how to use the build, the tool, the AI agent, the dashboard. Async by default - video questions, written responses - with a live call when it helps. The thing every SaaS user manual misses: somebody on the other end who actually knows your business.
What you walk away with
Engagements usually combine more than one of these. The shape is part of the scope conversation, not a fixed package.
Written runbook
How the thing works, how to use it, what to do when it doesn't - in plain language, in your team's voice, hosted somewhere the team will actually open it. Updated when the build changes; replayable when somebody new joins.
Recorded video walkthroughs
Short clips alongside the written runbook for the steps that are easier shown than written. Hosted privately, replayable as many times as it takes. Useful for software steps, equipment-handling, or the bits new hires keep getting wrong.
Live workshop session
Half-day on-site or remote, walked through with the actual team who'll use the thing. Questions answered live, edge cases surfaced, the obvious-but-undocumented bits captured. Followed up in writing the next day.
Async support channel
Email or shared chat - whichever your team already uses. Response window agreed at scope, with escalation rules for the rare emergency. Not a ticket system, not an outsourced helpdesk, no per-seat metering.
How pricing works
Every training and support engagement is different; there's no public £ figure on this page, and not because it's a secret. A half-day workshop on a CRM, a monthly retainer for a shipped build, and a multi-week handover overlap don't share a price - pretending otherwise on a rate card means somebody is overpaying.
Engagement
Half-day workshop, multi-week handover overlap, single afternoon on a tool we didn't build - all scoped at engagement, agreed in writing before any session is booked. No grid, no tiers, no per-seat creep.
On-call retainer (optional)
The thing every shipped build needs - small changes, questions, triage, the occasional 'can you just...' request. Hours included, response window, and monthly price agreed when we scope it. Roll-over and roll-off rules in writing.
Pay monthly instead of all at once
Split-pay over monthly instalments is always available on one-off training engagements that don't fit a retainer. Number of months and terms agreed at scope, alongside the price - because every project, idea and vision is different.
Often paired with
Training and support sit naturally on top of anything else we ship - the build, the playbook, the AI agent. The handover is where they all converge.
Playbooks & SOPs
The written half. Playbook documents the standard moves; training walks the team through them and answers the questions the playbook didn't anticipate.
AI & LLM for business
Every AI build needs handover training - the operator who'll review the agent's conversations, the team who'll act on what it surfaces, the owner who'll review the monthly evaluation report.
Website build & hosting
A baseline handover is included on every build we ship; deeper rollouts (multi-team, regulated, change-management heavy) sit on top as their own engagement. From £99 build; hosting on top, agreed at scope.
FAQ
How much does training or ongoing support cost?
Agreed at scope, because every engagement is different. A half-day workshop, a multi-week handover overlap, a fixed monthly on-call retainer, a single afternoon on a tool we didn't build - all sit on different price shapes. We talk through what you actually need, agree the scope and the price in writing, then start. No grid, no tiers, no per-seat creep.
I didn't get the build from you. Can you still help?
Yes - this service is deliberately open to enquiries for anything you need an extra pair of hands on. A tool you bought, a build a previous agency shipped, a process you're trying to roll out, a team that's stuck on software you didn't write. We'll tell you honestly whether we're the right shape for it, and if we're not, who probably is.
Do you support old tech / legacy code?
Where we can, yes. Where we can't, we'll tell you - and tell you what we'd do about it. The honest answer matters more than the eager one. If the codebase is something nobody should be paying somebody to keep alive any more, we'll say so before we take your money.
Can you cover holiday or sick leave for our in-house team?
Yes - that's a retainer shape we do. Agreed in writing, with a hand-back at the end so your in-house team isn't dependent on us for things they should own. Useful for clinics, agencies, and product teams where the build can't go offline because one person's on holiday.
Do you do contract / hourly work?
Yes, scoped at engagement. The retainer covers the recurring small stuff; for larger pieces of work that don't fit a retainer, we scope and price them like any other build. Same posture - agreed in writing first, then the work.
How fast do you respond on the retainer?
Agreed at scope, because every team needs a different shape. Some retainers want same-business-day for anything; some want a one-hour acknowledgement on emergencies and a two-day turnaround on small changes; some don't need a response SLA at all, just a guarantee we'll do the work. The shape is part of the scope conversation, not a template we hand you.
What if I just have one question?
Fill in the form. If it's the kind of thing we can answer in an email, we'll often just answer it - no retainer, no engagement, no per-seat ask. If it's bigger than an email, we'll come back with a sketch of the shape we'd suggest. Either way, no calendar widget, no forced demo, no obligation.
What does the enquiry process look like?
Fill in the form below. Tell us what you need help with - a build we shipped, a tool you bought, a process you're stuck on, or just 'don't know, help'. We come back within 24 hours by email with what we think we'd do and what it would cost. If it lands, we agree it in writing and start.
Tell us what you need help with
Build we shipped, tool you bought, question you've been kicking down the road - what would you like an extra pair of hands on? Don't know what the shape is - that's fine, just write 'help' in the box. We'll come back within 24 hours by email with what we think we'd do and what it would cost.