Global Client Officer first.
Use the TP scorecard to help the GCO improve or differentiate one enterprise program; bring the site leader and enterprise CX owner into the same expansion thesis.
QBRs, events, budget windows, roadshows and outbound should advance a mapped opportunity—not become activity for its own sake.
The senior person is not automatically the right first person.
account truth + permission
proof + warm path
client or LOB access
baseline + workflow
multi-geo / strategic scale
The same account can be low priority in August and high priority six weeks before a QBR, budget lock or major ramp.
Examples from the mapped accounts—not generic personas.
Use the TP scorecard to help the GCO improve or differentiate one enterprise program; bring the site leader and enterprise CX owner into the same expansion thesis.
India growth and broad Sanas standardization mean the question is which new client program or module is not yet fully attached.
If active in CRM, start with the payer / provider program and AEP or member-service workflow—not the corporate CEO.
Andrew Wilmott or Brad Call can identify the highest-value healthcare, telecom, BFSI or retail programs across PH / LATAM.
Michael Mahar should open a specific adjacent owner—Rewards, guest care, reservations or the BPO behind the queue—not a broad intro tour.
Joint carrier account planning at Mavenir; advisor enablement and named-enterprise workshops through Telarus.
Each event starts with the account map: which executive is attending, what LOB / region matters, who knows them, and what outcome I want.
Private account meetings around known whitespace. Wyndham is proof this channel can create real business.
Clear architecture and deployment blockers for already-qualified expansion.
Member service, payer operations and post-AEP expansion conversations.
Post-peak service / conversion issues tied to specific outsourced programs.
A customer-service contract event can create a Sanas seat event.
enterprise change
which Sanas BPOs?
proof + economics
BPO + Sanas
new program rollout
Three or four real meetings in one market is a trip. The route should follow the assigned accounts, not a generic territory tour.
LATAM BPO leadership, Atento USNS / regional connections, nearshore expansion.
Mavenir + telecom / technical-support ecosystem.
Executive briefings, technical proof and founder / leadership access for priority accounts.
Hospitality, financial services and direct-enterprise expansion.
I would start from Sanas's existing funnel data, account-team norms and conversion benchmarks, then adjust my weekly activity to what actually creates qualified expansion pipeline.
Sit with CSMs, AEs and current customers first.
Build mutual paths before sourcing cold executives.
Call + email + LinkedIn against a named account hypothesis.
Meeting quality, accepted opportunity and pipeline matter more than raw volume.