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

SAP BTP Pricing Benchmarks

SAP Business Technology Platform (BTP) pricing benchmarks, credit cost per unit, service consumption rates, CPEA model data, and negotiation tactics.

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.

AI and ML. SAP BTP is the least anchored line in most estates: newest contracts, shortest terms, weakest switching costs. That makes it the easiest spend to redirect into cloud-native services, which is why it opens pursuits that an ERP conversation cannot.

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
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

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

Key points

The effective per-credit price in a RISE bundle is typically 15 to 25% higher than what organizations can achieve by negotiating BTP credits separately under a standalone CPEA agreement.
"We thought our RISE bundle included enough BTP. In year two, we hit 140% of our allocation and SAP invoiced the overages at $0.38 per credit, nearly 3x what we'd have paid if we'd negotiated a standalone CPEA alongside our RISE deal.
1. Multi-year commitment: Committing to 3+ years on CPEA achieves 8 to 15% better per-credit pricing than annual renewal.
SAP heavily rewards long-term predictability in BTP deals. 2. Volume step-up commitments: Agreeing to a defined annual credit increase (e.g., 20% year-over-year) in exchange for better pricing on the initial year.
Benchmark data shows 10 to 20% effective savings through this mechanism for organizations with excess hyperscaler commitments. 4. Bundling with RISE: If negotiating RISE, explicitly address BTP credit allocation and per-credit rate as a distinct line in the RISE negotiation.

What Is SAP BTP and Why Does Pricing Matter?

SAP Business Technology Platform (BTP) is SAP's cloud platform-as-a-service offering, the integration, extension, and data layer that underlies RISE with SAP, connects SAP and non-SAP systems, and enables custom development on SAP's cloud infrastructure. BTP is increasingly mandatory for organizations running RISE or S/4HANA Cloud, because it provides the services that make S/4HANA extensible without modifying core code.

For the full SAP pricing picture, see the SAP Pricing Benchmarks overview.

BTP pricing has become a significant budget concern in 2025 to 2026 for two reasons. First, RISE contracts include a baseline BTP credit allocation that many organizations discovered was insufficient for their actual usage, generating expensive overages. Second, BTP's service catalog has expanded significantly, and pricing complexity has grown in proportion, making it difficult for buyers to forecast consumption accurately.

BTP Pricing Models: CPEA, Subscription, and Pay-As-You-Go

SAP BTP can be purchased under three commercial models, each with different economics:

Model	How It Works	Best For	Price Premium vs. Best Rate
CPEA (Cloud Platform Enterprise Agreement)	Annual credit pool, consumed across all BTP services, flexible allocation	Enterprise, predictable but flexible usage	Baseline
Subscription	Fixed quantity of specific service capacity per year	Well-defined, stable workloads	+10 to 25% vs. CPEA equivalent
Pay-As-You-Go	Consumption-based, no commitment, invoiced monthly	Development, testing, unpredictable workloads	+40 to 80% vs. CPEA equivalent
RISE Bundled	Fixed credit allocation included in RISE contract	Organizations on RISE, baseline only	Overages at +35 to 60% premium

Benchmark Your BTP Spend

Find out if your BTP credit pricing and allocation is at market rate, and how to negotiate a better position before your next renewal.

BTP Credit Pricing Benchmarks 2026

BTP credits are the currency of the CPEA model, the unit through which different BTP services are consumed. Services consume credits at different rates (a low-consumption service might use 0.01 credits per API call; a high-compute service might use 10 credits per hour).

The price per credit at purchase determines the effective cost of every BTP service. Organizations that negotiate better credit pricing achieve savings on everything they run on BTP, the leverage compounds across the entire service portfolio.

Annual Credit Commitment	SAP List Price / Credit	Median Negotiated	Top-Quartile (Best Deals)	Discount Range
Under 25,000 credits	$0.32 to $0.42	$0.26 to $0.35	$0.22 to $0.28	12 to 22%
25,000 to 100,000 credits	$0.26 to $0.34	$0.20 to $0.27	$0.16 to $0.22	18 to 28%
100,000 to 500,000 credits	$0.20 to $0.28	$0.15 to $0.21	$0.12 to $0.17	22 to 36%
500,000 to 2M credits	$0.16 to $0.22	$0.11 to $0.16	$0.08 to $0.13	28 to 42%
Over 2M credits	$0.12 to $0.18	$0.08 to $0.12	$0.06 to $0.09	32 to 50%

RISE Bundled BTP vs. Standalone CPEA

RISE with SAP includes a BTP credit allocation as part of the bundle. The effective per-credit price in a RISE bundle is typically 15 to 25% higher than what organizations can achieve by negotiating BTP credits separately under a standalone CPEA agreement. This is because SAP bundles BTP at a premium within RISE, the allocation looks "free" but its economic value is embedded in the RISE total cost at above-market rates.

"We thought our RISE bundle included enough BTP. In year two, we hit 140% of our allocation and SAP invoiced the overages at $0.38 per credit, nearly 3x what we'd have paid if we'd negotiated a standalone CPEA alongside our RISE deal. The benchmark data would have told us to address this before signing."

BTP Service Consumption Rate Benchmarks

Understanding credit consumption rates per BTP service is essential for forecasting total BTP cost. The following consumption benchmarks reflect typical enterprise usage patterns:

