The merchant said yes. The revenue didn’t.

A queue after the yes. Four teams. No owner.

Three stages, in your vocabulary. I use your terms on the first call; you shouldn’t have to translate your own business for me.

1. Closed won

   The finish line that isn’t.

   You call it: Closed won ≠ live · MRR vs processed volume · time to first transaction

   The board ends where the revenue starts. A merchant who signed in March can still be waiting to process in June, and the forecast counted it in March. Sixty-eight percent of companies miss their forecast by more than ten percent; in a payments business the miss is usually sitting in this queue. MRR and processed volume are two different pipelines, and only one of them appears on the sales board. It isn’t the one finance reports. Time to first transaction predicts churn better than any satisfaction score you can collect: most churn happens in the first ninety days, and the first ninety days start at the signature, not at go-live.

   The fixThe stages after the yes on the same board, with an owner and an age on every record.

2. Compliance

   KYC collected too late.

   You call it: KYC · KYB · FICA pack · “requirements outstanding” · handover

   The pack is chased after the signature instead of gathered at the demo. Gathered at the demo it is a week; chased after the yes it is a quarter. Every document that arrives late is a week of processing volume that never happened. Banks say they contact a client four times during onboarding; the clients say eight. Somebody is counting wrong, and it isn’t the customer. Then the handover: sales to compliance to onboarding to retention, four teams, and in most builds no single owner across the four. In South Africa the FIC Act requires identity established and verified in the course of establishing the relationship, a legal gate before go-live, which is the strongest argument there is for asking at the demo.

   The fixThe KYC pack as an entry checklist on the demo stage, and one named owner per merchant across all four teams.

3. Expansion

   Nobody asks for the second product.

   You call it: Cross-sell · upsell · “once they’re settled”

   The cheapest revenue you have sits inside merchants already live. No trigger, no owner, no stage, so it happens when the merchant thinks of it. Companies with net revenue retention over 100% get more than half their revenue from expansion, and grow twice as fast as those under it. Salesforce gets roughly three-quarters of its new bookings from existing customers. Your version of that number is currently unknown, because nobody is counting it. That’s not a relationship. That’s a stage.

   The fixAn expansion stage with a trigger (first transaction plus ninety days, or a volume threshold) and an owner.

One record per merchant, first contact to first transaction.

A named owner at every stage, including the stages after the yes. The KYC pack moved forward into the demo as an entry checklist rather than chased afterwards. Handover replaced by a checklist the next team can see before the account arrives. A view of every application by stage and age, so a stall becomes visible inside the week it happens rather than the quarter.

Then the same system rolled out across every market you operate in, with the local teams trained on it directly rather than sent a process document. Nothing gets ripped out that works: if the CRM does sales well and a service desk does onboarding well, the two get a shared spine rather than a replacement.

Three numbers you’d watch afterwards. Not a dashboard nobody opens.

Proof. The forecast said one thing. Month-end said another.

Sales isn’t the bottleneck. The queue behind it is.

Asked by founders, sales directors and the ops lead who inherits the queue.

1. First move

   What do we fix first?

   Move the KYC pack to the demo. It is the single cheapest change and it collapses the compliance stage, because every document that arrives late is a week of processing volume that never happened. Then put one name against each merchant end to end, so a stall has somebody to belong to.

   → Why CRM rollouts die in month three: collected at the demo it is a week.

2. Your stack

   We already run HubSpot. Do we replace it?

   No. Nothing gets ripped out that works. HubSpot is usually fine at the front half; what’s missing is the half after closed-won — stages, owners and ages for compliance, go-live and expansion. I design the process first and build it where you already work.

   → CRM problem, or process problem? The front half was never the problem.

3. Sales

   Won’t asking for KYC at the demo slow the close?

   It’s the objection every sales team raises, and the data says the opposite: the merchants who leave are the ones who were asked eight times after signing, not once before. A merchant who’s keen hands over documents. A merchant who’s been waiting six weeks doesn’t.

   → What evidence should move a deal to the next stage? Asked once while they’re keen, or eight times after.

4. Scale

   We operate in three countries. Does one pipeline hold?

   It held across South Africa, Namibia and Botswana. One pipeline, local compliance requirements as stage checklists rather than separate boards, and each market’s team trained on it directly. Different requirements, same shape — which is what makes the numbers comparable across markets for the first time.

   → Reset my stages, with the extra agreed in writing before work starts: three markets, one system.