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

SaaS Pricing Models Explained: Per-Seat, Consumption, Platf…

Enterprise benchmark data on SaaS pricing models. Per-seat, consumption-based, and platform licensing compared, with negotiation implications for.

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.

Data and analytics. SaaS 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
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

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

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

Key points

Most enterprise deployments show 20 to 40% of provisioned seats with low or no utilization at any given time.
The average enterprise Snowflake deployment grows 35 to 55% annually in credit consumption; Datadog deployments grow 25 to 45% annually as monitoring coverage expands.
Our benchmark data shows the sweet spot for Snowflake commitments at 60 to 70% of projected peak consumption; for AWS at 50 to 65%; for Datadog at 70 to 80%.
This decomposition approach typically reveals 20 to 35% savings opportunities compared to organizations that accept bundled platform pricing without component-level analysis.
Commitment level determines your discount tier, committing at 60 to 70% of projected peak usage is typically optimal, providing discount access without over-committing.

Model 1: Per-Seat (Per-User) Pricing

Per-seat pricing remains the most common model in enterprise SaaS. A defined price is charged for each named user or licensed seat per year (or per month), regardless of how heavily that user utilizes the platform. Salesforce, Microsoft 365, Workday, ServiceNow (for most modules), Okta, Slack, and Zoom all use per-seat pricing as their base structure.

Why Per-Seat Pricing Persists

Per-seat pricing is predictable for both buyer and vendor. Buyers can model their annual spend based on headcount. Vendors generate reliable recurring revenue that scales linearly with user growth. The model also creates natural expansion revenue, as organizations grow, SaaS costs grow with them, without any renegotiation required on the vendor's part.

The risk for buyers is structural over-licensing. Most enterprise deployments show 20 to 40% of provisioned seats with low or no utilization at any given time. For large deals, this unused capacity represents significant waste, and a lever that informed procurement teams use in renewal negotiations.

Benchmarking Per-Seat Pricing

Per-seat pricing is the most straightforward model to benchmark because the unit of comparison is clear: price per seat per year, normalized to a comparable feature tier. The variables that drive the most significant pricing differences between comparable transactions are:

Total seat count: Volume discounts are the most impactful driver of per-seat price, the difference between a 200-seat and a 5,000-seat deal for the same product can be 40 to 60% on a per-seat basis
Contract duration: Multi-year commitments (3-year vs. 1-year) typically command 8 to 15% discounts
Edition tier: The specific feature set licensed (Enterprise vs. Unlimited, Pro vs. Enterprise) must be controlled for in any meaningful benchmark comparison
Competitive situation: Active competitive evaluations, where an alternative vendor is genuinely in play, can move achievable pricing by 10 to 20% below non-competitive transaction benchmarks

Vendor / Product	List Price/Seat/Yr	500 to 1K Seats	1K to 5K Seats	5K+ Seats
Salesforce Sales Cloud Ent.	$1,800	$1,170 to $1,350	$990 to $1,170	$720 to $990
ServiceNow ITSM Pro	$1,500	$975 to $1,200	$825 to $1,050	$600 to $825
Okta Workforce Identity	$180	$126 to $153	$108 to $135	$90 to $117
Microsoft 365 E3	$432	$346 to $389	$302 to $368	$259 to $346
Zoom Enterprise	$250	$175 to $215	$150 to $188	$113 to $163

Benchmark Your Per-Seat SaaS Contracts

Get market pricing data for Salesforce, ServiceNow, Okta, and 50+ per-seat SaaS vendors. 48-hour delivery, Confidential.

Model 2: Consumption-Based (Usage-Based) Pricing

Consumption-based pricing charges organizations for what they actually use, API calls, queries processed, data ingested, compute credits consumed, or similar usage units. Snowflake, Datadog, Twilio, AWS, Azure, and GCP all use consumption-based or hybrid consumption pricing for their core products.

The Economics of Consumption Pricing

