What happens after it goes live
Data drifts, models go stale, and vendors change their APIs without asking. Support starts the day it goes live, with a fixed monthly scope and agreed response times.
What support covers
- Monitoring of data, model and integrations against the agreed test
- First-line triage and fixes for incidents
- Compatible updates to dependencies, models and security
- Usage, capacity and cost tracking
- Quarterly review
- Current documentation and runbooks
What happens when something goes wrong
- 01Monitoring flags the change.
- 02We identify what's affected and who's using it.
- 03We investigate data, model, code and external dependencies.
- 04We fix it, if the work is within scope.
- 05We document the cause and update the runbook.
Work we scope separately
- a new capability or workflow
- a new data source
- a new interface or report
- a major change to business logic
Each of these gets its own scope and price. Once it is live, it joins the support arrangement.
Ownership and exit
Your data, your environment and anything configured specifically for you stays yours. Credentials, documentation and runbooks are kept current, so a competent team could pick this up without us.
Reusable Bitsized components remain our property; you keep a perpetual licence to use what's installed, with a clean handover if the relationship ends.
Agree support before the build starts
Before work begins, you will know what we are building, what we will run afterwards and what the monthly fee covers.