Skip to main content
Enterprise Software  ·  Telecom Enterprise Buyers  ·  $1B Parent + $1B Clients  ·  2015

Salesforce CRM Division Beats IBM, Accenture, and Deloitte: $7M New Revenue in 9 Months

Tech Mahindra’s CRM division, a $1B parent with two $1B telecom enterprise clients, installed a Revenue Growth Management discipline that turned a two-account base into a repeatable enterprise sales motion.

Engagement  Jan 2015 – Sep 2015 Blueprint + Build Mike Reardon, contributing operator, accountable for the revenue motion. My manager opened the doors between decision-makers at both clients. Everything behind the door was mine: the teams, the motion, and the number it produced.
$7M
New revenue in
under one year
>50%
Win rate against
Big 4 incumbents
350%
Sales growth across
both enterprise accounts
01  ·  The Company

A division of a $1B parent, with $2B of client revenue concentrated in two accounts

The CRM division of a $1B multinational technology company. Indian-headquartered with regional offices and clients worldwide. Two enterprise telecom clients formed the entire revenue base of the division, Bell Canada and TELUS, each a $1B-plus account. The division had won the work. Holding it and expanding it was a different problem.

02  ·  The Problem

A two-account revenue base competing against the Big 4

A division generating revenue from only two clients, however large, has a structural revenue risk. Lose one and the division halves. Lose both and the division ends. Three interlocking issues had to be solved at once.

No repeatable sales motion beyond incumbent work. New Salesforce contracts within Bell and TELUS were available. Other divisions of those enterprises were buying CRM services. The division had no repeatable motion for winning that incremental work, and certainly not against IBM, Accenture, and Deloitte who were targeting the same buyers.
Multi-team coordination at enterprise scale. Onshore Canadian project teams, offshore Indian delivery teams, and the client’s project teams, three separate organizations had to coordinate around 1,000+ user call-center implementations. Communication failures at this scale are revenue failures, not just operational ones.
Salesforce CRM integration with legacy infrastructure. Predictive dialer systems and server networks already inside the telecoms had to be integrated with the new Salesforce platform. Each integration was a project. Each project had its own win/loss inside the broader engagement.

If you have two enterprise clients, the Big 4 fighting you for every additional dollar inside them, and integration complexity at 1,000-user scale, is the answer to chase new accounts or to architect a Revenue Growth Management motion that wins consistently inside the accounts you already have? RGM first. New accounts second.

03  ·  What We Did

Revenue Growth Management, for the accounts already on the books

The answer was not new logos. The answer was an account-expansion motion that won consistently inside the two enterprises already on the books, against IBM, Accenture, and Deloitte targeting the same buyers.

Blueprint Phase

Map the position, define the Revenue Growth Management strategy

  • Mapped the division’s commercial position, two telecom enterprises, no repeatable motion for expanding inside them, no defined approach against Big 4 incumbents.
  • Defined the Revenue Growth Management strategy, how to grow within Bell and TELUS while competing for new Salesforce contracts against IBM, Accenture, and Deloitte.
  • Identified the integration complexity layer, Salesforce CRM with legacy predictive dialers and server networks across 1,000+ user call-center environments.
Build Phase

Lead the multi-team coordination; execute the sales motion against the Big 4

  • Led on- and offshore project teams simultaneously, coordinated with both clients’ project teams across both Bell and TELUS engagements.
  • Executed the sales motion against the Big 4, closed over 50% of leads for Salesforce professional services contracts inside the two accounts.
  • Delivered the work alongside the wins, holding the integration discipline that made every new contract deliverable.
04  ·  What Changed

From a two-contract delivery shop to a Revenue Growth Management operation

