Marketing Hub · Internal
Hooks · v2 · 8 differentiated openers

Eight ways to start a Rightlander post.

Most posts will use one of these eight hooks. Each names the tone, three example openers you can adapt, what to do, what not to do, and which segments it serves best.

Jump to
01The named-number hook02The regulator-specific clock03The two-line contradiction04The customer story drop (anonymised)05The eight-years pattern recognition06The conference field-report take07The plainspoken Trackback hook08The 'what we saw this month' drop
01

The named-number hook

Open with one specific, ugly, real number — not rounded, not 'nearly', not 'roughly'.

Tone Bloomberg-terminal calm. Don't apologise for the number. Let it sit.
Three example openers
14,231 closed Telegram channels we're scanning today.
47 unauthorised bonus pages from one operator's affiliate network in 9 days.
0.7% of brand-bidding budget went to a single sub-affiliate. Until it didn't.
Do
  • Use the actual scanning number — not an estimate
  • Pair the number with the smallest unit of time (today, this week, in 9 days)
  • Lead with the number; the explanation comes second
Don't
  • Don't round to 14,000 — 14,231 is the post
  • Don't open with 'Did you know that…' — that signals filler
  • Don't bury the number in line three
Best for
iGamingTrading & CryptoBrand & General
02

The regulator-specific clock

Name the regulator, name the deadline, count the working days. Not 'soon' — '17 working days from today'.

Tone Compliance newsletter, not panic. Information density beats urgency.
Three example openers
FCA finfluencer enforcement window opens 03 June. 17 working days from today.
ANJ deadline for affiliate self-attestation: 30 September. Programmes that don't file lose their licence to operate.
MGA Q2 reporting closes Friday. Three of our customers filed yesterday. Two are still negotiating with their networks.
Do
  • Cite the specific regulator article or guidance reference
  • Convert the date into working days — buyers think in calendars, not dates
  • Name what happens if the deadline is missed
Don't
  • Don't write 'regulators are getting tougher' — name one
  • Don't predict what the regulator will do — describe what they've published
Best for
iGamingTrading & CryptoPharma & HFSS
03

The two-line contradiction

Sentence one is the conventional wisdom. Sentence two is the data that breaks it. White space between them.

Tone Confident but not smug. The reader should feel they spotted the contradiction with you, not because of you.
Three example openers
Smaller markets are safer.

They aren't. Bonus-attribution leakage is 3.4x higher in tier-3 markets than tier-1.
Compliance is a footnote in e-commerce.

Acer's three biggest affiliates were brand-bidding inside their CPM. The footnote was £120k a quarter.
FinProm killed the IB programme.

It didn't. It killed the IB programmes that didn't separate registration from acquisition. Two of our FX customers grew their IB book by 40% in Q1.
Do
  • Format as two paragraphs with a real line break
  • Make sentence one indistinguishable from a LinkedIn cliché
  • Make sentence two so specific it could only come from data
Don't
  • Don't use 'But here's the thing…' as the bridge — let the white space do the work
  • Don't soften sentence two with 'in some cases' — be specific or don't post
Best for
E-commerce EnterpriseTrading & CryptoTrackback · SME
04

The customer story drop (anonymised)

A real story, no name, one number, one decision. The pattern is the post — not the customer.

Tone Customer-success newsletter voice. First-person plural. Avoid 'one of our partners' — say what they were and what they did.
Three example openers
A UK-licensed iGaming operator asked us to scan one specific affiliate. We found 47 unauthorised bonus pages in 9 days. They terminated 3 sub-affiliates. Their next regulator email never came.
An FX broker on FCA permissions paused their finfluencer programme last month. We helped them turn it back on in 11 days. Net new IB registrations up 18% week-on-week since.
A pharma marketer with HFSS exposure asked us if their affiliate network was 'roughly compliant'. We mapped their full creator-to-claim chain. 6% of claims were out of scope. They had 14 days to fix it before MHRA's next review.
Do
  • Always open with what the customer was — not who
  • Use one number per story — pick the most surprising one
  • End with the decision the customer made, not the feature you sold
Don't
  • Don't say 'one of our customers' — say 'a UK-licensed iGaming operator'
  • Don't lead with the feature; the feature is in the verb
  • Don't reuse the same customer story twice in 90 days
Best for
iGamingTrading & CryptoE-commerce EnterprisePharma & HFSS
05

The eight-years pattern recognition

