Review growth evidence
Funnel data, positioning, channels, team rhythm, and what's been tried. Plain-English view of where pipeline breaks.
How it works
Diagnose. Build. Test. Transfer.
Most consultancy engagements are a black box. This one isn't. Here's exactly what happens week by week, what the cadence looks like, and what you walk away with.
First 30 days
What happens in month one.
Same sequence on most engagements — emphasis shifts with your bottleneck.
Name the bottleneck
Reset priorities around the binding constraint — positioning, acquisition, conversion, reporting, or ownership.
Build the first artefacts
Channel hierarchy, reporting rhythm, campaign priorities — documented so the team can execute.
Install weekly cadence
Weekly growth meeting format, owners, and decision log so momentum doesn't depend on the founder alone.
The operating system
What feeds the work — and what you leave with.
A single picture of how growth inputs flow through diagnosis, experiments, and cadence into assets the team can run without founder heroics.
Inputs
- ICP
- Channels
- Funnel
- Reporting
- Team cadence
WSS system
- Diagnosis
- Experiments
- Reporting
- Weekly rhythm
Outcomes
- Pipeline clarity
- Decision rules
- Transfer pack
The engagement rhythm
Diagnose. Build. Test. Transfer.
Phase 1 — Diagnose
Find the real constraint across ICP, positioning, funnel, channels, reporting, and team cadence. Ends in a plain-English bottleneck statement everyone agrees on.
Phase 2 — Build
Turn the decision into pages, campaigns, workflows, dashboards, and a weekly rhythm. Existing assets get rewired before new ones are built.
Phase 3 — Test
Run focused experiments with clear hypotheses, owners, and decision rules. ICE-scored, sequenced, and cut fast if they don't move the metric.
Phase 4 — Transfer
Document the system so the founder, team, and vendors can keep running it. Handover doc, dashboard read-me, vendor SLAs, decision rules — all written.
Deliverables
The work is in the artefacts, not the deck.
Representative, anonymized snapshots of what ships inside an engagement — not client-specific screenshots. Exported at 2× for sharp displays; WebP for load time.
Weekly cadence
One rhythm, every week.
No mystery, no Friday-afternoon "what's been happening?" calls. The week is the same shape, every week.
Mon
Weekly priorities locked. Owners and decision rules attached to every test in the backlog.
Tue–Thu
Execution. Briefs ship, copy ships, pages ship. Async on Slack. Daniel is in the build, not just review.
Fri
Numbers review against the scorecard. What's working, what to scale, what to kill. Decisions logged.
What you get
Practical working assets your team can use.
Everything below is something the team can edit, run, or hand to a vendor on day 91 without us in the room.
- Direct Slack and email — Daniel responds to commercial questions same-day
- A working backlog you can see and edit in Notion
- A weekly numbers dashboard tied to the metric we agreed in week one
- Monthly business review pack for the board or leadership team
- Every brief, page, and campaign written and shipped — not just specced
- On the way out: a 10–15 page handover doc so the system survives the engagement
FAQ
How engagements run in practice.
Is every engagement exactly 12 weeks?
Diagnosis and sprint windows vary by scope. The four-phase shape is consistent: diagnose, build, test, transfer — but timelines flex with team capacity and channel complexity.
What if we already have an agency?
Common. The weekly rhythm includes directing agency work inside one system: priorities, briefs, and stop/scale decisions — not competing channel plans.
What does transfer mean in practice?
Written decision rules, dashboard ownership, meeting format, and vendor SLAs so the team can run the rhythm without daily operator dependency.
Related reading
Notes that pair with this page.
Next step
See if this rhythm fits your team.
Bring the current growth picture. 20 minutes. Plain English.