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

Dynamics 365 F&O Discount Negotiation: Tactics That Work

How to negotiate Microsoft Dynamics 365 F&O discounts in 2026. Real discount ranges, EA levers, Azure bundling, 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.

ERP and core business systems. Dynamics 365 F&O anchors migration pursuits. The licence line will never be partner revenue, but the infrastructure, integration, and data layer underneath it is exactly the consumption case a cloud seller wants attached to the account.

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 enterprises land 20 to 40% off Dynamics 365 Finance & Operations list on new deals and 10 to 22% at renewal.
Microsoft account executives will tell you Dynamics 365 pricing is "list-price-driven" and that their published tier structure (Base $210/user/month, Attach $30) is the pricing.
Microsoft is gaining share, from under 3% of the enterprise ERP market in 2018 to 7 to 9% in 2026, but it's still behind.
Each $1M of MACC commitment typically unlocks 3 to 5 additional points of discount on Dynamics.
Every $1M of MACC commitment typically unlocks 3 to 5 points of Dynamics discount.
Negotiate the MACC rate card separately from the Dynamics deal; target 20 to 35% off Azure list rates for the committed capacity.
This is often worth more economically than a 5% headline discount improvement and is routinely granted without deal-desk escalation if pushed at the AE level.
Demand: true-up at the current effective discount, not list; annual settlement with a 90-day grace window for new hires; no immediate true-up events for seat additions under 5% of base.
Discount capacity roughly 75 to 85% of June close.
At first renewal, increases capped at lower of CPI or 3% per year.

Why Dynamics 365 F&O Discounts Are Larger Than They Admit

Microsoft account executives will tell you Dynamics 365 pricing is "list-price-driven" and that their published tier structure (Base $210/user/month, Attach $30) is the pricing. That's technically accurate for a SKU-by-SKU retail purchase and almost entirely irrelevant to any real enterprise contract. Five structural dynamics make real Dynamics 365 discounts much larger than the reps lead with.

First, Dynamics 365 F&O is a late entrant in the ERP market against SAP and Oracle. Microsoft is gaining share, from under 3% of the enterprise ERP market in 2018 to 7 to 9% in 2026, but it's still behind. Every F&O deal Microsoft wins against SAP or Oracle is disproportionately valuable as a market-share datapoint. Competitive pressure on F&O deals therefore produces more concession depth than on commoditized Microsoft products like Office or Azure. Bring a live SAP or Oracle RFP to an F&O negotiation and you change the deal's strategic priority inside Microsoft.

Second, the Enterprise Agreement (EA) is Microsoft's most powerful commercial instrument, and its biggest pricing flex mechanism. Dynamics 365 licenses can be rolled into a broader EA that includes Microsoft 365 (E3/E5), Azure, Power Platform, and Dynamics. Inside the EA, Microsoft can grant discount depth that would be unavailable on a standalone Dynamics purchase. Conversely, Microsoft's EA renewal teams routinely try to move Dynamics out of the EA at renewal to capture per-SKU pricing, a trap buyers should defend against aggressively.

Third, Azure consumption commitment is a lever. D365 F&O runs on Azure, and Microsoft will trade Dynamics discount depth for higher Azure MACC (Microsoft Azure Consumption Commitment). Each $1M of MACC commitment typically unlocks 3 to 5 additional points of discount on Dynamics. If you're growing Azure anyway, the commitment is effectively free leverage. If you're not, forcing Azure commitment for Dynamics discount is a wash, avoid it.

Fourth, Microsoft's fiscal year ends June 30. Q4 (April to June) and particularly the final two weeks of June carry significant quota pressure. Compared to SAP and Oracle, Microsoft's quota structure is more distributed (partner-led channel, direct sales, account-assigned reps) which flattens Q4 spikes slightly, but end-of-fiscal-year discount windows are real and material.

Fifth, Microsoft's channel partner ecosystem creates pricing arbitrage. Dynamics 365 can be purchased direct, through Cloud Solution Providers (CSPs), through Licensing Solution Providers (LSPs), or through implementation partners like Avanade, KPMG, and Sikich. Each channel has different margin structures and different discount flexibility. Running a partner bid process, asking 2 to 3 partners to quote on an identical licensing scope, typically unlocks 5 to 12 points of discount that Microsoft's direct sales team wouldn't grant.

