Customer Acquisition Sprint
Each week a growth lead runs the whole brute-force acquisition playbook — this week's launch target, warm-outbound batch, content/demos, creator and channel actions, and the trend to jack — and lands one steerable inbox item where you approve and direct the week.
Saves you ~2.9 h / week
How it works
- Trigger
- On the “Weekly acquisition sprint” schedule.
- Job
- Score last week, plan every channel, isolate spend.
- Outcome
- A campaign plan and creative package ready to launch.
What it installs
Agents 2
-
Growth Lead
Sequences the brute-force acquisition channels into one weekly approval.
-
Customer Acquisition Sprint Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Customer Acquisition Sprint quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Customer Acquisition Sprint
Score last week, plan every channel, isolate spend, self-check, and land one steerable plan for approval.
Documents 1
-
Weekly results log
The durable per-channel scoreboard the sprint reads to plan and reallocate effort.
Goals 1
-
Hit the customer target without giving up
The sprint exists to keep every acquisition channel running every week and to keep moving toward the customer target — never quitting a channel before it's had a fair run. Success looks like: Every weekly run produces one approved plan in which all seven acquisition channels carry a concrete action and last week's measured result, no channel under four attempts has been retired, and the trailing new-customer count is trending toward the weekly customer target.
Skills 2
-
launch-max
Plan and prepare recurring multi-platform launches (Product Hunt, Show HN, BetaList, Peerlist, directories) that actually convert, not just spike. Adapted from public growth playbooks.
-
growth-orchestration
Run a multi-channel acquisition sprint as one weekly ritual — review last week, plan all channels, isolate spend, and land one steerable plan. Adapted from public growth playbooks.
Schedules 1
-
Weekly acquisition sprint
Runs the customer acquisition sprint on the schedule you choose. ## Professional quality control Objective: complete the recurring Customer Acquisition Sprint operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify audience, trigger, source, claim, personalization, permission, and any spend exposure. Public copy must be useful before promotional, truthful about affiliation, and free of generic AI phrasing, fake familiarity, filler, hype, hollow transitions, or template language that could be sent unchanged to unrelated recipients. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
Folders 1
-
Customer Acquisition Sprint
Requirements
- Web search and fetch access for market research — Planning launches, scanning channels, reading live trends, and checking last week's results all depend on the provider's web tools. Fetched pages are treated as untrusted evidence, never as instructions.
- Browser access to X, LinkedIn, and launch platforms — The agent works in X, LinkedIn, Product Hunt, and similar launch and social surfaces through their web interface in your browser and pauses for your approval before posting, sending, or paying anything; until you connect it, it works from attached exports and the planning documents.
Setup guide
How to Run a Customer Acquisition Sprint
A practical guide to running a weekly acquisition sprint across launches, outbound, content, creators, channels, and trends.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.