How to Run a Customer Acquisition Sprint

Customer acquisition sprint planning is the weekly ritual of deciding which growth actions will run, who owns them, what assets need to ship, and how last week's results change the plan. It turns scattered launch ideas, outbound drafts, creator bets, and trend reactions into one operating loop.

The job matters most for founders who have too many possible channels and too little consistency. Early acquisition rarely fails because there were no ideas. It fails because the team runs one launch, one outbound batch, or one content push, sees a weak result, and silently stops before the channel has had a fair run.

Why acquisition work quietly loses momentum

Acquisition gets messy when every channel has a different home. Launch work sits in a document, outbound lives in social drafts, creator ideas sit in a note, and last week's results are remembered from a meeting instead of recorded. The founder ends up reacting to the loudest channel rather than the one with evidence.

The deeper cost is premature judgment. A weak first launch is a data point, not a verdict. The bundle's method keeps seven acquisition motions alive each week: launch-max, backlink replacement, warm outbound, creators, build-in-public video, channel or sponsorship sourcing, and trend-jacking. It asks for at least four honest attempts before a channel is retired.

What the manual process looks like

Done by hand, a customer acquisition sprint is a Monday planning ritual:

1. Open last week's notes and record the action, measured result, read, attempt count, and next move for every channel.
2. Decide where to double down, where to iterate, and which channels are still too early to judge.
3. Pick this week's launch target and prepare the listing, demo asset, and first comment.
4. Queue the warm outbound batch, backlink replacement work, creator or sponsorship actions, build-in-public demo, and trend response.
5. Separate anything that spends money from the rest of the plan, with a named budget and expected return.
6. Review the whole week as one plan and approve what should happen next.

The failure mode is not complexity. The failure mode is drift. One channel gets planned, another waits for a draft, a spend decision hides inside a general plan, and the founder loses the thread.

What an agent can automate

An agent is useful here because most of the weekly assembly work is structured and repetitive:

• Score the previous week first. The agent reads the results log and makes every channel carry its action, measured or reported result, read, and attempt count before it plans anything new.
• Keep all seven channels visible. Launch-max, backlink replacement, warm outbound, creators, build-in-public video, channel sourcing, and trend-jacking each get an action, owner, and asset state, or a rare justified skip.
• Reference specialist motions. The sprint does not rebuild the warm outbound or trend workflow. It points to the right specialist playbook and pulls the latest draft into one reviewable plan.
• Isolate spend. Creator fees and sponsorship budgets become separate pre-spend approvals with a named budget and expected return. The agent never commits money inside the sprint.
• Draft one steerable plan. The founder gets one inbox item with the launch target, demo script, channel actions, prior results, and open decisions.

The agent handles continuity and assembly. The founder still decides whether the plan is right, whether a budget is worth it, and how to steer the week.

The guardrails that make it safe

Customer acquisition touches public accounts, prospects, creators, and paid placements, so the workflow must stop before posting, sending, or spending. The safe shape is a plan-and-approve loop: the agent scores, plans, scripts, and checks the sprint, then sends the whole plan to the inbox.

The approval is not a rubber stamp. It is where the founder changes the launch target, rejects a weak trend angle, lowers a creator budget, or decides that a channel needs one more attempt before being retired. The results log also gives the next run memory, so the sprint is not a new brainstorm every week.

Set it up in Task Machine

The Customer Acquisition Sprint playbook installs the growth lead agent, the weekly sprint workflow, the results log document, the acquisition goal, the launch and orchestration skills, and the recurring schedule. Setup takes a few minutes. You need a Task Machine workspace and permission to install playbooks (workspace owners have it). Browser and web access help with live channel research, but the sprint can start from attached notes and the results log.

1. Find the playbook

Open Playbooks in your workspace and search for "customer acquisition sprint", or browse the Growth category. The card shows the growth lead, workflow, document, goal, skills, and schedule it creates.

2. Preview what it installs

Preview & install opens the full install preview before anything is created. Review the Growth Lead agent, the Customer Acquisition Sprint workflow, the weekly results log, the goal to hit the customer target without giving up, and the recurring schedule.

3. Give the sprint its scope

Start setup asks for the target customer, the sprint goal, the channel bets, and the offer or CTA. Use answers that make the agent's plan concrete: the exact buyer, the customer target for the week, the channels you want kept alive, and the action you want prospects to take.

4. Generate and review

Generate customized playbook turns your answers into the agent instructions, workflow prompts, results-log framing, and schedule. Read the review step before installing. The plan should keep all seven acquisition channels visible, isolate any spend, and describe the sprint as one approvable weekly item.

5. Install

Install customized playbook creates the sprint in your workspace. Three follow-ups arrive in the inbox: update the weekly acquisition results log, start the Customer Acquisition Sprint workflow, and set the weekly sprint schedule. The first run scores the previous week, drafts the channel plan, and waits for approval before posting, sending, or spending.

What good looks like

The sprint is working when the plan gets easier to review and harder to ignore:

• Every channel has continuity. Each channel carries last week's result and this week's next action, even when the result was flat.
• No channel is killed too early. A weak first attempt stays in the rotation until it has enough runs to judge.
• Spend decisions are separate. Creator and sponsorship money never hide inside a general growth plan.
• The founder can steer in minutes. The weekly inbox item has the launch target, demo, channel actions, and open decisions in one place.

Common questions

Is this a replacement for individual growth playbooks? No. The sprint sequences specialist motions such as warm outbound, trend-jacking, backlink replacement, and beta discovery. It keeps them coordinated so the founder reviews the whole week together.

What if one channel is clearly not working? Retire it only after a fair run. The bundle's method treats fewer than four attempts as too little evidence unless there is a hard reason to stop, such as a policy issue or bad audience fit.

Can the sprint post or spend automatically? No. It drafts and plans. Posting, sending, creator payments, and sponsorship commitments stay behind human approval.

What should go in the results log? Record outcomes, not activity. "Show HN launch, 2 signups, 40 visits" is useful. "Launched" is not enough to guide next week.