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 Indirect Access Cost Benchmarks

Real SAP indirect access cost benchmarks from enterprise contracts. Understand document-based pricing, settlement ranges, and how to negotiate.

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.

ERP and core business systems. SAP Indirect Access Cost 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

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

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

Key points

Critical benchmark finding: The average SAP indirect access settlement in our dataset is $4.2M. Organizations that identified and remediated their indirect access exposure before SAP's audit program found them paid an average of $890K for proper licensing, a $3.3M difference in outcomes.
This interpretation led to multi-million dollar audit findings against major corporations including Diageo (£54.5M settlement), AB InBev, and others.
In virtually every scenario, digital access (document-based) pricing is 60 to 70% cheaper than named user licensing for indirect access scenarios.
Yet 41% of SAP customers in our benchmark dataset had not converted their indirect access exposure to digital access licensing meaning they were either unprotected from an audit or paying inflated named-user rates.
The spread between P25 and P75 negotiated rates is striking, organizations at the 75th percentile (best negotiators) pay 25 to 33% less per document than those at the 25th percentile.
The ratio between SAP's initial audit demand and the median settlement outcome is consistently around 60%, meaning SAP typically opens negotiations at roughly 1.6× what they expect to receive.
Organizations with external benchmark data and experienced SAP licensing counsel settled at 35 to 40% of the initial demand on average.
Benchmark median cost for enterprise RPA deployments on SAP: $340K to $890K annually under digital access licensing.
Organizations that negotiated "bot-friendly" SAP contracts, defining RPA actions as equivalent to a single digital user rather than generating per-document fees, achieved costs 62% lower than this median.
An organization processing 50,000 orders per month creates 600,000 annual order documents, at even a negotiated rate of $4.20 per 1,000 documents, this equals $2,520/month or $30,240/year for sales orders alone.

Understanding SAP Indirect Access: The Licensing Mechanics

SAP indirect access occurs when a user accesses SAP data or functionality through a non-SAP interface, a custom-built portal, a Salesforce integration, an RPA bot, a custom mobile app, or a third-party middleware system. Historically, SAP claimed that such access required named user licenses equivalent to a direct user of the SAP system. This interpretation led to multi-million dollar audit findings against major corporations including Diageo (£54.5M settlement), AB InBev, and others.

In 2018, SAP introduced "digital access licensing", a document-based model that charges per SAP document created, rather than per named user. This was framed as a simpler, more predictable alternative. In practice, both licensing models coexist in SAP contracts today, and the choice between them has enormous cost implications.

Named User vs. Document-Based Digital Access: Cost Comparison

Access Scenario	Named User Model Cost	Digital Access (Document) Cost	Benchmark Outcome
E-commerce portal (10K orders/month)	$1.2M to $3.8M/year	$180K to $420K/year	Digital 68% cheaper
Salesforce CRM integration	$640K to $1.9M/year	$90K to $280K/year	Digital 71% cheaper
RPA bots (50 attended + unattended)	$280K to $920K/year	$45K to $180K/year	Digital 64% cheaper
Supplier portal (200 suppliers)	$380K to $1.1M/year	$60K to $190K/year	Digital 67% cheaper
Custom mobile app (field workforce)	$420K to $1.4M/year	$110K to $340K/year	Digital 66% cheaper

In virtually every scenario, digital access (document-based) pricing is 60 to 70% cheaper than named user licensing for indirect access scenarios. Yet 41% of SAP customers in our benchmark dataset had not converted their indirect access exposure to digital access licensing meaning they were either unprotected from an audit or paying inflated named-user rates.

$4.2M

Avg. settlement (audited firms)

$890K

Avg. cost (proactive licensing)

41%

SAP customers with unresolved exposure

68%

Cheaper: digital vs. named user model

SAP Digital Access Benchmark Pricing

SAP's digital access document prices are nominally published but subject to significant negotiation. List prices for the five core document types are:

Document Type	SAP List Price / 1,000 docs	Benchmark Negotiated (P25)	Benchmark Negotiated (P75)	Max Discount Achieved
Sales Order	$8.00	$5.60	$4.20	58%
Delivery	$5.00	$3.50	$2.60	55%
Goods Receipt	$5.00	$3.40	$2.50	54%
Supplier Invoice	$7.00	$4.90	$3.60	52%
Journal Entry	$4.00	$2.90	$2.10	51%

The spread between P25 and P75 negotiated rates is striking, organizations at the 75th percentile (best negotiators) pay 25 to 33% less per document than those at the 25th percentile. This variation is almost entirely explained by three factors: (1) whether the customer had benchmark data on peer pricing, (2) the size of the digital access deal relative to the overall SAP relationship, and (3) whether the negotiation occurred during a renewal (high leverage) versus a standalone audit settlement (low leverage).

SAP Indirect Access Audit Settlement Benchmarks

When SAP identifies unlicensed indirect access during an audit, the settlement negotiation is one of the most consequential financial discussions an IT team will have. Our benchmark dataset covers SAP indirect access audit settlements.

Settlement Range by Organization Revenue

