Skip to content
FORKOFF
Playbooks · The exact systems FORKOFF runs

The operating playbook forcold outreach cadence.

Long-form operating documents. The cadence, the copy rules, the measurement layer, the abandon thresholds. Read them once. Hire FORKOFF to run them. Proof ship every Monday in the audit ledger.

By application · 5 engagements per quarterDocumentation deliverables · execution by FORKOFFDubai HQ · Operating from DIFC
7Playbooks published
5Channel anchors in progress
By applicationEngagements that run them
Dubai HQOperating from DIFC
Seven playbooks live · five in progress

The systems behind every FORKOFF engagement.

Each playbook is the operating manual for one channel anchor. Cold outreach earns the first reply. Founder-led growth earns ongoing trust velocity. Answer engine optimization earns LLM recall. Read the playbook. Hire FORKOFF to run it.

Cold outreach cadence

Live

The D1 / D3 / D5 / D7 / D9 / D11 six-touch cadence FORKOFF runs across LinkedIn, email, and Twitter. Open-rate floors, response thresholds, copy rules, and the exact stack.

▸ Anchor service · Founder funnel

Open playbook

Founder-led growth

Live

Founder voice as the operating distribution channel. Voice capture cadence, content factory, distribution map across LinkedIn / Twitter / podcast / email, and the measurement layer.

▸ Anchor service · Founder funnel

Open playbook

Answer engine optimization

Live

Citation engineering for ChatGPT, Claude, Gemini, and Perplexity. Per-LLM citation measurement, schema.org playbook, llms.txt, and the parasite ladder that earns answer-engine recall.

▸ Anchor service · Answer engine optimization

Open playbook

LinkedIn distribution cadence

Live

Five posts a week. Carousel and native video weighted. Engagement loops, executive comment squads, account-based amplification, and the paid threshold gate.

▸ Anchor service · LinkedIn marketing

Open playbook

Twitter content stack

Live

Three-tier content factory. Anchor threads, quote tweets, and long-form replies. Founder voice capture, KOL retweet stacks, the Hormozi clipboard, and founder-led PR loops.

▸ Anchor service · Twitter marketing

Open playbook

Podcast distribution

Live

12-episode pop-up default. Guest curation framework, broadcast production stack, RSS / YouTube / clips distribution map, and the 8 to 14 derivative repurposing factory.

▸ Anchor service · Podcast

Open playbook

Discord ecosystem activation

Live

Layer 4 access, not mod-as-a-service. Three surfaces: monthly AMA, weekly retro thread, qualified alpha drops. Channel architecture, role gating, and the weekly report anchored to qualified engagement.

▸ Anchor service · Founder funnel

Open playbook
Why playbooks fail without an operator

Reading the playbook is not the system.
Running it is.

Five failure modes FORKOFF observes when a team reads the playbook but cannot ship the cadence in production. The fix column is the operating model FORKOFF runs by default.

playbook-without-execution.csv
  • Row 01
    Reject reasonPlaybook only, no operator
    Audit detail

    Founder reads the playbook, ships nothing. The cadence stays in a Notion doc for 90 days.

    FORKOFF fix

    FORKOFF runs the playbook. Audit ledger ships every Monday with the receipt the playbook predicted.

  • Row 02
    Reject reasonCherry-picked tactics, no system
    Audit detail

    Team copies one touch from the cadence and skips the other five. The compounding effect never lands.

    FORKOFF fix

    Six touches ship in sequence with the copy rules and abandon thresholds. Nothing skipped.

  • Row 03
    Reject reasonGeneric copy, no ICP fit
    Audit detail

    Playbook copy is the lowest common denominator. ICP signal is missing, so the cadence converts at floor.

    FORKOFF fix

    FORKOFF rewrites the cadence per ICP cohort using the validate-prospects gate before it ships.

  • Row 04
    Reject reasonNo measurement, no abandon rule
    Audit detail

    Cadence runs forever on the same list. Reply rate decays under 1 percent and team keeps sending.

    FORKOFF fix

    Open-rate floor, response threshold, and abandon rule wired into the dashboard before touch one.

  • Row 05
    Reject reasonTooling sprawl, no audit trail
    Audit detail

    Three sequencers, two CRMs, one spreadsheet. No single source of truth for what shipped vs replied.

    FORKOFF fix

    One sequencer, one inbox health monitor, one weekly receipt. The audit trail is the deliverable.

5 / 5 patterns auditedSource: FORKOFF engagement intakePre-engagement diagnostic
Playbook only vs FORKOFF execution

The playbook is the manual.
The proof is the deliverable.

Two ways to use a FORKOFF playbook. Read it and run it yourself, or apply for the engagement and let FORKOFF run it. The cadence is the same; the verified proof and outcome-anchored milestones only ship under the engagement.

← scroll horizontally to see more →

FeaturePlaybook onlyRead it, run it yourselfFORKOFF execution + receiptsFORKOFF runs the playbook for you
CostFree readRetainer · By application
Time-to-first-proof60 to 90 days10 to 14 days
Audit ledger
Per-ICP rewrite
Abandon rule wired inpartial
Weekly Monday proof
Inbox health monitor
Founder voice capturepartial
FAQ · 7 questions

Frequently asked questions

How do I read the FORKOFF playbooks?

Each playbook is a long-form operating document. TL;DR at the top, table of contents, then 10 to 15 sections of the exact system FORKOFF runs. Read top to bottom once, then return to the section that matches the engagement phase you are in.

Can I license a playbook for my team?

The playbooks are public. The execution is gated. If your team wants the playbook plus FORKOFF execution, the engagement is by application, capped at 5 engagements per quarter, with a 90-day retainer minimum.

Can FORKOFF run the playbook for us?

Yes. That is the default model. FORKOFF runs the cadence, ships the proof, and the founder reviews the audit ledger every Monday. The playbook is the operating manual; the engagement is the operator.

How often do you update the playbooks?

Quarterly. When a tactic stops carrying weight in production, it gets pulled. When a new pattern earns 3 proof across 3 engagements, it gets added. The current revision date is at the top of each playbook.

Why only seven playbooks?

These are the seven channel anchors that earn outcome floors across every FORKOFF engagement. Five more channel-anchor playbooks are in progress and will ship as the proof behind them clear the 3-engagement threshold.

Do the playbooks reference real FORKOFF engagements?

The patterns are anonymized. Named-client proof stay in the deal room on application. The shapes, abandon thresholds, and copy rules in the playbooks are the exact ones FORKOFF runs in production.

Where does each playbook anchor in the FORKOFF service stack?

Cold outreach and founder-led growth anchor to the founder funnel service. Answer engine optimization anchors to the AEO service page. Each playbook links into the canonical service page that runs the engagement.

Apply for the engagement

Read the playbooks.
Apply to have FORKOFF run them.

By application, capped at 5 engagements per quarter. Each playbook anchors to a canonical service page where the engagement runs. The verified proof ships every Monday. Pair with founder funnel or answer engine optimization depending on the surface that wins your buyer.