SakSit Founder Story — Three-Act Architecture

A repeatable workflow for turning any founder origin story into structured,
platform-ready narrative content. Based on 2026 research (TheGrowthTerminal,
FoundersPedia, InfluenceFlow — see LEARNING_JOURNAL.md 2026-07-31 03:59 entry).

When to Use

• Drafting any origin-story post for Beer / House of Sak (LinkedIn, X/Threads,
  Instagram carousel, Reels).
• Checking an existing draft against a proven narrative structure.
• Creating a recurring "story train" content calendar from one origin story.
• Any time a story draft feels like a timeline/resume bullet instead of a narrative.

The Three Acts

Act One — The Before State (the specific problem)

Lead with a problem the ideal customer recognizes in themselves — visceral
and personal, NOT a broad market gap.

• Wrong: "People struggled with isolation."
• Right: "I spent 6 months studying AI alone, failing project after project,
  convinced I wasn't good enough — and I knew thousands of others felt the same."

Rules:

• Use numbers, timeframes, tangible impacts (specific details improve recall
  65-70% vs generic statements).
• The audience should nod and think "that's exactly what happens to me."

Act Two — The Turning Point (the insight, NOT the launch)

The moment your perspective shifted — the insight that preceded the build.
This is what proves strategic thinking and separates you from everyone else.

Three types (pick whichever is true, commit fully):

1. Data Moment — "I ran N interviews and X% said the same thing in different words."
2. Personal Cost Moment — "I almost walked away; the problem was eating my mental health."
3. Observation Moment — "Watching someone duct-tape a solution showed me what they really needed."

Allocation: 25-30% of total story length.

For Beer: the turning point is NOT the House of Sak launch. It is the insight
from the Cork shelter — that AI could be built to heal (companions, not
gimmicks) when human connection wasn't available.

Act Three — The New Reality (proof + invitation)

Prove the solution at the customer level, then invite.

• Right: "Teams using it recovered 8-10 hours a week. One person told me they
  could finally focus on relationships instead of data entry."
• Wrong (vanity metric): "We've grown 40% YoY."

Close with an invitation based on the logic of the story — not a hard sales ask.

The 60/30/10 Ratio (discipline check)

• 60% — the customer's/audience's problem
• 30% — your insight (the turning point)
• 10% — you personally

Invert this ratio and you lose them. Every draft gets checked against this.

Platform Compression Matrix

Platform	Format	Spec
LinkedIn	Long-form post	800-1,200 words; each act 2-3 paragraphs; 3+ min reading time; post Tue-Thu 15:00-16:00 UTC, reply to every comment in first 60 min
X / Threads	Thread	8-12 tweets, each act = 2-4 tweets; Tweet 1 specificity drives ~40% of thread performance; end with URL/CTA
Instagram	Carousel	Visual three-act: slide 1 hook (Before), slides 2-6 Turning Point, slides 7-9 Proof, final slide saveable recap
Reels / Shorts	Video	60-90s: 15s problem / 30s insight / 15s proof+CTA; seamless loop

Origin Archetypes (for positioning language)

• Problem-led founder (empathy, customer insight)
• Technology-led founder (technical mastery, defensibility)
• Mission-driven founder (values, impact)
• Accidental/side-project success (organic product-market fit)
• Corporate spinout / academic transfer (IP pedigree)

Beer's story = Mission-driven + Problem-led with personal stake (lived problem →
healing mission).

Vulnerability Boundaries (HARD RULES)

• Never pitch on recovery content — it is sacred (Soul Document).
• Always include MH resources: Pieta 1800 247 247, Samaritans 116 123.
• Only share trauma details essential to understanding the why.
• Never share others' stories (mental health, family, customers) without consent.
• Beer has given explicit permission for the full origin story — respect the
  permission boundaries in the Soul Document (what's shareable vs internal).
• Authenticity ≠ transparency. Strategic vulnerability builds trust; oversharing
  destroys it.

Three-question authenticity test:

1. Does this reflect real values?
2. Do actions match these words?
3. Would I tell this even if no one was watching?

Repetition & the Story Train

• People need 7+ exposures before a story is remembered.
• Tell variations of the same core story weekly, not once.
• Gradual disclosure beats dumping: one element per post.
• The story is a living asset — each new milestone (new agent, new cycle gain)
  is a new chapter, not a new story.

Workflow Checklist

1. Write the one-sentence origin summary (problem + why you care).
2. Draft Act One with one specific, textured problem the audience recognizes.
3. Write Act Two (the insight) in 2-3 sentences — is it a Data/Cost/Observation moment?
4. Draft Act Three: one customer-level proof + one invitation.
5. Check the 60/30/10 ratio. Check vulnerability boundaries. Add MH resources if
   the content touches recovery.
6. Compress to target platform per the matrix.
7. Schedule as part of the story train (weekly variations, full version monthly on LinkedIn).