---
name: make-it-land
description: >-
  Shapes an internal message so a sound bet survives the retelling — explaining
  the roadmap to the team, a founder or exec update, a resource ask — anchored
  on observed customer behavior. Use when the thinking is right but the telling
  is diluting it. "Help my CEO understand this bet." / "Explain the quarterly
  roadmap to the team." / "How do I frame this for the roadmap?" / "Make this
  land." Internal
  communication only — not sales, marketing, or customer-facing copy. Do not use
  for customer interviews (prep-customer-interview, review-interview,
  extract-customer-insights).
---

# Make it land

Turn rambling into a message that moves a decision. Direct, no hedge — same
voice as `pressure-test-a-bet`.

## House style

Answer first, in one sentence. Then only the evidence that carries it. Evidence is selected, not gathered — the two quotes that carry it, not the six that mention it. Every section earns its place by changing what they'd do this week; if it doesn't, cut it. Slack, not email. No preamble, no applause, and none of "the move" / "the play" / "the tell" / "the key insight here" / "Here's my take."

Applies to how you talk to them *and* to the message you draft.

## Output contract

| | Rule |
|---|------|
| **Line 1** | Insight or ask — not warmup |
| **Deliver** | Slack-length + paragraph version |
| **Bounce** | If observed behavior exists, lead with it. If it doesn't, name what the message rests on — customer signal, inference, or conviction. Don't invent proof. |

## Structure

**Audience → Behavior → Insight → Ask**

1. **Audience** — what do they care about right now?
2. **Behavior** — one observed fact. Not a feature. Not a theme.
3. **Insight** — so what?
4. **Ask** — decide / approve / unblock / align. One per message.

One proof point if available: ticket count, anonymized quote, or metric.

## Examples

**Before:** "We've been doing discovery on reporting and customers have mentioned wanting better visibility and we think this could be a big opportunity next quarter…"

**After:** "Ops managers export to Excel every Monday for a status report their VP never asked for. Ask: one sprint on visibility-without-export, or does [other bet] win? Need a call by Friday."

**Before:** "Q3 roadmap: Salesforce integration, reporting improvements, and some performance work. Let me know if you have questions."

**After:** "Q3 is one bet: deal context stops dying between our tool and the CRM — reps copy-paste notes today, and 3 of 5 recent churns dropped off when deals got complex. Reporting and perf slip to Q4. Say something now if that breaks a commitment you've made."