Strategy + design
- Brief and scope
- Sitemap and flows
- Responsive UI system
- Review prototype
Web development procedure
The eight stages
- 01
Discovery
Goals, audiences, constraints, stakeholders, and success criteria.
Client outputBrief
CheckpointScope approval: we agree what is in and out of the first release before design begins.
- 02
Content and architecture
Content audit, sitemap, feature list, data model, and user journeys.
Client outputSitemap or product structure
- 03
UX and visual system
Wireframes, prototypes, typography, colour, components, and accessibility.
Client outputPrototype
- 04
Technical planning
Stack, hosting, integrations, security, analytics, and deployment workflow.
Client outputTechnical plan
- 05
Responsive build
Front end, back end, CMS, forms, APIs, mobile behaviour, and performance.
Client outputTested build
- 06
Content and SEO
Migration, metadata, structured content, redirects, and search readiness.
Client outputLaunch checklist
- 07
QA and acceptance
Functional, responsive, browser, accessibility, security, and performance tests.
Client outputDocumentation
CheckpointPre-launch acceptance: you sign off against the agreed scope and the QA results before we deploy.
- 08
Launch and handover
Production deployment, monitoring, training, documentation, and iteration backlog.
Client outputImprovement backlog
Scope
What a complete build can include
Engineering
- Front end
- Back end / APIs / CMS
- Forms and integrations
- Cross-browser support
Readiness
- SEO foundations
- Analytics
- Performance and accessibility
- Security and privacy
Handover
- Hosting and deployment
- Admin training
- Documentation
- Iteration plan
Always included
- Discovery and a written brief
- A responsive build with cross-browser QA
- An accessibility and performance baseline
- Deployment, documentation, and handover
Depends on project scope
- A CMS or a custom back end and APIs
- Third-party integrations, authentication, and billing
- Content migration and redirect mapping
- Native Android or iOS applications
- Ongoing maintenance and feature iteration after launch
Ownership after launchThe final system is documented and ready for the client team to operate.
Before we start
Every engagement starts with three questions.
- What user or business problem must the product solve?
- What is the smallest strong release that proves value?
- How will success be measured after launch?
Ready to map your build to these stages?
Send a short brief and we'll come back with where it starts and what the first strong release looks like.