How it works
A shared process for websites, business tools and digital products. You know what we are building, where your feedback fits, and what happens after launch.
Discovery and scope
We start with the audience, the purpose and your priorities. For a website, that includes the content and route to enquiry. For a tool, the working process and existing data. For a product, the user and the first useful release. We agree deliverables, responsibilities, price and timing before the build begins.
Design and review
We make the direction tangible through layouts, content or a prototype appropriate to the project. You review the important journeys early. We agree which decisions need your input and how revisions will be handled within the scope.
Build and test
We build in reviewable stages and test the agreed journeys across relevant devices. Integrations, permissions, payments and data migration are checked where they are part of the project. You try the work before launch and we resolve the issues that affect the agreed scope.
Launch and handover
We agree the launch checks and hand over the source, accounts and documentation. Guidance helps you use what has been built. Hosting, paid services, maintenance and any further development are explained and scoped separately, so ownership does not hide the running costs.
A plan you can review, not a timeline to guess at.
Scope, content readiness, integrations and feedback all affect delivery. We agree milestones with you and flag changes before they become extra work.
Security and data ownership
Access, personal data and retention requirements are discussed as part of the scope.
Your custom source code and deployment accounts are handed over. External services and open-source components retain their own terms.
Backups, monitoring, security reviews and ongoing support are agreed according to the needs of your project.