The Discount Levers That Actually Work With Microsoft

These seven levers produce material concessions in Dynamics 365 F&O deals. Use them together, individually, most of them get dismissed.

01, Run a credible SAP or Oracle Fusion RFP

Competitive pressure remains the single largest discount driver. F&O is Microsoft's ERP horse in the market-share race; losing a high-visibility deal to SAP or Oracle carries strategic weight inside Microsoft, not just quota weight. Run the RFP 9 to 12 months before your target close. Share redacted scoring with the Microsoft account team, enough to make the competitor real, not so much that you reveal your preference.

02, Bundle Dynamics into your EA, not alongside it

Microsoft's EA team has broader discount authority than the Dynamics team has on standalone deals. Rolling Dynamics 365 F&O licenses into your EA, typically at the next EA true-up or renewal, unlocks additional discount depth and co-term alignment. Conversely, avoid "Dynamics Price List" standalone purchases outside the EA; discount depth there is materially lower. If your EA renewal is 18 months away, time your Dynamics deal to coincide with it.

03, Use Azure MACC as a commercial lever

Every $1M of MACC commitment typically unlocks 3 to 5 points of Dynamics discount. If you have Azure growth planned, turn it into Dynamics discount. Don't invent Azure commitment you don't need, the consumption still has to be useful. Negotiate the MACC rate card separately from the Dynamics deal; target 20 to 35% off Azure list rates for the committed capacity.

04, Force unit pricing consistency across ramp

Microsoft's default contract structure uses ramp pricing: year-one per-user cost is discounted, years 2 to 5 are at a higher rate (called "protected list"). Demand a flat unit price across the initial term. This is often worth more economically than a 5% headline discount improvement and is routinely granted without deal-desk escalation if pushed at the AE level.

05, Kill the true-up at list

Microsoft's EA includes annual true-ups: new seats added during the year are priced at the original per-user rate, billed in arrears. Dynamics has a harsher variant in some contracts where true-up occurs at then-current list. Demand: true-up at the current effective discount, not list; annual settlement with a 90-day grace window for new hires; no immediate true-up events for seat additions under 5% of base.

06, Run a channel partner bid

Solicit identical-scope quotes from 2 to 3 CSPs or LSPs (Crayon, SoftwareOne, Insight, etc.). Partner margin varies and partners compete aggressively for reference accounts. The resulting bid sheet is negotiating leverage against Microsoft direct too, Microsoft will often match or beat the best partner quote to retain the direct relationship. Net effect: 5 to 12 additional points of discount.

07, Negotiate co-term alignment for M365 + Dynamics + Azure

By default, M365 E3/E5 licenses, Dynamics, and Azure MACC commitments have different term expirations. Co-terming them to a single anniversary simplifies renewal and, critically, creates a single leverage point against Microsoft rather than three fragmented renewals where Microsoft can play one product's renewal leverage against another's. Microsoft's EA team will grant co-term alignment without material fee impact if asked early.

Typical Discount Ranges: What Comparable Companies Actually Achieve

These ranges come from Dynamics 365 F&O contracts benchmarked by our team in 2024 to 2026, segmented by deal size and competitive dynamic. "Achievable with leverage" assumes an EA-integrated deal, live SAP or Oracle RFP, Microsoft Q4 timing, Azure MACC bundling, and channel partner bid pressure.

Deal Size (ACV)	Typical Discount	Achievable With Leverage	Notes
Under $500K	10 to 18%	20 to 26%	Standalone Dynamics pricing; limited EA leverage at this size.
$500K to $1M	15 to 22%	25 to 34%	EA integration and channel bid unlock meaningful additional discount.
$1M to $5M	22 to 32%	35 to 45%	Sweet spot, deal desk engages, MACC bundling effective.
$5M to $10M	28 to 38%	42 to 50%	Microsoft executive sponsorship; co-term alignment with M365 + Azure.
$10M+ ACV	32 to 42%	48 to 56%	Strategic tier; reference value, custom terms, multi-year MACC commitment.

A common Dynamics negotiation error is treating it as a standalone purchase rather than an EA-integrated commitment. Deals negotiated standalone against Microsoft's Dynamics price list routinely come in 15 to 25 points below what the same customer could achieve by repositioning the deal inside their EA. Don't let Microsoft's Dynamics sales team pull you out of EA context to maximize their own margin.

