The Microsoft Copilot for Sales and Copilot for Service overlays carry their own per-user seat price, their own qualifying-base requirement and a Dynamics 365 attach option. The Admodum read on the overlay construct, the breakeven adoption and the renewal-time disposition.
Copilot for Sales is a role-based add-on for sellers; Copilot for Service is the equivalent for customer-service agents. Each is positioned as a productivity layer over the seller's or agent's day, integrating with the CRM or service surface and with the M365 surface (Outlook, Teams, Word, Excel) the user already runs.
Each overlay bundles M365 Copilot. Where M365 Copilot has list price thirty US dollars per user per month, Copilot for Sales and Copilot for Service sit at roughly fifty per month each (so the overlay above M365 Copilot is roughly twenty dollars). At enterprise discount the absolute prices fall but the relative ratio holds.
The wider Copilot economics context sits at Copilot seat economics; the wider M365 plan-tier context sits at Microsoft 365 plans; the wider editorial sits in the Microsoft pillar.
The qualifying base for Copilot for Sales and Copilot for Service is Microsoft 365 E3 or E5 (or Business Standard / Premium on the smaller-deployment SKUs). Without the qualifying M365 plan, the Sales or Service overlay cannot be assigned. The qualifying-base requirement applies at the user level: each assigned user must hold the qualifying M365 plan, not a tenant-wide entitlement.
The buyer-side discipline is to map the qualifying base: every seller assigned Copilot for Sales must hold E3 / E5; the seller population that sits on F-series or Business Basic cannot be assigned the overlay. The qualifying-base test is a frequent surprise during the SAM engagement (see SAM audit anatomy).
The wider seat-assignment hygiene sits at seat-assignment hygiene; the per-user per-device construct sits at per-user versus per-device; the wider frontline-plan context sits at M365 frontline plans.
Copilot for Sales integrates natively with Dynamics 365 Sales (Microsoft's own CRM) and with Salesforce (the third-party CRM). The native integration covers opportunity records, account records, contact records, activity records and the email-to-CRM data flow. Copilot for Service integrates natively with Dynamics 365 Customer Service and with ServiceNow and Salesforce Service Cloud (the third-party service-management surfaces).
For a buyer running Salesforce as the CRM and Dynamics 365 nowhere, the Copilot for Sales overlay still delivers value (Outlook integration, Teams integration, account summarisation against the Salesforce data); for a buyer running Dynamics 365 Sales, the overlay is the natural extension and the data plane is tighter.
For a buyer already running Dynamics 365 Sales Enterprise or Dynamics 365 Customer Service Enterprise, the Copilot for Sales or Copilot for Service overlay is the natural attach (see Dynamics 365 base-and-attach). The overlay sits at a roughly thirty-percent uplift on the Dynamics 365 base-plus-attach economic and triggers the workload-by-workload adoption read.
The buyer-side discipline at attach is to read the overlay as a Dynamics 365 expansion, not as a separate Copilot decision. The Dynamics 365 user is already paying ninety-five (Sales Enterprise) or ninety-five (Customer Service Enterprise) per month for the base; the Copilot overlay sits on top.
The wider Dynamics 365 user-licensing context sits at Dynamics 365 base-and-attach; the team-member subset sits at Dynamics 365 team member; the wider account-team conversation sits at the Microsoft account team.
The renewal-time disposition runs against the workload exercise rate. The workload signals on Copilot for Sales: opportunity records updated by the assistant per user per week, customer summaries generated per opportunity, CRM data synthesised in Outlook draft replies, account-related email triage. The workload signals on Copilot for Service: ticket summaries generated, knowledge-article citations, agent response drafts accepted, average handle time reduction.
The breakeven adoption per user runs against the per-user labour cost: at a fully-loaded seller cost of one hundred thousand US dollars per year, the seventy-two-dollar-per-month overlay (above the M365 Copilot base) pays back at roughly fifteen minutes of seller time per week saved. The renewal-time decision then reads against the population that exceeds that threshold.
The wider Copilot adoption reading sits at Copilot pilot methodology; the wider Copilot economics read sits at Copilot seat economics; the broader account-team and fiscal-year context sits at the Microsoft fiscal year.
At renewal the buyer holds six artefacts on the Copilot for Sales and Service estate: the qualifying-base map (seller and agent populations with E3 / E5 entitlement, the qualifying-base gap if any), the per-user workload exercise rate (the trailing-twelve-month signal), the CRM-integration audit (which surfaces are connected, which records flow, which Outlook and Teams workflows trigger), the breakeven-adoption read (the per-user labour cost and the time-saving threshold), the right-tiering decision (the populations to retain, the populations to step down to standalone M365 Copilot or to remove) and the renewal-quantum forecast.
The wider engagement sits at the Microsoft practice; the aggregated reading list sits at the Microsoft knowledge hub; the engagement-models read sits at Fixed Fee, Contingency and Annual Retainer; renewal moments route to the Renewal Programme; engagement opens at contact.
The adoption reading that drives the renewal-time disposition.
A senior Admodum Microsoft advisor will read your qualifying-base map, the workload-exercise rate and the CRM integration audit against the breakeven-adoption framework on a private call. Renewal moments route to the Renewal Programme.