Should ServiceNow kill its CSM module?
No — but the steelmanned case for killing CSM is real and McDermott's team has clearly run the math. ServiceNow's Customer Service Management module is sub-15% of revenue (~10-12% per analyst triangulation), it loses head-to-head against Salesforce Service Cloud + Agentforce in B2C, and Zendesk plus AI-natives like Decagon are compressing the mid-market floor.
The IT-buyer trust ServiceNow built over 20 years does not transfer cleanly to the customer-service CRO buyer, who lives in a different procurement universe. But killing CSM would be a strategic unforced error: Now CRM positioning needs CSM as its foundation, the named B2B enterprise CSM book (NVIDIA, BT Group, Visa, Equinix) is a real wedge, and Workflow Data Fabric ties CSM to IT context in a way no pure-play competitor can match.
The right move is not to kill CSM — it is to kill the wrong parts of CSM (B2C contact-center, marketing-automation creep, commerce-side features) and double down on B2B enterprise CSM tied to IT operations, with a Decagon-class acquisition to compress the AI-agent gap.
The Steelmanned Case For Killing CSM
- Sub-15% of revenue, low NRR contribution — CSM is a rounding error against ITSM + ITOM + HRSD; killing it frees engineering + sales capacity for higher-leverage bets
- Salesforce Service Cloud + Agentforce wins B2C decisively — Benioff has a 20-year head start on customer-service CRM workflows and Agentforce is closing the AI-agent gap fast
- Zendesk + AI-natives compress the mid-market — Decagon, Sierra, Ada are eating sub-$1B-revenue customer-service deals at price points ServiceNow cannot profitably serve
- ServiceNow's IT-buyer trust does not transfer to the CCO/CRO buyer — different procurement, different RFP language, different reference customers; CSM sales cycles are 30-40% longer than ITSM
- Opportunity cost is enormous — every dollar of R&D in CSM is a dollar not in AI agents, Workflow Data Fabric, or vertical industry products where ServiceNow has uncontested share
The 4 Reasons To Keep CSM
- Now CRM positioning needs CSM as foundation — McDermott has publicly framed Now CRM as the enterprise CRM alternative; killing CSM guts that narrative on day one
- B2B enterprise CSM is a real wedge — NVIDIA, BT Group, Visa, Equinix run CSM at scale because it ties customer issues to IT root cause in a single workflow
- Workflow Data Fabric ties CSM to IT context — single-pane CIO + CCO view is a defensible moat no pure-play CRM competitor can replicate
- Killing it would signal weakness — Salesforce + Microsoft would reposition aggressively; ServiceNow would be tagged as an "IT-only" company forever, capping the TAM story Wall Street has priced in
What Killing CSM Would Cost
- Named-customer churn risk — NVIDIA, BT, Visa, Equinix have multi-year CSM contracts; sunsetting forces them to Salesforce or Microsoft and risks adjacent ITSM revenue
- Brand impact — "ServiceNow exited customer service" headline is permanent; the Now Platform narrative dies with it
- Sales-team disruption — ~15-20% of enterprise AEs carry CSM quota components; comp-plan rebuild + attrition would hit FY27 bookings
- Lost AI-agent revenue line — customer service is the highest-volume use case for Now Assist agents; killing CSM removes the showcase
- Public-market reaction — analysts would read the kill as a TAM contraction; multiple compression of even 2-3 turns wipes $40-60B of market cap on a $200B+ company
The Refocus Alternative — Kill The Wrong Parts
- Kill B2C contact-center features — high-volume voice, IVR, consumer-facing chat; concede to Salesforce + Genesys + Five9
- Kill marketing-automation features — anything that overlaps Marketing Cloud or HubSpot; ServiceNow has no business in campaign orchestration
- Kill commerce-side features — order management, returns, B2C cart recovery; this is Shopify + Salesforce Commerce Cloud territory
- Kill mid-market SKUs that lose to Zendesk — stop chasing sub-$10K-ARR deals; the unit economics never work
- Double down on B2B enterprise CSM tied to IT — large-enterprise customer issues that map to IT incidents, change management, and asset records
- Reposition the surviving module as "Enterprise Service Operations" — distinct from generic CRM customer service, anchored in IT-operational truth
The Veeva Pattern (Don't Kill, Spin Out)
- Precedent — Veeva spun out of Salesforce in 2007 as a vertical CRM for life sciences; today a ~$30B public company that beat Salesforce in its niche
- Pattern applied — ServiceNow could spin CSM into "ServiceNow CRM" sub-brand with its own GM, P&L, and sales motion
- Strategic logic — separates the CCO/CRO buyer motion from the CIO buyer motion without losing the platform tie
- Optionality — sub-brand can be sold, partially divested, or IPO'd later if it grows into a real franchise
- Risk — sub-brand without full separation often gets the worst of both worlds; only works if McDermott commits real capital + autonomy
What McDermott Should Actually Do
- Refocus CSM exclusively on B2B enterprise — sunset the B2C SKU, narrow the ICP to Global 2000
- Integrate Now Assist deeply for customer-service AI agents — make CSM the showcase deployment for agentic Now Platform
- Partner with named contact-center vendors instead of building — Five9, Genesys, NICE for voice + IVR; stop competing in adjacent capability
- Acquire Decagon for $300-500M — compress the AI-native gap by 18-24 months and inherit a customer base ServiceNow could never sell to organically
- Set a $2B FY28 CSM revenue target as public commitment — forces internal accountability and signals to Wall Street that CSM is not on the chopping block
- Quarterly CSM-specific analyst day — the module is too important to bury inside the omnibus earnings narrative
Strategy Options
| Option | Revenue Impact | Customer Impact | Competitive Impact | Recommendation |
|---|---|---|---|---|
| Kill outright | -$2-3B ARR, -$40-60B market cap | NVIDIA/BT/Visa/Equinix churn risk | Salesforce + Microsoft reposition; ServiceNow tagged "IT-only" | Do not do |
| Sunset slowly (3yr) | -$1-2B ARR over 3yr | Managed migration, brand damage | Competitors fill the gap before sunset completes | Do not do |
| Refocus on B2B enterprise | Flat short-term, +$1-2B by FY28 | Mid-market churn, enterprise upsell | Defensible niche; concede B2C cleanly | Do this |
| Spin out as ServiceNow CRM sub-brand | Neutral 24mo, optionality after | Buyer-motion clarity for CCO/CRO | Veeva pattern; separates from CIO motion | Consider as Plan B |
| Keep + invest broadly | +$500M-1B by FY28 | Continued mid-market loss to Zendesk | Stuck-in-the-middle vs Salesforce + AI-natives | Worse than refocus |
| Refocus + Decagon acquisition | +$2-3B by FY28 | Inherit AI-native customer base | Compresses Agentforce gap by 18-24mo | Best path |
| Partner-only (kill build) | Flat | Dependency on Five9/Genesys/NICE | Loses platform-control narrative | Half-measure |
Strategic Decision Flow
FAQ
What is the steelmanned case for killing ServiceNow CSM? CSM is sub-15% of revenue (a rounding error against ITSM, ITOM, and HRSD), loses head-to-head to Salesforce Service Cloud plus Agentforce in B2C, and faces mid-market compression from Decagon, Sierra, and Ada. ServiceNow's IT-buyer trust doesn't transfer to the CCO/CRO buyer, and CSM sales cycles run 30-40% longer than ITSM.
Every R&D dollar in CSM is one not spent on AI agents or vertical products where the company has uncontested share.
Why would killing CSM be a strategic error? Now CRM positioning needs CSM as its foundation, and named B2B accounts like NVIDIA, BT Group, Visa, and Equinix run it because it ties customer issues to IT root cause in one workflow. Workflow Data Fabric gives a single-pane CIO plus CCO view no pure-play CRM rival can replicate.
Killing it would tag ServiceNow as "IT-only" forever and signal weakness to Salesforce and Microsoft.
What would killing CSM actually cost? Named-customer churn risk threatens multi-year contracts and adjacent ITSM revenue, and 15-20% of enterprise AEs carry CSM quota components, so a comp-plan rebuild would hit FY27 bookings. Analysts would read the exit as TAM contraction; even 2-3 turns of multiple compression would wipe $40-60B of market cap on a $200B+ company.
It would also remove the highest-volume showcase for Now Assist agents.
Which parts of CSM does the article recommend killing instead? The refocus alternative kills the wrong parts: B2C contact-center features (high-volume voice, IVR, consumer chat), marketing-automation creep, commerce-side features like order management and cart recovery, and mid-market SKUs that lose to Zendesk.
The surviving module gets repositioned as "Enterprise Service Operations," anchored in IT-operational truth and tied to IT incidents, change management, and asset records.
What is the Veeva pattern and how would it apply? Veeva spun out of Salesforce in 2007 as a vertical life-sciences CRM and is now a ~$30B public company that beat Salesforce in its niche. Applied to ServiceNow, CSM could spin into a "ServiceNow CRM" sub-brand with its own GM, P&L, and sales motion, separating the CCO/CRO buyer from the CIO buyer.
The risk is that a half-separated sub-brand gets the worst of both worlds unless McDermott commits real capital and autonomy.
Bottom Line
No, ServiceNow should not kill CSM — but the steelmanned kill case is strong enough that doing nothing is also wrong. The right play is to kill the wrong parts (B2C, marketing, commerce, mid-market), double down on B2B enterprise CSM tied to IT context, and acquire Decagon to compress the AI-agent gap.
McDermott has the capital, the customer base, and the platform leverage to make CSM a $2B FY28 line — but only if he stops trying to be everything to everyone in customer service. *(see also: q1623, q1625, q1634)*