SalesValue blog

ServiceNow CRM implementation strategy: The Middle Out Approach

thomas@salesvalue.com (Thomas Thejn) — Sat, 20 Dec 2025 07:50:40 GMT

Are you considering ServiceNow CRM Sales and Order management and CPQ?

ServiceNow CRM Sales and Order management and CPQ have some powerful functionalities that can help streamline the Lead-to-Cash processes, especially for Technology Providers and Telecommunication companies. Therefore we see many companies that are evaluating and considering ServiceNow CRM.

Many companies already have ServiceNow Customer Service Management (CSM) handling post-sales support, ServiceNow ITSM for IT operations and a classical CRM solution like Salesforce or Microsoft Dynamics handling the front-end sales hustle.

Now, you want to bridge the gap using ServiceNow Sales and Order Management (SOM) and CPQ.

The million-dollar question is: In what order do you roll these out? Do you fix the quoting process first? Do you tackle order fulfillment? Or do you try to rip and replace the CRM immediately?

Getting this sequence wrong results in "shelf-ware" and frustrated sales teams. Getting it right creates a seamless flow from "Opportunity" to "Renewal."

This article describes a popular approach that I call “The Middle Out” Approach. Later blogs will explore alternative strategies.

Phase 1: The Foundation – Product Data & Catalog Management

To be able to optimize your Lead-to-Cash workflows, you must harmonize your product data.

We often experience that in a split environment, with an external CRM and ServiceNow for support and operations, the definition of a "product" often differs. Sales cares about price and bundling and operations and fulfillment cares about provisioning and assets.

I have seen many CRM implementations where opportunities only have a simple line item like “Support” and an estimated price. Operations needs to know what exactly has been agreed and link it to SLA definitions, sold products and infrastructure components, so they have to dig into the contract documents to find the data they need and manually enter this in ServiceNow. This means there is no direct link from the CRM to ServiceNow and a lot of manual work.

The Goal: Create a unified Product Catalog within ServiceNow.
The Action: Centralize your product definitions, pricing, and compatibility rules in ServiceNow. Even if the quote happens elsewhere, ServiceNow must become the system of record for what you sell, so it knows how to fulfill it.

Pro Tip: If your product data is messy, no amount of integration or automation will fix your process. Fix the data first.

Phase 2: Order Management - The Bridge

Many organizations are tempted to start with CPQ Quote because it’s "sexy" and visible to Sales. This is a mistake. If you implement CPQ without a robust fulfillment engine behind it, you are just letting sales reps quote deals faster, but don’t have a fulfillment engine.

We recommend to implement the Order Management module of SOM first:

Why: You need to fill the "black hole" that exists between the CRM "Closed Won" status and the CSM "Active Asset" status.
The Workflow:
1. Deal is marked "Closed Won" in your external CRM.
2. Integration triggers an Order in ServiceNow SOM.
3. ServiceNow orchestrates the decomposition, breaking the bundle into parts, and fulfillment, provisioning software, shipping hardware, dispatching field service.
4. Upon completion, it automatically updates the CSM Install Base

As described above we often experience that this step is done manually. By implementing ServiceNow Order Management you optimize your Lead-to-Cash process, which eliminates a lot of manual efforts and errors.

The Value: This immediately benefits your operations team. Support agents can finally see exactly what was sold and its current deployment status without swiveling chairs.

Phase 3: CPQ (Configure, Price, Quote)

Once your fulfillment engine (Phase 2) is running, you can move upstream to CPQ.

Now that ServiceNow knows how to fulfill an order, it is perfectly positioned to tell Sales how to configure it.

The Strategy: You don't necessarily need to force Sales Reps out of their external CRM. You can embed the ServiceNow CPQ interface inside your external CRM e.g., via iframe or canvas app.
The Benefit: Sales reps stay in their preferred environment, but the logic (pricing, bundling, compatibility) is driven by ServiceNow.
Why this order matters: Because you did Phase 1 and 2 first, the quote generated in Phase 3 is guaranteed to be fulfillable. You eliminate "clean orders" issues where Sales sells something Operations cannot deliver.

Phase 4: Sales Force Automation

The final piece of the puzzle is moving the actual Opportunity and Lead management into ServiceNow Sales Force Automation.

The Decision: If your organization is deeply retrenched in Salesforce or Dynamics for pipeline management, you may never do this step—and that is okay.
The Pivot: However, if you are looking to optimize your Lead-to-Cash flow, consolidate license costs and have a simpler sales cycle, migrating the "Front Office" to ServiceNow is the final step.

Summary: The "Middle-Out" Approach

With this implementation strategy we work from the Middle-Out.

Sequence	Module	Purpose	Stakeholder Benefit
1	Product Catalog	The "Brain"	Data consistency across the enterprise.
2	Order Management	The "Backbone"	Ops & CSM get visibility; Support knows what the customer owns.
3	CPQ	The "Mouth"	Sales quotes complex bundles accurately based on fulfillment rules.
4	SFA (CRM)	The "Face"	(Optional) Full platform consolidation.

By prioritizing Order Management, you leverage your existing CSM investment immediately, turning your support team into proactive partners who know the customer's context the moment they pick up the phone.

The Un-CRM: Why ServiceNow is Rewriting the Rulebook

thomas@salesvalue.com (Thomas Thejn) — Wed, 10 Dec 2025 19:26:38 GMT

The Un-CRM: Why ServiceNow is Rewriting the Rulebook for Telcos and Tech Providers

