Custom growth project
Handle the technical work that does not fit inside a monthly backlog.
Scope major migrations, rebuilds, indexation problems and technical remediation as defined projects with clear boundaries and approval.
Custom quote · fixed scope · approval required for material changes
- 01Technical diagnostic
- 02Migration planning
- 03Crawl/indexation remediation
- 04Rendering analysis
- 05Architecture changes
- 06QA and post-launch verification
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 migration or rebuild creates concentrated technical risk.
The remediation backlog is too large for normal monthly capacity.
Rendering, crawl or indexation issues require engineering coordination.
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.
Typical scope
What this project may include.
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.