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

SAP S/4HANA Discount Negotiation: Tactics That Work

How to negotiate a SAP S/4HANA discount in 2026. Real discount ranges, levers, timing, 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.

Data and analytics. SAP S/4HANA 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

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

Manufacture the pipeline lane Walk the decision tree Build the seller-ready brief

Key points

Real enterprises negotiate 25 to 45% off list on new deals and 15 to 25% off at renewal.
Forcing SAP to decompose the RISE quote into line items almost always reveals 8 to 15% of "hidden" discount capacity that was never on the opening table.
SAP's fiscal year ends December 31, and Q4 represents roughly 40% of annual software bookings.
The account executive can approve discounts up to a certain threshold (often ~20%).
Bringing indirect access to the table proactively and solving it as part of a renewal or new purchase typically costs 5 to 10% of list in concession, rather than 50%+ of list in an audit settlement.
We have never seen a 40%+ discount achieved without a live competing proposal from at least Oracle or Microsoft. "Credible" means: a signed NDA with the competitor, a scoped statement of work, a named executive sponsor at the competitor, and an implementation partner lined up.
You'll typically find hyperscaler infrastructure marked up 35 to 60% over raw cloud spend, that alone is 4 to 7% of the total RISE envelope.
Standard SAP cloud contracts include a 3 to 5% annual price uplift after year one.
Over a 5-year RISE term at 4% CAGR, that's roughly 22% compound uplift on year-one pricing.
Demand a flat per-user price for the full contract term, or at minimum a 2% hard cap tied to CPI. This single clause is often worth more economically than a 5% upfront discount, and SAP can grant it without deal-desk escalation if you push at the AE level.

Why SAP S/4HANA Discounts Are Larger Than They Admit

SAP account executives will tell you "our discounts are governed by volume matrices" and "we can't go below our floor." Both statements are technically true, and almost entirely irrelevant to the deal you're actually doing. SAP's public floor is a reference point used to make every concession feel like a gift. The real pricing envelope is much wider, for five structural reasons.

First, SAP is in the middle of a multi-year forced migration from SAP ECC to S/4HANA. Mainstream maintenance for the ECC platform ends in 2027, with extended support stretching into 2030 at a steep premium. That migration deadline is an existential revenue event for SAP: every ECC customer that doesn't convert to S/4HANA is a customer that churns. Internally, SAP sales teams are measured on S/4HANA conversion rates, not just quota. Customers who credibly signal they may evaluate Oracle Fusion or Microsoft Dynamics instead of converting are worth far more in margin concession than a net-new deal.

Second, RISE with SAP and GROW with SAP bundles compound discount opportunity. Each bundle includes license, maintenance, cloud infrastructure, integration services, and premium support. When SAP quotes a single RISE price, they are obscuring how much margin is stacked in each layer, infrastructure margin is lower (SAP passes through hyperscaler cost plus a markup), services margin is high, and support margin is very high. Forcing SAP to decompose the RISE quote into line items almost always reveals 8 to 15% of "hidden" discount capacity that was never on the opening table.

Third, quota pressure is real and cyclical. SAP's fiscal year ends December 31, and Q4 represents roughly 40% of annual software bookings. Regional teams run out of pipeline in November and start cannibalizing Q1 deals to hit year-end targets. If you can credibly offer a Q4 close with a signed PO, discounts shift materially in your favor. The same effect, smaller, but measurable, shows up at the end of Q2 (half-year).

Fourth, SAP's internal deal-desk escalation path has defined discount tiers. The account executive can approve discounts up to a certain threshold (often ~20%). Above that, a regional VP approves. Above that, global deal desk. Each step up unlocks material additional discount authority, but only if the AE is pushed hard enough to escalate. Most buyers never force that escalation, which is why they settle at the AE's authority ceiling.

Fifth, SAP's indirect-access and "digital documents" exposure gives them asymmetric liability they'd rather resolve in a broader commercial settlement. If you have any systems reading SAP data (BI tools, data lakes, custom apps, RPA bots), SAP legally could audit you for indirect access charges. They usually won't, unless negotiations go badly. Bringing indirect access to the table proactively and solving it as part of a renewal or new purchase typically costs 5 to 10% of list in concession, rather than 50%+ of list in an audit settlement.

The Discount Levers That Actually Work With SAP

These are the seven negotiation levers that have consistently produced material concessions in our benchmarked SAP deals. Use them together; individually, they're easy for SAP to shrug off.

01, Run a credible Oracle Fusion or Microsoft Dynamics RFP

Competitive pressure is the single largest discount driver in SAP deals. We have never seen a 40%+ discount achieved without a live competing proposal from at least Oracle or Microsoft. "Credible" means: a signed NDA with the competitor, a scoped statement of work, a named executive sponsor at the competitor, and an implementation partner lined up. If all you have is a PowerPoint comparison chart, SAP knows. Run the RFP 9 to 12 months before your target close. Share redacted scoring with SAP's AE, enough to signal the competitor is real, not so much that you reveal your preference.

