The pattern
The founder shares something their team, co-founder, or company would prefer stayed internal. They name the person who didn't want it shared. Then they share it anyway - with specific numbers, real tools, actual outcomes. The tension between "I shouldn't" and "I'm doing it anyway" is the scroll-stopper. The specificity is the proof that the tension is real.
Why it works
First, the tension changes how people read. LinkedIn feeds are full of "lessons learned" and frameworks. When someone signals that the information carries internal consequences, the reader's brain shifts from browse mode to attention mode. Austin's posts that use this framing outperform his baseline by 2.4x on average engagement.
Second, the format forces specificity. You can't frame something as forbidden knowledge and then share a vague insight. It has to be real numbers, real tools, real outcomes. Austin's version included response rates, pipeline dollar amounts, tool names, and play-by-play breakdowns. Vague forbidden knowledge reads as clickbait. Specific forbidden knowledge reads as access. His audience knows the difference - the posts that include hard numbers pull 3x the comments of those that don't.
Third, comment-to-like ratio goes vertical. Austin's forbidden knowledge posts pull a 40% comment-to-like ratio. Most founders sit at 5-10%. The format invites questions, debate, and sharing. Each comment pushes the post further. His tech stack reveal hit 3,341 comments - the highest-engagement post in the dataset by a factor of 4.
The structure
The setup (1-3 sentences)
Name the specific person or group who didn't want this shared. "My team" is okay. "My co-founder Garrett" is better. A first name makes the tension feel real because it is real. Add one detail that shows you're sharing on your own terms - humor works if it's natural to your voice. Don't over-explain why you're sharing. The act of sharing is the explanation.
The reveal (bulk of the post)
The actual thing. Numbers. Tools. Plays. Outcomes. This is where the value lives. The setup earned the reader's attention, and the reveal has to justify it. If the forbidden knowledge turns out to be a mild opinion or a generic framework, the pattern backfires and the audience feels tricked. The content has to feel genuinely internal - something a competitor could use, something that shows how the sausage gets made, something the reader couldn't find in a blog post.
The honest caveat (2-3 sentences)
Acknowledge one limitation, nuance, or thing that didn't work. This separates the pattern from clickbait. Austin's version after the stack reveal: "The tools matter less than the signal logic. I could swap out half of what's on this list and the results would hold." The caveat makes the whole post more believable because it shows the founder has perspective, not just bravado.
The close (1-2 sentences)
Short. Either a forward-looking statement ("I'll keep sharing as long as they let me"), a direct invitation ("save this"), or one takeaway that distills the post. Don't ask for engagement. Don't summarize. Don't restate the setup. The reveal already did the work.
How to find your version
Answer these before prompting Claude. The draft quality depends entirely on the quality of these answers. If you can't be specific here, the pattern won't hold.
- 1. What internal number, play, stack, or outcome would your co-founder or team prefer stayed in the Slack channel?
- 2. Who specifically would prefer it stayed private? (A real name or role - not "my team" unless that's genuinely how you'd say it.)
- 3. Why would they prefer it stay internal? (Competitive intelligence? Reveals how easy something actually is? Shows a number that looks too good or too bad?)
- 4. What are the specific details you're willing to include? (Tool names, dollar amounts, response rates, timelines, headcount - the more concrete the better.)
- 5. What's the honest caveat - the part that's more nuanced than the headline version? (What doesn't work about this, what you'd do differently, what the number doesn't capture.)
Prompt
Paste this alongside your Voice Profile into any Claude conversation.
What this looks like in the wild
Austin's version (abbreviated): "Garrett and Rhea have been telling me not to share this for weeks. I waited until they were both in back-to-backs. This is the full warm outbound stack. Every layer, what it does, why we built it this way. $139M in annualized pipeline. 2 people. This is what's running behind it..."
Result: 3,341 comments, his highest engagement by 4x. The pattern worked because Garrett and Rhea are real people at Unify with real reasons to keep the stack private. The reveal included actual tools and pipeline numbers a competitor could reverse-engineer. And the caveat - "the tools matter less than the signal logic" - added a genuine insight that made the whole post more useful than a simple tool list.
The signal it creates
Comments from ICP accounts. People who ask detailed questions about the tools, numbers, or plays are telling you they're thinking about the same problem. Those comments are signal your GTM system can act on - an ICP contact who comments "what's your response rate on the job change play?" just told you exactly what they care about.
Profile views from decision-makers. The forbidden knowledge frame attracts senior people evaluating approaches. A VP who views your profile after reading a stack reveal is warmer than one who clicked a paid ad. They already know your name and have context on how you think.
Saves and shares. "Saving this for my team" is the strongest buying signal in the feed. The content entered a buying committee conversation without you sending a single outbound message. Track saves if your analytics allow it - they correlate with pipeline more reliably than likes.