1. Project start and schedule
The project begins after both parties sign the Statement of Work, the initial invoice is paid if required, and the client supplies the access, content, and decisions identified as prerequisites. Published package timing is an estimate for the stated scope, not a guaranteed completion date. The schedule may change when scope changes or required client materials, decisions, or approvals are delayed.
2. Review and acceptance
Each milestone is delivered for review using the method stated in the SOW. The client should provide consolidated feedback within the stated review window. Included revision rounds and the acceptance process are described in the project agreement. New features or a change to an approved direction require written approval and may affect cost and timing.
3. Final delivery and handoff
After the agreed final invoice is paid, the Developer will deliver or deploy the project as described in the SOW. This may include source files, a deployment to the client’s hosting or domain, documentation, and a handoff meeting. Account ownership, access, hosting, backups, domains, licenses, and third-party subscriptions are transferred or set up only as expressly stated in the written scope.
4. Credentials and third-party services
Clients should provide access through secure, least-privilege account invitations whenever possible, not by sending passwords in ordinary email. Third-party services, hosting, domain registration, licenses, and payment-provider accounts remain subject to their own availability, fees, terms, and approval. The Developer does not promise that a third party will approve an account or integration.
5. Support after delivery
Ongoing updates, monitoring, incident response, and maintenance are not included unless listed in the SOW or a separate maintenance agreement. Response-time or uptime commitments apply only when an executed agreement explicitly states them. See Support & Maintenance Terms and the Master Services Agreement.