Routine care
Updates, configuration changes and health checks are handled before maintenance becomes a crisis.
Managed technical support
Keep it online. Keep it clear. Keep improving.
Ongoing technical support for communities that need routine updates, dependable troubleshooting and planned improvements after launch.
UpdatesHealth checksFixesOptimisationConfigurationDocumentation
Why ongoing support
Small problems stay small when someone owns the technical follow-through.
Support is scoped around an expected workload, so priorities and boundaries remain clear for both sides.
Context retained
Less time is lost explaining the whole setup again whenever a change or issue appears.
Changes controlled
Backups, access, testing and documentation are treated as part of the work rather than an afterthought.
Monthly plans
Choose the level of involvement you need.
The final agreement defines included workload, supported systems, communication channel and any response expectations.
Essential Care
£40/mo
Routine upkeep for a smaller, stable setup.
- Routine plugin or software updates
- Basic bug fixes
- Small configuration changes
- Monthly health check
- Short maintenance summary
Community Care
£100/mo
More active maintenance for a growing community.
- Everything in Essential
- Weekly maintenance window
- Performance checks
- Agreed feature or configuration work
- Priority over one-off requests
- Monthly recommendations
Managed Operations
£250+/mo
Hands-on technical ownership across multiple community systems.
- Server and Discord maintenance
- Incident investigation
- Ongoing optimisation
- Planned improvements
- Technical coordination
- Custom reporting and scope
Plans are not unlimited development retainers. Included workload and any rollover rules are defined in the written agreement.
Clear boundaries
Support works best when the responsibilities are explicit.
Before a plan starts, we agree what is supported, who controls each account, how changes are requested and what sits outside the monthly allowance.
High-volume development, guaranteed round-the-clock emergency cover and substantial new projects require a separate scope.
01Supported systemsThe exact servers, websites, bots or integrations covered.
02Expected workloadA realistic allowance for maintenance and small changes.
03Access and ownershipYou keep ownership; access is limited to what the work requires.
04EscalationUrgent issues and larger work are handled under agreed terms.
Important: Plan names and prices are starting guides. Availability, response expectations, included hours and emergency arrangements must be confirmed in your individual support agreement.
Support FAQ
Set expectations before anything breaks.
Is support available for projects you did not build?
Usually, after a technical review. Existing quality, documentation, access and third-party dependencies affect what can be supported safely.
Does a monthly plan guarantee 24/7 availability?
No. Any guaranteed coverage or response time must be explicitly agreed in writing and priced around the level of availability required.
Can I request new features?
Small agreed changes may fit within a plan. Larger development work is quoted separately so routine maintenance is not displaced.
Can I cancel a monthly plan?
Cancellation terms will be stated in the service agreement before the plan begins. No long-term commitment should be assumed from this page alone.
Need continuity?
Give the technical work an owner before it becomes urgent.
Describe the systems, current pain points and the level of help you expect each month.