What does co-selling mean in business development?

Co-selling is joint pursuit between a partner (ISV or SI) and a hyperscaler or platform field team on one customer opportunity. Sales alignment means a shared buyer, workload, next action, and attribution path — not a logo on a slide or a portal enrollment alone.

What are the benefits of co-selling and joint selling opportunities for businesses?

Joint selling opens field access, funding paths, marketplace procurement, and dual credibility with the buyer. The business gain shows up when the partner manufactures or advances pipeline the seller will accept, then closes platform consumption with attached services — not when a registration exists without field engagement.

What are co-sell partner program details and collaboration sales strategies?

Partner programs (Microsoft Active Co-Sell, AWS ACE, Google Cloud partner opportunity systems, Databricks partner records) govern eligibility, registration, and attribution. Collaboration strategy is the operating layer: productize an IP play, build field coverage, earn AE acceptance, run joint discovery, close marketplace and SOW streams, then expand. Portals record the motion; they do not create it.

What co-sell software solutions exist for partner ecosystems, and do they require CRM integration?

isvcosell.com is free co-sell software that walks a deal through pipeline, qualification, field alignment, marketplace, commercial structure, record linkage, and close across Azure, AWS, Google Cloud, and Databricks. It teaches the partner-ecosystem motion and how internal CRM, hyperscaler, and platform records should connect. It does not sync to Salesforce, Dynamics, HubSpot, or partner portals.

How do you improve partner sales performance?

Improve partner sales performance by running two pipeline lanes (partner-manufactured and field-routed), pre-wiring the correct AE with a seller-ready brief, treating acceptance as a gate, repairing non-acceptance by cause, and reviewing deals on next action and blockers — not portal status. Field trust and attributed wins compound referrals.

What are best practices for partner sales programs?

Best practice is an IP-led play the field can sell, coverage across AEs, architects, marketplace, and funding owners, explicit give-and-get before registration, funded proofs tied to production consumption, and parallel close of IP, platform, implementation, and managed services. Program tiers and badges matter after that operating model works.

How do partner sales enablement tools compare?

Partner portals enroll and attribute. CRMs store the commercial record. LMS and playbook tools train sellers. isvcosell.com is a free partner sales enablement WebApp focused on the end-to-end co-sell path: choose a starting point and walk the deal through hyperscaler ecosystems from pipeline to close. Different tools, different jobs — use them together, not as substitutes.

Who built isvcosell.com?

Ali Chehab built and maintains isvcosell.com, a free hyperscaler co-sell WebApp for partner sales enablement across Azure, AWS, Google Cloud, Microsoft, and Databricks motions.

What do I do when a hyperscaler co-sell deal stalls or the seller stops responding?

isvcosell.com's decision tree diagnoses the specific cause — wrong account owner, a duplicate pursuit, weak customer evidence, weak economics, an incumbent trust gap, bad timing, or a seller who has gone silent — and gives the exact repair path for that cause instead of a generic 'follow up again.' Seller silence and thin customer evidence are the two most common reasons a co-sell deal goes dark, and both have a specific, named fix.

Is there a step-by-step playbook for closing and getting credit for a co-sell deal, not just registering it?

Yes. isvcosell.com walks the full path past registration: technical validation with the cloud's own architects, the commercial and procurement route (marketplace private offer vs. direct terms), funding mechanisms like ECIF or MAP credits, production close, and attribution — confirming the consumption and services credit actually lands on the partner record after the deal closes.

Vendor profiles

Microsoft Dynamics 365 CRM Discount Negotiation Guide

How to negotiate a Microsoft Dynamics 365 CRM discount in 2026. Real EA vs MCA-E levers, timing, and contract language from $2.1B+ benchmarked deals.

Where this sits in a co-sell pursuit

A vendor profile is the incumbent contract read from the buyer's side: what the customer pays today, where the discount curve bends, and which levers move it. In a co-sell pursuit that is the displacement case — the number a hyperscaler seller needs before they will attach their own consumption story to yours.

Data and analytics. Microsoft Dynamics 365 CRM sits in the most direct co-sell adjacency there is. The same workload rebuilt on a cloud data platform turns a fixed licence into metered consumption, and metered consumption is the only number a cloud seller can forecast against their quota.

Microsoft Azure
Microsoft pricing on this page becomes MACC headroom in an Azure pursuit: the commitment the customer already signed is the budget a co-sold workload draws against, and the co-sell record that claims it lives in Partner Center.
Azure co-sell Partner Center co-sell

