Useful today.
Looked after tomorrow.
Plan who maintains the workspace, how your team gets help and how future changes are handled. Each support agreement sets out the scope, costs and responsibilities.
Email support ↗Know what happens
after handover.
As your team uses the system, we can review the next bottleneck together and agree the improvements worth making.
Keep the essentials
working.
Support can cover fixes, dependency updates and upkeep of the agreed integrations. The plan names the parts we maintain and anything managed by your team or another provider.
Ask for the next
improvement.
A field label, an approval step or a new view can matter once people use the workspace every day. We review the request, agree its scope and test the change against the workflow it affects.
Make responsibilities
clear.
Access, hosting, data export, documentation and ownership terms are agreed for the project. We also define the handover steps if your team or another builder will maintain it.
A few practical
questions.
Are hosting and AI costs included?
The proposal identifies the expected hosting, AI, messaging and other provider costs, including who pays them. Usage-based charges and subscriptions are discussed as part of the scope.
What if we need a larger feature later?
Bring the workflow you want to change. We check how the request affects the existing system and agree a separate scope when it falls outside the support arrangement.
What if we want to manage the workspace ourselves?
We discuss that during scoping. The project agreement sets out account access, code and data arrangements, documentation and the work needed for a handover.