Service scope
Web Development
Build a website your team can use and maintain, with readable content, accessible navigation, and a defined launch checklist. Agree the pages, integrations, and acceptance checks before development so the handover is as clear as the design.
For a business site, a focused landing-page project, or a Shopify store setup. The initial review determines whether static HTML, a CMS, or an existing commerce platform fits your editing and operational needs.
Discuss Web Development scopeDeliverables
- An agreed page inventory, navigation plan, content requirements, and platform decision based on your business and editing needs.
- Responsive templates with semantic HTML, keyboard access, visible focus, usable forms, and mobile layout checks for the agreed pages.
- SEO foundations including page titles, canonical URLs, crawl rules, sitemap entries, and relevant structured data tied to visible content.
- The agreed integrations, such as a form endpoint, analytics, product setup, or store configuration, with a documented test plan.
- A launch and handover checklist covering custom code or theme changes, account access, deployment configuration, test evidence, and remaining maintenance tasks.
What you need to provide
Provide approved copy, brand assets and their usage rights, page priorities, domain and hosting access, and a decision-maker for design reviews. A Shopify scope also needs product information, store access through suitable permissions, and owner-managed payment and shipping details. Legal policies and consent decisions must come from your business or advisers; they are not generated as a substitute for advice.
Timelines and dependencies
The initial reply target is 24 hours; a standard free review is targeted within 48 hours after website details and required access arrive. Design, build, review, and launch dates are agreed after page count, integrations, and content readiness are clear. Late content, new features, or delayed approvals can change those dates; scope changes are agreed before implementation.
Pricing approach
Quotes depend on the page and template count, platform, custom design needs, integrations, content preparation, migration work, and testing requirements. The proposal lists review rounds and payment milestones. Domains, hosting, paid themes, apps, email delivery, payment-provider fees, and ongoing support are identified separately where relevant.
Ownership and handover
Use domain, hosting, store, and deployment accounts controlled by your business. Handover includes the agreed custom files or repository access, configuration notes, and editing instructions. Third-party themes, fonts, apps, and other licensed assets remain subject to their licences. Custom-work terms and ongoing maintenance responsibilities are confirmed in the proposal.
Reporting and evidence
Progress updates track completed pages, pending content, review decisions, integration status, and blockers. The launch report records functional checks and measured performance conditions. Post-launch analytics or monthly maintenance reports require a separate agreed scope, suitable tracking, and access.
Limitations and exclusions
A launch does not guarantee indexing, rankings, conversions, universal accessibility conformance, or a fixed speed score. Performance varies with hosting, device, connection, content, and third-party apps. Unlimited revisions, ongoing content entry, custom backend features, store operation, and security incident response are excluded unless specifically scoped.
How the work proceeds
Define the build
Agree the page count, platform, content supply, integrations, review rounds, acceptance criteria, and exclusions. Identify responsibilities for domains, email, store policies, payments, and launch approval.
Design and implement
Create the approved page structure and responsive templates. Implement only the agreed features, with content review checkpoints before the final launch build.
Test before launch
Check keyboard and mobile use, forms and selected integrations, internal links, canonical URLs, sitemap access, redirects, and representative performance measurements. Record limits of the testing environment.
Deploy and hand over
Launch after approval, verify the public routes, and provide the agreed files or repository changes plus deployment and editing guidance. Confirm the support window and ongoing maintenance scope in writing.
Frequently asked questions
What will I receive?
An agreed page inventory, navigation plan, content requirements, and platform decision based on your business and editing needs. Responsive templates with semantic HTML, keyboard access, visible focus, usable forms, and mobile layout checks for the agreed pages. SEO foundations including page titles, canonical URLs, crawl rules, sitemap entries, and relevant structured data tied to visible content. The agreed integrations, such as a form endpoint, analytics, product setup, or store configuration, with a documented test plan. A launch and handover checklist covering custom code or theme changes, account access, deployment configuration, test evidence, and remaining maintenance tasks.
What do you need before starting?
Provide approved copy, brand assets and their usage rights, page priorities, domain and hosting access, and a decision-maker for design reviews. A Shopify scope also needs product information, store access through suitable permissions, and owner-managed payment and shipping details. Legal policies and consent decisions must come from your business or advisers; they are not generated as a substitute for advice.
When will I receive the work?
The initial reply target is 24 hours; a standard free review is targeted within 48 hours after website details and required access arrive. Design, build, review, and launch dates are agreed after page count, integrations, and content readiness are clear. Late content, new features, or delayed approvals can change those dates; scope changes are agreed before implementation.
How is the engagement priced?
Quotes depend on the page and template count, platform, custom design needs, integrations, content preparation, migration work, and testing requirements. The proposal lists review rounds and payment milestones. Domains, hosting, paid themes, apps, email delivery, payment-provider fees, and ongoing support are identified separately where relevant.
Who owns the accounts and receives the files?
Use domain, hosting, store, and deployment accounts controlled by your business. Handover includes the agreed custom files or repository access, configuration notes, and editing instructions. Third-party themes, fonts, apps, and other licensed assets remain subject to their licences. Custom-work terms and ongoing maintenance responsibilities are confirmed in the proposal.
What evidence and reporting will I receive?
Progress updates track completed pages, pending content, review decisions, integration status, and blockers. The launch report records functional checks and measured performance conditions. Post-launch analytics or monthly maintenance reports require a separate agreed scope, suitable tracking, and access.
What is outside scope or cannot be guaranteed?
A launch does not guarantee indexing, rankings, conversions, universal accessibility conformance, or a fixed speed score. Performance varies with hosting, device, connection, content, and third-party apps. Unlimited revisions, ongoing content entry, custom backend features, store operation, and security incident response are excluded unless specifically scoped.
Can you work on my store without sharing the owner password?
Yes: use role-based access appropriate to the platform and the work. Shopify supports permission-controlled collaborator access. Keep billing and ownership under your business administrator, grant only the permissions required, and review or remove temporary access at handover.
Start with the scope
Send your website or asset URLs, priorities, and relevant constraints. Please do not send passwords or sensitive documents through the enquiry form. The next step is to confirm what can be reviewed, what needs access, and what belongs in a written proposal.
Platform reference: Shopify: collaborator accounts. Platform requirements may change; eligibility and available permissions are checked during scoping.