Organization Revenue	SAP Initial Demand	Median Settlement	Best Outcome (P75)	Duration
$500M to $2B	$1.8M to $6.2M	$1.1M	$640K	4 to 8 months
$2B to $5B	$4.2M to $14M	$2.8M	$1.6M	6 to 12 months
$5B to $15B	$9.8M to $38M	$6.4M	$3.8M	8 to 18 months
$15B+	$22M to $140M+	$18M	$9.2M	12 to 24 months

The ratio between SAP's initial audit demand and the median settlement outcome is consistently around 60%, meaning SAP typically opens negotiations at roughly 1.6× what they expect to receive. Organizations with external benchmark data and experienced SAP licensing counsel settled at 35 to 40% of the initial demand on average.

Key Settlement Levers (Benchmark-Validated)

Our analysis of 89 audit settlements identifies five negotiating points that most reliably reduce SAP indirect access settlement costs:

Document volume caps: Rather than paying per document retroactively, negotiate a fixed annual document cap with a settlement true-up. Best-in-class organizations converted retroactive exposure to forward-looking digital access caps at 40 to 55% of the initial audit demand.
RISE with SAP migration credit: Organizations willing to commit to RISE with SAP (the cloud ERP subscription) during settlement negotiations received average credit of 28 to 34% against their settlement amount. This is a significant lever, but only worthwhile if the RISE migration is already under consideration.
Exclusion of internal integration scenarios: SAP's audit methodology often incorrectly includes SAP-to-SAP integrations (e.g., SAP BW accessing SAP ECC) as "indirect access." Benchmark data shows 23% of initial audit demands included such scenarios incorrectly, and their removal reduced the final settlement by 18% on average.
Named user conversion credit: Organizations that could demonstrate existing named-user licenses covering at least some indirect users received partial credit against the digital access settlement. Average credit: 14 to 22% of settlement amount.
Timing and payment structure: Spreading settlement payments over 24 to 36 months rather than paying upfront was achieved by 67% of settled cases. In high-interest-rate environments, this represents meaningful NPV savings.

SAP Indirect Access by Scenario: Cost Benchmarks

RPA and Automation Tools

Robotic Process Automation (RPA) is the fastest-growing indirect access cost trigger. As organizations deploy UiPath, Automation Anywhere, Blue Prism, and similar tools to automate SAP transactions, each bot action potentially creates a document requiring digital access licensing. Benchmark median cost for enterprise RPA deployments on SAP: $340K to $890K annually under digital access licensing. Organizations that negotiated "bot-friendly" SAP contracts, defining RPA actions as equivalent to a single digital user rather than generating per-document fees, achieved costs 62% lower than this median.

E-Commerce Platforms

B2B and B2C e-commerce integrations with SAP are the highest-volume indirect access scenarios. An organization processing 50,000 orders per month creates 600,000 annual order documents, at even a negotiated rate of $4.20 per 1,000 documents, this equals $2,520/month or $30,240/year for sales orders alone. When combined with deliveries, goods receipts, and invoices, the total digital access cost for a mid-size e-commerce operation benchmarks at $180K to $420K annually.

CRM Integration (Salesforce and Dynamics 365)

Salesforce-to-SAP and Dynamics 365-to-SAP integrations are present in 78% of the SAP customers in our benchmark database. When Salesforce creates SAP sales orders, the resulting documents require digital access licensing. Best-practice organizations have negotiated "API connector" agreements with SAP that provide a fixed annual fee for CRM-generated documents rather than per-document metering. Fixed annual connector fees benchmark at $90K to $280K vs. variable per-document costs of $180K to $640K for comparable transaction volumes.

Start Free Trial

Access the Full SAP Indirect Access Benchmark Dataset

Our free trial includes 1 benchmark report. Run an SAP digital access benchmark against 300+ comparable organizations and identify where your licensing exposure lies.

Proactive Digital Access Licensing: Cost vs. Audit Risk

The strategic question for most SAP customers is whether to proactively license indirect access or wait for SAP to raise it. Our benchmark analysis provides a clear answer:

Proactive licensing cost benchmark: $890K average (median). Reactive audit settlement cost benchmark: $4.2M average (median). The cost of proactive licensing is 79% lower than the cost of an audit settlement, and proactive licensing eliminates 12 to 24 months of audit process risk, management distraction, and potential litigation exposure.

The optimal time to address SAP indirect access is during an EA renewal or RISE with SAP commercial discussion, when the organization has maximum leverage. Outside of a renewal, the second-best time is during a proactive "right-to-use" assessment before SAP's audit team identifies the issue, typically triggered by SAP's LAM (License Audit Management) process, which has become significantly more aggressive since 2023.

Benchmark: Organizations That Got It Right

Our top-quartile outcomes share three common characteristics:

Pre-negotiation landscape review: They mapped all third-party systems touching SAP before engaging SAP in licensing discussions, allowing them to control the scope narrative.
External benchmark data: They entered negotiations with verified peer pricing data, preventing SAP from anchoring on inflated list rates.
Renewal timing: They addressed indirect access during an EA or RISE renewal, converting it from a liability into a structured digital access entitlement at favorable rates.