Contents
This is a case study of how a mid-sized defence manufacturer in the Middle East fixed its customer information systems. Customer data lived in three places, quotes went out with inconsistent pricing and approvals got lost in email. The fix was a single customer record in Microsoft Dynamics, rule-based quoting in Experlogix CPQ, and an automated handoff of approved quotes into SAP Sales and Distribution (SD) through SAP Cloud Integration. Quote turnaround fell by 35% on average. It is written for sales operations, IT and finance leaders in manufacturers with long, configurable, compliance-heavy sales cycles. The rollout sequence and lessons near the end are the parts to reuse.
When defence teams ask for customer information systems, they usually mean more than a CRM. They want structure: a place where complex decisions sit together in context, across long sales cycles, compliance-heavy workflows and changing groups of decision-makers.
In my role as Digital Transformation Director at a defence company, I was asked to solve exactly this. The problem was not missing effort. People were doing the work. The issue was that the effort had no home. No shared platform, no visibility, and no alignment between what was being sold and what was being planned.
A mid-sized defence manufacturer in the Middle East. It operated behind the scenes: not a public brand, and visibility was not the point. Its components were used in military aviation and secure communications.
Every sale followed a detailed path: engineering reviews, compliance checks, internal approvals, version-controlled quotes. It was not chaotic, but it was heavy.
The customer information systems were falling apart. Sales used one platform. Support used another. Operations worked from spreadsheets, offline folders and documents that were out of date before anyone opened them.
Here is what was broken and what it cost:
| What was broken | Impact |
|---|---|
| No CRM for opportunity flow or visibility of decision-makers | No shared picture of where each deal stood |
| Pricing handled manually with no consistent record | Quotes went out with outdated or conflicting numbers |
| Approvals through email, often lost or delayed | Compliance audit trails were incomplete |
| Customer records duplicated across systems, with slightly different details | Nobody could say which version was accurate |
On paper it looked structured. Follow a quote from creation to delivery and it fell apart. Approvals stalled without clear ownership. Pricing depended on who submitted the quote. Quotes were buried in email threads. Teams asked each other the same questions again and again. None of these were dramatic failures, but over months the small delays added up, and for a business with long sales cycles the lost momentum mattered more than most people realised.
The goal was not to replace everything. It was to reduce friction without making anything harder to use: helping the systems reflect how the teams already worked, not forcing people into rigid processes.
I spent time with the teams before touching any configuration. I watched how work moved from capture to delivery, where the tools got in the way, and where people had stopped trusting the data.
Three priorities came out of those sessions:
- One shared customer record, visible to sales, support and operations in the same format. No more parallel versions.
- Structured quoting, following consistent rules for configuration and pricing instead of individual habits and old templates.
- Connected order execution, with a clean handoff from approved quote to SAP SD and no manual re-entry.
| System | What it solved |
|---|---|
| Microsoft Dynamics CRM | One customer record, linked to sales activity and opportunities |
| Experlogix Configure Price Quote (CPQ) | Product configuration rules, pricing logic, quote versions |
| SAP Sales and Distribution (SD) | Order execution and fulfilment |
| SAP Cloud Integration (CPI) | Integration layer connecting CPQ and CRM to SAP SD |
Microsoft Dynamics as the foundation. We needed one place where customer information was accurate and visible in full context. Dynamics gave us a place to start untangling the data. Familiarity with the platform helped, and so did its fit with Outlook and Teams. It did not require people to start over; it needed adjustments to fit how the business worked. Once teams saw the same data in the same format across functions, trust started to build.
Experlogix CPQ for configuration and pricing. Before, quoting was done in too many different ways. People relied on memory and manual edits. We set Experlogix up with defined rules for product combinations, pricing tied to configurations, and approval routing by deal type and value. It felt limiting at first, and some people were not shy about saying so, but it removed the ambiguity. Engineering received cleaner quotes, and sales stopped adjusting prices from memory of previous deals.
SAP SD through SAP CPI. SAP SD was already in use for orders. The gap was the handoff: an approved quote still had to be re-keyed into SAP. We integrated the two through SAP CPI, so approved quotes pushed straight into SAP as orders and customer and order data stayed in sync between Dynamics and SAP. Where we hit limitations, we added custom logic. It was not elegant in every case, but it worked.
- Customer recordMicrosoft Dynamics, one version for every team
- Configure and priceExperlogix CPQ rules for combinations and pricing
- ApproveRouted by deal type and value
- Create the orderSAP CPI pushes the approved quote into SAP SD
- FulfilSAP SD, with customer data kept in sync
No re-entry, and an audit trail from approval to order
The rollout was phased over roughly six to eight months. Nothing dramatic: layered changes, validated at each step.
- Pilot. A small group of users and specific scenarios focused on CRM and CPQ. We tested edge cases, surfaced gaps and made changes before scaling.
- Clean the data. Customer records were consolidated and de-duplicated before they went into Dynamics, with compliance documents linked to the right opportunities. This took longer than the configuration.
- Extend across departments. Once the pilot workflows were refined, the solution went to sales, support and operations.
- Integrate SAP SD midway. The CPQ-to-SAP integration went live once the upstream systems were stable, so early problems did not cascade into orders.
Security and compliance were designed in from day one. For a defence client, audit trail integrity and role-based access are not optional. We defined access roles clearly and tracked approval trails. Data residency was settled early: all data stayed within the UAE, in line with defence-sector rules. That slowed us slightly at the start, and it prevented more serious problems later.
Training was practical: short sessions, targeted materials, live demonstrations and how-to videos, continuing across weeks and months rather than in one session. Adoption was not perfect at first. Steady support and visible benefits overcame the early hesitation. The turning point came when teams used the tools in real situations and found that the data they got back was correct.
| Outcome | What changed |
|---|---|
| Quote turnaround time | Down 35% on average; hours saved on many deals and several days on complex ones |
| Configuration accuracy | Validation rules prevented errors before they reached engineering |
| Audit readiness | Compliance checks no longer needed a last-minute rush |
| Cross-team alignment | Sales, support and operations worked from the same customer record |
The 35% reduction did not happen in the first week. Early cycles still involved clarifications and corrections. Once product rules and pricing logic were consistent, quoting sped up. Sales representatives no longer chased approvals or fixed reused templates. The system handled those steps.
Customer Information Systems only create value when they reduce hesitation. Once teams stopped second-guessing each other's data, speed and confidence followed.
Alignment matters more than technology. The technical build was the easier part. Getting teams to trust one source of truth and stop maintaining their own records was harder. It meant showing people the data was reliable before asking them to depend on it.
Integration details matter more than features. The CPQ-to-SAP SD integration is what made the whole system valuable. A standalone CRM and standalone quoting with manual order entry would each have helped a little. The connection between them is where the friction disappeared.
Support and training make it stick. Deployed and abandoned is not delivered. Training continued for weeks and months after go-live, and that period is where adoption either takes hold or unravels.
The architecture still holds: CRM for the customer record, CPQ for structured quoting, ERP integration for order execution. Three things would change if the same engagement started now.
The integration platform. SAP CPI is now the Cloud Integration capability inside SAP Integration Suite, alongside API management, event-based integration and prebuilt integration content. A Dynamics-to-CPQ-to-SAP SD flow would take less design time today. My SAP Cloud Integration guide covers the platform.
SAP's own CRM would be on the shortlist. With an SAP SD back end, a new engagement should compare SAP Sales Cloud, which now includes Joule, with Microsoft Dynamics. Dynamics was the right choice here because of existing familiarity. The answer still depends on capability and integration preferences, but the SAP-native option is a more credible contender than it used to be. My comparison of CRM systems for SAP covers the options.
US federal scope needs a different hosting model. This client did not need it, but a defence company with US federal operations would look at SAP National Security Services (SAP NS2). In 2025 it received a provisional authorisation to run S/4HANA Cloud Private Edition and SAP BTP at FedRAMP+ Impact Level 5, with US-only operations.
Defence-specific requirements (audit trails, role-based access, version control on quotes, data residency) apply whatever the platform generation. For the wider compliance picture, see my guide to SAP compliance in the public sector.
Why was Microsoft Dynamics selected over other CRM platforms?
It could manage the full customer lifecycle, from lead to opportunity to post-sales engagement, and handle the long, complex deal cycles of defence sales. Its fit with Outlook and Teams helped adoption, and the team's familiarity with it lowered the barrier further.
Access control, audit logging, flexibility and room to scale were the other deciding factors for a compliance-heavy client.
What role did Experlogix CPQ play, and why CPQ at all?
Defence products have complex configuration rules. A price list cannot capture the interaction between product variants, compliance requirements and customer-specific terms. Without CPQ, each quote depended on whoever built it knowing the rules.
Experlogix put those rules into the quoting tool. A sales representative got validation feedback while building the quote, not a correction from engineering days later. Errors moved upstream, where they are cheap to fix.
How was SAP SD integrated with CRM and CPQ?
SAP CPI acted as the middleware. An approved quote in Experlogix triggered a flow that created the order in SAP SD with the right line items, pricing and customer data. CPI also kept customer and order data in sync between Dynamics and SAP, with validation rules to stop mismatched data.
Before, someone copied each approved quote into SAP by hand. Automating it removed re-entry errors and created a clean audit trail from approval to order.
What were the biggest challenges during implementation?
Data quality first. Customer data was inconsistent across departments, with duplicates and missing fields, and it had to be cleaned before Dynamics could be the source of truth.
Integration mapping came second, especially for product configurations and pricing across three systems. Third was aligning sales, engineering, IT and finance, particularly when ownership of parts of the process changed.
How was security and compliance handled?
It was built in from day one. Every component had to meet internal security policies and national regulations. Role-based access limited who could see and change which records. Full audit trails covered quoting, approvals and data changes. All data stayed in the UAE, in line with defence-sector rules.
Because the design started from those requirements, the data was already in the right shape when compliance reviews came round.
How long did the rollout take?
Roughly six to eight months, in phases. It began with a pilot focused on CRM and CPQ, extended across departments after feedback, and added the SAP SD integration midway once the upstream systems were stable. Training, support and tuning continued throughout.
Can this model be applied to other defence or manufacturing companies?
Yes, wherever sales cycles are long, products are configurable and compliance documentation is required: aerospace, industrial equipment and any business where a quote needs engineering validation before it goes out.
The specific tools matter less than the integration logic. The approved quote must flow into the ERP without re-entry, and the customer record must be a single source of truth.
Written by
