Articulate. The GTM Three offers, written The table The rules Arm A Arm B Arm C Before you send
Copy + wireframes · Gold Digger

Three offers, written

Nine emails and three landing pages. Every merge field is resolved in code and checked against the 982 loaded agents — nothing here merges to an empty string on send. Companion to the GTM.

0 · The three, side by side

Everything below in one table. Email above, landing page beneath, and the objection each arm actually has to survive.

A — Dead Pipeline Report B — Extract, AED 500 C — Pay me out of the deal
Offer A one-page report on his own twelve-month transaction record. Free. No product named anywhere. Twenty minutes on his phone, dormant WhatsApp enquiries pulled into a classified list. AED 500, list shown before payment. The same work, free. AED 2,500 if a name off the list closes a deal. Twelve months, capped at three.
What it tests Whether the data asset is the business. Whether the wedge is real. The untested hypothesis the plan rests on. Whether the aligned, recurring model has pull — closest arm to the AED 3–5k objective.
The email
Subject your last three months
No number, so nothing in it can be wrong.
how many people are in your phone?
A question he can't answer and now wants to.
no fee unless it makes you money
The offer is the subject. Nothing withheld.
Hook
line one, merged
Identical across all three arms — one of four resolved variants: "You closed 3 sales in the spring. Nothing since April. Same 56 listings on the board." Holding the hook constant is what makes the offers comparable.
The turn
the sentence that earns the CTA
"It's free and there's nothing attached to it. I want to know whether the report is any good, and you're better placed to tell me than I am." "Extract reads those threads on your own phone, with you watching… AED 500, against AED 31,533 on a deal." "That part costs you nothing. Not a trial and not a discount. Nothing."
CTA One WhatsApp deep link, tokenised per agent. No second link, no tracked button, no calendar. The tap is the metric — opens are meaningless under Apple Mail Privacy Protection.
The objection "Why is this free — and how do you know my sales record?" Reciprocity without a reason reads as bait, and a stranger citing your numbers is unsettling. "You want access to my phone." His WhatsApp holds client budgets, passport scans, deal terms. This is the biggest single objection in the campaign. "Too good — what am I signing?" An unbounded obligation to a stranger is frightening, however generous the headline.
Handled by Scale defuses it: "every agent in Dubai — twelve months of it, 69,746 deals". Not you specifically, not privately. Then the honest reason it's free: he's testing the report. Placement, not wording. "On your own phone, with you watching… nothing leaves the device and I keep no copy"before the price, never after. The cap, stated in the same breath as the fee: "Three deals maximum, so the most this can ever cost you is 7,500." Plus: one page, signed, before anything is plugged in.
The landing page
URL /report?t={{token}} /extract /deal
Headline "{{first_name}} — your twelve months." "There is a year of buried enquiries in your phone." "I'll do it for nothing. Pay me if it pays you."
Above the fold His own three stats — sales, listings, last recorded sale. Nothing asked. The privacy strip, then price and reversal. Privacy comes first, always. The four terms in plain lines: nothing up front · 2,500 a deal · 7,500 maximum · nothing if nothing closes.
Page CTA "WhatsApp me for the rest" — after the fold, once only. "WhatsApp me" — above the fold and repeated after objections. "WhatsApp me" — above the fold and after the agreement.
Page objection "What are you holding back, and why?" "Is this legal? Do you see my contacts? Does it work on my phone? What if it finds nothing?" "Where's the catch buried?"
Handled by Holding back the analysis, not his data. His record is all on the page; the three recommendations are the only thing worth a conversation, and that's said out loud. Answered flat, in a list, in his words — plus the sample output shown redacted, and the consent form offered in advance rather than produced on the day. Publishing the actual one-page agreement on the page, readable, before anyone has to ask for it.
Proof carried The data itself is the proof. No case study needed. Empty — blocked on Paul's three numbers. The weakest-supported arm, on the one that asks for money. "69,746 Dubai transactions read, 11,787 agents scored" — why he'd take the bet.
Delivery load if it works None. The report generates from data on disk. An operator, per phone, every time. An operator per phone — and the paperwork.
Biggest risk Reads as content marketing, or reads as creepy. The hook sentence is the dial. Asking a stranger for money with no proof attached. Attribution. He closes and doesn't tell you.

