Microsoft Dynamics 365 CRM
Connect the customer relationship
across sales, service and insight.
FragmentedConnected
Sales, service, customer insight and business process capability connected around the customer relationship, built from the Microsoft applications the process genuinely needs rather than every capability available.
CRM should help the organisation understand the customer relationship, not simply record customer activity.
When customer activity becomes harder to coordinate
The problem is rarely that the organisation has no customer data.
It is usually that the information, the activity and the ownership sit in different places, so the next action depends on who happens to know.
If several of these are familiar, the first CRM question is coordination rather than storage.
Customer information is scattered
Important context lives across inboxes, spreadsheets, ERP, documents and individual knowledge.
Pipeline is hard to trust
Opportunities exist, but stage, value, activity and next action are inconsistent.
Follow-up depends on people
Important activity is remembered rather than systematically coordinated.
Service is fragmented
Cases, communication and ownership are difficult to see in one place.
Teams work differently
Sales, service and operations use different processes and definitions.
Reporting needs reconstruction
Leadership cannot easily see pipeline, service workload or customer activity.
Customer history is incomplete
The person handling the next interaction may not understand what happened before.
CRM exists but adoption is low
The platform is technically live but users work around it.
CRM should make the next customer decision clearer. Not simply record the last interaction.
The real value of CRM comes from helping people understand who the customer is, what is happening, who owns the next action and what the relationship needs next.
What changes when the relationship is connected
One customer operating model, from first interest to renewed commitment.
Not every organisation needs every stage or every Dynamics application. The model is a way to decide what matters first.
01
Attract
Interest arrives from campaigns, referrals, partners and the market.
02
Engage
Early conversations become visible rather than personal.
03
Qualify
Decide what is real before it consumes commercial effort.
04
Sell
Progress opportunities with clear ownership and next actions.
05
Serve
Handle issues, requests and cases against the same relationship.
06
Retain
Keep the relationship healthy after the first commitment.
07
Grow
Extend the relationship where value has been demonstrated.
Customer data
The information every team needs before the next interaction.
Activity
What has happened, and what is currently in progress.
Ownership
Who is accountable for the next action.
Automation
Predictable coordination handled by the platform, not by memory.
Insight
Enough visibility for leadership to see movement and risk.
Pipeline credibility
A pipeline is not believable simply because the opportunity exists in CRM.
Dynamics 365 makes commercial discipline visible. It does not create that discipline by itself. The maturity below is about evidence, not about configuring more stages.
01
Lead
Interest exists. Nothing has been tested yet.
02
Qualified opportunity
A real customer problem, a relevant stakeholder and a reason to act.
03
Active pipeline
Meaningful engagement, an accountable owner and a clear next action.
04
Forecastable opportunity
Evidence supports the value, the timing and the customer's route to a decision.
05
Commercial commitment
The customer has committed, and delivery can be planned against it.
What should move an opportunity forward
- An understood customer problem
- Relevant stakeholders identified
- Meaningful customer engagement
- A clear next action
- An accountable owner
- A realistic value
- Realistic timing
- Stage entry and exit criteria
- Known blockers
- Recent activity
- An appropriate delivery route
Recorded opportunity value is not automatically forecast value.
A CRM cannot fix a sales process nobody agrees on
- What makes an opportunity real?
- When should it enter the pipeline?
- What information is required?
- Who owns the next action?
- What changes the stage?
- What makes an opportunity forecastable?
- When should it close?
What should CRM solve first?
Do not start by trying to transform every customer process at once.
The question is which first problem creates enough value to justify the change it asks of people.
Sales
Make lead and opportunity management consistent.
Service
Create clearer case ownership and resolution.
Relationship
Bring important stakeholder activity into one place.
Case management
Structure a focused process around ownership and action.
Customer data
Improve the quality and connection of customer information.
Automation
Remove repetitive coordination.
Which Microsoft capability may be relevant
CRM is the outcome. The applications are how it is assembled.
Microsoft does not sell a single product called Dynamics 365 CRM. A CRM solution uses the applications the customer process needs, and very few organisations need all of them.
Dynamics 365 Sales
Leads, accounts, contacts, opportunities, activity, pipeline stages, forecasting and quotes where appropriate.
Dynamics 365 Customer Service
Cases, queues, ownership, knowledge, communication, entitlements and resolution.
Dynamics 365 Customer Insights - Journeys
Forms, consent, segments, customer journeys, event-driven engagement, nurture and campaign interaction.
Dynamics 365 Customer Insights - Data
Unified customer profiles, customer data, segmentation, enrichment and behaviour activated across sales, service and engagement.
Dynamics 365 Field Service
Work orders, scheduling, resources, assets and mobile execution, where service delivery includes field operations.
Dataverse
The shared data platform, security model and business logic underneath the customer solution.
Power Apps and Power Automate
A focused application or automated coordination where that fits the process better than the core CRM experience.
Power Pages
External interaction with customers, members or partners, where a portal is genuinely required.
Power BI
Reporting and analysis beyond standard Dynamics views and dashboards.
Customer Insights - Journeys and Customer Insights - Data are distinct capabilities, and neither is automatically part of a CRM implementation. Qualification decides whether either belongs in the customer operating model, and whether the organisation can operate and govern it once it is live.
Capability in business terms
Open only what is relevant. Each area explains the customer process it supports rather than listing product features.
- Cases, queues, ownership, priority and status
- Activities, knowledge and communication
- Entitlements and SLAs where appropriate
- Escalation, resolution and service dashboards
- Service teams should be able to see what happened, what is waiting, who owns it and what needs to happen next
Customer view
Give teams the context they need before the next interaction.
Built from the information the process genuinely needs rather than every field the platform can hold.
- Account
- Contact
- Relationship
- Activity history
- Open opportunities
- Open cases
- Products and services where integrated
- Orders and financial context where integrated
- Communications
- Tasks
- Notes
- Documents
- Stakeholders
Where CRM and ERP are integrated, product, order and financial context can be made visible alongside the relationship. Where they are not, the design should be honest about what CRM does and does not know.
CRM and ERP
Decide which platform is authoritative, object by object.
CRM typically coordinates customer engagement. ERP typically governs transactional and operational execution. The architecture determines which platform is authoritative for each process and data object, and no single ownership model fits every organisation.
Account and customer
Which platform is authoritative for the customer record, and how the other is kept accurate.
Contact
Usually coordinated in CRM, though ERP may hold transactional contacts of its own.
Product
Normally governed in ERP and surfaced in CRM where selling needs it.
Pricing
Where price is calculated, and whether CRM may quote independently.
Quote
Which platform produces the quote, and what happens on acceptance.
Order
Where the order becomes real, and how CRM sees its progress.
Availability
Whether CRM shows live availability or a periodic position.
Credit
Where credit status is held, and whether it constrains selling.
Invoice
Where invoices live, and what financial context CRM should show.
Service history
Whether service history sits with the relationship, the asset or the transaction.
Where Business Central is the ERP
CRM may connect customer engagement to customers, products, sales orders, availability, invoices and wider operational context.
Explore Business CentralWhere enterprise ERP is required
CRM may connect with Dynamics 365 Finance and Supply Chain Management around product data, pricing, availability, sales orders, service context and enterprise customer data.
Explore Finance and Supply Chain ManagementBefore designing another integration
More integrations do not make a better CRM solution.
Retain and integrate
The dependency is genuinely needed and worth connecting.
Replace
Standard Microsoft capability may cover it without another integration.
Consolidate
Several overlapping systems may become one.
Retire
The system exists because it always has, not because it is needed.
Defer
The dependency is real but does not belong in the first release.
Where an integration is genuinely needed, design it properly:
- Ownership
- System of record
- Data direction
- Frequency
- Error handling
- Reconciliation where needed
- Support ownership
- Security
- Testability
Specialised operating models
Some organisations run a service model so specialised that forcing every requirement into generic CRM case configuration creates a system that is hard to operate and harder to change. Where that is true, a purpose-built solution on Microsoft technology may fit better.
AI with purpose
Use AI to reduce administration and improve context.
AI is the last step in a sequence, not the first. Microsoft provides AI-assisted experiences across Dynamics 365 and Microsoft 365, and we add configured automation or bespoke capability only where the business activity justifies it.
01
Process
Agree how the work should be done before automating any of it.
02
Data
Assistance is only as good as the customer information underneath it.
03
Automation
Remove repeatable coordination with configured workflow.
04
Insight
Make movement, workload and risk visible to the people accountable.
05
AI
Reduce administration and improve context where that genuinely helps.
- Summarise customer history
- Draft routine email
- Prepare meeting context
- Find relevant knowledge
- Summarise cases
- Surface missing information
- Highlight follow-up
- Support pipeline review
- Support service triage
- Identify patterns
AI should not commit a forecast, approve a commercial offer or close a service case that needs professional judgement without human review.
CRM assessment
Answer a few questions and get a likely direction.
This is what we would examine before recommending applications, scope or a delivery route. It is indicative rather than a decision, and every answer is carried into the conversation so nothing has to be repeated.
Indicative signal
Answer the questions and we will show a likely direction. This is not an automated solution decision: final application scope and architecture always require qualification.
Your answers are carried through, so you will not be asked to repeat them. Final qualification is always a conversation.
When CRM may be relevant
- Customer information is fragmented.
- Pipeline visibility is unreliable.
- Sales follow-up is inconsistent.
- Service cases lack ownership.
- Relationship history is difficult to find.
- Manual coordination consumes time.
- Leadership needs better customer insight.
- Existing CRM adoption is poor.
- Customer processes need to connect with ERP.
What you receive
01Priority customer process
The first problem worth solving, and why it is first.
02Likely Microsoft direction
Which applications are likely to be relevant, and which are not needed yet.
03Data view
What condition the customer data is in, and who needs to own it.
04Integration considerations
Which dependencies are real, and which should be replaced, deferred or retired.
05Adoption considerations
What has to change in behaviour, not only in software.
06Recommended next conversation
Transform, RAPID 10, standard delivery, Recover or Optimise.
An assessment result is a likely direction and a recommended next conversation. Final solution architecture requires qualification.
Delivery routes
The platform may be the same. The right starting point may not be.
Four routes, one question: what is actually true today? Choosing the wrong route is usually why a CRM programme becomes expensive.
Transform
If the customer operating model is unclear, start with the transformation question.
- Sales and service processes
- CRM and ERP boundaries
- Customer data architecture
- Multiple operating models
- What CRM should solve first
Recover
If CRM is already live but confidence has fallen, first establish what is true.
- Poor adoption
- Heavy customisation
- Unstable platform
- Untrusted data
- Weak reporting
- Integration problems
- Unclear ownership
- Over budget
- Behind programme expectations
- Uncontrolled backlog
- Not supporting the intended process
A struggling CRM does not automatically need replacing. Recovery starts by establishing what is actually happening.
Explore RecoverOptimise
A live CRM should continue to improve.
- Adoption
- Data quality
- Automation
- Reporting
- Pipeline discipline
- Case management
- Integrations
- Licensing
- AI
- User experience
On acceleration
RAPID 10 is one qualified delivery route, not the default.
Where the first customer process is clear, scope can be controlled, standard capability fits and the organisation can maintain the required decision pace, RAPID 10 may be appropriate. Where it is not, standard delivery is often the better commercial decision, Transform may need to come first, a troubled programme may need Recover, and a live platform may need Optimise.
See how RAPID 10 is qualifiedHow implementation is controlled
Start with the customer process, then configure the technology.
The same disciplined route whether the first release is accelerated or conventional.
Understand
Business problem, users and customer process.
Design
Future workflow, data, roles and integration.
Validate
Representative scenarios with real users.
Configure
Build the agreed Dynamics and Power Platform solution.
Connect
Integrate the required systems.
Migrate
Move qualified customer data.
Prove
Test critical business processes.
Cutover
Move controlled into the new customer process.
Adopt
Prepare users and managers.
Improve
Use real experience to refine the platform.
Cutover
Cutover is the controlled transition into the new customer process. Not every CRM go-live is a large weekend event. Depending on scope, it may include:
- Production deployment
- Final data migration
- Security and roles
- Users and access
- Integrations
- Dashboards and reporting
- Communications
- Training
- Legacy process retirement
- Support arrangements
Confidence gates
Four points where we decide together whether to continue.
A gate is a decision point rather than a warning. Each one confirms that the conditions for the next stage of investment still hold.
Gate 1
Before design
Process and platform fit
Confirm that the problem, the users and the platform direction are understood well enough to justify design.
Confirmed at this gate
- The problem being solved
- The intended first outcome
- Who the users are
- Standard capability fit
- Platform direction
- Major dependencies
Decision
Proceed · Narrow the scope · Transform first · Consider an alternative platform
Gate 2
Before build
Design and readiness
Confirm that the future process is agreed and the organisation is ready to support what is about to be built.
Confirmed at this gate
- Future process
- Data ownership
- Data condition
- Integration approach
- Security model
- Business owners and key users
- Environment readiness
- Adoption and change plan
Decision
Proceed · Resolve readiness first · Re-scope
Gate 3
Before go-live planning
Prove
Confirm that the solution works end to end against real scenarios rather than against the build plan.
Confirmed at this gate
- Critical end-to-end scenarios
- Data
- Roles and security
- Integrations
- Automation
- Reports
- User acceptance testing
- User readiness
Decision
Proceed · Remediate · Re-plan
Gate 4
Before go-live
Go-live
A shared decision on whether the organisation is ready to run the customer process in the new platform.
Confirmed at this gate
- Production readiness
- Final data position
- Users and access
- Integrations
- Reporting
- Ownership
- Support arrangements
- Training and change
- Material open risks
Decision
Go · No-go · Controlled deferral
Shared responsibility
A partner can provide method, architecture and delivery. It cannot make the customer's business decisions.
These roles do not need to be full-time. They do need to exist, and they need to be able to decide.
Executive sponsor
Owns the business outcome and resolves escalations when priorities conflict.
Process owner
Can decide how the sales, service or relationship process should actually work.
Data owner
Owns data meaning, cleansing decisions and validation of what is migrated.
Key users
Participate in validation, testing and adoption, and represent how the work is really done.
Technical and integration owners
Provide the knowledge and decisions required for connected systems.
Change owner
Ensures the new CRM process becomes the real process rather than extra administration.
Decision availability
Questions that affect design and scope need timely answers to keep the plan honest.
Customer data
The migration question is what the future process needs, not how to copy everything.
Full historical copying is rarely as valuable as it feels during planning, and it is often the most expensive part of a CRM programme.
Likely first-release data
Depending on scope, this is usually what the new process needs on day one.
- Accounts
- Contacts
- Open leads
- Open opportunities
- Active cases
- Ownership
- Relevant relationship and reference data
- Consent data where applicable
Potentially useful
Valuable where there is a clear reason the future process needs it.
- Selected recent activities and history
- Agreed relationship history
- Relevant closed information where justified
Requires deeper qualification
Often expensive, and rarely as useful in practice as it feels during planning.
- Complete historical migration
- Large email and activity history
- Duplicate-heavy datasets
- Poor-quality legacy CRM data
- Multiple source systems
- Unclear customer or master data ownership
InteliSense provides the migration structure, mapping, tooling and execution. The customer owns the business meaning, the cleansing and duplicate decisions, the validation, the interpretation of consent and compliance obligations, and the final sign-off. We are not your legal advisers on privacy or consent.
Delivery disciplines
Validation, security and adoption decide whether CRM lands.
Show users the process before assumptions become configuration.
- Lead to opportunity, and opportunity progression
- Account management and case creation
- Case resolution, escalation and customer communication
- CRM and ERP handoff, reporting and security
- Show users the process before assumptions become configuration, using representative customer data where appropriate
CRM only creates value when people trust it enough to use it.
What we prove in a CRM walkthrough
Every view should make a decision easier.
A walkthrough is built around your process rather than a generic feature demo, so what you see is the work your teams actually do.
Customer context
Give teams the context they need before the next interaction, in one place.
Opportunity and pipeline
Show what is active, what has changed and what needs to happen next.
Case and service queue
Make it obvious what is waiting, who owns it and what is at risk of being missed.
Automation
Show where predictable coordination no longer depends on somebody remembering.
CRM and ERP handoff
Show where the engagement process hands over to the transactional one.
Reporting
Turn pipeline, service and activity into questions leadership can answer quickly.
What happens after go-live
CRM should become better as the organisation learns from using it.
Go-live is where adoption starts. What follows is a value relationship rather than an implementation transaction, and none of it is a commitment the customer has to make in advance.
Operate
Run the customer process reliably in the platform.
Support
Resolve issues and keep the environment healthy.
Adopt
Make the platform the place the work actually happens.
Optimise
Improve process, data quality and user experience.
Automate
Remove repetitive coordination from daily work.
Insight
Give leadership visibility of movement and risk.
Expand
Extend to more teams, processes or capability where value is proven.
Where later value usually comes from
- Adoption
- Data quality
- Process improvement
- Automation
- Reporting
- Integrations
- Customer Insights
- Customer service
- Field Service
- Power Platform
- AI
- Additional teams
- Additional processes
Evidence
General customer evidence, and what it does and does not prove.
These videos are customers describing what it is like to work with InteliSense on Microsoft Dynamics 365. None of them is presented as CRM-specific, RAPID 10, Sales or Customer Service proof, and none should be read as evidence of a particular CRM outcome.
Customer voice
What customers say about working with us.
Customer voices
InteliSense customers
Hear our customers talk about InteliSense
Organisations we have worked with
These organisations have worked with InteliSense across a range of Microsoft engagements. Their presence here is not a claim about CRM scope, capability or delivery timescale.
How we work
CRM works better when the process is clear before the fields are configured.
Business process first
Start with what the team needs to achieve.
Focus the first problem
Do not implement every CRM capability at once.
Data discipline
Make ownership and quality part of the solution.
Connect CRM and ERP
Design the handoff between engagement and transaction.
Validate early
Use real scenarios with real users.
Adoption by design
Build the process people are expected to use.
Automate with purpose
Remove repetitive coordination.
Improve after go-live
Continue refining from evidence.
Common questions
Questions leaders ask about CRM.
What should CRM solve first?
Start with the customer process that needs to work better.
If sales, service, case management or customer information is becoming harder to coordinate, we can help determine what Dynamics 365 should solve first and which delivery route makes sense.