Growth playbooks you can actually run
Each playbook is one outcome, broken into stages with the sequence that matters. Run them by hand if you have the hours — or hand them to the agents, who run them as standing programmes.
These are working programmes, not listicles: diagnose-first sequences with honest measurement built in, written from how the WorkDaddy agents actually execute the same work. Every playbook states which agents own which stage, but the method stands on its own — a merchant with time and discipline can run any of them manually. The difference the agents make is that the playbook keeps running after week three.
Reduce cart abandonment
A diagnostic-first programme: find why carts die, fix the causes, then automate recovery.
Learn more →Increase average order value
Raise AOV with co-purchase data, threshold design, and offers that do not train discounting.
Learn more →Improve store page speed
A field-data-first speed programme: measure real users, fix by layer, prevent regression.
Learn more →Rank in AI search
A programme for getting retrieved, cited, and recommended by AI answer engines.
Learn more →Build a welcome flow
The first-week sequence that converts a signup into a first order — built on intent, not days.
Learn more →Optimise product titles
Titles that match how buyers search — across store, Google, and marketplace surfaces.
Learn more →Plan a BFCM campaign
The peak-sales campaign programme: offer architecture, list warm-up, sequencing, and load readiness.
Learn more →Set up GA4 e-commerce tracking
The tracking foundation everything else stands on — events, parameters, and validation.
Learn more →Run a post-purchase survey
One question at the right moment — attribution truth and objection intel from real buyers.
Learn more →Win back lapsed customers
A re-engagement programme built on real churn windows, honest offers, and a sunset policy.
Learn more →Localise a store
Enter a new market with real localisation: structure, vocabulary, and permanent sync.
Learn more →Write collection copy
Collection page copy that helps buyers choose — and gives the page a reason to rank.
Learn more →Build a B2B quote funnel
From spec-complete pages to fast structured follow-up — the wholesale conversion machine.
Learn more →Run a technical SEO audit
The store-specific audit: crawl reality, indexation truth, structured data, and speed.
Learn more →Product launch checklist
The complete launch sequence — page, tracking, search, email — as a checklist that runs itself.
Learn more →Improve mobile conversion
Close the mobile gap: thumb-reach reality, speed on real devices, and checkout friction.
Learn more →Structure internal links
An internal link architecture that spreads authority to revenue pages — maintained, not decayed.
Learn more →Build an abandoned browse flow
Recover interest that never reached the cart — with intent thresholds that keep it welcome.
Learn more →Measure marketing attribution
An honest attribution setup for stores: clean data, triangulated methods, stated uncertainty.
Learn more →Design a loyalty programme
A loyalty programme designed from repeat-purchase economics — not points for their own sake.
Learn more →How the playbooks are built
Each follows the same skeleton: measure before touching anything, fix causes in impact order, automate what remains, and install the schedule that prevents decay. The recurring theme is sequence — most growth tactics fail not because they are wrong but because they are run before their prerequisites.
Where to start
If tracking is uncertain, start with the GA4 setup playbook — every other playbook stands on it. Otherwise, start where your funnel visibly leaks: cart abandonment for checkout losses, page speed for mobile-heavy traffic, the welcome flow if email revenue is thin. One playbook run properly beats three run in parallel.
Frequently asked questions
Are these playbooks usable without WorkDaddy?
Yes, deliberately. The method sections are complete and tool-agnostic. The agent notes at the end of each describe how the same work runs as a standing programme — that is the product pitch, and it is clearly separated from the method.
How long does a playbook take to run?
Each states its own rhythm, but the honest pattern is: days for the diagnostic stage, weeks for the fixes, and forever for the maintenance stage — which is exactly the stage manual execution tends to abandon.
In what order should I run several?
Tracking first if in doubt, then whichever addresses your largest measured leak. Playbooks that share a diagnostic base (the funnel ones, the email ones) chain naturally — each states its prerequisites.
How do these relate to the use-case pages?
A use case describes a problem and how the agents divide it; a playbook is the step-by-step programme for one outcome. Use cases answer "can this be handled?", playbooks answer "what exactly happens, in what order?"
Put the team to work on your store
Connect your storefront, analytics, and email stack, set a goal, and let the agents run the work end to end. Start on the free plan with your own model key.