Dynamics 365 Sales & CRM — Complete Guide
Lead Management · Sales Pipeline · Quotes & Orders · AI Copilot · Forecasting · Scenarios · Cheat Sheet
Table of Contents
- Core Concepts — Basics
- Sales Pipeline & Opportunity Management
- Products, Quotes & Orders
- AI Features & Copilot for Sales
- Sales Accelerator & Sequences
- Forecasting & Goals
- Configuration, Security & Integration
- Scenario-Based Questions
- Cheat Sheet — Quick Reference
1. Core Concepts — Basics
What is Dynamics 365 Sales and what are its core capabilities?
Dynamics 365 Sales is a cloud-based CRM application built on Dataverse that helps sales organisations manage their entire sales process — from lead generation to deal closure.
Core capabilities:
- Lead management: capture, qualify, and convert leads into opportunities
- Opportunity management: track deals through a defined sales pipeline with stages
- Account & Contact management: 360-degree view of customers and key contacts
- Activity management: emails, calls, meetings, tasks linked to sales records
- Quote-to-Order: create quotes, orders, and invoices within the CRM
- Sales forecasting: predict revenue based on pipeline and deal probabilities
- AI & Copilot: relationship intelligence, conversation intelligence, predictive scoring
- Sales analytics: dashboards and reports on pipeline health, win rates, team performance
What are the main tables (entities) in D365 Sales?
Core Sales entity relationships:
Lead → (qualify) → Contact + Account + Opportunity
↓
Quote(s)
↓
Order(s)
↓
Invoice(s)
Key entities:
Lead → unqualified prospect. Not yet a customer in the system.
Contact → individual person. Related to Account.
Account → company/organisation. Parent of Contacts.
Opportunity → potential deal. Linked to Account + Contact.
Quote → formal price proposal. Created from Opportunity.
Order → confirmed purchase. Created from Quote.
Invoice → billing document. Created from Order.
Product → item sold. Added to Quote/Order as line items.
Price List → defines pricing for products per market/currency.
Competitor → tracks competing vendors in a deal.
Goal → revenue/activity target for a rep or team.
Territory → geographic or account-based sales assignment.
Tip: The Lead → Opportunity → Quote → Order → Invoice pipeline is the most tested D365 Sales sequence in. Know every step and what triggers each conversion.
What are the D365 Sales licensing tiers?
| Licence | Key Features |
|---|---|
| Sales Professional | Core CRM — leads, opps, accounts, contacts, activities, basic dashboards |
| Sales Enterprise | All Professional + sequences, forecasting, relationship analytics, conversation intelligence, LinkedIn integration |
| Sales Premium | All Enterprise + predictive lead/opportunity scoring, advanced AI relationship analytics |
| Microsoft Relationship Sales (MRS) | Sales Enterprise + LinkedIn Sales Navigator — combined licence |
| Copilot for Sales | AI assistant across Outlook, Teams, D365 — meeting summaries, email drafting, CRM updates |
What is the difference between a Lead and an Opportunity?
Lead: an unqualified potential prospect. Represents an expression of interest not yet evaluated. May be a real buyer or may be disqualified. Stored in a separate Lead table — NOT yet an Account/Contact in the system.
Opportunity: a qualified, viable potential deal. Has confirmed buying intent, budget, and authority. Linked to an existing Account and Contact. Has an estimated value, close date, and sales stage.
Lead qualification decision:
"Is this a real sales opportunity?"
YES → Qualify lead → system creates:
→ Contact (the person)
→ Account (the company)
→ Opportunity (the deal)
All linked and pre-populated from lead data
NO → Disqualify lead:
Status reasons: Lost / No Longer Interested / Cannot Contact
Key distinction:
Lead = potential interest, no confirmed customer record
Opportunity = confirmed prospect with Account and Contact in the system
Tip: Never create an Opportunity directly without a Lead (unless the Account already exists). Lead qualification is the data quality gate — it prevents polluting the system with unqualified prospects as Accounts.
What activities are used in D365 Sales and how are they tracked?
| Activity | Description |
|---|---|
| Sent/received emails tracked from Outlook via D365 App for Outlook | |
| Phone Call | Outbound/inbound calls logged manually or via Conversation Intelligence |
| Appointment | Meetings linked to D365 records — syncs with Outlook Calendar |
| Task | Follow-up actions assigned to reps with due dates |
| Teams call | Recorded via Conversation Intelligence |
All activities are linked to a Regarding record (Lead, Opportunity, Account, Contact) and appear in the unified timeline on that record's form.
2. Sales Pipeline & Opportunity Management
What is a Business Process Flow (BPF) for Opportunities?
A Business Process Flow is a stage-based visual guide overlaid on the Opportunity form — ensuring consistent sales methodology across all reps.
Default Opportunity Sales Process stages:
1. Qualify → confirm BANT (Budget, Authority, Need, Timeline)
Required steps: Est. Revenue, Decision Maker?, Identify Sales Team
2. Develop → understand requirements, solution mapping
Required steps: Customer Need, Proposed Solution, Identify Competitors
3. Propose → formal proposal / quote presentation
Required steps: Identify Key Stakeholders, Present Proposal
4. Close → negotiate and get final decision
Required steps: Complete Final Proposal, Confirm Decision Date, Final Proposal Sent
Custom BPF example (MEDDIC methodology):
Metrics → Economic Buyer → Decision Criteria → Decision Process → Identify Pain → Champion
BPF data stored in Dataverse:
→ Active stage, days in each stage, stage completion %
→ Reportable in Power BI for funnel/conversion analysis
Tip: BPF stage data is stored in Dataverse and fully reportable. "Days in stage" and "stage-to-stage conversion rate" are critical pipeline health metrics available only because of the BPF.
What are Opportunity Close reasons and why are they important?
Close as Won dialog:
→ Actual Revenue: confirmed deal value (may differ from estimated)
→ Actual Close Date: when deal was signed
→ Competitor: who else was considered
→ Description: close notes
Close as Lost dialog:
→ Status Reason (REQUIRED custom field — make it mandatory):
Lost to Competitor / No Budget / No Decision Made /
Product Not a Fit / Wrong Timing / Relationship Lost
→ Competitor: who won the deal
→ Description: detailed loss notes
Why loss reasons matter:
→ Win/loss by competitor: identify which competitors you lose to most → competitive battlecards
→ Win/loss by product: identify product gaps → roadmap input
→ Win/loss by rep: identify coaching needs → training
→ Win/loss by stage: identify where deals fall off → process improvement
→ Win/loss by deal size: identify sweet spot → ICP refinement
Tip: Always make loss reason a required field on the Close as Lost dialog. Without required loss reasons, reps enter generic answers and the data becomes useless for analysis.
What is the Opportunity probability and how is it used?
Opportunity Probability (0–100%) indicates the likelihood of winning the deal. In the default setup it is manually set by the rep, often tied to the sales stage:
Default probability by stage:
Qualify: 10%
Develop: 20%
Propose: 50%
Close: 75%
Won: 100%
Lost: 0%
Used in forecasting calculations:
Expected Revenue = Estimated Value × Probability
($500,000 × 75%) = $375,000 expected revenue
With Predictive Opportunity Scoring (Sales Premium):
→ AI calculates probability based on historical win patterns
→ Overrides manual probability with data-driven score
→ Factors: deal age, activity level, stakeholder engagement, competitive presence
3. Products, Quotes & Orders
What is the Product Catalog in D365 Sales?
| Component | Description |
|---|---|
| Product families | Hierarchical grouping. Shared properties inherited by child products. |
| Products | Individual items or services with default price and unit. |
| Unit groups | Units of measure (e.g., "Pieces": Each, Dozen, Pack) with conversion factors. |
| Price lists | Selling prices per market, currency, customer segment, or promotion. |
| Price list items | Link product to price list with specific price (fixed or % of list). |
| Discount lists | Volume-based or criteria-based discounts applied to quote lines. |
Example product catalog:
Product Family: Software Licences
Product: CRM Starter (annual) → $1,200/seat
Product: CRM Enterprise (annual) → $2,400/seat
Product: CRM Premium (annual) → $3,600/seat
Price Lists:
EMEA GBP List: CRM Starter £950, Enterprise £1,900
APAC USD List: CRM Starter $1,100, Enterprise $2,200
Partner List: 20% discount off standard list price
Unit Groups:
Software: Seat / 5-Pack (4.5×/seat) / 25-Pack (4×/seat)
What is the Quote lifecycle in D365 Sales?
Quote statuses:
Draft → being built. Fully editable. Not sent to customer.
Active → locked and sent to customer. Cannot be edited directly.
Won → customer accepted. Triggers Order creation.
Closed → declined or expired.
Revised → new Draft version created from an Active quote.
Lifecycle flow:
[Draft] → Add products, pricing, discounts, terms
→ [Activate] → Quote locked, PDF generated, sent to customer
→ Customer responds:
Accepted → [Won] → Create Order from Quote
Declined → [Closed]
Needs changes → [Revise] → New Draft created
Previous Active quote auto-closed
Quote line items:
→ Catalog products with quantity, unit, price, discount, tax
→ Write-in products: non-catalog items (custom services)
→ Manual price override (with approval workflow if configured)
→ Sub-totals, pre-freight total, freight, discount, tax, total amount
Warning: Once a Quote is Activated it is locked for editing. Use "Revise" to make changes — this creates a new Draft and closes the previous Active quote. Maintain revision history for audit purposes.
What are the key differences between Quote, Order, and Invoice?
| Quote | Order | Invoice | |
|---|---|---|---|
| Represents | Price proposal | Confirmed purchase | Billing document |
| Created from | Opportunity | Won Quote (or directly) | Order |
| Customer committed | No | Yes | Yes |
| Editable | Yes (Draft) / No (Active) | Yes (Active) | Limited |
| Key statuses | Draft → Active → Won/Closed | Active → Fulfilled → Cancelled | Active → Paid → Cancelled |
| Triggers | — | Fulfilment / delivery process | Payment processing |
D365 Sales vs ERP:
D365 Sales: Quote/Order/Invoice for CRM pipeline visibility
ERP (Business Central, SAP): Full financial processing
→ GL posting, inventory management, payment reconciliation
→ Integration: D365 Order → ERP Order → ERP Invoice → D365 Invoice sync
4. AI Features & Copilot for Sales
What is Copilot for Sales and what can it do?
Copilot for Sales (formerly Viva Sales) is an AI assistant working across Microsoft 365 and D365 Sales.
| Capability | Description |
|---|---|
| Email summary & response | Summarises email threads, drafts contextually relevant replies with CRM data |
| Meeting preparation brief | Before a Teams meeting: account info, open opps, recent activities, talking points |
| Meeting summary & actions | After Teams meeting: summary, action items, suggested CRM updates |
| CRM updates from Outlook/Teams | Update opp stage, close date, notes without switching to D365 |
| Opportunity summary | One-click AI summary: key details, recent activities, stakeholders, risks |
Tip: Copilot for Sales is the answer to "how do you increase CRM adoption." Reps work in Outlook and Teams — Copilot brings CRM into their daily workflow rather than requiring a context switch to D365.
What is Predictive Lead and Opportunity Scoring?
Both use ML models trained on historical D365 data to assign a score (0–100) and grade (A/B/C/D).
Predictive Lead Scoring (Sales Premium):
Analyses: firmographics, lead source, engagement signals, demographics
Score: 0-100 (A=80-100, B=60-79, C=40-59, D=0-39)
Shows: influencing factors (positive/negative)
Use: prioritise high-grade leads in the Sales Accelerator worklist
Predictive Opportunity Scoring (Sales Premium):
Analyses: deal age, activities, stakeholder engagement, competitor presence,
product mix, historical win patterns
Score: 0-100
Shows: factors driving score up or down
Use: identify at-risk opportunities, prioritise rep focus
Model training:
→ Trained on YOUR org's historical Won/Lost opportunities
→ Requires ~40+ won + 40+ lost opportunities to activate
→ Auto-refreshes weekly as new data accumulates
→ Gets more accurate over time — self-improving
Key point: The model is trained on YOUR organisation's data — not generic industry benchmarks. It improves as you close more deals. Mention this to show deep understanding.
What is Conversation Intelligence?
Conversation Intelligence analyses recorded Teams sales calls using AI to extract insights and coaching opportunities.
- Call recording and transcription: auto-records Teams calls, transcribes speech to text
- AI analysis: extracts keywords, topics, competitor mentions, action items, customer questions
- Talk-to-listen ratio: measures rep vs customer speaking time — coaching signal (ideal: rep speaks <50% of the time)
- Keyword tracking: alerts when tracked keywords mentioned (competitor names, pricing objections, "cancel")
- Call highlights: auto-marks key moments in transcript (objections, questions, competitor mentions)
- Manager coaching: review AI highlights without listening to full recordings — scale quality review
Tip: Conversation Intelligence solves the "call quality black box" problem. Managers traditionally could only review sampled calls. AI analysis makes it possible to review all calls at scale.
What is Relationship Analytics?
Relationship Analytics analyses communication between sales reps and customers to provide health scores and engagement insights.
| Feature | Description |
|---|---|
| Relationship health score | A/B/C/D grade based on interaction frequency and recency |
| Activity analytics | Email open rates, meeting frequency, response times, last contact date |
| Who knows whom | Identifies colleagues with existing relationships to customer contacts |
| Relationship risk | Flags opps/accounts where engagement has dropped — risk of going dark |
| LinkedIn integration | Shared connections, job changes, company news from Sales Navigator |
5. Sales Accelerator & Sequences
What is the Sales Accelerator?
The Sales Accelerator is a unified productivity workspace for inside sales teams — a prioritised worklist and focused working environment.
- Worklist: all records requiring action today, ordered by priority
- Up next widget: next recommended action for each record
- Inline communication: send emails, make calls directly from the worklist
- Priority scores: AI-prioritised — highest-scoring leads and opps appear first
- Skip and snooze: reps snooze records to re-appear later or skip sequence steps with a reason
Tip: Sales Accelerator removes context switching — reps work through their entire day from one focused interface without jumping between records. The answer to "how do you improve inside sales productivity."
What are Sales Sequences (Cadences)?
Sales Sequences are automated, time-based action plans assigned to Leads or Opportunities guiding reps through consistent outreach activities.
Example sequence: "New Enterprise Lead Outreach"
Day 1: Email — Send personalised intro email (AI-drafted template)
Day 2: Phone call — Follow up on email
Day 4: LinkedIn connection request
Day 7: Email — Send relevant case study
Day 10: Phone call — Discovery conversation request
Day 14: Task — Add to 90-day nurture campaign if no response
Sequence features:
→ Auto-creates activities on the record at the right time
→ Rep sees "Up Next" activity in Sales Accelerator
→ Completing activity early unlocks the next step immediately
→ If deal advances: sequence can be disconnected
→ Analytics: email open rates, response rates, meeting booking % by step
Sequence types:
→ Lead sequences: for new lead outreach
→ Opportunity sequences: for deal nurturing and follow-up
→ Account sequences: for customer success / renewal outreach
6. Forecasting & Goals
What is Sales Forecasting in D365 Sales?
Sales Forecasting predicts revenue for a period based on pipeline opportunities — rolled up through the sales hierarchy.
Forecast configuration:
→ Period: monthly / quarterly / yearly
→ Hierarchy: based on Manager field on User record
→ Forecast columns (configurable):
Quota: target assigned by manager
Committed: deals rep is highly confident of closing this period
Best Case: Committed + possible deals
Won: already closed-won in the period
Pipeline: all open deals in forecast period
Gap: Quota minus Won/Committed
Forecast categories on Opportunity (rep-managed):
Best Case → possible close this period
Committed → rep is highly confident this period
Omitted → excluded (stalled or not this period)
Won → auto-set on Close as Won
Lost → auto-set on Close as Lost
Hierarchy rollup example:
Rep A: Committed $200K | Best Case $350K
Rep B: Committed $300K | Best Case $400K
Manager: Committed $500K | Best Case $750K
Director: sees all managers rolled up
Tip: Forecast category is rep-managed and separate from probability %. A rep can have a 70% probability opportunity marked "Omitted" from forecast if the deal has stalled. This gives managers realistic pipeline visibility.
What are Goals and Goal Metrics?
Goals allow managers to define revenue targets and track progress in real time.
Goal Metric: defines WHAT is measured
→ "Revenue Won" metric: measures Opportunity Actual Revenue (Won)
→ "New Logos" metric: counts new Accounts created from Won opps
→ Rollup fields: Actual (achieved), In Progress (open pipeline)
Goal:
→ Linked to a Goal Metric
→ Assigned to: User or Team
→ Period: monthly / quarterly / fiscal year
→ Target: $500,000 revenue Q1
→ Actual: auto-calculated from Won opps in period
→ In Progress: auto-calculated from open pipeline
Goal hierarchy:
Rep goals roll up → Manager goal → Director goal → VP goal
Each manager sees their team's aggregate vs target
Example:
Rep A: Q1 target $250K → actual $180K → 72% of quota
Rep B: Q1 target $300K → actual $320K → 107% of quota
Manager: Q1 target $550K → actual $500K → 91% of quota
7. Configuration, Security & Integration
How does the D365 Sales security model work?
Key security roles:
System Administrator → full access, all configuration
System Customizer → customise without data access
Sales Manager → manage team records, reports, coaching
Salesperson → manage own records, limited team visibility
Business Unit hierarchy:
Contoso Ltd (root BU)
└── EMEA BU
├── UK BU → UK Sales Team
└── DACH BU → DACH Sales Team
Security scope per role:
Account: User scope → rep sees only accounts they own
Opportunity: BU scope → rep sees all opps in their BU
Lead: User scope → rep sees only their own leads
Field-level security:
→ Restrict Actual Revenue, Contract Terms, Discount Authority
→ Only Sales Managers and Directors see deal financials
Territory management:
→ Assign accounts to territories (geographic or industry-based)
→ Automatic assignment rules based on postal code, country, or account attributes
→ Territory membership drives which rep is auto-assigned new accounts
What are the key customisation points in D365 Sales?
| Layer | Customisation |
|---|---|
| Forms | Customise Opportunity, Lead, Quote forms — add fields, sections, subgrids |
| Views | Configure list views — My Open Opps, Team Pipeline, Stale Deals |
| Business rules | Field show/hide/set/validate (e.g., hide Competitor field unless stage = Propose) |
| Business Process Flows | Custom sales stages matching org's sales methodology |
| Plugins | C# server-side logic (e.g., auto-assign territory on Account create) |
| Power Automate | Automated actions (approval flows, notifications, ERP sync) |
| Dashboards | Custom sales dashboards for rep, manager, executive views |
What are the key D365 Sales integrations?
| Integration | Description |
|---|---|
| D365 App for Outlook | Track emails/appointments to D365 records; Copilot for Sales in Outlook |
| Microsoft Teams | D365 records in Teams; Teams calls recorded via Conversation Intelligence |
| LinkedIn Sales Navigator | Embedded in Account/Contact/Lead/Opp forms — profile, InMail, connections |
| ERP (Business Central, SAP) | Sync products, price lists, orders, invoices between D365 and ERP |
| D365 Marketing / Customer Insights | Campaign-generated leads flow to D365 Sales; attribution tracking |
| Power BI | Pipeline reports, win/loss analysis, forecast accuracy on Dataverse data |
8. Scenario-Based Questions
Scenario: Sales reps are not updating D365 — pipeline data is stale. How do you fix this?
Root cause: reps work in Outlook and Teams, not D365. Logging activity is manual and feels like admin overhead.
Solutions:
- Copilot for Sales in Outlook: email auto-capture logs activity to D365 automatically — zero manual effort. Reps see CRM context in their inbox.
- Teams integration: link Teams meetings to D365 opps. Post-meeting, Copilot generates summary and suggests CRM updates — rep approves with one click.
- Sales Accelerator: reps start their day in a prioritised worklist driven by D365 — making D365 where work happens, not a separate admin task.
- Sales Sequences: auto-create activities on records — rep's next action is always defined, reducing the "what should I do?" friction.
- Required fields: make Close Date and Forecast Category required on Opportunity. Keep required fields minimal — every unnecessary required field increases friction.
- Manager accountability: managers review pipeline in D365 weekly 1:1s. Stale records become visible and uncomfortable.
Tip: CRM adoption is both a process and technology problem. Copilot and auto-capture reduce friction. Manager behaviour drives compliance. Both are required.
Scenario: Design a D365 Sales implementation for a B2B SaaS company with field and inside sales teams.
Architecture:
- Business units: Field Sales BU (enterprise, >500 employees) and Inside Sales BU (SMB, ≤500)
- Lead routing: inbound website leads → Power Automate → auto-assign based on company size
- Sales Processes (BPF):
- Field sales: 6-stage enterprise BPF (Qualify → Discover → Technical Validation → Business Case → Negotiate → Close)
- Inside sales: 4-stage velocity BPF (Qualify → Demo → Proposal → Close)
- Products & Pricing: SaaS tiers (Starter/Growth/Enterprise), annual/monthly price lists, volume discount lists (≥50 seats: 10% off)
- Sequences: inside sales sequences for high-velocity outreach (Day 1 email → Day 2 call → Day 4 follow-up)
- AI: Predictive Lead Scoring for inside reps' worklist prioritisation. Conversation Intelligence for inside rep call coaching.
- Forecasting: quarterly forecast by team (Inside vs Field) rolled up to VP Sales. Separate quotas per team.
- Copilot for Sales: Outlook + Teams integration for both teams — email capture, meeting prep, post-meeting CRM updates.
Scenario: Configure approval workflows for discounts above 20% on quotes.
- Add "Total Discount %" calculated field to the Quote form
- Power Automate approval flow triggered on Quote status = "Pending Approval":
Condition: If Total Discount % > 50 → escalate to VP Sales + FinanceCondition:
If Total Discount % > 35 → escalate to Sales DirectorCondition:
If Total Discount % > 20 → send to Sales ManagerCondition:
If Total Discount % ≤ 20 → auto-approveOn approval:
set Quote status = "Approved", notify repOn rejection:
set status = "Draft", notify rep with manager comment - Business rule: lock discount field when Quote status = "Activated" — prevents post-approval changes
- Audit trail: approval history stored as activity records on the Quote — full visibility of approver, date, and decision
Scenario: Pipeline reviews show opportunities stalling at the Proposal stage. How do you diagnose and fix it?
Diagnose:
- Power BI: "Days in stage" report — if Proposal stage is 3x other stages, confirmed bottleneck
- Win/loss analysis: filter lost opps that stalled in Proposal. Common reasons: "Pricing" and "No budget approval"
- Conversation Intelligence: review call recordings from Proposal-stage opps — identify common unaddressed objections
- BPF compliance: check if reps are progressing to Proposal without completing Develop stage requirements (budget confirmed? decision maker identified?)
Fix:
- Make "Budget approval process identified" a required step in the Develop stage BPF
- Add Proposal stage sequence: auto-reminder every 3 days to follow up on proposal
- Knowledge base of objection handling for common pricing challenges
- Automatic alert when opportunity spends >14 days in Proposal → supervisor notification
- "Price sensitivity" field on Opportunity — flag deals where pricing is a known risk for proactive manager coaching
Scenario: How do you implement territory management for a global sales org?
Requirement: APAC, EMEA, and AMER regions. Each region has country-level territories. Accounts auto-assigned to the right rep.
- Create territory hierarchy:
Global Territory├── AMER│ ├── US-West (rep: John)│ ├── US-East (rep: Sarah)│ └── Canada (rep: Mike)├── EMEA│ ├── UK + Ireland (rep: Emma)│ └── DACH (rep: Klaus)└── APAC ├── ANZ (rep: David) └── ASEAN (rep: Priya) - Auto-assignment rules: Power Automate flow on Account Create — check
address1_country→ assign to matching territory member - Security: Salesperson role with BU scope scoped to their territory BU — only sees their territory's accounts/opps
- Reporting: pipeline and quota attainment filterable by territory in Power BI dashboard
- Territory changes: reassignment flow when territory boundaries change — bulk update Account ownership via Power Automate
9. Cheat Sheet — Quick Reference
Sales Entity Lifecycle
Lead (unqualified):
statecode: Open(0) / Qualified(1) / Disqualified(2)
Qualify → creates Contact + Account + Opportunity
Disqualify → status reasons: Lost / No Longer Interested / Cannot Contact
Opportunity:
statecode: Open(0) / Won(1) / Lost(2)
Status reasons (Open): In Progress / On Hold
Close Won → creates blank Order (rep adds products)
Close Lost → requires loss reason (make it required!)
Quote:
Status: Draft → Active → Won/Closed/Revised
Order:
Status: Active → Fulfilled → Cancelled
Invoice:
Status: Active (unpaid) → Paid → Cancelled
Forecasting Quick Reference
Forecast categories (rep-managed):
Best Case → possible close this period
Committed → highly confident this period
Omitted → excluded (stalled or out of period)
Won → auto-set on Close as Won
Lost → auto-set on Close as Lost
Forecast columns (admin-configured):
Quota | Won | Committed | Best Case | Pipeline | Gap to Quota
Expected Revenue formula:
Expected = Estimated Value × Probability %
($500K × 75%) = $375K expected
Hierarchy: Rep → Manager → Director → VP
All levels see their team's aggregate rolled up in real time
AI Features Summary
Copilot for Sales (add-on):
→ Email drafting in Outlook (CRM-contextual)
→ Meeting prep brief before Teams calls
→ Meeting summary + action items after Teams calls
→ Opportunity summary (one click)
→ CRM updates from Outlook/Teams
Predictive Lead Scoring (Sales Premium):
→ 0-100 score, A/B/C/D grade
→ Trained on org's own historical Won/Lost leads
→ Prioritises Sales Accelerator worklist
Predictive Opportunity Scoring (Sales Premium):
→ 0-100 score, A/B/C/D grade
→ Trained on org's own Won/Lost opportunities
→ Gets more accurate over time
Conversation Intelligence (Enterprise+):
→ Auto-records and transcribes Teams sales calls
→ Talk-to-listen ratio, keyword tracking
→ AI highlights (objections, questions, competitors)
→ Manager coaching at scale
Relationship Analytics (Enterprise+):
→ Relationship health score A/B/C/D
→ Engagement drop alerts
→ Who-knows-whom for warm introductions
→ LinkedIn integration (with Sales Navigator)
Key D365 Sales KPIs
Win Rate = Won Opps / Total Closed Opps × 100
Avg Deal Size = Total Won Revenue / Won Opp Count
Sales Cycle Len = Avg days from Lead qual to Close Won
Pipeline Coverage= Pipeline Value / Quota Target (ideal: 3-4×)
Quota Attainment = Actual Revenue / Quota × 100
Forecast Accuracy= Actual Revenue / Committed Forecast × 100
Lead Conversion = Qualified Leads / Total Leads × 100
Stage Conversion = Opps entering stage / Opps exiting Won
Top 10 Tips
- Lead vs Opportunity — Lead = potential interest, no customer record. Opportunity = qualified deal with Account and Contact. Qualification is the data quality gate. Never skip it.
- Loss reasons are required fields — make loss reason mandatory on Close as Lost. Optional fields are ignored by reps and make win/loss analysis meaningless.
- BPF stage data is reportable — Business Process Flow stage, days in stage, and conversion rates are stored in Dataverse and fully reportable in Power BI. This is a differentiated insight.
- Forecast category ≠ probability — forecast category is rep-managed (Committed/Best Case/Omitted) and separate from the % probability field. A 70% probability opp can be Omitted from forecast if stalled.
- Copilot for Sales = adoption accelerator — reps work in Outlook and Teams. Copilot for Sales brings CRM into their workflow. This is the answer to every "how do you improve CRM adoption" question.
- Predictive scoring uses YOUR data — models are trained on your org's historical won/lost records, not generic industry data. They improve over time. This is a key differentiator vs. rules-based scoring.
- Quote Revise, not Edit — once a Quote is Active (sent to customer), you cannot edit it. Use Revise to create a new Draft version. The Active quote is automatically closed.
- Sales Accelerator for inside sales — one focused worklist driven by sequences and AI scores. The answer to any inside sales productivity question.
- Conversation Intelligence scales quality review — managers can't listen to all calls. AI highlights, talk-to-listen ratio, and keyword alerts make it possible to coach all reps, not just sampled ones.
- Goals roll up the hierarchy — rep goals auto-roll up to manager → director → VP. This gives real-time quota attainment visibility at every level of the org without manual aggregation.
No comments:
Post a Comment