Custom growth project
Connect search visibility to the actions the business actually values.
Design analytics and attribution so search performance can be interpreted beyond traffic and ranking movement.
Typical timeline: 3–5 weeks · fixed price agreed after scoping
- 01Measurement architecture
- 02Conversion event design
- 03UTM and source logic
- 04Funnel attribution
- 05Dashboard requirements
- 06QA and documentation
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.
Search reporting stops at sessions or rankings.
Lead sources are lost between landing page and sales follow-up.
Leadership cannot connect search investments to pipeline.
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.
Measurement architecture
A document showing how analytics, tag management, forms, call tracking and CRM connect, and which system is the source of truth for each metric.
Conversion event plan
Named, defined conversion events for forms, calls, bookings and key engagement, with the parameters each event records.
UTM and source conventions
A source and campaign naming standard, plus logic that carries original source data from the landing page into the CRM record.
Configured tracking
Events, conversions and source capture set up in your analytics and tag manager, then tested across devices and form types.
Dashboard
A dashboard showing search visibility, conversions and pipeline together, built in your reporting tool or fully specified for your team to build.
QA log and documentation
A record of every tag and event tested, with plain-language documentation your team can use to maintain the setup.
Timeline
Typically 3–5 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
- Admin access to analytics, tag manager and your CRM
- A sales or revenue operations contact who understands the lead lifecycle
- The questions leadership wants the reporting to answer
- Developer support if tracking needs code changes outside the tag manager
- Week 1
Audit and requirements
We audit current tracking, talk with the people who use the reports, and agree which business outcomes the setup must measure.
- Week 2
Design
We design the measurement architecture, event plan and source logic, and review them with your marketing and sales operations contacts.
- Weeks 3–4
Implementation
We configure tags, events, source capture and CRM fields, and build or specify the dashboard against the agreed requirements.
- Week 5
QA and documentation
We test every event and source path, fix issues, and hand over documentation with a walkthrough of the reports.
Questions
Common questions about this project.
How is an analytics project priced?
We agree a fixed price in writing after a short scoping call. The price depends mostly on how many systems need to connect, and how much existing tracking has to be repaired before new work can sit on top of it.
Will this tell us which keyword produced each sale?
Not exactly, and we will be clear about that. Privacy controls, multi-step journeys and offline conversations limit what any attribution model can prove. A good setup shows which pages, topics and channels contribute to qualified pipeline, with the assumptions written down so leadership can trust and question the numbers.
Who owns the tracking setup when you finish?
You do. Everything is configured in your own accounts, and the documentation explains each event, field and report. If you later move to a managed plan with us, we use the same setup for ongoing reporting. If you work with someone else, they can pick it up directly.
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.