BTP Service	Credit Consumption Unit	Typical Consumption	Annual Cost (At $0.18/credit)
Integration Suite	Per message / per GB data	10M to 100M msgs/year	$18K to $180K
SAP Build (Low-Code)	Per app user / per month	500 to 5,000 users/month	$25K to $250K
Data Intelligence / Datasphere	Per capacity unit / hour	Variable by workload	$40K to $400K+
HANA Cloud	Per compute/storage block	Variable by instance size	$50K to $600K+
API Management	Per API call (millions)	50M to 500M calls/year	$10K to $100K
SAP AI Core	Per compute hour / per inference	Rapidly growing workloads	$20K to $200K+
Business Rules / Workflow	Per execution	1M to 50M executions/year	$5K to $50K

Model Your BTP Credit Consumption

Before committing to a credit allocation, model your actual consumption against benchmark usage data. Avoid the overage trap, or the over-purchase trap.

Request BTP Modeling

The BTP Overage Trap

The single most common source of BTP budget overruns is overage charges. When organizations exceed their contracted credit allocation, SAP charges overages at rates significantly above the contracted per-credit price. Benchmark data on overage premiums:

RISE bundled BTP overages: 35 to 65% premium over the effective bundle rate
CPEA overage charges: 25 to 45% premium over the contracted credit rate
Pay-As-You-Go consumption above baseline estimates: list rates, no discount

Organizations that hit overages in year 2 or 3 of a RISE contract, when BTP usage has ramped up but the credit allocation hasn't, face both the immediate overage cost and a mid-term negotiation with SAP to increase their credit allocation, typically at less favorable pricing than they'd have gotten upfront.

Avoiding the Overage Trap: Negotiation Provisions

The provisions that prevent overage cost escalation, negotiable in approximately half of enterprise BTP deals:

Credit carryover: Unused credits roll forward to the next contract year. Achievable in ~50% of enterprise negotiations. Critical for organizations in ramp-up years.
Overage rate cap: Negotiating that any overages are charged at the contracted per-credit rate (not at a premium). Achievable in ~35% of negotiations, typically with a volume trigger.
Annual credit flexibility: The ability to adjust (flex up or down) the annual credit commitment within defined bands without penalty. Achievable in ~40% of multi-year CPEA deals.
Credit reallocation rights: Moving credits from one BTP service type to another within the overall pool. Standard in CPEA; not always available in subscription models.

BTP Negotiation Strategy

BTP is best negotiated as part of a broader SAP commercial conversation, RISE, ECC renewal, or a major new license purchase, rather than in isolation. As a standalone negotiation, BTP carries less leverage because the organizational commitment to SAP is already assumed.

Key BTP Negotiation Levers

The most effective levers in BTP-specific commercial negotiations:

Multi-year commitment: Committing to 3+ years on CPEA achieves 8 to 15% better per-credit pricing than annual renewal. SAP heavily rewards long-term predictability in BTP deals.
Volume step-up commitments: Agreeing to a defined annual credit increase (e.g., 20% year-over-year) in exchange for better pricing on the initial year. Works when usage genuinely will increase.
Hyperscaler marketplace routing: Organizations with AWS or Azure marketplace credits (through EDP/MACC programs) can route BTP purchases through SAP's marketplace presence, allowing BTP spend to count toward hyperscaler commitments. Benchmark data shows 10 to 20% effective savings through this mechanism for organizations with excess hyperscaler commitments.
Bundling with RISE: If negotiating RISE, explicitly address BTP credit allocation and per-credit rate as a distinct line in the RISE negotiation. Organizations that leave BTP implicit in RISE typically receive insufficient credit allocations at premium bundle rates.

BTP Pricing Red Flags, Signs You're Overpaying

RISE contract BTP allocation is less than 80% of your projected Year 2 consumption
No credit carryover provisions in your CPEA or RISE contract
Overage rate in your contract exceeds 20% premium over contracted credit rate
BTP was not explicitly negotiated as a separate line item in your RISE deal
HANA Cloud or Integration Suite not separately benchmarked before contract
No annual credit flex rights in a 3+ year CPEA deal

BTP AI Services: The Emerging Cost Driver

SAP's AI capabilities, SAP Joule (generative AI), SAP AI Core, and AI Foundation services, are all delivered through BTP and consumed from the BTP credit pool. In 2026, AI service consumption is the fastest-growing source of BTP credit spend in organizations actively using SAP AI.

Benchmark data on SAP AI service credit consumption is still maturing, many organizations are in early adoption phases. Key observations from our database:

Organizations running SAP Joule for conversational AI in S/4HANA are consuming 15 to 40% more BTP credits than projected in their original budgets
SAP AI Core compute costs for custom model training can exceed Integration Suite and HANA Cloud combined for data-intensive use cases
Organizations that negotiate "AI services included at contracted credit rate" in their 2026 RISE or CPEA renewals avoid premium AI add-on pricing that SAP will likely introduce as AI becomes standard

SAP Pricing Benchmark Series Overview: SAP Pricing Benchmarks (Pillar) SAP RISE Pricing Benchmarks SAP S/4HANA Migration Cost Benchmarks SAP Indirect Access Pricing Benchmarks SAP Maintenance Pricing: Benchmark vs Market SAP BTP Pricing Benchmarks (This Article)