24 Founder Post Triggers
Credibility before traction comes from the specificity of the problem you work on, not the size of your wins. Every trigger below already happened — pick one and publish it.
Customer Evidence (6)
- The surprising sentence — a customer line that changed your view. Verbatim.
- The real no — the actual reason a prospect declined, not the polite one.
- The exit reason — why someone churned, plus your read.
- The recurring question — asked three times in support. Answer it publicly.
- Their words, not yours — how a customer described you to someone else.
- The unintended use — someone using it for something you never designed.
Numbers You Can Stand Behind (5)
- Before and after — one conversion rate, one change, both figures.
- The retention read — a churn number plus your honest diagnosis.
- Channel cost direction — what a channel costs, and whether that is rising.
- The failed experiment — what you tried, what it returned, what you concluded.
- The expectation gap — forecast versus what landed.
Decisions and Reversals (5)
- What you cut — a feature removed, and what removing it cost.
- The reversal — a decision your team argued you out of.
- The thing nobody used — built, shipped, ignored.
- The pricing change — what moved, and why.
- The deliberate no — a customer, segment, or feature you turned down.
Product as Demonstration (4)
- Raw output — what it just produced, unedited.
- Before and after artifact — the same task with and without it.
- The hard part — a genuinely difficult problem, and your solution.
- What it refuses to do — a constraint you built on purpose.
Position and Category (4)
- The real comparison set — who buyers actually weigh you against.
- The disagreed belief — category orthodoxy you think is wrong.
- The loose term, defined — a vague word, made precise.
- The unpriced change — a market shift most have not adjusted to.
Play Selector
Pick one and hold it — they train different expectations and combine badly. Cases: references/plays.md.
| Play |
Run when |
Triggers |
| Publish real numbers |
You have data and tolerate exposure |
7–11 |
| Content on audience pain |
You serve a specific, badly-served group |
1–6, 24 |
| Speaking is showing |
The product's output is visible |
17–20 |
| Position alignment |
The company's claim is already clear |
21–23 |
Opening Lines (Lowest-Effort Tier)
Share something already circulating, add one sentence of real judgment:
- "This matches what we see with our own users: …"
- "Most people read this as X. The more useful takeaway is Y."
- "The part everyone skips: …"
- "We tried this. It worked / it didn't, because …"
- "I believed this a quarter ago. What changed my mind: …"
Ramp and cadence: references/first-four-weeks.md.
Pre-Publish Check
What good looks like
- Strong founders write from one specific thing that happened; weak ones write from a general position. A draft with no first-hand fact is noise wearing the costume of insight.
- The common mistake is waiting for results. The second is posting announcements — they answer "what shipped" instead of "what this means for you".
- It is working when strangers engage and what they say back names your topic. Scattered replies mean the topic has not landed.
- Track inbound that names your specific problem. Better signal than follower count, and earlier.
Rules
- MUST anchor every post in a first-hand event from the work.
- MUST hold ~70% of output inside one topic.
- NEVER publish a number you cannot stand behind, or dress up a bad one.
- NEVER wait for results to start.
Example prompts
Give me 3 post triggers I can write today from this week's customer calls.
Which play fits a product whose output is a generated document?
Turn trigger #8 into a draft — our 90-day retention is 22%.
1---2name: founder-post-triggers-243description: Use this skill when a founder has no results to point at and needs something to publish — "I have nothing to post about", "what do I write when we haven't launched", "who would even listen to me", "should I build a personal brand", "our CAC is climbing and we have no budget". Twenty-four things that already happened this week and are publishable, in five categories, plus the play selector, copy-paste opening lines, and the pre-publish check.4---56# 24 Founder Post Triggers78Credibility before traction comes from the specificity of the problem you work on, not the size of your wins. Every trigger below already happened — pick one and publish it.910## Customer Evidence (6)11121. **The surprising sentence** — a customer line that changed your view. Verbatim.132. **The real no** — the actual reason a prospect declined, not the polite one.143. **The exit reason** — why someone churned, plus your read.154. **The recurring question** — asked three times in support. Answer it publicly.165. **Their words, not yours** — how a customer described you to someone else.176. **The unintended use** — someone using it for something you never designed.1819## Numbers You Can Stand Behind (5)20217. **Before and after** — one conversion rate, one change, both figures.228. **The retention read** — a churn number plus your honest diagnosis.239. **Channel cost direction** — what a channel costs, and whether that is rising.2410. **The failed experiment** — what you tried, what it returned, what you concluded.2511. **The expectation gap** — forecast versus what landed.2627## Decisions and Reversals (5)282912. **What you cut** — a feature removed, and what removing it cost.3013. **The reversal** — a decision your team argued you out of.3114. **The thing nobody used** — built, shipped, ignored.3215. **The pricing change** — what moved, and why.3316. **The deliberate no** — a customer, segment, or feature you turned down.3435## Product as Demonstration (4)363717. **Raw output** — what it just produced, unedited.3818. **Before and after artifact** — the same task with and without it.3919. **The hard part** — a genuinely difficult problem, and your solution.4020. **What it refuses to do** — a constraint you built on purpose.4142## Position and Category (4)434421. **The real comparison set** — who buyers actually weigh you against.4522. **The disagreed belief** — category orthodoxy you think is wrong.4623. **The loose term, defined** — a vague word, made precise.4724. **The unpriced change** — a market shift most have not adjusted to.4849## Play Selector5051Pick one and hold it — they train different expectations and combine badly. Cases: [references/plays.md](references/plays.md).5253| Play | Run when | Triggers |54|---|---|---|55| Publish real numbers | You have data and tolerate exposure | 7–11 |56| Content on audience pain | You serve a specific, badly-served group | 1–6, 24 |57| Speaking is showing | The product's output is visible | 17–20 |58| Position alignment | The company's claim is already clear | 21–23 |5960## Opening Lines (Lowest-Effort Tier)6162Share something already circulating, add one sentence of real judgment:6364- "This matches what we see with our own users: …"65- "Most people read this as X. The more useful takeaway is Y."66- "The part everyone skips: …"67- "We tried this. It worked / it didn't, because …"68- "I believed this a quarter ago. What changed my mind: …"6970Ramp and cadence: [references/first-four-weeks.md](references/first-four-weeks.md).7172## Pre-Publish Check7374- [ ] Contains one first-hand fact — a quote, a number, a reversal75- [ ] Could NOT have been written by someone who read the same articles76- [ ] Inside your one chosen topic (hold ~70% of output there)77- [ ] States a process, not an opinion78- [ ] Any number in it, you can stand behind unedited7980## What good looks like8182- Strong founders write from one specific thing that happened; weak ones write from a general position. A draft with no first-hand fact is noise wearing the costume of insight.83- The common mistake is waiting for results. The second is posting announcements — they answer "what shipped" instead of "what this means for you".84- It is working when strangers engage and what they say back names your topic. Scattered replies mean the topic has not landed.85- Track inbound that names your specific problem. Better signal than follower count, and earlier.8687## Rules8889- MUST anchor every post in a first-hand event from the work.90- MUST hold ~70% of output inside one topic.91- NEVER publish a number you cannot stand behind, or dress up a bad one.92- NEVER wait for results to start.9394## Example prompts9596```97Give me 3 post triggers I can write today from this week's customer calls.98```99100```101Which play fits a product whose output is a generated document?102```103104```105Turn trigger #8 into a draft — our 90-day retention is 22%.106```