A process you can plan around.
Nine stages, each with a written output. You always know what stage the project is in and what is waiting on whom.
Discovery
Clarify the business goal behind the request: what the site must achieve commercially, who uses it, and what currently blocks progress.
Requirements & scope
Turn discovery into a written scope: pages, features, integrations, content responsibilities and explicit exclusions.
Proposal & approval
Provide a fixed price and timeline against the scope, with payment milestones and assumptions stated plainly.
Planning & architecture
Decide the technical approach before writing code: data model, platform choice, integrations and risk points.
UI/UX & implementation
Build in reviewable increments with working staging environments, so progress can be seen rather than described.
Quality assurance
Test the actual workflows — forms, checkout, permissions, edge cases — on real devices and both themes.
Client review
A structured review round with a written change list, so feedback is versioned rather than open-ended.
Deployment & handover
Deploy with backups, redirects, monitoring and analytics configured; hand over credentials and documentation.
Maintenance & support
Optional ongoing support: updates, monitoring, backups and a defined allowance for small changes.
Response times
Enquiries answered within one business day. Weekly written progress updates during delivery.
Change control
Scope changes are quoted and approved before they are built — no silent additions to the invoice.
Handover
Credentials, documentation and a walkthrough. You own the accounts and the code you paid for.
Process questions
What happens after launch?
Deployment includes documentation and a handover walkthrough. Ongoing maintenance and support is available as a retainer.