Cold outreach cadence
LiveThe 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
Long-form operating documents. The cadence, the copy rules, the measurement layer, the abandon thresholds. Read them once. Hire FORKOFF to run them. Receipts ship every Monday in the audit ledger.
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.
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
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
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
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
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
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
Layer 4 access, not mod-as-a-service. Three surfaces: monthly AMA, weekly retro thread, qualified alpha drops. Channel architecture, role gating, and the audit ledger anchored to qualified engagement.
▸ Anchor service · Founder funnel
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.
Founder reads the playbook, ships nothing. The cadence stays in a Notion doc for 90 days.
FORKOFF runs the playbook. Audit ledger ships every Monday with the receipt the playbook predicted.
Team copies one touch from the cadence and skips the other five. The compounding effect never lands.
Six touches ship in sequence with the copy rules and abandon thresholds. Nothing skipped.
Playbook copy is the lowest common denominator. ICP signal is missing, so the cadence converts at floor.
FORKOFF rewrites the cadence per ICP cohort using the validate-prospects gate before it ships.
Cadence runs forever on the same list. Reply rate decays under 1 percent and team keeps sending.
Open-rate floor, response threshold, and abandon rule wired into the dashboard before touch one.
Three sequencers, two CRMs, one spreadsheet. No single source of truth for what shipped vs replied.
One sequencer, one inbox health monitor, one weekly receipt. The audit trail 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 audit ledger and outcome-anchored milestones only ship under the engagement.
← scroll horizontally to see more →
| Feature | Playbook onlyRead it, run it yourself | FORKOFF execution + receiptsFORKOFF runs the playbook for you |
|---|---|---|
| Cost | Free read | Retainer · By application |
| Time-to-first-receipt | 60 to 90 days | 10 to 14 days |
| Audit ledger | ||
| Per-ICP rewrite | ||
| Abandon rule wired in | partial | |
| Weekly Monday receipt | ||
| Inbox health monitor | ||
| Founder voice capture | partial | |
| Refund logic on outcome floor |
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.
By application, capped at 5 engagements per quarter. Each playbook anchors to a canonical service page where the engagement runs. The audit ledger ships every Monday. Pair with founder funnel or answer engine optimization depending on the surface that wins your buyer.
Crypto conference sponsorship ROI 2026: first-party CPQL benchmark, repeat-sponsor rate, clip output, time-to-meeting across the FORKOFF H1 2026 client cohort.
Read
The Q2 2026 debate on crypto conference ROI broken down with first-party math: when the same room delivers 50x or 0.1x, the 4 inputs that flip it, and the
Read
How to host a side event at a crypto conference. 30-day playbook (T-30 to T-0) across 5 lanes plus cost bands, sponsor mechanics, Luma funnel, 8 failure modes.
Read