Custom growth project
Build the site around search, information and conversion requirements from the start.
Plan and implement websites or major sections where search architecture, technical performance and commercial UX need to be designed together.
Typical timeline: 8–14 weeks · fixed price agreed after scoping
- 01Technical architecture
- 02Search-safe IA
- 03Component/page development
- 04Performance considerations
- 05Schema and metadata
- 06Launch QA
When to use it
Scope this separately when the opportunity is concentrated enough to deserve a project.
Growth Services sit beside managed search work rather than inside every retainer. The goal is to make scope boundaries clearer, not to create surprise add-ons.
A rebuild is likely to disrupt search equity.
The current CMS or architecture limits search implementation.
New commercial experiences require development beyond monthly service capacity.
Project model
Evidence → scope → build → verify.
Define the constraint
Start from the search, funnel or operational evidence that justifies the project.
Lock the scope
Agree the deliverables, required inputs, acceptance criteria and limits on included work.
Implement
Build the agreed work without silently expanding into unrelated tasks.
Verify
QA the output and, where measurable, reconnect it to the visibility or conversion signal that started the project.
Deliverables
What you receive.
Technical architecture plan
Recommendations on CMS, hosting, rendering approach and integrations, chosen for search performance, editing needs and what your team can maintain.
Search-safe information architecture
A sitemap, URL structure and internal linking model based on search demand, with a redirect map from any existing URLs.
Templates and components
Reusable components and templates for services, locations, articles and landing pages, so new pages start with sound search structure.
Built website or section
The developed site or section, responsive and accessible, with content migrated or entered and editor access set up for your team.
Schema and metadata framework
Structured data, titles, descriptions and canonical rules built into templates, rather than added by hand page by page.
Launch QA and verification
Pre-launch checks of redirects, performance, tracking and indexation settings, then post-launch monitoring of crawl and search visibility.
Timeline
Typically 8–14 weeks.
The exact schedule is set in your proposal. It depends on scope, approvals and how quickly we receive access and inputs.
What we need from you
- Access to the current site, hosting, domain and DNS settings
- Brand assets, design files and any existing style guide
- Content owners who can supply or approve page content on schedule
- A single decision-maker for design and launch approvals
- Details of required integrations, such as CRM, booking or payment tools
- Weeks 1–2
Discovery and architecture
We review the current site, search data and business requirements, then agree the platform, sitemap and URL structure with you.
- Weeks 3–5
Design and templates
We design the key templates and components, review them with you, and finalize content requirements for each page type.
- Weeks 6–11
Development and content
We build the templates and pages, migrate or enter content, and add structured data, metadata and conversion tracking.
- Weeks 12–14
QA, launch and verification
We test across devices, check redirects and performance, launch on an agreed date, and monitor search signals after go-live.
Questions
Common questions about this project.
How is a website build priced?
Each build is quoted at a fixed price after scoping, once we understand the number of templates, the content volume and the integrations involved. Larger builds can be split into phases, each with its own written scope and price, so you approve the work in stages.
What happens if the scope changes during the build?
Scope often shifts on a build, and that is fine. We log each requested change, explain its effect on timeline and cost, and only proceed once you approve it in writing. During scoping we agree what counts as a normal revision and what counts as an addition, so there are no surprises.
Who owns the website and code?
The project agreement sets this out before work starts. We plan for the site to run on hosting and accounts in your name and avoid tools that would tie you to us, so another developer can maintain it if you choose.
Commercial terms
A scoped project—not open-ended hourly billing.
Your proposal sets out the deliverables, fixed project price and agreed labor limit. Work outside that scope requires your approval before it starts.