Custom software does not stop at launch. Geoff's Lab can help keep your system maintained, backed up, secure and supported with clear response targets agreed around your business needs.
When a system becomes part of daily operations, the business needs more than code. It needs a clear support process, agreed responsibilities, reliable backups, security updates, documentation, and a practical way to prioritise issues when something goes wrong.
That matters even more when the software supports bookings, payments, reporting, stock, customer records, staff workflows, condominium management, procurement, dashboards, internal workflows or other business-critical processes. A steady support plan helps reduce friction, minimise downtime and improve continuity without turning the relationship into legal jargon.
Dashboards, portals, booking systems, payment flows, reporting tools, customer records and internal workflows.
Structured records, data-entry systems, reporting dashboards and systems that replace complex spreadsheets.
Mobile applications with maintainable back-end systems, user journeys and business-specific workflows.
Controlled panels for managing content, users, records, reports, payments, orders or operational data.
Connections between payment providers, email systems, external platforms, business tools and internal databases.
Deployment, monitoring and hosting support where Geoff's Lab is responsible for the managed environment.
Specialised local tools, data processing systems, workstation software and device-support applications.
Role-based access, audit trails, safer data handling, backups, controlled admin areas and practical security improvements.
Each client system is different. A small internal dashboard does not need the same support arrangement as a business-critical booking, payment, stock or operations platform. Geoff's Lab discusses support commitments around the actual business risk, the hosting model, the maintenance scope and the practical needs of the people using the software.
This page shows example targets and typical SLA targets. Final commitments are discussed and agreed with each client rather than published as a one-size-fits-all public guarantee.
When an issue is reported, it should be classified by business impact. This helps focus urgent attention where the business is most affected.
| Priority | Meaning | Examples | Example Initial Response | Example Workaround Target | Example Resolution Target |
|---|---|---|---|---|---|
| Priority 1 - Critical | The software is unavailable or unusable for all or most users, or a major business operation cannot continue. | Complete outage, login unavailable, payment, order, booking or stock system down, suspected data loss, serious security incident, production database unavailable. | Within 1 hour. | Within 4 hours. | Within 1 business day, where technically possible. |
| Priority 2 - High | An important function is broken, but the whole system is not down. | Major module unavailable, important report cannot be generated, key integration stopped working, some users blocked from essential features. | Within 4 business hours. | Within 1 business day. | Within 2 to 3 business days. |
| Priority 3 - Medium | A feature is not working correctly, but business can continue. | Non-critical feature failure, performance degradation, minor integration issue, bug with a reasonable workaround. | Within 1 business day. | Within 3 business days. | Within 5 to 10 business days. |
| Priority 4 - Low | Minor bug, cosmetic issue, general question or non-urgent request. | Typographical errors, layout issues, minor inconvenience, general guidance. | Within 2 business days. | As agreed. | Next planned maintenance release or as agreed. |
Where Geoff's Lab is responsible for hosting, deployment, monitoring or infrastructure management, the support agreement can include an availability target. A typical example is 99.5% monthly uptime for systems where the managed environment is under Geoff's Lab's control.
That can include scheduled maintenance windows, emergency maintenance for security or stability, and practical outage communication. It should also be clear that third-party provider outages, client-caused outages and force majeure events sit outside direct control.
For systems under Geoff's Lab's control, support plans can include backup and recovery procedures that are practical rather than theoretical. Backups are only useful if they can be restored. Where backup management is included, restoration testing can be part of the support plan.
Typical arrangements may cover database backups at least once every 24 hours, critical file and configuration backups at least once every 24 hours, retention for at least 30 days, secure storage and restoration testing at least once every 6 months.
Support and maintenance should help keep the system focused, secure and maintainable. Geoff's Lab approaches this with grounded, practical measures rather than absolute claims. The goal is to reduce avoidable risk, improve visibility and respond properly if an issue needs investigation.
That can include role-based access, safer data handling, controlled admin panels, patching, encrypted connections where appropriate and sensible separation between development, testing and production where reasonable.
A good support agreement should be clear about the difference between maintenance and new work. SLA-backed support usually covers maintenance, bug fixes, stability, updates and agreed support activities. New features, new reports, major design changes, workflow changes, extra integrations and new business requirements are usually handled as change requests.
Geoff's Lab believes clients should have appropriate access to their code, data, documentation and systems. Support agreements can include documentation and continuity measures so the business is not left dependent on undocumented processes or a single point of failure.
The client's business should not be held hostage by unclear access, missing documentation or avoidable key-person risk. The aim is a maintainable system built around your specific requirements, with continuity planned in a practical way.
A good SLA should also define what sits outside the provider's control. Clear boundaries help avoid confusion while keeping the agreement fair and realistic.
This is especially relevant for businesses that have outgrown spreadsheets, teams using custom dashboards or databases, companies running booking, payment or order workflows, condominium and property management systems, restaurants with procurement or stock processes, organisations using research, education, XR or device-support platforms, and any company that needs a maintained, secure and documented digital system.
Share the system, the workflow, or the operational risk you want to reduce. Geoff's Lab can review the setup and propose a practical support plan with clear responsibilities, response targets, maintenance scope, backups and continuity measures.