Pattern library

Operator-led system: choose a job (Relate → Reframe → Prove → Invite → React), pick a pattern and format, then apply it when creating content. Reframe replaces generic “explain” — it is the authority layer.

Core thesis — Most teams don't have a tool problem — they have a decision → execution gap.

Relate → Reframe → Prove → Invite

Light Reach’s funnel: reach the pain, shift the mental model, show visible workflow change, then a bounded next step. React is for timely takes without drifting from thesis.

Search patterns

Goal

Format

26 patterns

Format execution

Demo
Outcome → Workflow → Result
New content with format
Workflow breakdown
Define outcome → Remove decisions → Assign ownership → Execute → Tighten
New content with format
Operator memo
pain → diagnosis → why teams get this wrong → clearer model
New content with format
Use case stack
Don't say: AI improves productivity. → Say: generate PRD → tasks → owners → workflow → fewer handoffs.
New content with format
Launch (Light Reach version)
This removes N decisions from your workflow. → This turns meetings into execution. → This replaces N steps with one system.
New content with format
Proof + CTA combo
show result → one-sentence explanation → CTA immediately after
New content with format

Weekly rhythm

Day 1: Relate — Reach and recognition
Day 2: Prove — Trust through visible transformation
Day 3: Reframe — Authority and model shift
Day 4: Relate — Repeat recognition
Day 5: Invite — Capture response and signal
Day 6: Prove — Reinforce trust
Day 7: React — Relevance without identity drift

Product shortcuts

compress

Patterns: Cost compression, Tool illusion, Step reduction, Feature skepticism, Output transformation

foundry

Patterns: Translation layer, Ownership gap, Before / after, Workflow collapse, Execution loop

actionary

Patterns: Meeting → action transformation, Ownership gap, Step reduction, Workflow collapse, Diagnostic ask

Content principles

Start with workflow pain, not generic AI commentary.
Use operator language: shipping, ownership, handoffs, friction, ambiguity, execution, decision load.
Show transformation whenever possible.
Explain less, show more (especially short-form).
Every post should ladder upward: relate → authority → proof → invite.

TikTok / Reels

Outcome → Workflow → Result

Show first, explain second.
Minimal, sharp text overlays.
Visual proof whenever possible.

X

Insight → Punchline

One idea only.
Compress hard.
Avoid explanation unless necessary.
Write for repostability.

Context → Mechanism → Business impact

Slightly longer setup is okay.
Bullets improve scanability.
Always explain team impact.
Pair proof with business consequence.

Publish QA

Clarity

Is the problem legible in the first line or first seconds?
Is the hook sharper than the explanation?

Positioning

Does this sound like Light Reach, or generic B2B SaaS?
Is the decision → execution gap visible?

Proof

Is there visible or concrete proof?
If not, is the post at least delivering a strong reframe?

Platform fit

Show-first enough for TikTok?
Compressed enough for X?
Contextual enough for LinkedIn?

Conversion

If there is a CTA, is it bounded and useful?
If there is no CTA, is the post still strategically valuable?

What to avoid

Generic AI commentary
Feature lists without workflow relevance
Vague productivity advice
Motivational posting without proof
Over-explaining simple ideas
Using every platform the same way
Reacting to every trend without a systems angle