1 · What is held constant

Same 982 Dubai agents. Same three-email cadence — day 0, day 4, day 10. Same signature. Same call to action: a WhatsApp deep link carrying a per-agent token, so the tap joins back to the Airtable row and tells you which arm produced it.

What varies is one thing only: the offer. Arm A asks for no money and sells nothing. Arm B asks for AED 500 for a product. Arm C asks for nothing now and a share later. If the arms differed on subject line, tone, length and offer all at once, a result would tell you nothing about which lever moved.

2 · What can actually be merged

This is the part that quietly kills campaigns. The transaction fall-off is the strongest line available — and it exists for 283 of the 982. Writing copy that assumes it, then finding at send time that most of the list renders a blank, is how a good idea ships broken.

So every hook resolves in pipeline/merge.py into one of four variants, and each has a line that is literally true of the agent receiving it and checkable by them. No estimates, no rates, no market averages.

VariantCountConditionThe line it produces
zero144Two or more sales in the prior quarter, none since"You closed 3 sales in the spring. Nothing since April. Same 56 listings on the board."
fell139Sales fell quarter on quarter"You closed 2 sales in the spring and 1 since. Same you, same board, fewer deals."
quiet318A last sale date exists but no clean window comparison"Your last recorded sale was May. You've got 36 live listings waiting on the next one."
generic381No transaction record — listings and tenure only"You've got 95 live listings in Damac Hills, and 14 years of Dubai behind you."
The variants are evenly spread across arms by construction — arm A gets 51 zero / 43 fell / 108 quiet / 126 generic, and B and C are within a handful of that. No arm draws a stronger hook than another, so a difference in reply rate is a difference in offer.

Two other coverage facts worth knowing before you read the copy. Only 61% have a commission figure, so anywhere a number appears there is a no-number alternative — {{commission_clause}} resolves to either "against AED 31,533 on a deal" or "against one deal". And two agents of 982 have no usable first name; those greet as "Quick one —" rather than an empty comma. Twenty-one more arrive in block capitals from the portal and are title-cased on the way out.

3 · Rules for all three

4 · Arm A — the Dead Pipeline Report

Mechanism

Reciprocity, and curiosity about oneself

We know something true and slightly uncomfortable about this agent that he has never seen written down. We tell him one line of it for free, ask for no money, and offer the rest. The only cost of finding out is a WhatsApp message.

The frame is "help me test this", not "let me sell you this". It is disarming, it is true, and it makes replying a favour rather than a purchase — which is a much smaller thing to ask of a man whose income just fell.

Subject line: your last three months

Lower case, no capitals, no number, no pitch. It is true for all four hook variants, it reads like a message from someone who knows him, and there is nothing in it that can be wrong. The obvious alternative — putting the number in the subject — is rejected for the same reason the invented "2,000 contacts" was: the moment a checkable claim sits in the subject line, being wrong costs you the open.

The sequence

The line to watch is the hook. Telling a man a stranger has been reading his sales record is either compelling or unsettling, and there is very little in between. "I've been pulling the public transaction record for every agent in Dubai" is doing the defusing — it says everyone, publicly, not you specifically, not privately. If Arm A underperforms, that sentence is the first thing to rewrite, not the offer.

The page — /report?t={{token}}

The email promises a report. If the tap lands on a product page, the promise breaks and the arm is contaminated by Arm B. This page shows the agent his own data, rendered live from Airtable by token, and asks for nothing above the fold.