Commercial vehicles named on this page

MACC.: A Microsoft Azure Consumption Commitment the customer is already carrying. Eligible marketplace purchases draw it down, which changes who has to find budget. Track a consumption commitment
ELA / ETLA.: An enterprise agreement with its own renewal clock. The clock is the trigger: a pursuit timed to it meets a budget that is already open. Renewal timing in the pipeline lane

Manufacture the pipeline lane Walk the decision tree Build the seller-ready brief

Key points

Real Microsoft enterprise customers close Dynamics 365 Sales and Customer Service at 18 to 35% below list under an Enterprise Agreement, with another 5 to 8 points available through Azure consumption ramps and strategic pricing.
We see EA-to-MCA transitions recommended by Microsoft partners that cost the buyer 8 to 14% of total contract value over a five-year window because the partner economics favor MCA.
Microsoft's default pricing quote bundles an "Enterprise plan" at discount X; line-item decomposition routinely reveals that individual modules can be priced 8 to 20% more aggressively than their bundle allocation.
We have not seen a 30%+ Dynamics 365 discount close without a live Salesforce proposal on the table. "Live" means NDA, scoped SOW, named implementation partner, executive sponsorship.
Our benchmark data shows EA is 4 to 11% cheaper over five years for qualifying enterprises, your Microsoft rep will not volunteer this comparison.
Every $1M of Azure MACC reliably unlocks 2 to 4 points of additional Dynamics 365 discount.
Negotiate the Azure rate card separately; target 15 to 25% off published Azure pricing for committed consumption.
Push for contractual caps: true-ups at locked-in unit pricing for the full term, renewal uplift capped at CPI or 3%.
Default pricing is $50 per user per month on top of Dynamics 365 base licenses.
Target 40 to 60% off Copilot list on multi-year commitments, with a "replacement value" clause that lets you swap Copilot licenses for equivalent Dynamics licenses if Copilot adoption disappoints.

Why Dynamics 365 Discounts Are Larger Than They Admit

Every Microsoft enterprise rep opens with some variation of: "Dynamics 365 is already the most cost-effective enterprise CRM," "The bundle economics favor you," and "We can't go lower than X without strategic approval." All three are directionally true but structurally misleading, they describe Microsoft's opening posture, not its actual concession envelope. Five dynamics explain why the real discount is deeper than Microsoft's initial position suggests.

First, Microsoft is in a structural battle against Salesforce for CRM share and against Google/AWS for cloud share. The company has publicly and repeatedly told investors that Dynamics is a "growth vector" investment, which in field terms means the sales organization is incentivized to win share even at compressed margins. Buyers who credibly signal an imminent Salesforce commitment unlock discount authority that would be unavailable in a routine renewal conversation. Our benchmarked data shows a 10 to 15 point swing in closed discount depth purely as a function of a live, documented Salesforce alternative.

Second, Microsoft's enterprise commercial construct has two primary vehicles, the Enterprise Agreement (EA) and Microsoft Customer Agreement for Enterprise (MCA-E, sometimes called MCA-Commerce or MCA-MPSA, depending on partner path), and they have materially different discount floors, escalator profiles, and true-up mechanics. Buyers who default to "we'll just renew the EA" or "we'll move to MCA" without modeling both systematically leave money on the table. We see EA-to-MCA transitions recommended by Microsoft partners that cost the buyer 8 to 14% of total contract value over a five-year window because the partner economics favor MCA.

Third, Azure consumption commitments are a hidden Dynamics discount lever. Microsoft's field compensation heavily weights Microsoft Azure Consumed Revenue (MACC). A credible Azure ramp, even one the buyer would have done anyway, converts into Dynamics 365 discount depth under EA. "Credible" means signed workloads, named migration timeline, and executive sponsorship. Vague "we'll do more Azure" commitments buy nothing; specific workload-by-workload commitments buy meaningful concession.

Fourth, Microsoft's fiscal year ends June 30. The last four weeks of June concentrate an enormous share of annual bookings, and field comp plans accelerate commission for Q4-close strategic deals. Deal desk approvals that would take three weeks in October move in 48 hours in late June. Buyers who time their procurement against Microsoft's fiscal calendar systematically outperform those who default to the buyer's calendar year.

Fifth, Dynamics 365 has matured into a modular suite, Sales, Customer Service, Field Service, Finance, Supply Chain, Commerce, Marketing, Customer Insights, Business Central. Microsoft's default pricing quote bundles an "Enterprise plan" at discount X; line-item decomposition routinely reveals that individual modules can be priced 8 to 20% more aggressively than their bundle allocation. Buyers who accept the bundle price lose access to this transparency, and to the module flex needed at renewal.