Timing Your Microsoft Negotiation for Maximum Leverage

Microsoft's fiscal calendar: Q1 = Jul to Sep, Q2 = Oct to Dec, Q3 = Jan to Mar, Q4 = Apr to Jun. The two key windows: Microsoft Q4 close (final two weeks of June) and Microsoft Q2 close (final two weeks of December). Note the overlap with calendar-year close creates additional leverage in late December.

The Q4 Window (April to June)

Microsoft's largest quarter by bookings. The final two weeks of June carry the most quota pressure of the year. Deal desk turnaround compresses from 7 business days to 2. MACC and EA teams have maximum discount authority in Q4 to accommodate strategic deals.

The Q2 Close (December)

Late December carries meaningful pressure both from Microsoft fiscal Q2 close and from buyer calendar-year budget dynamics. Discount capacity roughly 75 to 85% of June close. Useful for buyers whose internal budget cycles won't support a June close.

The Worst Times

July and August (Microsoft's Q1) are the worst. Quotas just reset. Deal desk is catching up on Q4 backlog. October is also weak, mid-quarter, no pressure. Close deals in Q4 or Q2 where possible.

EA Renewal Timing

Start EA renewal prep 18 months before expiration. Run competitive discovery and RFP 12 months out. Negotiate 4 to 6 months out. Sign 90 days before renewal date. The single most common EA renewal mistake is starting too late, Microsoft knows at 90 days you can't credibly threaten to exit, and prices accordingly.

What to Do When Microsoft Says No

Microsoft's sales motion is more consultative than SAP or Oracle's but no less tactical. Here's how to push through the standard nos.

"That's not a standard EA discount." EA discounts exist on a spectrum, not a ladder. The published "EA Level A/B/C/D" tiers are guideposts, not limits. Counter: "Our benchmark data shows enterprises of our size with comparable commitments achieve [X]% off on F&O. Help me understand the gap."

"I'd need to escalate to the EA team." Escalate. The EA team's discount authority is broader than the Dynamics team's. Forcing the handoff often produces movement.

"Dynamics pricing is set by the Dynamics BG (business group)." True, but the BG works with Microsoft's commercial operations team on strategic deals. Request: "Please route this through deal desk for strategic deal review. I'm available to support the business case."

"We can't price below MACC floor." There is no hard MACC floor below which Microsoft cannot discount, only thresholds that require escalation. If your deal size warrants, the escalation will happen.

"Your true-up will reprice at renewal." Don't accept it. Demand contractual language that mid-term seat additions are discounted at the same effective rate as the original deal, and that future seat adds carry forward into renewal pricing.

Get a 48-hour D365 benchmark

We compare your Microsoft Dynamics proposal line-by-line against benchmarked EA and standalone contracts. Discount gap, MACC efficiency, true-up exposure, quantified.

Contract Language That Protects You at Renewal

These clauses preserve your leverage at EA renewal and protect against silent price creep.

Price Protection

Unit pricing flat across the initial EA term. At first renewal, increases capped at lower of CPI or 3% per year. Applies to Dynamics, M365, and Azure MACC uniformly.

True-Up Discipline

Mid-term seat additions priced at the same effective discount as the original deal, not at list. Annual true-up settlement, not rolling. 90-day grace window for new hires. Additions under 5% of base waive the immediate true-up.

Co-Term and Ramp Protection

M365, Dynamics, and Azure co-termed to a single anniversary. Ramp pricing (if applicable) flat across the ramp period, not escalating.

Termination Rights

Right to terminate for convenience after 24 months with 180 days' notice and pro-rata refund. Free assignment for M&A and corporate events. Defined SLAs with termination for non-performance.

MACC Flexibility

Unused Azure MACC rolls over up to 12 months. Right to convert spend across Azure services without penalty. Published rate card honored for the full term.

Channel Flexibility

Right to move between CSP, LSP, and direct channels mid-term without price change. Prevents Microsoft or a partner from using channel lock-in as a renewal lever.

Benchmarking Rights

Right to benchmark your deal at renewal against comparable EA customers. If pricing exceeds comparable benchmarks by more than 10%, Microsoft agrees to good-faith renegotiation.