Mobile · above the fold
BarGold Digger · Dubai transaction records
H1Nourossama — your twelve months.
StandfirstEverything below is from the public record. You gave us nothing to build it.
Three stat cardsSales, 12 months · Live listings · Last recorded sale
fold — no ask above this line
Bar chart — your sales by month
Mobile · scroll
SectionWhere you sit in Zabeel — your rank against 11,787 Dubai agents, by transactions and by board size
SectionThe gap — listings held vs deals closed. Yours, and the market's.
Blurred · "Three things I'd do with this"
Unlock lineThe last section is the only part I won't put on a public page.
Single CTAWhatsApp me for the rest →
FooterWho I am · Articulate, Dubai · DED licence · No data was collected to build this

Why the last section is held back. Everything above it is data — impressive, but it does not require a conversation. The recommendations do, and they are the only thing on the page worth a WhatsApp message. Holding back the analysis rather than the numbers is also the honest way round: you are not hiding his own record from him to extract a lead.

Build note. The tokenised version needs a Worker reading Airtable by Send Token — half a day, and the Events table is already designed to receive the page view and the tap. A static fallback works for round one: one page, one real worked example, same CTA. It will convert worse, and the difference between the two is itself worth measuring if you have the appetite for a fourth cell.

5 · Arm B — Extract at AED 500

Mechanism

A small definite price against their own large number

Five hundred dirhams is a decision a working agent can make without asking anyone. Set against the median commission on this list — AED 36,912, computed from their own sales — it stops being a purchase and becomes a rounding error.

The risk it carries is the privacy objection, and no sentence removes it. What removes it is the delivery model: on your phone, you watching, nothing leaves the device. Say that before the price, not after.

Subject line: how many people are in your phone?

It asks a question he cannot answer and will now want to. It contains no claim, so nothing in it can be checked and found wrong. And it sets up the guess — the gap between what he thinks is in there and what is actually in there is the entire product demonstration, and it costs nothing to run.

The sequence

Two lines from the earlier draft are deliberately not here. "Commission here is 2%" — telling a Dubai agent what Dubai commission is reads as an outsider writing, which undercuts everything else. And "if it comes back thin you've lost ten minutes" — risk reversal should remove the failure case, not plant it. Also gone: the invented Tuesday-enquiry anecdote, replaced with a framing that is true of everyone and asserted of no one.

The page — /extract

Mobile · above the fold
BarGold Digger
H1There is a year of buried enquiries in your phone.
Privacy strip — above the fold, alwaysOn your phone. You watch the screen. Nothing is uploaded, nothing is kept, you hold the drive at the end.
Price + reversalAED 500 · You see the list before you pay
CTAWhatsApp me →
fold
Mobile · scroll
Three steps1 · Plug in, twenty minutes · 2 · Watch the list build · 3 · Take the drive, pay if it's worth it
Sample output — the list, redacted
Reference block — BLOCKED"Paul Lunghis at BossCouple. He guessed X. It found Y. Z were still live. He'll take your call."
Objections, answered flatIs this legal · Do you see my contacts · iPhone or Android · What if it finds nothing
CTA repeatWhatsApp me →
FooterArticulate, Dubai · DED licence · Consent form, in advance
The reference block is the only empty region on any of these three pages, and it is on the arm that asks for money — where proof matters most. It is blocked on one phone call to Paul. Until it fills, Arm B is the weakest-supported arm and should be read as testing the price, not the product.

6 · Arm C — pay me out of the deal

Mechanism

The sender takes the risk

Every other message in that inbox this morning wanted money or a meeting. This one wants neither, and says so in the first line. That is the fastest available way to be read as something other than a vendor.

It also tests the commercial model directly rather than through a proxy. If agents will agree a share, the same shape scales to a brokerage — and a brokerage on a share is the recurring revenue this whole exercise is for.

Subject line: no fee unless it makes you money

The terms — decide these before a single email sends

A vague share is worse than no offer. It sounds generous, then becomes an argument with the first person who says yes. The version below is picked because it is collectible without auditing anybody's commission.

