type: output format: text-post date: 2026-05-07 status: ready-to-publish platform: linkedin, facebook, instagram concept_source: angle-expansion campaign: delegation-infrastructure

Delegation Infrastructure — Organic Batch 002

Generated: 2026-05-07 Concept: Three additional angles into the Delegation Vacuum campaign, complementing batch 001 and the article (delegation-vacuum.html). Each post enters from a reader perspective the article doesn't directly address.

Source: delegation-infrastructure-content-2026-05-03.md (proof points, voice), delegation-vacuum.html (frame, vocabulary, central reveal that examples sit in finished deliverables nobody opens), organic-batch-001.md (avoiding angle overlap).

LinkedIn Post — The Deliverables Already Exist

You've documented your standard.

Not in an SOP, not in a training doc.

You've documented it in seventy completed deliverables — sitting in project folders nobody opens.

Each one carries your decision patterns: the structure you default to, the trade-offs you accept without thinking.

You close each engagement, file the deliverables, and start the next one from a blank page.

When your team asked for examples, you couldn't think of one to send. The standard you've held sits unread.

Extract them into a system and the production set takes 45 minutes — work that used to take days, with the standard intact and no weekend rebuilds.

The standard exists. You've already produced it seventy times.

(Full pattern in the first comment.)

Framework

Recognition reversal. The reader (practice owner) believes "I haven't documented my standard yet." The post reveals: you have — seventy times — but it sits in a form your team can't access. Pulls the article's central reveal forward as the post's spine.

Voice Check

• [x] Hook stops scroll — "You've documented your standard." Direct second-person claim that surprises.
• [x] Single POV throughout (second-person, reader = practice owner)
• [x] Single protagonist (the reader)
• [x] AOS vocabulary — standard, system, production set, decision patterns, structure, trade-offs
• [x] Avoids banned words — no coaching, mindset, journey, transformation
• [x] One CTA — first-comment link
• [x] Aligns with article — "The standard exists. You've already produced it seventy times" echoes the article's anchor reveal ("Seventy examples of his standard sat in folders nobody opened")

Copy QC Notes

• Twinning (Pattern 1): none. "Not in an SOP, not in a training doc" is parallel emphasis (single sentence with comma), not negation-correction.
• Mirror reversal: "documented your standard" / "documented it in seventy" — same word repeated for the reveal beat (intentional structural punch), not Pattern 1 reversal.
• Three-beat parallels (Pattern 2): "the structure you default to, the trade-offs you accept without thinking" — two-item list, under threshold.
• Identical openers (Pattern 11): "You've documented" appears twice in the opening. Two iterations form the reveal arc; not three.
• Dramatic beats: "Not in an SOP, not in a training doc." Single sentence with comma — counts as one beat, within limit.
• R1 End Strong: every sentence ends on content word (standard, doc, opens, thinking, page, send, unread, rebuilds, done, times, comment).

Facebook Post — The Hiring Trap

You're about to hire to fix this.

The team member keeps returning work that misses what you'd have built. The obvious move is to bring on someone more senior.

That hire is going to fail for the same reason the last two did.

The infrastructure doesn't exist yet.

There's no documented standard. The examples sit in finished deliverables nobody opens. The quality bar lives in your head, where no one else can read it.

A new hire walks into the same vacuum. Six months in, you'll be rebuilding their work over the weekend too.

I worked with a firm owner who hired three times. Each round, more senior. Same outcome.

We extracted 70+ examples from his strongest engagement and built them into a production system with a quality bar embedded in it.

First test on a new client: 45 minutes for the full set. The next hire has something to walk into.

(Wrote up the pattern from the engagement — first comment if you want it.)

Framework

Problem-Agitate-Solve. Hook names an active reader decision (about to hire). Agitates (the next hire walks into the same vacuum). Solves (extraction). Soft CTA.

Voice Check

• [x] Hook stops scroll — names a decision the reader is currently considering
• [x] Sounds like creator — pattern-revealing, no sales language
• [x] AOS vocabulary — vacuum, standard, examples, infrastructure, production system, quality bar
• [x] Avoids banned words
• [x] One CTA — first-comment link
• [x] Aligns with article — "examples sit in finished deliverables nobody opens" directly echoes the article's central reveal

Copy QC Notes

