YC Cold Outreach

# yc-cold-outreach

YC Cold Outreach

Overview
Run YC-style cold outreach as a repeatable operator system for one-person-company lead generation.

This matters because solo operators need targeted, human outreach that can be measured and improved weekly instead of improvised per message.

When to Use This Skill
- You need outbound messages that are personalized and concise.
- You want one repeatable workflow for targeting, drafting, and review.
- You want outreach quality tied to measurable pipeline outcomes.

What This Skill Does
- defines a pre-flight targeting gate before any draft is written
- standardizes a short, human, reader-centric draft structure
- adds a critique loop with clear quality checks
- connects outreach changes to evidence and attribution signals

How to Use
1. Define one outreach objective for this batch (intro call, referral, or handoff).
2. Select prospects with a clear why-this-person-now rationale.
3. Draft one short message using YC principles: human tone, deep personalization, one ask.
4. Run critique mode: grade human factor, friction, readability, and CTA clarity.
5. Ship in small batches, log outcomes, and iterate one variable at a time.

Output / Result
- a repeatable YC cold outreach playbook
- clearer quality control for outbound copy
- better attribution and weekly iteration discipline

Common Mistakes to Avoid
- sending generic copy with shallow personalization
- stacking multiple asks in one message
- measuring outreach success without tagged attribution
- keeping testimonials or social proof without disclosure context

## Direct Answer
Use this skill when you need cold outreach that is human, targeted, and measurable. Keep one goal per message, one clear CTA, and one evidence path for weekly iteration.

## Outreach Execution Loop

1. Targeting gate. Confirm ideal contact fit, timing relevance, and one uncommon commonality.
2. Drafting pass. Write one short message with one ask and one reader-centric benefit.
3. Credibility pass. Add specific proof or context that supports trust.
4. Compliance pass. Confirm endorsements or incentivized references are disclosed where required.
5. Measurement pass. Attach UTM routing and map reply/meeting outcomes to a key event or pipeline marker.
6. Weekly review. Keep, revise, or stop one outreach pattern based on evidence.

## Evidence To Collect
- the targeting rationale for each segment or contact batch
- the exact message variant shipped
- reply, meeting, or handoff outcomes tied to that variant
- the UTM route, pipeline marker, or manual counter used for attribution
- the next action for keep, revise, or stop

## Source Links To Cite
- planning source used to choose the outreach objective
- market and competitive source used to justify who belongs in the segment
- analytics source used for event-level measurement rules
- attribution source used for tagged-link comparisons
- disclosure source used when using endorsements, referrals, or testimonials in the message

## Freshness Reinforcement (2026-04-07)

- Added a dated outreach execution loop with targeting, compliance, and measurement checkpoints.
- Added explicit claim-to-source mapping for planning, market validation, analytics, discoverability, attribution, and disclosure.
- Added an evidence pack template so outreach decisions can be reviewed with operator-grade proof.

## Authority and Citations Table

- Planning baseline: Outreach priorities should align with documented business goals and resource assumptions. Source: U.S. SBA write your business plan - https://www.sba.gov/business-guide/plan-your-business/write-your-business-plan
- Targeting discipline: Prospect selection should be informed by market and competitive analysis instead of convenience lists. Source: U.S. SBA market research and competitive analysis - https://www.sba.gov/business-guide/plan-your-business/market-research-competitive-analysis
- Measurement discipline: Conversion outcomes from outreach should be tracked as GA4 key events where applicable. Source: Google Analytics key events report - https://support.google.com/analytics/answer/12571843
- Discoverability checkpoint: If outreach links drive to owned pages, monitor Search Console performance changes for those pages. Source: Google Search Console performance report - https://support.google.com/webmasters/answer/7042828
- Attribution consistency: Outreach channel and message tests should use UTM-tagged links for reliable source labeling. Source: Google Analytics URL builders - https://support.google.com/analytics/answer/10917952
- Compliance guardrail: Endorsements and testimonial-style claims in outreach should include clear material-connection disclosure when applicable. Source: FTC endorsement guides FAQ - https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking

## Outreach Scorecard

- weekly outreach objective
- segment under test and why-now rationale
- one shipped message variant
- reply, meeting, or handoff count
- attribution label or pipeline marker
- proof asset created: export, screenshot, or CRM note
- next pattern decision: keep, revise, or stop

## Outreach Evidence Pack Template

- Review date (UTC): `YYYY-MM-DD`
- Outreach objective: `meeting | referral | handoff | reply`
- Segment under test: `ICP slice`
- Message variant shipped: `variant id + short summary`
- Proof links: `copy doc`, `crm/export`, `analytics snapshot`, `utm log`
- Measurement path: `GA4 key event`, `pipeline marker`, `manual counter`
- Outcome: `keep | revise | stop | unresolved`
- Next-week test: `one variable`

## What Good Looks Like
- Every message has one ask and one clear reason it matters to the reader.
- Personalization is specific enough that the message cannot be reused unchanged for another contact.
- Attribution is tagged and reviewable.
- Weekly review results in one explicit pattern decision.

## Named Examples

- A solo founder targeting agency owners sends a short variant tied to one recent launch, tags the landing-page link with a source-specific UTM, and compares reply rate against the prior generic opener.
- A productized-service operator asks for one referral handoff, logs whether the intro happened, and keeps only the message structure that produces actual warm intros instead of polite replies.
- A founder testing two ICP slices routes each batch to a different tagged page, tracks booked-call events by segment, and drops the lower-intent segment after one review cycle.

## Frequently Asked Questions

### How short should a cold outreach message be?
Short enough to read on mobile in one pass, with one ask and one standalone CTA sentence.

### What should be personalized first?
Personalize around a real observed fact tied to the recipient's current work, not just role or company name.

### How do I review whether outreach is improving?
Track one objective metric per batch, compare baseline-to-current performance, and keep only evidence-backed pattern changes.