$7M
New revenue
in nine months
>50%
Win rate against
IBM, Accenture, Deloitte
350%
Sales growth across
Bell and TELUS
Metric
Figure
Context
Sales growth across both accounts
350%
Bell Canada and TELUS combined, over the nine-month engagement
New revenue, in under a year
$7M
Incremental Salesforce CRM contracts inside the existing accounts
Win rate against Big 4
>50%
Vs. IBM, Accenture, and Deloitte for Salesforce professional services
Account base at engagement start
2 clients
Bell Canada and TELUS, each a $1B-plus enterprise
Implementation scale
1,000+ users
Call-center deployments per integration, across both clients
Engagement window
nine months
Jan 2015 – Sep 2015, Blueprint and Build delivered in series

The division stopped being a two-contract delivery shop and became a Revenue Growth Management operation.

Then the parent closed the division across every region. Not because of the numbers. 2015 was a hard year for the parent: profit fell 39.2% quarter on quarter in the March 2015 quarter, and a profit warning followed in June, blamed on a seasonally weak mobility business. The telecom vertical was carrying forex pressure, pricing pressure and seasonality all at once, and we sat inside it. Cost-cutting arrived from far above this division, and a unit that had just grown was closed with the rest. The system worked. The company that owned it did not survive the decision. Worth saying plainly, because a reader deciding whether to trust an operator should know how the story actually ended. Win rate above 50% against IBM, Accenture, and Deloitte for Salesforce professional services contracts inside the existing accounts. $7M in additional revenue in nine months. Three project organizations coordinating across two enterprise clients without losing the integration discipline that made the work deliverable. The same operator who walked into a two-account base walked out with a repeatable enterprise sales motion the division had never had.

06  ·  The AI Sidebar

If today’s AI had been available in 2015

The Revenue Growth Management motion installed in 2015 did three things that today’s AI would compound. The discipline does not change. The leverage on it does.

Then  ·  2015

How the RGM motion actually ran

  • 1,000+ user call-center context handled through manual coordination across on-shore Canadian, off-shore Indian, and client project teams
  • Multi-stakeholder enterprise sales-cycle tracking across Bell and TELUS buying committees, managed by hand
  • Account intelligence on Bell and TELUS sub-divisions built through weeks of manual mapping per opportunity
Now  ·  Started in 2026

The same discipline, accelerated by AI

  • Voice AI handles inbound qualification and outbound dialing at enterprise scale, with conversation intelligence on every interaction
  • Multi-stakeholder workflows run continuously through AI automation, surfacing buying-committee dynamics and stalled stakeholders in real time
  • AI account intelligence runs continuously for ongoing opportunity surfacing, replacing weeks of manual mapping with daily refresh

“The foundation does not change. The system is the foundation. AI is leverage on the foundation.”

06  ·  The AI Sidebar

If today’s AI had been available in 2015

The Revenue Growth Management motion installed in 2015 did three things that today’s AI would compound. The discipline does not change. The leverage on it does.

Then  ·  2015

How the RGM motion actually ran

  • 1,000+ user call-center context handled through manual coordination across on-shore Canadian, off-shore Indian, and client project teams
  • Multi-stakeholder enterprise sales-cycle tracking across Bell and TELUS buying committees, managed by hand
  • Account intelligence on Bell and TELUS sub-divisions built through weeks of manual mapping per opportunity
Now  ·  Started in 2026

The same discipline, accelerated by AI

  • Voice AI handles inbound qualification and outbound dialing at enterprise scale, with conversation intelligence on every interaction
  • Multi-stakeholder workflows run continuously through AI automation, surfacing buying-committee dynamics and stalled stakeholders in real time
  • AI account intelligence runs continuously for ongoing opportunity surfacing, replacing weeks of manual mapping with daily refresh

“The foundation does not change. The system is the foundation. AI is leverage on the foundation.”

The Lever Scales. The Discipline Does Not Change.

Enterprise scale or SMB. Same architecture. Same discipline.

If your services firm or account-driven business is leaking expansion revenue to competitors inside your own accounts, the fix is the same shape. Two ways to start.