Systems that drift after a project ends — patches behind, no one watching
Service
Garden Care
The optional monthly care routine for systems a FORT has delivered or stabilised. Garden Care runs on PRUNE — Performance checks, Reports, Updates, Nurture, Enhancements — in three tiers: Garden Care (one agreed application or workflow boundary), Garden Growth (adding one SEO or paid-search lane), and Garden Operations (a broader, individually scoped register).
At a glance
- Garden Care: one agreed boundary, scheduled health checks, routine compatible patches, a monthly status report, one minor adjustment up to 30 minutes
- Garden Growth: everything in Garden Care plus one growth lane — SEO (one property, monthly report, up to two bounded on-page improvements) or paid search (one platform, up to two existing campaigns, agreed spend ceiling, you fund the ads)
- Garden Operations: an individually scoped asset and service register, more frequent reviews, reserved small improvements
- The PRUNE routine — Performance checks, Reports, Updates, Nurture, Enhancements — with the tier scope deciding which activities are included
4-step processOngoing retainer option
Common issues
What we see most often.
Small fixes and tweaks that never quite get done
No plain-language view of whether things are healthy
Ad-hoc support with no agreed boundaries or response expectations
What we support
Practical help, not a rebuild.
- Garden Care: one agreed boundary, scheduled health checks, routine compatible patches, a monthly status report, one minor adjustment up to 30 minutes
- Garden Growth: everything in Garden Care plus one growth lane — SEO (one property, monthly report, up to two bounded on-page improvements) or paid search (one platform, up to two existing campaigns, agreed spend ceiling, you fund the ads)
- Garden Operations: an individually scoped asset and service register, more frequent reviews, reserved small improvements
- The PRUNE routine — Performance checks, Reports, Updates, Nurture, Enhancements — with the tier scope deciding which activities are included
Process
How we work.
Agree the asset and service register — what is inside the care boundary
Run scheduled health checks and routine compatible patches
Report monthly, in plain language, against the agreed register
Keep bounded improvements inside the agreed allowance; scope anything larger as a FORT
Proof
Seen in practice.
Real systems, measured honestly — every claim labelled verified, estimated, or qualitative.
Crypto transaction platform for a private banking service
Fintech — founder's prior contract (at Kabru) · Transaction flows shipped inside the live private banking platform, deployed as scalable containerised services.
E-commerce platform for a national music rights organisation
Music rights / entertainment — founder's prior agency work (at Glasshouse) · A production e-commerce platform serving a national rights organisation, delivered within an agency team.
Retainer path
Ongoing ownership.
Care is optional and paid monthly in advance: an initial three-month term, then 30 days' cancellation notice. Support runs weekdays 09:00–17:00 in your contracted timezone, with acknowledgement within one business day — not a 24/7 incident service. New features become FORTs; no automatic rollover or unlimited backlog.
Related services
Explore other support options.
Website Maintenance
For businesses with existing websites that need updates, fixes, SEO implementation, performance work, security support, forms, landing pages, and practical improvement.
Web Application Maintenance
For existing applications that need bug fixes, enhancements, refactoring, infrastructure support, and ongoing development.
CRM & Automation
For businesses that need better CRM workflows, lead routing, email automation, API integrations, reporting, and data synchronisation.
Related reading
From the Insights hub.
What a monthly care plan should include — and what it should never promise
What should a maintenance retainer actually deliver each month — and which promises are warning signs? A buyer's anatomy of a healthy care plan.
Next step
Not sure this is the right fit?
Start with a free fit check. A paid Technical Review then maps one agreed system or workflow, its risks, dependencies and improvement options. You approve the scope and fee before it starts.
FORT / Sprint Assist — A defined outcome and a scoped delivery cycle — typically a two-week FORT with agreed acceptance criteria and a clean handover.
Reserved Capability — Ongoing access to a fractional digital department: the systems you depend on kept healthy, improved steadily and extended when the business needs it.
Partner / White-label Capability — Delivery support for agencies and partners: our senior engineers behind your client work, under your brand and your client relationship.
Discuss your first FORT