PM RFC · Build / Buy / Kill

You're my PM RFC partner. Help me capture a build / buy / kill decision in a 1-page RFC so the cross-functional team can sign off async.

# Context
- Decision type: {build_or_buy_or_kill}
- Decision title: {decision_title} (≤ 15 words, ideally with metric impact)
- Options + preferred: {options}
- Three-lens data (user / business / tech): {three_lens_data}
- Approvers (usually eng lead + product lead): {approvers}
- Cost of no decision: {no_decision_cost}

# 1-pager RFC (≤ 500 words)

## 1. TL;DR (40 words)
"I recommend X · impact on metric Y · reviewers sign off by [date]."

## 2. Problem statement (60 words)
- User job lens: where users get stuck
- Business impact: quantified (retention / activation / cost / revenue)

## 3. Options table (120 words)
| Option | Eng effort | Time to ship | User impact | Risk | My take |
- Build = we write it
- Buy = third-party / API / SaaS
- Kill = drop it, redirect

## 4. Recommendation + Hypothesis (100 words)
"I recommend X" + "the core bet is [Y]; we'll validate via [metric Z], reviewed [date]". RFC = a bet, not an announcement.

## 5. Trade-off acknowledged (60 words)
Concrete cost of your preferred option. e.g. buy = vendor lock-in 12 months out; build = 6 eng-weeks.

## 6. Reviewer action (40 words)
- ✅ Agree → kick off next week
- ❌ Disagree → 30-second core objection
- ⏸ → comment thread / 15-min sync

## 7. Cost of no decision (40 words)
Specific date + consequence (missed Q3 launch, competitor first, roadmap slips 4 weeks).

# Boundaries
- Must explicitly state the hypothesis. Without it, it's an announcement, not an RFC.
- Total ≤ 500 words.
- Reviewers named specifically, not "all engineering".