TermSettingWhy this and not the obvious alternative
Up frontNothingNot a trial, not a discount. The whole mechanism collapses if there is a number in the first half of the sentence.
TriggerA deal closes with a name that came off the listNot "a lead", not "a viewing" — a closed deal. Unambiguous, and it is the only event both sides can see.
FeeAED 2,500 per closed dealA flat fee, not a percentage. Ten per cent of commission requires him to show you the commission, which means an argument about the number and a reason to hide it. A flat fee needs no audit and reads as cheaper against the AED 36,912 median.
WindowTwelve monthsLong enough to cover a real Dubai sales cycle. Longer starts to feel like a lien on his business.
CapThree deals — AED 7,500The cap is for him, not you. An uncapped obligation to a stranger is frightening; a known maximum is a decision. It costs you the tail and buys you the yes.
PaperworkOne page, before anything is plugged inDoubles as the consent form the extraction needs anyway. Two problems, one signature.
The honest weakness: attribution. If a name from the list buys four months later through his own follow-up, does he tell you? Between strangers, sometimes not. The fee is set low enough that paying it is easier than arguing, and the cap is set so the honest answer is never expensive — but this arm relies on goodwill in a way the other two do not, and that is a real cost of running it, not a detail to paper over.

The sequence

The page — /deal

On this page the terms are the hero. Anything that looks like a sales page undermines the one thing the offer has going for it, which is that it does not sound like a sales page.

Mobile · above the fold
BarGold Digger
H1I'll do it for nothing. Pay me if it pays you.
The terms — plain, four lines, above the foldUp front: nothing · If a name closes: AED 2,500 · Maximum ever: 7,500 · If nothing closes: nothing
CTAWhatsApp me →
fold
Mobile · scroll
What I actually doTwenty minutes on your phone, you watching. Nothing uploaded, nothing kept, you hold the drive.
Why I'd take that bet69,746 Dubai transactions read. 11,787 agents scored. I know what a board like yours usually has behind it.
What "closes" meansA signed deal with a name off the list. Not a lead, not a viewing. Twelve months.
The one-page agreement — shown, not described
CTA repeatWhatsApp me →
FooterArticulate, Dubai · DED licence · The agreement, in full

Showing the agreement is the whole page. An offer this good invites the question what's the catch, and the answer has to be visible rather than promised. Put the actual one-pager on the page, readable, before anyone has to ask for it.

7 · Before you send

CheckWhy
1Domain bought, three mailboxes, SPF / DKIM / DMARC, warmup runningFourteen to twenty-one days. Nothing below matters until this clock is started, and the clock does not start itself.
2Paul's three numbers — guessed, found, still liveFills the only empty region on any of these pages, and it sits on the arm that asks for money.
3Extract timed on a real phoneArm B says "about twenty minutes" and Arm C says "an afternoon". Both are currently assumptions. If it is ninety minutes a phone, both emails are wrong and the day-rate model goes with them.
4Arm C's terms signed off and drafted as one pageTwo of the three emails commit to numbers. They cannot go out before the document behind them exists.
5WhatsApp Business profile live on +971 50 508 4451Display name, description, hours, away message. Every arm converts into this one screen; a nameless mobile number undoes the email that earned the tap.
6Seed-send all three variants to yourself and read them on a phoneMerge fields render, links resolve, line breaks survive. Most agents read on a phone and these were written for that column width.
7First fifty only, then read the bounce rateThese addresses came off Property Finder's payload and have never been validated. A high bounce on a cold domain does compounding damage — find out on fifty, not on 982.
Ready now: pipeline/send/arm-A.csv, arm-B.csv, arm-C.csv — 328 / 327 / 327 rows, every merge field resolved, hook variants balanced across arms, WhatsApp deep links tokenised per agent. They import into Smartlead as three campaigns without further work.

Articulate · Gold Digger · copy and wireframes written 21 August 2026. Merge-field coverage measured from pipeline/send-batch.csv on the day of writing. Sample hook lines are real rows from the loaded batch. Nothing in this copy asserts a number that is not in the harvest.