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.

Benchmark analysis

Reserved Instance vs On-Demand

Reserved Instance vs On-Demand cloud pricing benchmarks for AWS, Azure, and GCP. Real discount ranges by commitment term, coverage rates, and the.

Where this sits in a co-sell pursuit

Benchmark analysis sets the price expectation the customer brings into the room. Co-sell works the other side of the same table, so read this for the objection you will meet, not the discount you will offer.

AWS
On AWS the same money shows up as EDP or PPA position. The pursuit is shared through ACE in Partner Central, and Marketplace private offers are the procurement route that lets committed spend absorb the deal.
AWS co-sell AWS ACE
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
Google Cloud
Google Cloud carries the commitment as committed-use discounts and a negotiated spend agreement. Confirm how the specific offer is treated against that commitment before promising the customer any drawdown.
Google Cloud co-sell Google Cloud Partner Advantage

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
AWS EDP.: An AWS committed-spend agreement. Marketplace procurement is how a third-party purchase lands against it instead of against a new budget line. AWS Marketplace procurement
Committed use.: Google Cloud commitment mechanics. What counts toward the commitment is offer-specific, so verify the treatment for this customer and this offer. Committed use discounts

Qualify the pursuit jointly Walk the decision tree Build the seller-ready brief

Key points

The price gap between on-demand and reserved rates is the largest, most defensible discount available in cloud, and yet the median enterprise captures only 55-65% of the potential savings.
Based on analysis of enterprise cloud contracts: the average enterprise with $10M annual compute spend leaves $1.8-2.4M on the table annually through suboptimal RI/Savings Plan coverage.
For enterprises with Windows Server workloads and Software Assurance, Azure Reserved Instances with Hybrid Benefit can deliver 65-75% discounts versus on-demand, outpacing equivalent AWS discounts for the same workload type.
Note: GCP's Sustained Use Discounts (SUDs) provide automatic discounts even without any commitment, up to 30% for instances running 100% of a month.
The CUD discount stacks on top of SUD: a 3-year CUD provides 46-57% off on-demand, but the on-demand rate it's discounted against is already lower than AWS's equivalent due to SUD.
The implication: bridging from median (60%) to top-quartile (85%) coverage on a $10M compute bill saves approximately $2.2M annually.
This calculation assumes a blended RI discount of 40% (conservative) and applies the incremental savings from the additional 25% of compute moved from on-demand to reserved pricing.
Scenario: Company with $15M annual AWS compute spend.
The solution: commit at 80-85% of current steady-state, not 100%.
Benchmark: enterprises using automated RI recommendation tools achieve 8-12% higher coverage rates than those managing reservations manually, per our data.

The Most Consistent Savings Opportunity in Cloud

If there is a single cloud optimization action that produces the most predictable, highest-ROI result for enterprise organizations, it is increasing Reserved Instance (RI) and Savings Plan coverage of steady-state compute workloads. The price gap between on-demand and reserved rates is the largest, most defensible discount available in cloud, and yet the median enterprise captures only 55-65% of the potential savings.

This article is part of our Cloud Pricing Benchmarks: AWS vs Azure vs GCP Complete Guide. Here we focus on the RI vs on-demand price gap across all three major cloud providers, what the discounts actually look like, how coverage rates vary by enterprise maturity, and how to bridge the gap between where most organizations are and where the top quartile operates.

Based on analysis of enterprise cloud contracts: the average enterprise with $10M annual compute spend leaves $1.8-2.4M on the table annually through suboptimal RI/Savings Plan coverage. The full savings potential is there every single year, it simply requires systematic commitment management to capture it.

AWS: Reserved Instances and Savings Plans

AWS offers two main commitment mechanisms that deliver discounts versus on-demand: Reserved Instances and Savings Plans. Understanding both is essential for maximizing coverage.

AWS Reserved Instance Discount Benchmarks

RI Type	Term	Payment	Discount vs On-Demand	Best For
Standard RI	1 year	No Upfront	30 to 40%	Predictable compute, flexibility needed
Standard RI	1 year	All Upfront	38 to 45%	Cash available, cost certainty needed
Standard RI	3 year	No Upfront	45 to 55%	Stable architecture, 3+ year horizon
Standard RI	3 year	All Upfront	55 to 65%	Maximum savings, highest confidence workloads
Convertible RI	1 year	No Upfront	20 to 30%	Workloads that may change instance family
Convertible RI	3 year	No Upfront	35 to 45%	Long commitment with flexibility to convert

AWS Savings Plans: More Flexible, Similar Discounts

AWS Savings Plans were introduced as a more flexible alternative to Reserved Instances. They deliver comparable discounts but can apply to any EC2 instance type across regions (Compute Savings Plans) or within a specific instance family and region (EC2 Instance Savings Plans).

