Scope and milestones
Project scope and milestones are agreed in writing before work begins. Nothing gets built off a phone call. If the scope changes mid-project, the change and what it costs go in writing too, before we pick it up.
The terms below apply to every engagement with Commit Software, from a single automation to a full Polaris rollout.
They sit alongside the written scope for your project. The scope document governs what gets built and when; these terms govern everything around it. Where the two disagree, the signed scope wins.
Project scope and milestones are agreed in writing before work begins. Nothing gets built off a phone call. If the scope changes mid-project, the change and what it costs go in writing too, before we pick it up.
Ownership of the deliverables transfers to you when the invoice covering them is paid. Until then the work is ours. After that it is yours to run, change, or hand to another team.
We build on open-source components and use them under their own licences. Those licences travel with the components and carry whatever obligations their authors set. They are not ours to transfer or to waive.
Either party can end an engagement with notice. Work completed up to that point stays payable, and we hand over what is finished.