CAST
Arjun — NeoMarketing sales lead, Netcore. Same audit discipline as the first meeting. Three months on, he’s back with a different kind of page.
Maya — CMO of the same D2C fashion brand. The 90-day NeoMails test closed out. She isn’t asking whether the doctrine is real any more — she’s asking who is accountable for running it.
Setting: Maya’s office, three months after the pilot closed. Her REACQ% has moved. Her Real Reach has moved. This time, she requested the meeting.
Before the Meeting
Maya’s Monday starts the way it always has: a dashboard that looks busy enough to be reassuring. Campaigns shipped on schedule. Journeys are running. The agency sent its weekly update. Underneath the campaign layer, though, she’s started looking at a different number — 31,000 stalled KYC upgrades from the last quarter, sitting in a queue nobody owns. The dashboard didn’t lie about what went out. It just never measured what got finished. That’s the number she wants to talk about today, not the pilot recap.
1
The Handoff Problem
“So Now You’re Selling Me a Third Thing?”
Maya’s mental shift: proof of concept isn’t the same question as who runs it at scale.
Arjun sits. No printed page this time — he opens with a question instead.
Arjun: Before I show you anything, tell me what broke when you tried to run the next stage yourselves.
Maya doesn’t hesitate. She’s been waiting to say this.
Maya: Nothing broke. It just didn’t scale. My team ran the 100,000-ID test beautifully because it was 100,000 IDs and it had my best analyst on it for ninety days. My Rest base is 2.8 million. I don’t have four more of her. And it’s not just Rest — I pulled the KYC queue last week. Thirty-one thousand upgrades stalled, some for months. Nobody owns that number. It just sits there.
Arjun: That’s not a people problem. It’s a bandwidth ceiling every in-house team hits at the same point — segment refresh, message variants, journey branches. It’s structural, not a reflection on your team.
Maya: Fine. So who runs it? Because if the answer is a new vendor, I want to say now — I already have Netcore for the platform, I already have you for Atrium and Meridian. I am not adding a fourth relationship to manage a problem you told me was one system.
Arjun places a single card on the table — no deck, one page.
Arjun: It isn’t a fourth relationship. It’s the delivery arm of the two you already have.
Maya: Walk me through it. Slowly.
Arjun: Meridian is the underwriting logic for your Best customers — Beta plus Alpha plus Carry, the outcome contract. Atrium is the same logic for Rest and Next. Neither of those is a team that shows up and does the work every day. Progency is that team — Martech Growth Engineers, running the actual interventions inside Meridian’s rules for your Best customers, and inside Atrium’s rules for your Rest base. One name. One accountable team. It doesn’t sit beside Meridian and Atrium — it’s how they get delivered.
Maya: So when my Best customer’s renewal quote goes stale, that’s Progency working inside Meridian’s rules. And when a dormant subscriber needs winning back before I pay Meta for her again, that’s Progency inside Atrium’s rules. And my stalled KYC pool — those are engaged customers mid-upgrade, not dormant — so that’s Meridian’s side too.
Arjun: Exactly right. We call the first two Finish and the second Recover. Different customers, different job, same team, same accountability line back to you.
Maya reads the card again. She just leaves it face up on the desk, which Arjun has learned to read as a good sign.
Maya: There’s a political question underneath this too, and I want to ask it directly. My in-house team is going to hear ‘Progency’ and assume you’re taking over their job. How do I tell them that’s not what’s happening?
Arjun: You tell them the truth, and it holds up: Progency doesn’t touch BAU. It only works declared leakage pools — named groups where your own team has already agreed the journey has stalled, the outcome is measurable, and there’s a clear baseline to beat. Your team keeps everything else: brand, strategy, the customers CRM already serves well. We’re not asking for their job. We’re asking for the pools they’ve already told you they can’t get to.
Maya: That I can sell internally. Alright. I believe the structure. I don’t yet believe the economics. Let’s get into that.
Key Takeaway: Maya’s objection was never about whether the doctrine works. It was about vendor sprawl and internal politics. The answer that lands isn’t a better pitch — it’s proof that nothing new is being added to her stack, and nothing is being taken from her team.
2
Under Fire
“My Retargeting Already Does That. Why Do I Need You?”
Maya’s mental shift: from structural sign-off to pricing sign-off.
Maya pulls up her own dashboard — turning her screen so Arjun can see it.
Maya: Here’s my abandoned-cart flow. Dynamic ads, product-level, running right now on Meta. You’re going to tell me Progency does this better, and I want to know exactly why, because on paper this already looks like one-to-one targeting to me.
Arjun: It is one-to-one targeting. I’m not going to tell you adtech can’t do this — that claim doesn’t survive five minutes with your own dashboard open. What I’ll say instead: Meta is matching a device to a product probabilistically and charging you a CPM to show it again. We already know deterministically who this customer is, we know exactly which size and colour she left in the cart, the follow-up costs us next to nothing to send, and because it runs against a holdout you agree to upfront, you get a clean number for what it actually recovered — not an attribution model’s estimate.
Maya: So the pitch isn’t ‘adtech can’t.’ It’s ‘we’re cheaper, more precise, and provable.’ Which also means cart probably isn’t where I should start — you’ve just told me my own baseline there is already decent.
Arjun: That’s exactly right, and most brands miss it. Cart is the most-solved leak in the business, which makes it the worst place to prove Alpha — the gap between us and your current effort is narrowest exactly there. Your KYC pool is a better first test. Nobody’s retargeting a half-finished KYC form.
Maya sits back. This is the point in the last meeting where the conversation turned to money. She gets there faster this time.
Maya: My finance team already killed one version of this. Someone on your side proposed a flat fee per email open on the dormant base. My head of ops called it ‘charging us to annoy our own customers.’ It was a hard no, and I don’t want to relitigate it.
Arjun: You’re right to have killed it. That proposal was a mistake — an open is an impression, not an outcome. Charging for it is the exact thing Never Pay Fixed exists to stop, and I’d have told your ops team the same thing if I’d been in that room.
Maya: Then what do I actually pay for?
Arjun: A ladder, with names your finance team can actually look up. You never pay for an open. Pay-for-Action starts weak — a click, a reply — and climbs to strong: a completed KYC step, a qualified lead, a quote requested. Pay-for-Data sits alongside it — we hand back a qualified field your CRM was missing, like a renewal date, and it’s priced by usable fields, not raw data points. Pay-in-Email sits at the top, on the Beta-Alpha-Carry structure, whenever you’re ready for it.
Maya: And if I never move past Pay-for-Action?
Arjun: Then that’s what this pool is worth to you, and we don’t force the issue. But most brands climb the ladder once the first rung proves out — because the number that convinces a CFO is never the pitch, it’s the first quarter’s actual holdout comparison.
Maya: One more thing before we move on. If I run both Finish and Recover, which one do I actually get first? I don’t have budget or attention for both to start simultaneously.
Arjun: Finish, honestly. It’s not the bigger story — Recover, reactivating someone before Meta re-buys her, is the sentence that gets vendors like me in the door. But Finish has shorter cycles. A stalled KYC step resolves in weeks. Recover on a genuinely dormant customer takes longer to prove and longer to fund, since we’re not paid until the outcome lands. Start with Finish, let it pay for itself faster, and run Recover alongside it once the first cheque clears.
Maya writes one word on her notepad: sequencing. Underlines it once.
Key Takeaway: Maya’s finance team had already correctly rejected a flawed pricing model. Arjun’s job wasn’t to defend it — it was to agree it was wrong and show what replaced it. Conceding a bad idea landed harder than defending a good one would have.
3
The Close
“What’s Actually Yours, and What’s Everyone Else’s Too?”
Maya’s mental shift: from pricing sign-off to a test she can defend upward.
Maya leans forward — the question she always asks, arriving a little earlier than usual this time.
Maya: Here’s what worries me longer term. The tooling you’ve described — tracking, templates, the AMP layer — none of that sounds hard for a competitor to copy in a year. What actually stops me from switching to whoever undercuts you next?
Arjun: Nothing stops you, on the tooling. You’re right that any competent vendor can build similar utilities eventually. What they can’t copy is the record underneath it — every action Progency has run, on every type of stuck customer, across every brand we’ve touched, and what it actually produced. We call it the Decision Trace Graph. It’s inside our Context Graphs, and every intervention writes back to it. A year from now, the tenth brand we do this for benefits from what we learned on the first nine. A new entrant starts at zero.
Maya: So the tools get me started. The trace record is what compounds.
Arjun: That’s the honest version, yes.
Maya nods slowly — the same motion Arjun remembers from the end of the first meeting.
Maya: Fifteen years in this industry. Every eighteen months someone tells me the delivery model has changed and this time it’s structural. Convince me this isn’t that, one more time, quickly.
Arjun: I won’t try to convince you in the abstract. Give me one pool — not your whole Rest base, not a transformation programme. One declared leakage pool, a fixed window, a holdout your own team agrees to upfront. If it doesn’t beat the holdout, you’ve lost two months on customers who were already stuck. If it does, we’ve proven the delivery model on your own data, not a case study from someone else’s brand.
He places the second card of the meeting on the table.
Maya: Stalled KYC upgrades. That’s the pool I already told you about — thirty-one thousand of them, and I know it’s been ignored for two quarters.
Arjun: Then that’s the pool.
Maya: Sixty days. No platform change, no new budget line, Pay-for-Action so my finance team doesn’t reopen the objection from last time. And I want the review to be more specific than ‘did it work.’
Arjun: What does the review look like on your side?
Maya: Five questions, not a deck. How many customers actually moved. What they actually did. What usable data we captured along the way. What revenue it produced, if any. And what happened next to the holdout. If you can’t answer those five cleanly at day sixty, I don’t care how good the pitch was.
Arjun: Agreed — those are the right five, and they’re the same ones we’d hold ourselves to internally. One thing — do you want this framed as a Progency engagement in the write-up, or folded into the Meridian relationship you already have signed off?
Maya: Fold it in. My board already approved Meridian. I’d rather this look like Meridian doing its job properly than a new line item.
Arjun: Noted. It runs under Meridian.
Key Takeaway: Maya didn’t ask for a bigger commitment — she asked for the smallest one that would still tell her the truth, and she named her own success criteria rather than accepting Arjun’s. That’s the same shape as her first close, and it’s the shape Progency is built to survive: no transformation required, just a fair test on one real pool, judged on the buyer’s terms.
After the Meeting
Arjun leaves the cards on the table this time — Maya asked him to. She pulls up the KYC pool herself before her next meeting starts: names, stalled dates, how long each one has sat untouched. She’s seen this data before. She has just never looked at it as something with a price on either side of the ledger — what it’s costing her to ignore, and what it would cost to finally close. She forwards the pool definition to her ops lead with one line: “Sixty days. Five questions. Let’s find out.”
