// CanDo Studio
Further development after the first delivery
Once the software is live, Studio stays as an ongoing relationship: retainers for further development, operation, and planned change — not care of plant in a building.
Further development
- Scope
- Planned work on the running system: new flows, extensions, steering — for the same customer.
- Hours
- Agreed per engagement in the package.
- Response
- Scheduled sprints, not emergency.
- Exclusions
- First delivery, greenfield work, work on systems CanDo did not build.
- Price
- Enquiry
Operation
- Scope
- Keep the delivered system running: operation, faults, small fixes.
- Hours
- Agreed per engagement in the package.
- Response
- Target agreed in the package.
- Exclusions
- New builds, systems CanDo does not look after, first delivery.
- Price
- Enquiry
Change
- Scope
- Change something after delivery: a form, a rule, an export — on the existing system.
- Hours
- A pool in the retainer, or per delivery.
- Response
- In the agreed sprints.
- Exclusions
- Systems CanDo does not look after, and work without an ongoing engagement.
- Price
- Enquiry
Agree the retainer before the next need
Hours and response belong in the agreement. Ask which package fits further development.