02, Decompose RISE into line items

Insist SAP break out the RISE quote into: S/4HANA license subscription, SAP Enterprise Support, SAP Business Technology Platform entitlement, hyperscaler infrastructure (AWS/Azure/GCP pass-through), managed services, and premium engagement. Then benchmark each line. You'll typically find hyperscaler infrastructure marked up 35 to 60% over raw cloud spend, that alone is 4 to 7% of the total RISE envelope. Demand a separate rate card you can reconcile quarterly.

03, Lock full-term pricing and kill the escalator

Standard SAP cloud contracts include a 3 to 5% annual price uplift after year one. Over a 5-year RISE term at 4% CAGR, that's roughly 22% compound uplift on year-one pricing. Demand a flat per-user price for the full contract term, or at minimum a 2% hard cap tied to CPI. This single clause is often worth more economically than a 5% upfront discount, and SAP can grant it without deal-desk escalation if you push at the AE level.

04, Negotiate a declining "true-up" instead of an immediate one

Classic SAP contracts require immediate true-up (at list price) the moment you exceed licensed user counts. Replace that with a trailing annual true-up, a ±10% seat variance band, and pre-agreed discount rates for additional seats (matching or beating your initial deal discount). Extra credit: negotiate a "true-down" right at renewal, the ability to drop seats if consumption falls, without penalty.

05, Resolve indirect access proactively and cap future exposure

List every system (BI tool, data lake, custom application, partner portal, RPA bot) that reads or writes SAP data. Get SAP to sign off on which are "licensed" and which are "exempt." Add a contractual clause that future indirect access liability for new systems is capped at a pre-agreed fee, typically 8 to 12% of core license, not the 30 to 50% SAP tries to extract in audit. This alone has saved our clients $500K to $8M in post-signature audit settlements.

06, Bundle, or explicitly unbundle SAP Ariba, SuccessFactors, and Analytics Cloud

SAP's other clouds (Ariba for procurement, SuccessFactors for HR, Analytics Cloud for BI, Signavio for process mining, LeanIX for EA) are all quota-bearing for the same account team. If you're buying more than one, demand they be priced as a portfolio, not as separate line items. If you're not buying multiple, aggressively refuse "preview bundles" that silently add seats and trigger an expensive full-price purchase at renewal.

07, Negotiate payment terms alongside price

Annual-in-advance is SAP's default. Quarterly-in-arrears saves a growing enterprise meaningful cash; monthly-in-arrears is almost unachievable but worth asking. Also negotiate: a milestone-based implementation payment schedule (not 100% upfront), a hypercare holdback (10% of services fees released 90 days after go-live), and a maintenance billing deferral until production cutover. These don't reduce headline price but materially improve project economics.

Typical Discount Ranges: What Comparable Companies Actually Achieve

These ranges come from SAP S/4HANA contracts benchmarked by our team in 2024 to 2026, segmented by deal size and competitive dynamic. Treat them as realistic targets, not guarantees. "Achievable with leverage" assumes a live competitor, Q4 timing, and a decomposed commercial model.

Deal Size (ACV)	Typical Discount	Achievable With Leverage	Notes
Under $500K	10 to 18%	20 to 28%	Deal-desk attention is minimal; AE authority caps most deals in the 15% range.
$500K to $1M	15 to 25%	28 to 38%	Regional VP escalation unlocks materially better pricing with Q4 pressure.
$1M to $5M	22 to 35%	35 to 48%	Sweet spot, global deal desk engages, Oracle/MSFT RFP delivers real leverage.
$5M to $10M	28 to 40%	42 to 52%	Executive sponsorship at SAP side increases negotiation depth.
$10M+ ACV	35 to 45%	48 to 60%	Strategic deal tier; custom terms, co-marketing concessions, reference value in play.

A common blind spot: procurement teams benchmark headline discount percentage but ignore the contract structure. A 38% discount with a 5% annual escalator, no true-up flexibility, and full indirect-access exposure is worse than a 30% discount with flat pricing, a 10% seat band, and written indirect-access exemptions. The economic difference over 5 years frequently exceeds 12% of total contract value.

Timing Your SAP Negotiation for Maximum Leverage

SAP runs on a strict fiscal calendar: Q1 = Jan to Mar, Q2 = Apr to Jun, Q3 = Jul to Sep, Q4 = Oct to Dec. Each quarter has its own pressure profile, but the two meaningful windows are Q4 (especially the last three weeks of December) and Q2 close (end of June).

The Q4 Window (October to December)

This is where roughly 40% of SAP's annual software bookings get signed. Deal desk turnaround times shrink from 10 business days to 2. Regional VPs are actively hunting pipeline. Discount authority is effectively at its maximum for the year. The catch: everyone knows this, and SAP tries to push marginal deals into Q4 with aggressive commitments. Don't let the close date become more important than the contract terms, agree to a Q4 close only if SAP agrees to your structural asks (flat pricing, true-up flexibility, indirect access resolution).

