Service delivery

1. Scope

Each engagement should have a written scope, deliverables, dependencies, exclusions, estimated timeline and payment schedule.

2. Client inputs

Delivery depends on timely access, content, decisions, approvals and third-party accounts from the client. Delays in these inputs may move the schedule.

3. Review and changes

Milestones are shared for review. Requests outside the agreed scope may be quoted separately or moved to a later milestone.

4. Handover

Handover may include source-code access, production deployment, credentials, build files and operating notes according to the agreement and after due payments.

5. Support

Any warranty period, response arrangement or monthly support plan must be stated in the proposal. New features and issues caused by unapproved third-party changes are not automatically included.