How to Run a Y Combinator Launch Playbook

A Y Combinator-style launch playbook is a weekly customer-acquisition system for doing the unscalable work before one channel is predictable. It combines repeated launches, competitor backlink outreach, warm outbound, creator recruitment, build-in-public video, channel sponsorships, and relevant trend-jacking into one operating rhythm.

The point is not to make launch work tidy. The point is to keep the founder from quitting after one weak attempt, confusing activity with customers, or spreading risky actions across chat threads with no approval boundary.

Why early launch work stalls

Early-stage teams often run one visible launch, get a mixed result, and move on. That makes the channel look like it failed when the real failure was under-sampling. A launch platform, a community post, a creator brief, and a competitor backlink request all need repetition and measurement before they teach you anything.

The other failure is mixing planning and execution authority. A founder wants aggressive customer work, but not accidental posts, spammy outreach, or unapproved sponsorship spend. The process needs to push hard while isolating every posting, sending, and spending decision.

What the manual process looks like

The weekly ritual has five parts:

1. Score last week's seven motions by customer outcomes, not effort.
2. Keep any channel alive until it has at least four honest attempts unless it is unsafe or irrelevant.
3. Plan this week's launch-max, backlink, warm outbound, creator, build-in-public, sponsorship, and trend motions.
4. Draft the assets, outreach, briefs, and spend packets each motion needs.
5. Approve posting, sending, and pre-spend decisions separately before anything leaves the workspace.

The scoreboard is the memory. Without it, every week starts from opinion again.

What an agent can automate

This playbook works well as a planning agent because the weekly shape is fixed:

• Score the prior week. The agent reads the scoreboard and records action, outcome, attempt count, and next move for every motion.
• Plan all seven motions. The agent names the exact action, asset, customer path, owner or specialist playbook, and approval type for launch-max, backlink replacement, warm outbound, UGC creators, build-in-public video, channel sponsorship, and trend-jacking.
• Separate approvals. The agent creates distinct packets for posting, sending, and pre-spend decisions, including worst-case cost and remaining cap when money is involved.
• Self-check before handoff. The agent confirms the plan covers every motion, uses customer outcomes instead of activity, and keeps channels alive long enough to learn.

The result is not an automatic growth machine. It is a founder-reviewable plan with the risky parts clearly separated.

The guardrails that make it safe

The playbook is intentionally aggressive about doing work, but conservative about authority. Nothing posts, sends, books, pays, or commits spend without approval.

The agent also stops when a surface forbids promotion, a claim is unverified, an ICP is unclear, a target list looks scraped beyond owned engagement, or a creator or sponsor needs a cap decision. That stop rule is what lets the weekly plan include many channels without turning into uncontrolled execution.

Set it up in Task Machine

The Y Combinator Launch Playbook installs the Launch Playbook Lead, three skills, the weekly launch playbook scoreboard document, a weekly workflow, a first-100-customers goal, and a schedule. Setup takes a few minutes. You need a Task Machine workspace and permission to install playbooks (workspace owners have it). Web and browser access help with research and platform work, but every post, send, and spend still waits for approval.

1. Find the playbook

Open Playbooks and find Y Combinator Launch Playbook in the Growth category. The gallery card shows the launch lead, workflow, scoreboard, skills, goal, and schedule it creates.

2. Preview what it installs

Choose Preview & install to review the launch lead, the weekly workflow, the scoreboard document, the skills, and the schedule before setup.

3. Define the launch scope

Select Start setup and fill in the startup or product name, launch audience, proof points, and approval gates. These answers keep the weekly plan tied to a real offer and explicit decision boundaries.

4. Generate and review

Choose Generate customized playbook. Review the launch lead, scoreboard, workflow, skills, goal, and schedule. Confirm that the approval gates cover all posting, sending, and pre-spend actions.

5. Install

Choose Install customized playbook. Three follow-ups land in your inbox: update the weekly launch playbook scoreboard, start the launch workflow, and set the weekly YC launch cadence. The first workflow scores the previous week, plans all seven motions, isolates approvals, self-checks the plan, and waits for approval.

What good looks like

The scoreboard should show customer outcomes, not just activity. Good weekly rows name signups, qualified replies, demos, referrals, or customers, plus the attempt count and next move.

The approval packets should also be separate. If one approval request mixes a Product Hunt post, a DM batch, and a paid creator brief, it is too hard to review safely.

Common questions

Is this only for startups applying to YC? No. The workflow is for YC-style early customer acquisition, especially the habit of doing repeated unscalable work until a channel teaches you something.

Does the playbook run all seven motions every week? Yes, unless there is a written reason to skip one. A channel usually needs at least four honest attempts before it is retired.

Can the agent commit sponsorship or creator spend? No. It can draft a spend packet and expected economics. A human approves before any rate, placement, or payment is committed.

What if one channel clearly works better than the others? The next weekly plan should double down on the working channel while still keeping the other motions alive until the stop rule or attempt threshold says otherwise.