From a buyer's perspective, consumption pricing has two faces. The value case is that organizations with variable or growing workloads pay only for what they use, there's no structural over-licensing waste. The cost risk is that consumption costs scale with usage in ways that are difficult to predict, and that vendors often negotiate commitment structures (EDPs, MACC agreements) that lock organizations into minimum spend levels that exceed actual consumption.

Our analysis of enterprise consumption pricing contracts shows that organizations consistently underestimate consumption cost growth. The average enterprise Snowflake deployment grows 35 to 55% annually in credit consumption; Datadog deployments grow 25 to 45% annually as monitoring coverage expands. These growth rates make commitment-level negotiations particularly consequential.

Benchmarking Consumption Pricing

Benchmarking consumption-based SaaS requires a different approach than per-seat pricing. The relevant benchmarks are cost-per-unit metrics: cost per Snowflake credit, cost per Datadog host per month, cost per Twilio message. These unit economics must then be calibrated to your specific usage profile, workload type, data volume, retention requirements, to produce a meaningful comparison.

The highest-value benchmarking activity for consumption vendors is commitment-level optimization. Organizations frequently commit to minimum spend levels that reflect ambitious growth projections, and then find themselves either over-committed (paying for unused capacity) or under-committed (paying list rates for consumption above the commitment tier). Our benchmark data shows the sweet spot for Snowflake commitments at 60 to 70% of projected peak consumption; for AWS at 50 to 65%; for Datadog at 70 to 80%.

"Consumption pricing gives vendors the ability to grow revenue without any renegotiation. Every additional data source added to Datadog, every new query workload on Snowflake, every outbound message via Twilio, the meter runs automatically. That's why unit-cost benchmarking at contract signing matters so much."

Vendor / Unit	List Unit Cost	Benchmark Range (Enterprise)	Typical Discount
Snowflake (credit, on-demand)	$2.00 to $4.00	$1.20 to $2.40	20 to 40%
Datadog (host/month)	$23 to $34	$14 to $23	25 to 40%
Databricks (DBU, all-purpose)	$0.15 to $0.55	$0.09 to $0.35	20 to 40%
Twilio (SMS outbound, per message)	$0.0079	$0.0045 to $0.0063	20 to 43%
Elastic Cloud (capacity unit/hr)	$0.095 to $0.175	$0.057 to $0.122	25 to 40%

Model 3: Platform Licensing

Platform licensing is a hybrid model where a base platform capacity fee is charged independently of, or in addition to, per-seat or per-user fees. ServiceNow is the archetypical example: while individual users are licensed per-seat, the Now Platform itself carries a platform capacity fee that scales with the number of active workflows, integrations, and process scope rather than with user count alone.

Other vendors that use platform components include Salesforce (Platform and Experience Cloud base licenses), SAP BTP (integration credits + API calls + application runtime), and Workday (integration platform and Extend modules charged separately from HCM seats).

Why Platform Licensing Is the Most Complex to Benchmark

Platform fees are the most difficult component to benchmark accurately for two reasons. First, the unit of measure is vendor-specific and not standardized across the market, ServiceNow's "process capacity" units are not directly comparable to Salesforce Platform licenses. Second, platform fees are frequently added to contracts mid-term as usage expands, making initial contract benchmarking only a partial picture of total cost.

Our approach to platform fee benchmarking involves decomposing the platform into its constituent services and benchmarking each component separately: integration throughput costs, workflow execution costs, API call costs, and storage costs. This decomposition approach typically reveals 20 to 35% savings opportunities compared to organizations that accept bundled platform pricing without component-level analysis.

Model-by-Model Negotiation Strategy

Negotiating Per-Seat Contracts

The primary levers in per-seat negotiation are volume, term, and competitive pressure. Volume discounts are automatic but often not maximized, vendors will offer additional volume tiers for incremental commitments. Multi-year terms (3-year vs. 1-year) provide a structured discount opportunity that most vendors will take. Competitive pressure, when backed by a credible alternative vendor in active evaluation, consistently moves per-seat pricing to the lower end of the benchmark range.

