The 30-day pilot
30 days. Day by day. Nothing hidden.
A controlled experiment on your customer journey, not a retainer with a vague scope. Here is exactly what happens, in what order, and what you get at the end of each day.
Week 01 · Day 1–7
Diagnose + build
Understand the business before touching anything. Then fix what is obviously broken.
Day 1
Kickoff and access
- Services, territory, capacity and job values
- Delegated access to the accounts you already own
- Agree what a good job looks like
What you get
Scope note and access checklist
Day 2
Google and local visibility audit
- Google Business Profile completeness
- Local search presence for core services
- Service-area coverage and category fit
What you get
Visibility findings list
Day 3
Website and conversion audit
- Page speed and mobile behaviour
- Calls, forms and CTA placement
- Trust, clarity and service-area signals
What you get
Conversion issue list, ranked
Day 4
Customer journey mapping
- Walk the journey as a customer would
- Log every step where a person can drop out
- Time the response path end to end
What you get
Journey map with friction points
Day 5
Measurement verification
- Confirm calls, forms and chats are all recorded
- Check source attribution
- Remove double counting
What you get
Measurement baseline you can trust
Day 6
Fix critical conversion issues
- Repair anything actively losing enquiries
- Make the primary action obvious on mobile
- Verify every form actually delivers
What you get
First set of shipped fixes
Day 7
Baseline review
- Record the starting numbers
- Agree the first experiments
- Confirm priorities with you
What you get
Signed-off pilot plan
Week 02 · Day 8–14
Launch + validate
Put the changes live and prove the plumbing works before judging results.
Day 8
Launch approved changes
- Ship the agreed page and journey changes
- Stage anything risky
- Log each change with a date
What you get
Change log entry per change
Day 9
Form testing
- Submit every form as a customer
- Confirm delivery, routing and notifications
- Check spam handling
What you get
Form test results
Day 10
Call path testing
- Call every published number
- Check ring time, routing and missed-call handling
- Confirm call tracking records the source
What you get
Call path test results
Day 11
Booking path testing
- Run the booking flow end to end
- Check availability and confirmations
- Test on a phone, not just a laptop
What you get
Booking path test results
Day 12
Lead capture verification
- Reconcile enquiries against the system of record
- Find leads landing nowhere
- Close the gaps
What you get
Every lead accounted for
Day 13
Lead quality review
- Read the actual enquiries
- Separate good-fit work from noise
- Note where bad-fit leads come from
What you get
Quality read on real enquiries
Day 14
Week two review
- What shipped, what moved, what did not
- Adjust the next experiments
- Share the running document
What you get
Week two written review
Week 03 · Day 15–21
Optimize
Find the biggest bottleneck and fix that one first. Not everything at once.
Day 15
Enquiry volume review
- Compare against the baseline
- Separate channel effects from page effects
- Flag anything seasonal
What you get
Volume read with context
Day 16
Enquiry quality review
- Score enquiries against fit criteria
- Look at the sources behind poor fit
- Tighten qualification questions
What you get
Quality scoring in place
Day 17
Response and booking rate review
- Measure time to first response
- Measure enquiry to booking rate
- Identify the slowest handoff
What you get
Response and booking numbers
Day 18
Identify the biggest leak
- Rank stages by lost opportunity
- Pick one stage to fix
- Write the hypothesis before changing anything
What you get
One named bottleneck
Day 19
Fix the weakest stage
- Ship the change for that stage only
- Keep everything else stable
- Set the success measure in advance
What you get
Targeted change, live
Day 20
Verify the change
- Re-test the affected path
- Watch for side effects elsewhere
- Confirm measurement still holds
What you get
Verified result or a clear no
Day 21
Document the cycle
- Record what changed and why
- Record what the numbers did
- Record what we would do differently
What you get
Written cycle record
Week 04 · Day 22–30
Prove + plan
Show the work honestly, including what did not move, and decide what happens next.
Day 22–24
Compile the evidence
- Before and after on each tracked metric
- Every change with its date
- Anything we could not measure reliably
What you get
Evidence pack
Day 25–26
Separate signal from noise
- Note sample sizes and time windows
- Mark results that are still unproven
- Avoid claiming causation we cannot support
What you get
Honest read on results
Day 27–28
Build the next-cycle plan
- Rank the remaining bottlenecks
- Define the next experiments
- Estimate effort against likely impact
What you get
Prioritised next 30 days
Day 29
Handover documentation
- System documentation you keep
- Access remains yours throughout
- Nothing locked behind us
What you get
Documentation handed over
Day 30
Pilot review
- Walk through the findings together
- Decide continue, adjust or stop
- No pressure either way
What you get
A clear decision
What the pilot includes
- A documented baseline before any change
- Fixes shipped, not just recommendations
- Every change logged with a date and a reason
- Weekly written reviews, no jargon
- Access and accounts stay in your name
- A prioritised plan for the next 30 days
What it does not include
- Guaranteed lead volumes
- Vanity metrics with no business meaning
- Locked-in contracts before you see the work
- Results claimed without measurement behind them
If the numbers don't move, we say so.