Savings Plan Type	Term	Discount Range	Coverage
Compute Savings Plan	1 year	20 to 37%	Any EC2, Fargate, Lambda
Compute Savings Plan	3 year	33 to 54%	Any EC2, Fargate, Lambda
EC2 Instance Savings Plan	1 year	30 to 45%	Specific instance family, any size in region
EC2 Instance Savings Plan	3 year	50 to 66%	Specific instance family, any size in region

"For most enterprises, AWS Savings Plans have replaced Reserved Instances as the preferred commitment mechanism. The flexibility to apply savings across any instance size in a family eliminates the primary operational complexity of RIs, resizing and modernizing instances, without sacrificing meaningful discount depth."

Azure: Reserved VM Instances and Azure Savings Plan

Azure mirrors AWS's two-track approach with Azure Reserved VM Instances (fixed to instance series) and Azure Savings Plan for Compute (flexible across instance types). Azure also benefits from Azure Hybrid Benefit layering on top of RI discounts for Windows Server workloads.

Azure Reserved Instance Discount Benchmarks

Reservation Type	Term	Discount vs On-Demand (Linux)	With Hybrid Benefit (Windows)
Azure Reserved VM Instance	1 year	35 to 45%	55 to 65%
Azure Reserved VM Instance	3 year	50 to 60%	65 to 75%
Azure Savings Plan for Compute	1 year	20 to 35%	40 to 55%
Azure Savings Plan for Compute	3 year	35 to 50%	55 to 68%

The Azure Hybrid Benefit effect is substantial. For enterprises with Windows Server workloads and Software Assurance, Azure Reserved Instances with Hybrid Benefit can deliver 65-75% discounts versus on-demand, outpacing equivalent AWS discounts for the same workload type. This is the primary reason Azure often wins on economics for Microsoft-ecosystem enterprises.

Benchmark Your RI Coverage

We analyze your cloud compute spend and identify your RI/Savings Plan coverage gaps, quantifying the annual cost of under-reserving.

GCP: Committed Use Discounts vs On-Demand

GCP's commitment mechanism (Committed Use Discounts) works differently from AWS and Azure in an important way: CUDs commit to resource amounts (vCPU/memory) rather than to specific instance types. This provides more flexibility post-commitment but requires resource-level forecasting.

GCP Commitment Type	Term	Discount vs On-Demand	Flexibility
Resource CUD (Compute)	1 year	28 to 35%	Any N1/N2 machine type in region
Resource CUD (Compute)	3 year	46 to 57%	Any N1/N2 machine type in region
Spend CUD (Cloud SQL)	1 year	20%	Any Cloud SQL in region
Spend CUD (Cloud Run)	1 year	17%	Cloud Run minutes in region
Sustained Use Discount (automatic)	No commitment	Up to 30% on 100%-running instances	Automatic, no commitment required

Note: GCP's Sustained Use Discounts (SUDs) provide automatic discounts even without any commitment, up to 30% for instances running 100% of a month. This means GCP's effective baseline rate for always-on workloads is already discounted relative to AWS's on-demand pricing before any CUDs are applied. The CUD discount stacks on top of SUD: a 3-year CUD provides 46-57% off on-demand, but the on-demand rate it's discounted against is already lower than AWS's equivalent due to SUD.

Enterprise RI Coverage Benchmarks: Where Organizations Stand

Knowing the discounts available is only part of the picture. The other critical variable is coverage rate, what percentage of eligible compute spend is actually covered by reservations or commitment programs.

Enterprise Maturity Level	AWS RI/SP Coverage	Azure Reservation Coverage	GCP CUD Coverage
Unoptimized (bottom quartile)	25 to 45%	20 to 40%	20 to 40%
Median enterprise	55 to 65%	50 to 62%	50 to 62%
Top quartile	80 to 90%	78 to 88%	75 to 87%
Best-in-class	88 to 95%	85 to 93%	82 to 90%

The implication: bridging from median (60%) to top-quartile (85%) coverage on a $10M compute bill saves approximately $2.2M annually. This calculation assumes a blended RI discount of 40% (conservative) and applies the incremental savings from the additional 25% of compute moved from on-demand to reserved pricing.

The True Cost of Under-Reserving: A Worked Example

To make this concrete, let's model the cost of under-reserving for a representative enterprise.

Scenario: Company with $15M annual AWS compute spend

Current RI/Savings Plan coverage: 58% of compute
On-demand portion: 42% × $15M = $6.3M at full on-demand rates
Steady-state workloads within that on-demand portion (reservable): ~70% of $6.3M = $4.41M
Available discount if reserved (1-year Compute SP): 35% average
Annual savings opportunity: $4.41M × 35% = $1.54M/year

That $1.54M is available every year. It doesn't require contract negotiation with AWS. It doesn't require a new vendor. It requires purchasing Savings Plans for workloads that are already running, already predictable, already steady-state.

Why don't organizations capture it? Our interviews with FinOps teams identify three recurring obstacles:

