How Sahel Transfer recovered 18 points of KYC completion in 11 weeks
CRO
A worked example, not a client result. The organisation, the figures and the quotation below show how an engagement of this shape is structured and what it sets out to move. They are not outcomes achieved for a named client.
PaySetuMarketing
PaySetu doubled repeat send rate by rebuilding lifecycle on transaction state
A signup-focused email programme was replaced with triggers tied to what senders actually did, and to when their corridor's remittance cycle peaked.
2.4xrepeat send rate
+31%second-send within 60 days
2.4xREPEAT SEND RATE
+31%SECOND-SEND WITHIN 60 DAYS
−22%BLENDED CAC
16 wksENGAGEMENT
Measured over 16 weeks against a matched prior period. Attribution and confidence notes available on request.
The situation
PaySetu ran a monthly newsletter and a welcome series, both written well and both firing on a calendar. Open rates were respectable. Nobody could point to a transfer that either had produced.
The founder's instinct was that email was simply weak in this category and that the budget belonged in paid acquisition. That is a common conclusion in remittance and it is usually wrong for a specific reason: the messages were not responding to anything the sender had done.
A single number reframed the whole conversation. Seventy-one percent of verified senders had made exactly one transfer and never returned. The business was paying full acquisition cost for customers worth a single transaction.
What we found
Lifecycle in remittance is not a content problem, it is a trigger problem. PaySetu had transaction data, corridor data, rate data and KYC status, and none of it was connected to a message.
Senders on the Gulf to India corridor also transfer on a rhythm that a marketing calendar cannot see: pay cycles, school fee windows, festival periods and family events. A newsletter on the first Tuesday of the month arrives at a moment that means nothing to anyone.
We also found the rate alerts were untargeted. Every subscriber received every alert, including for corridors they had never used, which had trained a meaningful share of the list to ignore the sender entirely.
Funnel and diagnostic table
| Stage or area | Position | Cumulative or detail | Read |
|---|---|---|---|
| Verified senders | 100% | 100% | Baseline |
| First transfer completed | 62% | 62% | Healthy |
| Second transfer within 60 days | 29% | 18% | The gap |
| Third transfer within 120 days | 54% | 10% | Habit not forming |
| Active at 12 months | 7% | Value not realised |
What changed
1. Mapped every trigger available in the data: KYC status, transfer completion, elapsed time since last send, corridor rate movement, and failed or held transfers.
2. Built the second-send sequence first, because the gap between first and second transfer was the largest single loss in the business.
3. Timed campaigns to the corridor's own rhythm rather than to a marketing calendar, using pay cycles, fee windows and festival periods.
4. Made rate alerts corridor-specific, so a sender only hears about movement on a route they actually use.
5. Built a win-back sequence for lapsed senders with a suppression rule, so people who had genuinely left stopped being contacted.
Nothing in this programme was a new channel. Every message went out through the platform PaySetu already owned, to a list they already had, about corridors they already served.
The measurable difference came from firing on transaction state rather than on dates, and from accepting that a sender who has not transferred in nine months is a different person from one who transferred last week.
We used to celebrate signups. Now the only number on the wall is repeat send rate, and it has moved every month since we started.
— Rohit Menon, Founder, PaySetu
How the work ran
Trigger map from transaction state to message
Every available signal mapped, then reduced to the six that actually predict a second transfer.
Remittance cycle calendar per corridor
Pay cycles, fee windows and festival periods replacing a monthly send date.
Win-back cohort with suppression
Lapsed senders contacted once, properly, then suppressed rather than repeatedly mailed.
What moved
| Metric | Before | After | Change |
|---|---|---|---|
| Repeat send rate | Baseline | 2.4x | Improved |
| Second transfer within 60 days | 18% | 49% | +31pts |
| Rate alert engagement | Baseline | 3.6x | Improved |
| Unsubscribe rate | Baseline | −38% | Improved |
| Blended customer acquisition cost | Baseline | −22% | Improved |
| Messages sent per sender per month | Baseline | −44% | Fewer, better timed |
Mandatory line beneath: “Measured over 16 weeks against a matched prior period. Attribution and confidence notes available on request.”
The engagement in brief
Scope and shape
- Remittance app
- Gulf → India
- 16 weeks
- Marketing
The counterintuitive part was sending less. We cut volume by nearly half and every metric that matters improved.
— Rohit Menon, Founder, PaySetu
Same funnel, different corridor?
A fixed-fee growth audit covering acquisition, KYC completion, retention and tracking across your corridors. You keep the roadmap whether or not we work together.