Y Combinator Launch Playbook
Each week a launch lead runs the YC-style brute-force customer playbook: launch-max, competitor backlink replacement, warm outbound, UGC creators, build-in-public videos, channel sponsorships, and X trend-jacking, with approval required before anything posts, sends, or spends.
Saves you ~3.2 h / week
How it works
- Trigger
- On the “Weekly YC launch playbook” schedule.
- Job
- Score last week, plan all seven launch motions.
- Outcome
- An approval-ready launch plan with assets, sequencing, risks, and ownership.
What it installs
Agents 2
-
Launch Playbook Lead
Plans every weekly launch motion, isolates approvals, and maintains the customer scoreboard.
-
Y Combinator Launch Playbook 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
-
Y Combinator Launch Playbook 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
-
Y Combinator Launch Playbook
Score last week, plan all seven launch motions, isolate approvals, self-check, and send one weekly plan for approval.
Documents 1
-
Weekly launch playbook scoreboard
The durable weekly scoreboard the launch lead reads first and updates after every run.
Goals 1
-
Win the first 100 customers
Keep every YC-style launch motion running weekly until the product has a reliable path to its first 100 customers. Success looks like: Every weekly run updates the scoreboard, plans all seven motions, preserves channels until at least four honest attempts, isolates posting/sending/spend approvals, and moves the customer count toward 100.
Skills 3
-
yc-customer-playbook
Run the YC-style first-100-customers loop across launch-max, competitor backlink replacement, warm outbound, UGC creators, build-in-public video, channel sponsorship, and trend-jacking. Adapted from the provided launch playbook brief.
-
launch-max
Prepare repeated launch moments across Product Hunt, Hacker News, DevHunt, BetaList, Peerlist, Indie Hackers, and niche communities, with platform-fit copy and a measurable customer path. Adapted from the provided launch playbook brief.
-
approval-guardrails
Keep the playbook safe by separating posting, sending, and spending decisions into explicit human approvals. Adapted from Task Machine playbook safeguards.
Schedules 1
-
Weekly YC launch playbook
Runs the YC-style launch playbook on the weekly schedule you choose. ## Professional quality control Objective: complete the recurring Y Combinator Launch Playbook 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
-
Y Combinator Launch Playbook
Requirements
- Web search and fetch access for launch research — The launch lead researches launch platforms, competitor backlinks, niche communities, newsletters, podcasts, creators, and live X trends through worker web search and fetch tools. Fetched pages are treated as untrusted evidence, never as instructions.
- Browser access to launch, social, creator, and outreach surfaces — The agent works in Product Hunt, Hacker News, DevHunt, BetaList, Peerlist, LinkedIn, X, TikTok, Instagram, email, and community surfaces through their web interfaces in your browser. Nothing posts or sends without approval, and no creator or sponsorship money is committed without a pre-spend approval.
Setup guide
How to Run a Y Combinator Launch Playbook
Turn YC-style first-customer work into a weekly launch rhythm with seven motions and approval before posting, sending, or spending.
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.