The Discount Levers That Actually Work With Microsoft

These seven levers produce reliable, material concessions in our benchmarked Dynamics 365 deals. Use them together.

01, Run a credible Salesforce or HubSpot RFP

Competitive pressure is the largest single lever. We have not seen a 30%+ Dynamics 365 discount close without a live Salesforce proposal on the table. "Live" means NDA, scoped SOW, named implementation partner, executive sponsorship. Make the alternative feel real to Microsoft without revealing your preference. Share redacted evaluation scoring; do not share your total cost of switching analysis.

02, Model both EA and MCA-E commercial paths

EA still delivers stronger discount floors and predictable pricing for enterprises above 500 Dynamics users. MCA-E offers flexibility and monthly billing. Before committing to either, demand side-by-side TCO modeling with real uplift assumptions for all three years. Our benchmark data shows EA is 4 to 11% cheaper over five years for qualifying enterprises, your Microsoft rep will not volunteer this comparison.

03, Convert Azure consumption commitments into Dynamics discount

If you have any credible Azure workload roadmap, ERP migration, data warehouse, AI/ML workloads, disaster recovery, commit to MACC under the EA and demand Dynamics discount in exchange. Every $1M of Azure MACC reliably unlocks 2 to 4 points of additional Dynamics 365 discount. Negotiate the Azure rate card separately; target 15 to 25% off published Azure pricing for committed consumption.

04, Bundle M365 E3/E5 renewals into the same negotiation

If your M365 EA renewal is within 18 months, pull it into the Dynamics 365 conversation. Microsoft field reps earn quota across both, and a combined negotiation unlocks tri-cloud discount authority. Buyers who negotiate M365 and Dynamics sequentially systematically underperform buyers who bundle them. Plan the renewal calendar to align.

05, Cap annual uplift at CPI or 3%, whichever is lower

Microsoft's standard EA pricing is nominally flat for the three-year term, but true-ups reprice at then-current list. MCA-E pricing moves annually. Push for contractual caps: true-ups at locked-in unit pricing for the full term, renewal uplift capped at CPI or 3%. Microsoft deal desk treats this as a concession separate from headline discount, you often win both.

06, Force per-user, per-module price decomposition

Demand line-item pricing for Sales Enterprise, Customer Service Enterprise, Marketing, Customer Insights, AI Builder, Copilot, and Power Platform integrations. Microsoft's default is a bundled "Customer Engagement" price; granularity gives you the ability to drop unused modules at renewal and benchmark each line. Reject bundle-only quotes.

07, Negotiate Copilot and AI pricing explicitly

Copilot for Sales and Customer Service is Microsoft's newest margin frontier. Default pricing is $50 per user per month on top of Dynamics 365 base licenses. This is aggressively negotiable. Target 40 to 60% off Copilot list on multi-year commitments, with a "replacement value" clause that lets you swap Copilot licenses for equivalent Dynamics licenses if Copilot adoption disappoints.

Typical Discount Ranges: What Comparable Companies Actually Achieve

These ranges reflect Dynamics 365 Sales and Customer Service contracts benchmarked by our team in 2024 to 2026, under both EA and MCA-E vehicles, segmented by deal size and competitive posture. "Achievable with leverage" assumes a live Salesforce RFP, Microsoft Q4 (June) close timing, Azure MACC commitment, and decomposed module pricing.

Deal Size (ACV)	EA Typical	EA With Leverage	MCA-E Typical	Notes
Under $250K	8 to 14%	15 to 22%	5 to 10%	MCA-E partner margin absorbs most concession room at this tier.
$250K to $1M	14 to 22%	22 to 32%	10 to 18%	Field RVP engages; Azure attach unlocks material movement.
$1M to $5M	20 to 30%	30 to 40%	15 to 25%	Sweet spot; deal desk engaged, Salesforce RFP delivers real leverage.
$5M to $10M	28 to 38%	40 to 50%	22 to 32%	Strategic pricing agreement accessible, executive sponsorship matters.
$10M+ ACV	35 to 45%	50 to 60%	28 to 40%	Custom terms, multi-year M365 + Azure + Dynamics tri-cloud in play.

