Sell the next product when usage says so
I build expansion campaigns on what the account does: product-usage signals, cohort and lifecycle segmentation, offers sequenced after activation. At PingPong that meant campaign structures built around supplier segments and payment corridors.
The best upsell reads the account
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, so the offer waits on the account.
Every offer had to map to who the account was and how it used the product. On top of that sat the lifecycle engine I built for the cross-border payments line. I segmented by supplier size and payment corridor, taught the product before the first transaction, and fired activation on usage signals.
Each journey had one 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.
What has to be true
before an offer ships
01 · Segment by what the account is
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 re-cut those segments and re-scored the list in Salesforce and HubSpot, so the targeting keeps moving after import.
02 · Instrument the usage signal
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 useful? A supplier running habitual payments on one corridor has earned the offer. Registration alone does not put anyone in the queue, no matter what the quarter needs.
03 · Sequence expansion after activation
Five state triggers feed three journeys before this one, and expansion is the hop after them. Registered to first payment, first payment to habitual use, habitual use to the next product. Each hop is a journey with a number behind it, 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 keep each hop honest with product and sales: the account has to move before the offer does.
04 · Measure the expansion job
The discipline I use on partner incentives holds: pay attention to qualified outcomes. An expansion campaign works when it moves accounts to habitual use. I read the three hop rates separately, and there was never one named expansion metric above them. Spiking opens while moving nothing is quota pressure with better typography.
The trigger shipped. The offer never fired.
Supplier size and payment corridor decide who hears the offer
Expansion starts with how the list is cut. I segmented the cross-border payments line by supplier size and payment corridor, so each offer travels to accounts that share a behavior. The lifecycle engine I built carries that cut into every send.
On top of the cut sits the hop order: registered to first payment, first payment to habitual use, habitual use to the next product. Product education earns the first transaction, activation timed to usage signals earns the habit, and the cross-sell offer sits armed behind activation until the account moves. The same stage-before-offer rule runs through the lifecycle system I specced for a luxury skincare launch, with different segments and the same order.
Supplier size and payment corridor · registered → first payment → habitual use → next productGrowth that came from inside the system
The cross-border payments line grew from $2M to $76M in year one, then past $250M+ in year two, on the same engine I never rebuilt. I owned the demand side of that line end to end; sales owned the account relationships, with finance and product as partners. I built the cross-sell trigger and sequenced it behind activation. It never got its at-bat before I left, so I have no expansion split to show you.
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
Want expansion campaigns that read product usage?
Sequenced after activation, aimed at what the account already does.