If you walk into a boardroom and ask about CRM, the immediate answers are almost muscle memory: Salesforce, Microsoft Dynamics 365, maybe HubSpot. These platforms are the titans of the "Front Office CRM"—they are excellent at managing the commercial relationship.

But as a CIO in a Technology Provider or Telecommunications company I would personally select ServiceNow CRM.

In these industries, the commercial relationship is only 10% of the battle. The real challenge is the technical delivery, and customer support. And a good customer experience starts already in the sales phase when this is linked seamlessly to the delivery and operations.

While traditional CRMs have perfected the art of getting the signature, they often fail at what comes next: provisioning the applications and servers, onboarding to the managed services, installing the fiber line, activating the SaaS license, or shipping the router. This disconnect creates the "swivel-chair" effect, where a lot of knowledge is lost from sales to delivery, creating a bad customer experience, and missing a lot of opportunities for evolving the relationship.

Enter ServiceNow CRM. With the release of Sales and Order Management (SOM), they aren't just building another database of contacts. They are building a "System of Action" that connects the promise of a sale to the complex reality of technology service delivery.

Here is why ServiceNow’s approach is uniquely critical for the Tech and Telco sectors compared to Salesforce, Microsoft, and HubSpot.

1. The Core Philosophy: "System of Record" vs. "System of Action"

To understand the difference, you have to look at the DNA of the platforms.

The Traditional Players (Salesforce, Microsoft, HubSpot):

These are Systems of Record. Their job is to track the Lead and the Opportunity. In a simple retail or B2B context (selling boxes of paper), this is fine. But for Technology Providers and Telco's, once the deal is marked "Closed-Won," the hard work begins. Traditional CRMs don't connect directly with the delivery and operations.

ServiceNow:

ServiceNow is a workflow engine—a System of Action. Its DNA is in IT operations and Customer support. It understands that a "Sale" in the tech world is actually a trigger for a complex chain of digital events. It doesn't just record the order; it orchestrates the engineering tasks required to fulfill it.

The Key Difference: Salesforce and Microsoft focuses on Managing the Commercial Relationship. ServiceNow focuses on seamlessly integrating Sales, Service and Operations.

2. The Tech & Telco Dilemma: Dealing with "Order Decomposition"

This is where ServiceNow separates itself from the pack.

In Technology and Telco, a customer doesn't just buy one thing. They buy a "bundle" e.g., Managed Services agreement, Business Internet + SD-WAN + Licenses).

Salesforce and Microsoft often sees this as one line item with a price.
ServiceNow sees this as a composite order that must be "decomposed."

ServiceNow SOM natively takes that single commercial order and breaks it down into distinct technical orders:

Logistics: Ship the SD-WAN router.
Network Engineering: Provision the IP address and configure the firewall.
IT Ops: Automate the creation of 50 user accounts in the cloud.

While Salesforce requires heavy customization, add-ons or integrations to handle this, ServiceNow does this using the same workflow engine that already manages your Customer Service and IT infrastructure.

3. The "MACD" Nightmare (Move, Add, Change, Delete)

For subscription-based tech companies, the initial sale is easy. The nightmare is MACD.

Customer wants to add new applications or systems to the managed services agreement.
Customer moves offices and needs to move their fiber connection.

In a traditional CRM, these are administrative headaches. The sales rep often has no visibility into the current technical configuration of the customer's assets. They might sell an upgrade that is technically impossible in that region.

ServiceNow’s Advantage:

Because ServiceNow maintains the CMDB (Configuration Management Database) and the Installed Base, it knows the exact technical state of the customer at all times.

It knows the serial number of the router on-site.
It knows the current firmware version.
It prevents sales reps from selling incompatible add-ons (Rule-based selling).
It recommends upgrades and add-on products and services based on existing products.

4. Comparison: Handling a Complex Tech Order

Feature	Salesforce / Dynamics 365	ServiceNow SOM
Primary Goal	Pipeline visibility & Forecasting.	Order Orchestration & Fulfillment.
Data View	Customer Profile & Contract History.	Installed Base & Service Health.
Order Fulfillment	Requires integration to ERP or external Provisioning tools.	Native workflows trigger Network/Cloud Provisioning.
MACD (Changes)	complex; often disconnects old data from new.	Native; modifies the live asset record instantly.
Service Assurance	Reactive; logs a ticket when the customer complains.	Proactive; network alerts can auto-create cases before the customer calls.

5. Bridging the "Middle Office" Gap

Tech and Telco companies suffer most from the "Middle Office" gap—the messy layer between the Sales team (Front Office) and the Network/Finance teams (Back Office).

ServiceNow Sales & Order Management sits squarely here. It acts as the glue.

It allows a company to easily transition from the Sales to Customer Onboarding and Delivery of the Services in one integrated workflow and system.
It allows a Service Agent to see if a recent Network Outage is the reason a customer is calling to complain about a bill.

HubSpot and Microsoft generally lack this "Service Awareness." They know who the customer is, but they don't know the status of the services running the customer's business. ServiceNow does.

6. Summary: When to Choose Which?

Choose Salesforce or HubSpot if:

You are a pure-play SaaS startup with simple provisioning.
Your primary need is aggressive Lead Generation and Marketing Automation.
Verdict: Great for Acquiring the logo.

Choose ServiceNow SOM if:

You are a Telco, MSP (Managed Service Provider), or Hardware/Software Provider.
Your product requires physical installation, complex configuration, or multi-team coordination to deliver.
You struggle with high churn because "Sales sold it, but Ops couldn't deliver it on time."
You struggle with high cost of delivery and long time from lead to cash
Verdict: The only choice for Delivering the complex service.