Building one shared language for support and sales: a fintech case study
How PrimaCX designed a combined virtual training programme that gave two departments a common foundation — without losing what makes each role distinct.
The challenge
A growing fintech client came to PrimaCX with a familiar problem: as the business scaled, both their Customer Support and Sales teams needed stronger, more consistent skills — but training them separately meant twice the time investment, and risked leaving each team speaking a different language when a case crossed between departments.
Before designing anything, we ran a baseline needs assessment with the Support team to ground the training in reality rather than assumption. The results were clear and specific: 90% of agents named anxious, money-related customer interactions as their hardest scenario, and while the team already handled routine repeat requests well, escalation judgment was the clearest skill gap — some agents were escalating too early, others holding on to cases too long.
That data shaped everything that followed.
The approach: shared foundation, department tracks
Rather than building two disconnected training programmes, PrimaCX designed a single combined curriculum with a deliberate structure.
A shared foundation, where both teams trained together on the same underlying skill — genuinely listening and understanding before acting — taught through two parallel frameworks: LARA (Listen, Acknowledge, Reassure, Act) for support conversations, and SPIN (Situation, Problem, Implication, Need-Payoff) for sales discovery. Different applications, same discipline.
Department-specific tracks, where each team went deep on the skills specific to their role. Customer Support trained on HEAT for de-escalating irate customers, a customer segmentation model for handling repeat requests without impatience, and a three-tier escalation structure with clear response-time standards. Sales trained on LAER for objection handling, BANT for prospect qualification, and proven closing techniques paired with pipeline response-time standards.
A shared close, bringing both teams back together to address something training programmes often miss entirely: what happens when a support case reveals a sales opportunity, or a sales conversation surfaces a product issue. Both teams left with a clear, consistent handoff standard — the customer should never have to repeat their story.
What was delivered
The engagement wasn't a single workshop — it was a full training system:
A two-day virtual training programme, built for breakout-room delivery with live polling, virtual whiteboards, and role-play activities throughout.
A detailed Customer Support Framework — segmentation model, escalation tiers, and benchmarked service standards.
A dedicated de-escalation guide for handling irate customers, going deeper than the core curriculum on the single highest-stakes skill in the training.
Pre- and post-training assessments, built to be directly comparable, so skill and confidence shifts can be measured, not just assumed.
Facilitator and participant feedback tools, so the training's own effectiveness gets evaluated the same rigorous way the teams themselves were trained to work.
Why this approach works
Training two departments together isn't just more efficient — it's more effective. When Support and Sales share a foundational language, cross-team handoffs stop being a source of customer frustration and start being invisible to the customer entirely.
And because the curriculum was built from real baseline data rather than generic theory, every module addressed a gap the team had actually named, not one we assumed they had.