1. Brief
You share:
- Goals and deadline
- Sitemap or page list
- Designs or wireframes
- Content approach and CMS needs
- Accessibility target and performance budget
2. Scope and plan
I return:
- Delivery plan and milestones
- Assumptions and exclusions
- Risks and dependencies
3. Build
- Repo setup and environments
- Components and templates
- Content wiring and deploy pipeline
- Weekly progress notes, or per milestone
4. QA
- Responsive checks
- Keyboard and screen reader pass on key flows
- CWV and page weight checks
- Bug list with fixes tracked
5. Release and handover
- Launch checklist
- Docs, notes, and support window
- Optional training for editors
Scope guardrails
This is how I keep delivery smooth. It prevents budget drift and deadline pain.
Typical scope ranges
Small agency builds tend to fall into one of these buckets.
-
Starter site
3 to 5 templates. Up to 10 content pages. One form. -
Standard marketing site
5 to 8 templates. Up to 20 content pages. Two to three forms. -
Campaign or landing set
1 to 3 templates. Multiple variations. Tight turnaround.
Templates means page types, such as home, about, service, contact, article, case study, listing, detail.
What you provide
- Final content, or content placeholders with a clear delivery date
- Figma link preferred. Finalised layouts for each breakpoint you care about
- Brand assets. Logo, fonts, imagery
- Tracking requirements. Analytics, pixels, consent rules
- Legal pages copy, if needed
What I provide
- Front end build and integration for the agreed scope
- PR based delivery with review points
- Basic docs and handover notes
- Accessibility and performance checks against agreed targets
What counts as a revision
A revision is a change to layout or behaviour within the agreed templates. Included revisions usually cover:
- Copy tweaks and minor spacing changes
- Small component adjustments that do not change the page structure
- Fixes for missed requirements in the agreed scope
Not included as revisions:
- New components not in the original designs
- New templates or new page types
- Significant layout rework after sign off
- New integrations. Third party widgets, booking tools, product feeds
Change requests
A change request applies when the scope changes. I price it and schedule it before starting. Common triggers:
- Page or template count increases
- New component types appear in late designs
- Content arrives late and shifts milestones
- New forms, new fields, or new validation rules
- CMS requirements change after build starts
- New browser support or accessibility target appears mid project
- Stakeholder feedback introduces new requirements
Sign off points
To avoid endless loops, I use clear sign off moments.
- Design sign off before build starts
- Template sign off once the first template is built
- Content sign off before final QA
- Launch sign off before release
Content ownership
- You own content quality and approvals
- I implement content and templates as agreed
- If you want me to write or edit content, price it as a separate line item
Assumptions
- One primary reviewer on your side
- Feedback returned within agreed timeframes
- Assets and content delivered by the dates in the plan