Perceived risk of over-commitment. Teams are concerned about committing to capacity that might not be needed. The solution: commit at 80-85% of current steady-state, not 100%. This leaves buffer for reduction.
Lack of visibility into steady-state vs variable workloads. Without proper tagging and cost allocation, it's difficult to know which workloads are truly steady-state. Investment in cloud cost management tooling solves this.
Organizational disconnect between FinOps and engineering. Engineers provision on-demand; FinOps doesn't have authority to purchase commitments. This governance gap costs millions annually.

RI and Savings Plan Strategy: Best Practices

Start With Savings Plans, Not Reserved Instances

For AWS, start new reservation programs with Compute Savings Plans rather than Standard Reserved Instances. Compute SPs cover all EC2 instance types and sizes in any region, eliminating the risk of stranded RIs when workloads resize or migrate. The discount is slightly lower than Standard RIs for identical commitments, but the operational simplicity justifies it for most enterprises.

Tier Your Commitment Strategy by Confidence Level

Not all workloads have equal predictability. A tiered approach:

Tier 1, Highest confidence (3-year commitments): Core infrastructure that will exist for 3+ years: production databases, authentication services, core application servers. Target 3-year All Upfront RI or 3-year Savings Plans.
Tier 2, High confidence (1-year commitments): Application workloads that have been stable for 12+ months. Target 1-year No Upfront RI or 1-year Savings Plans.
Tier 3, Variable (Spot + On-Demand): Batch processing, variable traffic workloads, development environments. Use Spot for interruption-tolerant workloads, on-demand for everything else.

Automate RI Management

Manual RI/Savings Plan management at enterprise scale is not sustainable. Tools like AWS Cost Explorer, Azure Advisor, and GCP Cost Intelligence generate automated recommendations for RI purchases. Third-party tools (Spot.io, Apptio, CloudHealth) provide portfolio-level optimization across all three clouds simultaneously.

Benchmark: enterprises using automated RI recommendation tools achieve 8-12% higher coverage rates than those managing reservations manually, per our data. The investment in tooling pays back within 1-2 months.

Conclusion: The Reservation Action Plan

Reserved Instance and Savings Plan optimization is the foundational layer of cloud cost management. No other single action produces more predictable, more sustained savings. Your action plan:

Audit current coverage rates. Pull RI/SP coverage for AWS compute, Azure reservation coverage, and GCP CUD coverage. Compare to the benchmarks above.
Identify the coverage gap value. Calculate the on-demand spend that could be reserved, multiply by the applicable discount rate, and quantify the annual savings opportunity.
Segment workloads by commitment confidence. Identify Tier 1 (3-year), Tier 2 (1-year), and Tier 3 (spot/on-demand) workloads.
Purchase Savings Plans for immediate coverage expansion. AWS Compute Savings Plans are the fastest path to coverage improvement with lowest operational risk.
Set a coverage target. 85% of eligible compute covered by reservations is achievable for most enterprises within 90 days. Make it a team objective with clear ownership.

The companies that consistently optimize cloud costs don't have better tools or better vendors. They have better discipline about reserving what they know will run, and they validate that discipline against benchmark data to know when they're falling short. Start benchmarking your coverage today.

Table of Contents

The Most Consistent Savings Opportunity
AWS: RIs and Savings Plans
Azure: Reserved Instances
GCP: CUDs vs On-Demand
Coverage Rate Benchmarks
Cost of Under-Reserving
Strategy Best Practices
Action Plan

RI Coverage Benchmark

We analyze your cloud bills to show exactly where your RI/Savings Plan coverage falls short, and what it costs annually.

Cloud Pricing Index 2026

Full benchmark data on reserved pricing, coverage rates, and commitment optimization strategies.

Download Free

Frequently Asked Questions

What is the discount for a 1-year Reserved Instance on AWS?

AWS 1-year Standard Reserved Instances (No Upfront) typically provide 30-40% discount versus on-demand for general-purpose instances. 3-year No Upfront provides 45-55% discount. All Upfront for a 3-year term delivers 55-65% discount. Exact discounts vary by instance family, region, and operating system. Convertible RIs offer 5-10% less discount but allow converting to different instance families.

How does AWS Savings Plans compare to Reserved Instances?

AWS Savings Plans offer similar discounts (up to 66% off on-demand) but with significantly more flexibility. Compute Savings Plans apply to any EC2 instance type and size across regions, eliminating the risk of stranded RIs when workloads resize or migrate. For most enterprises, Savings Plans are now the preferred commitment mechanism over traditional Reserved Instances.

What is the optimal RI/Savings Plan coverage rate for an enterprise?

Top-quartile enterprises achieve 80-90% RI/Savings Plan coverage of eligible compute spend. The median enterprise sits at 55-65%. The gap between 65% and 85% coverage on a $10M annual compute spend represents approximately $2.2M in missed savings annually. Target 85% coverage as a sustainable benchmark, leaving 15% for genuinely variable workloads and operational buffer.