The secondary levers are frequently overlooked: utilization-based true-down rights (the ability to reduce seat count at renewal if utilization data shows consistent under-usage), seat reallocation flexibility (moving licenses between user classes without additional charge), and SKU mix optimization (right-sizing users between higher and lower edition tiers based on actual feature usage).

Negotiating Consumption Contracts

For consumption-based vendors, the critical negotiation variables are commitment level, unit pricing rate, and overage protections. Commitment level determines your discount tier, committing at 60 to 70% of projected peak usage is typically optimal, providing discount access without over-committing. Unit pricing rate negotiation should be based on per-unit benchmarks (cost per credit, cost per host) rather than total spend commitments. Overage protections, caps on the rate at which consumption above the committed level is charged, are frequently available but rarely requested proactively by buyers.

For a deeper treatment of cloud commitment optimization (which shares mechanics with SaaS consumption pricing), see our use case guide on cloud commitment optimization.

Negotiating Platform Contracts

Platform licensing negotiation requires a clear decomposition of what components are included in the platform fee and what constitutes out-of-scope consumption. Organizations that negotiate explicit platform capacity definitions, with documented inclusions and overage rates, consistently pay less over the contract term than those that accept umbrella platform license language that gives vendors discretion to determine what is "included."

Model Selection, Key Benchmarking Considerations

Per-seat pricing benchmarks against comparable deal sizes, volume tier is the most important normalization variable
Consumption pricing benchmarks at the unit-cost level, per credit, per host, per query, not at the total spend level
Platform licensing requires component-level decomposition to produce a meaningful benchmark
Hybrid models (per-seat + consumption + platform) are the most complex, and the highest value to benchmark given the multiple independent pricing components
AI add-on pricing cuts across all three model types and currently shows the widest variance between initial proposals and market benchmarks

The Rise of Hybrid Pricing Models

The real-world pricing structures of enterprise SaaS vendors are increasingly hybrid combinations of all three models. Salesforce charges per-seat for most clouds, consumption-based for Einstein AI credits and storage, and platform-based for Experience Cloud and MuleSoft integration capacity. ServiceNow charges per-seat for ITSM users, platform fees for workflow capacity, and consumption fees for IT operations analytics. SAP charges per-user for SuccessFactors and Concur, consumption-based for BTP integration credits, and platform fees for S/4HANA private cloud.

The procurement implication is that benchmarking a single component of a complex vendor relationship, the per-seat rate, for example, without understanding the full cost stack produces an incomplete picture. Our benchmark methodology for hybrid-model vendors always includes a full TCO analysis that captures all pricing components, not just the headline subscription.

The hidden costs embedded in hybrid pricing structures are analyzed in detail in our companion article on hidden costs in SaaS contracts. For a comprehensive view of what market pricing looks like across all these components, our SaaS Sprawl Cost Benchmark research paper provides the most detailed publicly available analysis of enterprise SaaS cost structures.

Choosing the Right Benchmarking Approach for Your Situation

The pricing model determines the benchmarking method. Per-seat vendors require per-unit price benchmarks normalized to deal size. Consumption vendors require unit-cost benchmarks calibrated to your usage profile. Platform vendors require component decomposition. Hybrid vendors require all three, applied to each cost component independently.

The practical implication is that comprehensive SaaS benchmarking cannot be reduced to a single data point or generic market report. It requires transaction-level data that has been calibrated to the specific characteristics of your deal, size, duration, competitive situation, and feature configuration. That calibration is what separates benchmark data that moves vendor pricing conversations from benchmark data that vendors dismiss as non-comparable.

Benchmark Your SaaS Models

Per-seat, consumption, or platform, we have transaction data for all three. 48-hour delivery.

SaaS Pricing Benchmarks Cluster