The Q2 Close Window (Second Half of June)

SAP's half-year close carries meaningful quota pressure, less dramatic than Q4, but often the best timing if you can't realistically close in Q4. Discount capacity is 70 to 80% of what you'd get at year-end. Useful when your internal buying process can't withstand a Q4 negotiation push, or when you want to avoid being one of 200 simultaneous deals SAP is scrambling to close.

The Worst Times

January, April, and July, the first month of each quarter, are the worst. AEs are resetting their pipeline. Deal desk is processing Q4's backlog. Concessions that would fly in December get declined in January. If you have a choice, never close an SAP deal in January.

Renewal Timing

Start renewal prep 12 months before contract expiration. Run competitive discovery 9 months out. Issue a formal RFP 6 months out. Receive SAP's opening renewal proposal 4 to 5 months out. Negotiate 2 to 4 months out. Sign 60 days before expiration, never on the expiration date itself, which eliminates your walk-away option. If SAP knows you're past your notice window for termination, they have no reason to move.

What to Do When SAP Says No

SAP account executives are trained to exhaust buyer leverage with a sequence of soft nos: "that's outside my authority," "the floor is the floor," "I'll have to ask, but it's unlikely." Here's how to push past each one.

"That's outside my authority." Translation: the AE can't personally approve it. That's fine, ask them to escalate. Every SAP deal desk has a documented approval matrix. If your ask is denied at one level, ask explicitly: "What level of approval would this require, and what's the pathway?" Force the escalation on paper.

"We've never done that." Usually false. Ask for precedent, you're not looking for another customer's contract, just confirmation the clause has been used. If SAP refuses to confirm precedent, counter with: "Then let's make this the first. I'm willing to be a reference account if we reach agreement."

"The price is the price." The price is never the price at SAP. Push back with specific benchmarks: "Our benchmark data shows enterprises of our size and deal shape achieve 32% off list on S/4HANA in Q4 with competitive alternatives. Your 18% offer is off-market. Help me understand the gap." Specificity forces SAP to counter with data, not posturing.

"That will put us under the deal desk floor." The deal desk floor exists to be escalated past when strategic deals require it. Your response: "I understand. Please submit the escalation. I'm available to join a call with your deal desk leadership to walk through the business case." AEs almost never want a customer on a deal desk call, that alone usually produces movement.

"We need the deal signed by Friday." You need to meet your business need. Their artificial deadlines are their problem. If SAP imposes an unreasonable deadline, confirm it in writing ("I understand you need signature by Friday to recognize this in Q4") and then miss it deliberately if the terms aren't right. A deal missed in Q4 becomes a bigger deal in Q1, for them, not for you.

Get a 48-hour SAP benchmark

We compare your SAP proposal line-by-line against benchmarked S/4HANA contracts. Discount gap, escalator exposure, indirect-access risk, quantified.

Contract Language That Protects You at Renewal

The discount you sign today evaporates at renewal if the contract doesn't include structural protections. These are the clauses every SAP S/4HANA contract should contain, written to your language, not SAP's template.

Price Protection Clause

Per-user pricing flat for the full initial term. At first renewal, increases capped at lower of CPI or 2% annually, measured against the most recent full-year US-CPI-U figure. Applies to license, subscription, maintenance, and support lines, not carved out to "infrastructure" or "managed services" to dodge the cap.

Seat Flexibility Band

Right to deploy ±10% of licensed seat count without mid-term true-up. True-up calculations performed annually, not on demand. Any excess seats priced at the effective per-seat rate of the initial deal, not list price.

Indirect Access Exemption and Cap

Written list of exempt integrations (BI tools, data lakes, specific custom apps). For future integrations, SAP's incremental indirect access fee is capped at a pre-agreed percentage of core license (target: 8 to 12%). Carve-out for read-only access in all cases.

Termination for Convenience

Right to terminate with 180 days' notice after the initial term, without penalty. Pro-rata refund of any prepaid fees. Assistance with data export at a pre-agreed rate (not "hourly consulting"). This is your leverage at every future renewal, without it, you're captive.

Audit Protection

SAP audit rights limited to once per 24 months. 60 days' advance notice required. Audit conducted remotely where possible. Disputes resolved via mutual tool selection, not SAP-mandated tools. Any claimed shortfalls capped at a defined amount, not unbounded.

Benchmarking Rights

Right to benchmark your deal at renewal against comparable SAP customers (via third parties like ISVCOSELL). If pricing is more than 10% above comparable benchmarks, SAP agrees to good-faith renegotiation. Not enforceable in litigation, but creates strong moral authority at renewal.

Assignment Rights

Free right to assign the contract in case of M&A, divestiture, or internal reorganization, without SAP's consent required. SAP's default contract requires written consent, which they use to extract additional fees during corporate events.