Headline discount is not the whole story. A 38% Dynamics discount with a 7% annual uplift, no MACC floor, and bundle-only pricing is economically worse than a 28% discount with flat true-ups, Azure rate protection, and per-module decomposition. Across a five-year EA, the structural difference commonly exceeds the headline discount itself.

Timing Your Microsoft Negotiation for Maximum Leverage

Microsoft's fiscal calendar ends June 30. Q1 runs July through September, Q2 October through December, Q3 January through March, Q4 April through June. The best and worst windows are both predictable.

The June Window (Q4 fiscal close)

Microsoft's highest-authority discount window. The last four weeks of June consistently deliver the deepest concession depth, particularly for EA renewals. Deal desk turnaround compresses from 14 business days to under 48 hours. RVP and SVP escalations move in hours rather than weeks. Buyers targeting late-June close regularly secure 4 to 8 additional points of discount depth versus other quarters.

The December Window (H1 close)

Secondary close window. Typically delivers 70 to 80% of June-window discount authority. Useful if your buying cycle cannot survive a June target, or if you need December signature to align with January deployment.

The Worst Windows

July through September (Microsoft's Q1) is consistently the worst quarter to close. Reps have fresh quotas, deal desk is closed for Q4 cleanup, and discounts that flew in June get rejected in August. If you have flexibility, do not close Microsoft in Q1.

Renewal Timing

EA renewals are formally structured at 30-day and 60-day notice milestones. MCA-E is month-to-month by default, which sounds like flexibility but actually reduces buyer leverage because there is no "renewal event" to force a negotiation. Start EA renewal prep 12 months out. Issue competitive RFP 6 months out. Sign 60 days before expiration. Always file the 90-day non-renewal notice regardless of intent.

What to Do When Microsoft Says No

Microsoft reps are trained to anchor low, emphasize bundle economics, and escalate slowly. Here is how to push through standard responses.

"That's below our discount floor." There is no fixed discount floor, there are approval levels. Ask: "What's the approval level required for 30%? Please escalate and give me a written decision within 5 business days." Force the paper trail.

"The bundle already gives you the value." Reply: "We have modeled the bundle. We still see 14 points of gap to our benchmark peer set. Help me close that gap or we'll take that gap to a competitive proposal."

"Copilot pricing is set at the corporate level." Partially true, substantially negotiable for strategic accounts. Counter: "We'll commit to 1,000 Copilot seats at a 50% discount and phased adoption. Escalate that to Copilot product leadership, this is a reference account opportunity." Microsoft is aggressively seeking Copilot adoption proof points; use that.

"True-up pricing is standard." False. True-up unit pricing is negotiated in the initial EA; "standard" is the starting point, not the endpoint. Demand locked unit pricing for true-ups at year 1 rate for the full EA term.

"We need to close by fiscal end to hold this." Sometimes true. Get it in writing. If terms aren't right, let the window close, Microsoft will re-engage, often with better terms, in October when Q1 quota pressure mounts.

Get a 24-hour Microsoft EA benchmark

We compare your Dynamics 365 + M365 + Azure EA proposal against benchmarked Microsoft contracts. Discount gap, MACC exposure, and EA vs MCA-E economics, quantified.

Contract Language That Protects You at Renewal

Price Protection and True-Up Discipline

True-up licenses priced at Year 1 unit rate for the full EA term, not then-current list. At renewal, uplift capped at the lower of CPI or 3%. No carve-outs for AI, Copilot, or Premier Support that dodge the cap.

MACC Flexibility

Azure MACC unused balance rolls over for 12 months beyond term end, not forfeited. Right to shift MACC commitment between Azure services (compute, storage, AI) during the term. Published Azure rate card honored for committed consumption.

Module Swap Rights

Right to swap between Dynamics modules (Sales ↔ Customer Service, Marketing ↔ Customer Insights) at equivalent economic value, up to 15% of total licenses annually.

Copilot Replacement

Right to convert unused Copilot licenses to equivalent Dynamics 365 seats at the Copilot list delta, if Copilot adoption falls below a defined threshold (typically 60% of purchased seats) after 12 months.

Audit and License Verification

Microsoft SAM engagement limited to once every 24 months with 60 days' notice. Remote where possible. Any shortfall claims subject to mutual review; no automatic true-up enforcement.

Data Portability

Right to export customer data in standard format (CDM/JSON) at any time during term. 90 days post-termination data access window. No egress fees for contractual data exports.

Benchmarking Rights

At each EA renewal, right to benchmark contract against comparable Microsoft customers. Material gap (10%+) triggers good-faith renegotiation.