A clear, predictable path from brief to launch.
Six stages that keep scope clear, progress visible and the final implementation faithful to the approved direction. Every stage ends with an explicit review point — no silent hand-offs.
Discovery and Scope
We clarify what the organisation offers, who the website is for and what action it should make easier. This produces an agreed scope before any design work begins.
Deliverables
- Discovery summary
- Agreed scope document
- Project plan and milestones
You provide
- Time for a structured discovery call
- Access to existing brand, content and analytics
- Honest answers about what is and is not working
Review point
Scope sign-off before design begins.
Structure and Direction
I map the information architecture and page structure, then agree the visual direction. Getting the structure right early is what keeps the rest of the project predictable.
Deliverables
- Sitemap and page hierarchy
- Wireframes for the most important pages
- Visual direction (typography, colour, layout mood)
You provide
- Feedback on structure and direction
- Confirmation of primary and secondary audiences
Review point
Structure and visual direction approved before build.
Design and Development
Design and frontend development run together. Pages are built on a shared staging website so you can review real screens rather than static mockups.
Deliverables
- Designed and built pages on a staging URL
- Design system tokens and components
- Responsive behaviour across breakpoints
You provide
- Timely feedback on staging screens
- Copy and asset supply per the agreed plan
Review point
Page-by-page approval on staging.
Review and Refinement
You review the work in progress and we refine the details: copy, spacing, responsive behaviour and interaction. Decisions stay documented and easy to follow.
Deliverables
- Refined pages with all feedback addressed
- Documented decision log
- Accessibility and performance checks
You provide
- Consolidated feedback rather than ad-hoc notes
- Final copy review
Review point
Final approval to enter launch.
Testing and Launch
Before launch I check performance, accessibility, responsive behaviour, links and metadata, then deploy the approved website to production.
Deliverables
- Pre-launch QA report
- Production deployment
- Sitemap and robots.txt submission
You provide
- DNS or hosting access where required
- Final go/no-go decision
Review point
Successful production deployment.
Handover and Support
You receive organised code, deployment details and a clear handover. I remain available for a defined support period to resolve anything that surfaces after launch.
Deliverables
- Code repository with documentation
- Deployment and environment notes
- Defined support period (typically 2 weeks)
You provide
- Internal handover to whoever maintains the site
- Reporting of any post-launch issues
Review point
Sign-off on handover and support closure.
Do you work fixed-price or hourly?
Most projects are fixed-price against an agreed scope. Hourly is available for frontend-only work where the scope is genuinely open-ended.
How long does a corporate website take?
A focused 6–10 page corporate website typically runs 4–8 weeks from discovery to launch. Larger or content-heavy sites take longer; the timeline is agreed at the end of discovery.
Do you write the copy?
I structure the messaging and write headlines and section intros. Long-form service copy is most often supplied by the client — I edit it for clarity and consistency.
Who hosts the website?
Most clients deploy on Vercel or Netlify. I help with the deployment and hand over full ownership of the hosting account at launch.
Ready to scope a project?
Share the current website and what you want the new one to achieve. I'll reply with a practical next step.