At a glance
- No physical shipping for digital services.
- Dates and acceptance criteria are agreed before work starts.
- Hosting, maintenance and support require an explicit scope.
Scope and delivery schedule
Before taking payment for a project, we agree the deliverables, milestones, estimated or committed dates, customer dependencies, review stages and completion criteria in writing. Website illustrations are examples, not a promise that every feature is included. Catalogue delivery windows are planning estimates, subject to the stated entry scope, scheduling and required access or materials; sending a quote-basket request does not reserve a start date. We explain any material change to the delivery schedule and agree the next steps.
How each service is delivered
- Website and app development: a review or staging link, source repository or release build, and deployment or app-store submission support where included.
- Design: agreed design files, prototypes, exported assets and handover notes through an agreed workspace or secure file link.
- Software, CRM and SaaS development: agreed code, configuration, test evidence, deployment instructions and access handover. A development project is distinct from an ongoing hosted subscription.
- Chatbots and integrations: agreed configuration or code, test scenarios, limitations, authorised integrations and handover guidance.
- Digital marketing: strategy documents, agreed creative or campaigns, account configuration and reporting. Ad-platform spend and approval are separate from our service delivery.
- Server setup and support: configuration records, agreed access transfer, maintenance reports and an operational handover. Backup and recovery duties must be explicit.
Customer access and dependencies
You are responsible for providing authorised accounts, suitable materials and timely consolidated feedback. We agree who owns domains, hosting, app-store and advertising accounts and who may make changes. Production credentials should be transferred through an agreed secure channel, not a public form or chatbot.
We notify the agreed project contact when deliverables are ready and maintain reasonable delivery evidence such as a handover message, repository release, access invitation or milestone record. Tell us promptly if access does not work so we can restore it or agree an alternative.
Review and completion
The order defines the review period and objective acceptance criteria. You can identify specific deviations from the agreed scope; we assess those and provide appropriate corrections or other remedies. A change of scope is priced and approved separately. These general policies do not deem work accepted merely because you have not replied.
Completion and any remaining matters are recorded in writing. Source-code rights, third-party licences and account access follow the agreed intellectual-property and handover provisions.
After delivery
Maintenance, hosting, monitoring, security testing, backups and support are included only when the order says so. The support agreement sets coverage, response targets, exclusions, renewal and cancellation. Customer support is available 24/7 by email and phone. That availability is distinct from a contractual response or resolution deadline, a particular uptime percentage or an unlimited revision allowance.
If delivery is delayed, incomplete or does not meet the agreed scope, contact us with the project reference. See the Refund & Cancellation Policy for how remedies and unearned fees are handled.