• "There's no documented standard. The examples sit in finished deliverables nobody opens. The quality bar lives in your head, where no one else can read it." — three short clauses with varied openers (There's no / The examples / The quality bar). Different subjects, different verbs. Pattern 11 safe (not 3 identical openers).
• "The infrastructure doesn't exist yet." — clean concrete claim. Replaces earlier "The thing they're being hired into doesn't exist" which used a placeholder noun and asked the reader to fill in the blank.
• "We extracted 70+ examples..." — direct verb construction. Replaces earlier "What fixed it was extracting..." which was conversational filler.
• "Each round, more senior. Same outcome." — short pair, intentional rhythm.
• No twinning, no mirror reversal.

Instagram Post — Inheritance / Step-Away Cost

You can't sell what's in your head.

You've built a practice that depends on you being in every Zoom session.

Every deliverable starts on your screen. Every quality call lands on your shoulders. The weekend rebuilds happen because nothing leaves the building without you watching and reworking it.

The day you try to step away — vacation, sabbatical, sick week, sell — the practice can't run.

One firm owner I worked with had spent years producing every engagement deliverable from scratch — assessments, reports, recommendations, all from his head. Seventy completed deliverables sat unread in his project folders. We extracted them into a production system with a quality bar embedded in it. First run with a new client: 45 minutes. Work that used to take days.

The practice now has a documented standard. A team can run the engagement without him on the call.

Infrastructure is what was missing.

Save this for the next time you tell yourself you'll document it later — full piece linked in bio.

Hashtags

#practiceowner #delegation #businesssystems #operationalexcellence #consultinglife #advisorypractice #businessinfrastructure #systemsthinking

Framework

Contrarian opener → cost stack → step-away list → proof → resolution → save-CTA + bio link.

Voice Check

• [x] First line stops scroll — "You can't sell what's in your head." Bold claim, content-word ending
• [x] Sounds like creator — direct, no fluff, save-worthy reframe
• [x] AOS vocabulary — system, standard, production system, infrastructure, deliverable
• [x] Avoids banned words
• [x] One CTA — save + bio link
• [x] Aligns with article — "Seventy completed deliverables sat unread in his project folders" directly mirrors the article's central reveal ("Seventy examples of his standard sat in project folders his team never opened")

Copy QC Notes

• "Every deliverable starts on your screen. Every quality call lands on your shoulders. The weekend rebuilds happen because nothing leaves the building without you watching and reworking it." — two "Every X" openers, third pivots to "The weekend rebuilds." Pattern 11 safe (under 3 identical openers).
• "vacation, sabbatical, sick week, sell" — four-item enumeration in dashes. Escalating consequence (everyday → planned → unplanned → extreme). Not parallel clauses.
• "assessments, reports, recommendations" — three-noun list inside a single sentence. Enumeration, not parallel clauses.
• Proof paragraph varied from FB: opener "One firm owner I worked with had spent years producing..." (focuses on production repetition) vs FB's "I worked with a firm owner who hired three times" (focuses on hiring repetition). Different sentence structure (period-pair on FB, comma-list on IG). No verbatim echo.
• Dramatic beats: "Infrastructure is what was missing." Functions as the post's conclusive beat (full sentence, not fragment). Within limit.
• No twinning, no mirror reversal.
• R1 End Strong: every sentence ends on content word (head, session, screen, shoulders, it, run, head, folders, it, minutes, days, standard, call, missing, bio).

Image Files

• LinkedIn: screenshot-02-delegation-infrastructure-linkedin.html — AOS brand (1200x1200). "Your standard is documented." / "Locked in folders no one studies." Eyebrow: ALREADY DOCUMENTED.
• Facebook: screenshot-02-delegation-infrastructure-fb.html — CYP brand (1080x1080). "Hiring won't fix this." / "The standard still lives in your head." Eyebrow: THE HIRING TRAP.
• Instagram: screenshot-02-delegation-infrastructure-ig.html — CYP brand (1080x1350). "You can't sell what's in your head." / "Every Zoom session still needs you." Eyebrow: WHAT DOESN'T TRANSFER.

Each image text passes the screenshot test — both lines work as complete claims without post context. No pronoun dependency on the post.

Cross-Asset Congruence Check

No contradictions across batches or with article.

Next Steps

• [ ] Schedule posting cadence — stagger across platforms, do not publish same day as batch 001
• [ ] LinkedIn first comment: link to delegation-vacuum.html once live
• [ ] Facebook first comment: same
• [ ] Instagram bio: update link to delegation-vacuum.html for campaign duration
• [ ] Optional: revisit closes in Phase 7 evergreen assembly to tee up specific article reveals