I build expansion campaigns on what the account actually does: product-usage signals, cohort and lifecycle segmentation, offers sequenced after activation. At PingPong that meant campaign structures built around supplier segments instead of geographies.
Most cross-sell programs are quota programs wearing a marketing costume. The quarter gets tight, an offer goes to the whole list, and the accounts that were quietly warming up learn to ignore the sender. I run expansion the other way around: as an explicit stage of the lifecycle system, from signup to expansion, with the offer waiting on the account rather than the account waiting on the calendar.
At PingPong I rebuilt campaign structures around supplier segments instead of geographies, so every offer mapped to who the account is and how it uses the product. On top of that sat the lifecycle engine I built for the cross-border payments line: segmentation by supplier size and payment corridor, product-education sequences for the first transaction, and activation programs timed to usage signals instead of calendar guesses.
Every journey I shipped carried a measurable expansion job: move a supplier from registered to first payment, then from first payment to habitual use. When retention and expansion run as a program with a number, the cross-sell conversation stops being a favor sales asks of marketing and becomes a stage the system already owns.
Cohort, firmographics and lifecycle stage first, geography last. I rebuilt PingPong's campaign structures around supplier segments for exactly this reason: a Shenzhen electronics supplier and a Warsaw logistics firm on the same corridor have more in common than two neighbors at different lifecycle stages. I layered AI-assisted segment refinement and lead scoring on top of HubSpot, Salesforce and Pipedrive so the targeting stays current instead of frozen at import time.
I wire product-usage signals, intent and account data into behavior-based triggers. The question a trigger answers is narrow: has this account done the thing that makes the next product genuinely useful? A supplier running habitual payments on one corridor is a cross-sell candidate; a supplier who registered last week is not, no matter what the quarter needs.
Registered to first payment, first payment to habitual use, habitual use to the next product. Each hop is its own journey with its own number, and no expansion offer jumps the queue. Product-education sequences earn the first transaction; activation programs timed to usage signals earn the habit; only then does the cross-sell fire. I partner with product, sales, engineering and data to keep those hops honest in long-cycle B2B.
Retention and expansion run as a program with a number. The same discipline I apply to partner incentives applies here: pay attention to qualified outcomes. An expansion campaign that moves accounts to habitual use is working; one that spikes opens and moves nothing is quota pressure with better typography.
The cross-border payments line grew from $2M to $76M in year one, then past $250M+ in year two, on the same engine with no structural reinvention. I owned marketing on that line end to end; sales owned the account relationships, with finance and product as partners on their sides. That second-year curve is the point of this whole page: it was compounding inside the system, existing accounts included, rather than a new acquisition push. Expansion did the work acquisition is usually asked to fake.
The unglamorous part made it possible. I automated lead handoff from ~12 hours to 1–2 minutes across the 200+ workflows I built, and that same operational backbone is what lets a usage-triggered offer reach the account while the signal is still warm. A cross-sell trigger that waits half a day is a calendar blast with extra steps.
$2M → $76M year one · $250M+ year two · handoff ~12h → 1–2 minI have worked with Daniel on a couple of different projects. He is a professional who brings his capability to learn things quickly to get work done successfully. His professional ethic and ease to adapt to any team make him a good element to any organization.
Bruce AuGeneral Manager
Sequenced after activation, aimed by what an account already does rather than by this month's quota.