All articles|
EthumEthum Knowledge Base
Log in
SOP

CONT-EXP-033: Pascal — Personal Journey vs Business Framework

About EthumLINKEDIN PERSONAL PROFILE

Status: Active X-SOP Created From: CONT-EXP-033: Pascal — Personal Journey vs Business Framework Owner: Haider Zaidi (Content Architect — Pascal LinkedIn + Strategy) Enforced By: Nabeel Abbas Review Cycle: Every 90 days ═══════════════════════════════════════════════════

WHAT WORKS ──────────────────────────────────────────────────

  1. Personal journey posts (Pascal's origin story, founder lessons, behind-the-scenes building ETHUM) outperformed business framework posts on engagement, comments, and inbound DMs because personal LinkedIn rewards human stories more than tactical playbooks — founders connect with people, not with frameworks.

  2. Founder-vulnerability moments (failures, pivots, hard decisions, lessons from mistakes) drove the highest engagement of any post type because they break the polished-founder pattern and invite readers to identify with Pascal's actual journey.

  3. Journey content generated more qualified inbound DMs than framework content because readers want to work with Pascal — not just learn from frameworks. Story builds trust; frameworks build authority. Trust converts faster.

EXACT PROCESS (Replicate Every Time) ────────────────────────────────────────────────── Step 1 — Journey Content Categories (Use These)

Origin Story Posts "I started ETHUM after watching 12 founders die from broken outreach systems. Here's what I saw…"

Failure / Pivot Posts "I burned $40K on a list-buying strategy in 2023. The lesson cost more than the money."

Behind-the-Scenes Posts "What it actually looks like to run 70 experiments a week — the messy version, not the LinkedIn version."

Hard Decision Posts "I let go of a $20K/month client last month. Here's why."

Founder Lessons (Pascal's POV) "After 18 months building ETHUM, the one thing I'd tell my younger self about hiring…"

Step 2 — The Story Structure (4-Part Framework)

Part 1: Hook (1–2 lines) Specific scene or contrarian statement. "I almost shut down ETHUM in month 4."

Part 2: Tension (3–6 lines) The struggle, the moment, the stakes. What was at risk. What hurt. What didn't work.

Part 3: Resolution (2–4 lines) What changed. The decision. The pivot.

Part 4: Insight (1–2 lines) The lesson — short, sharp, transferable.

Length: 150–250 words. No filler. End with a question CTA (per CONT-SOP-015).

Step 3 — Content Mix on Pascal's LinkedIn

✅ 60% Personal Journey content (this SOP) ✅ 30% Business Framework content (tactical, ICP-led) ✅ 10% Reactive / signal-led posts (opinions, takes)

Never go below 50% journey on Pascal's personal page.

Step 4 — Tone Rules (Non-Negotiable)

✅ First person ("I", "me", "we") — never third person ✅ Specific numbers ("$40K", "12 founders", "month 4") ✅ Real moments — date, place, decision, consequence ✅ Vulnerability with a lesson — never vulnerability alone ✅ Conversational — write how Pascal actually talks ❌ No corporate-speak ("leverage," "synergy," "stakeholders") ❌ No fake humility ("humbled to share…") ❌ No vague stories without a number or specific moment ❌ No oversharing (personal life, family, anything off-brand)

Step 5 — Source Material (Where Stories Come From)

✅ Weekly 15-min interview with Pascal (Haider runs it) ✅ Pascal's Slack messages, voice notes, off-the-cuff comments ✅ ETHUM internal wins / losses (with Pascal's sign-off) ✅ Pascal's pre-ETHUM career anecdotes ✅ Lessons from current client work (anonymized)

Step 6 — When to Use Journey vs Framework

Use Journey content for: ✅ Mondays (audience wants narrative to start the week) ✅ Pivotal company milestones ✅ Reactions to industry events / failures ✅ Founder day / anniversary moments ✅ Any post that needs comments + DMs over saves

Use Framework content for: ❌ Save-rate posts (frameworks save better than stories) ❌ SEO-friendly LinkedIn search topics ❌ Comment threads where Pascal wants to be cited as expert

QUALITY CONTROL ────────────────────────────────────────────────── ✅ Story has a specific moment (date, number, scene) ✅ Story follows the 4-part structure (Hook → Tension → Resolution → Insight) ✅ First-person POV throughout ✅ Vulnerability is paired with a lesson — never standalone ✅ 150–250 words, no filler ✅ Ends with question CTA (per CONT-SOP-015) ✅ Pascal has reviewed and approved the story before posting ✅ Logged in PASCAL_LINKEDIN_PERFORMANCE.md (engagement, comments, DMs)

EXPECTED RESULTS (Per Post) ────────────────────────────────────────────────── Conservative: 30–50% higher engagement than framework posts, 2x more comments, 1.5–2x more inbound DMs, deeper conversations in comments (5+ replies per thread) Optimistic: 70%+ engagement lift, 3x comment volume, qualified inbound DMs from founders asking to work with Pascal, viral post potential (500+ interactions, 50K+ impressions)