Leave-behind page

skills/leave-behind-page/SKILL.mdView on GitHub

This applies per segment and per event. It produces the thing a champion forwards internally, which is where most B2B deals are actually won.

Before you start

This skill works on its own. If the person has their own marketing brain (or any folder of context files about their company), read the files listed under reads in the header first and cite them for every fact. If they do not have one, do not look for one: ask for the two or three facts this play needs and go on. Never invent a fact; a blank is a question for the person.

Tools: this play speaks in verbs (check the CRM, pull the call, schedule the post). TOOLS.md at the root of this repo lists the tools recommended for each verb. The company’s own 1-context/stack.md wins when it exists. No tool is required; a spreadsheet and a mail client cover most of it.

The play

1. Read the context (see Before you start). Pick the audience: a segment, a persona, an event’s attendees. The page is written for the person who was not in the room.
2. Structure on one screen or one page: the problem in the buyer’s words; the outcome with the cleared number; three proof points (a customer story, a number, a recognition) each cleared through permission-check; one real product view; the next step with the rep’s booking link.
3. Copy in brand-voice, under 200 words. The headline is the outcome, not the product name.
4. Versions: one per segment, one per event (with the event’s name and the booth conversation’s hook), one per partner where the partner co-brands. Keep a version table with the date and the proof rows used.
5. Visuals through graphics-check: cleared logos, real screenshots, nothing clipped.
6. Build as a tracked page where the stack allows (so a forward shows up as a visit from the account) or a PDF where the buyer’s environment requires it. Hand the page to landing-page-brief for the build and tracking.
7. Refresh quarterly or when a proof point is retired in the tracker.

What good looks like

• The best operator writes for the boss who gets the forward, not the champion who got the demo.
• The mediocre version attaches the full deck.
• Good output is a page a rep sends in one line and a champion forwards without editing.

Rules

• MUST clear every proof point through permission-check and record the rows in the version table.
• MUST keep to one page or one screen.
• NEVER include pricing that is not published.
• NEVER let a retired proof point stay on a live version.