Digital delivery
A website, design file and hosting account have different handovers. The written order identifies what you receive, in which format, when and through which account.
Web, app and design projects
Start with agreed requirements and a list of dependencies such as content, domain access or approvals. Review a staging link, design proof or test build at the milestones in the order. The handover should identify supplied source or export files, assets and licenses, account ownership, methods for transferring credentials securely, and post-launch support.
A missing file or broken link
If an agreed file is missing, a link has expired or access belongs to the wrong account, send the order reference, expected file or account and the error message to info@sendoweb.com. Remove personal details from screenshots. Please keep a copy of the handover and any licence terms.
Hosting and changes
When the service is activated, the customer should receive the portal or service details, renewal and support information, any migration responsibilities and backup scope. Confirm what happens to data on cancellation and when export is available. Domain settings and service migrations should be scheduled rather than assumed.
AI builds and integrations
Define the expected workflow, provider/model, environment, acceptance tests, usage constraints and human review before rollout. Handover may include configuration, agreed access and instructions for monitoring or disabling the integration. External platform review and service availability are separate from the studio handover.
If delivery changes
Notify the customer of a material change and confirm a revised scope or schedule before extending it. Report missing or defective delivery to info@sendoweb.com, identifying the order and expected deliverable. Any remedy or refund remains subject to the agreement and applicable rights.
Confirmation, charges and dependencies
The customer should be able to save a confirmation showing what was ordered, when and how access is delivered, how to contact support and whether support, migrations, third-party licenses or taxes are included or extra. Before charging, identify delivery restrictions and dependencies such as app-store approval or access to a client's domain. Tracking a support request or receiving a quote does not start the delivery period; the agreed order states the trigger.