Sarafina/Ian-only. Open with the time horizon and the pattern that only shows up at scale.

Tone Substack essay, first person. Reflective. The reader should feel they're getting eight years of compressed observation in 200 words.
Three example openers
Eight years scanning affiliate content. The same compliance failure modes show up every cycle. The buyer changes; the failure doesn't.
I've watched three full enforcement cycles now. The pattern is always: regulator publishes → affiliates change channel → operators adjust → 18 months of quiet → new regulator publishes.
Eight years in, the question I get from every new compliance hire is the same: 'how do I know what I don't know?' That's the entire product, in one sentence.
Do
  • Always anchor in the time horizon — eight years, three cycles, four jurisdictions
  • Write in first person, past tense for the observation, present tense for the conclusion
  • End with a question or a single-sentence conclusion. No CTA
Don't
  • Don't write this from the company account — only Sarafina or Ian's personal account
  • Don't put a product name in the post body — keep the platform invisible
  • Don't add a 'thoughts?' at the end — the conclusion is the prompt
Best for
Brand & General
06

The conference field-report take

Posted from the floor, day of, with one named takeaway and one named disagreement.

Tone iPhone photo, not designed graphic. Authentic. Slightly opinionated. 80–120 words.
Three example openers
SBC Lisbon · day 1 · the operator panel agreed on a 'self-regulating affiliate ecosystem'. I disagreed. Self-regulation works in healthy markets. 70% of the affiliate web is unhealthy. Day 2 starts in 14 hours.
iGB Live · floor day · three product demos in a row showed AI-generated review sites as a feature, not a problem. We're scanning 14,000+ of these a week and shutting them down. The market hasn't decided yet which side it's on.
G2E Vegas · room 204 · saw a US tribal-operator panel where the chair said 'compliance is a cost centre'. The compliance head next to him visibly winced. Eight years in, that wince is the entire product positioning.
Do
  • Lead with the conference name and the room/day
  • Include one disagreement — not aggressive, but specific
  • Use the iPhone photo from the actual session — not a press shot
Don't
  • Don't post a 'we're at the booth' photo without an observation
  • Don't post until you have something to say — silence is fine
  • Don't use the company account — author with a personal account
Best for
iGamingE-commerce EnterpriseBrand & General
07

The plainspoken Trackback hook

Anti-enterprise. One short sentence. Picks a fight with the spreadsheet.

Tone Founder voice — but for SMEs, not investors. Plain English. The shortest possible version of the idea.
Three example openers
Stop running affiliate compliance from a spreadsheet.
Your first regulator email is the worst time to find out you don't have a system.
Twelve affiliates. One nerve-wracking inbox. Trackback fixes it for £49 a month.
Do
  • Keep the hook to one sentence — under 12 words ideally
  • Use the SME's vocabulary, not enterprise compliance language
  • Always include the price or the time-to-setup somewhere in the post body
Don't
  • Don't write 'enterprise-grade' more than once per post
  • Don't open with a feature list — open with the pain
  • Don't post Trackback hooks from Sarafina or Ian's account — keep this on Trackback channels
Best for
Trackback · SME
08

The 'what we saw this month' drop

Monthly, Nicole-led. Three observations from scanning data. No customer names. One number per observation.

Tone Industry-letter voice. Information-dense. The reader should screenshot at least one observation.
Three example openers
Three things we saw in scanning data this month: (1) Telegram-led acquisition up 31% in the iGaming Tier-2 markets. (2) AI-generated review sites now make up 22% of new affiliate domains we register. (3) Sub-affiliate hijacking is happening four hops down the chain — most operators don't scan past hop two.
May scanning summary: 14,231 closed channels under monitoring · 312 new bonus pages flagged · 47 customer enforcement actions supported · 1 emerging pattern in the Brazilian sportsbook market we'll write about next week.
What we saw in pharma scanning this month: 6% of HFSS-affiliate claims drifted out of scope mid-campaign. The drift always happens around the third creative refresh. We've started flagging it on day one of the refresh, not after.
Do
  • Three observations max — not five
  • Each observation has one number, no exceptions
  • End with one thing you'll write more about — drives the next post
Don't
  • Don't list everything you saw — the editing is the value
  • Don't include customer names, even anonymised, in the same post — split into separate stories
  • Don't make this monthly into 'monthly-ish' — the rhythm is the brand
Best for
Brand & GeneraliGamingPharma & HFSS
Copied