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

Confluence Atlassian Discount Negotiation 2026

How to negotiate Confluence Cloud Premium and Enterprise discounts. 2026 benchmarks, Atlassian bundling, and renewal clauses from $2.1B+ in analyzed 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.

AI and ML. Confluence Atlassian 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

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

Key points

Default Confluence renewals still carry 5 to 10% uplift on top of list-price increases that have pushed base per-user pricing materially higher over the past three years.
Buyers who understand the Atlassian strategic segment, and who bring Microsoft Loop, Notion, or Guru competitive pressure, routinely cut 25 to 35% off Enterprise list, cap uplift, and protect against mid-term list-price changes.
If you are a DC customer committing to Cloud migration, the effective 3-year cost can be 30 to 40% lower than staying on DC at renewal.
Enterprise tier is the strategic enterprise product, multiple instances, advanced security, 99.95% SLA, unlimited storage, and discounting authority on Enterprise is substantially deeper than Premium.
Strategic deal desk prices Confluence Enterprise with authority to 25 to 35% off list when competitive pressure and commitment size justify.
Stacked with competitive pressure and multi-year Together bundling, they compound into 28 to 38% off Confluence Cloud Enterprise list.
Frame the conversation around Enterprise-tier requirements, multiple instances, SAML, SCIM, data residency, Atlassian Access controls, 99.95% SLA, rather than letting the rep default to Premium.
The effective 3-year cost with migration incentives is often 30 to 40% lower than staying on DC renewal.
Atlassian's standard renewal uplift is 5 to 10% on Cloud subscription pricing.
Cap at lower of US CPI or 3%, but also insist on list-price-change protection for the committed term.

Why Confluence Discounts Are Larger Than They Admit

Atlassian's enterprise motion is asymmetric. The company prices aggressively on list and resists discounts at mid-market scale, but maintains deeper discount authority at strategic enterprise segments than reps typically signal. Five structural realities create deeper discount capacity than the initial conversation suggests.

First, Atlassian migrated from perpetual Data Center licensing to subscription Cloud pricing and the transition is incomplete. The company's primary strategic imperative is moving customers from Server (deprecated) and Data Center to Cloud, and specifically to Cloud Enterprise. Migration incentives exist that are not advertised: cloud-migration credits, extended trial windows, and Cloud Enterprise discounts that are materially deeper than baseline Cloud Premium pricing. If you are a DC customer committing to Cloud migration, the effective 3-year cost can be 30 to 40% lower than staying on DC at renewal.

Second, Confluence Cloud Enterprise pricing is structurally different from Cloud Premium. Enterprise tier is the strategic enterprise product, multiple instances, advanced security, 99.95% SLA, unlimited storage, and discounting authority on Enterprise is substantially deeper than Premium. Most Fortune 500 buyers need Enterprise tier capabilities (particularly data residency and Atlassian Access controls), but reps often default the conversation to Premium pricing because Premium commits the customer to a lower tier. Escalating explicitly to Enterprise tier discussion unlocks deal-desk authority that Premium negotiations do not access.

Third, Atlassian Together bundles (Jira Software plus Confluence plus Loom plus Rovo or Atlas) are a deal-desk volume lever. Customers who consolidate multiple Atlassian products into the Together bundle qualify for compound discount depth that standalone Confluence does not. The caveat: Together bundles often include products the customer will not deploy, funding discount through shelfware. Commit to Together only if you will use Jira, Confluence, and at least one additional component at material scale.

Fourth, mid-term list-price changes have become a standard renewal surprise. Atlassian raised list prices across Cloud Premium and Enterprise in 2023, 2024, and 2025, with the price change applying to renewal customers at their next renewal cycle, not just new customers. Without contractual protection, a renewal in 2026 may price off a 2025 list that is materially higher than the 2023 list the original contract was negotiated against. Pre-negotiated list-price-change protection for the committed term is the single largest underappreciated clause in Atlassian agreements.

Fifth, Atlassian's strategic account segment, Fortune 500 scale, multi-product, multi-year, operates under dedicated deal-desk authority that standard mid-market reps cannot access. Strategic deal desk prices Confluence Enterprise with authority to 25 to 35% off list when competitive pressure and commitment size justify. Reps rarely volunteer the escalation path; asking explicitly after presenting Microsoft Loop, Notion Enterprise, or Guru competitive proposals triggers it.

The Discount Levers That Actually Work With Atlassian

These seven levers reliably move Atlassian's strategic deal desk. Stacked with competitive pressure and multi-year Together bundling, they compound into 28 to 38% off Confluence Cloud Enterprise list.

01, Escalate explicitly to Atlassian strategic deal desk

Atlassian's standard rep coverage is oriented toward self-serve and mid-market; strategic enterprise deals are handled by a separate deal desk with different pricing authority. Request escalation explicitly. The trigger statement: "This is a strategic Fortune 500 decision across Jira and Confluence. Please escalate to strategic deal desk for commercial review." Without that escalation, the discount ceiling is materially lower than the strategic authority allows.

02, Bring a written Microsoft Loop or Notion Enterprise proposal

Written competitive proposals from Microsoft Loop with SharePoint and Copilot, Notion Enterprise, Guru, Slab, or Nuclino are the largest lever. Microsoft Loop is particularly powerful because most Fortune 500 customers already own M365 E3 or E5 and the incremental cost of Loop consolidation is low. Atlassian's deal desk has begun treating Loop as an existential threat to Confluence strategic retention, and pricing responsiveness has increased materially over 2025. Notion Enterprise is a close second, its consumer UX and AI features push Atlassian on product parity.

03, Target Confluence Cloud Enterprise tier, not Premium

Enterprise tier has deeper discount authority than Premium. Frame the conversation around Enterprise-tier requirements, multiple instances, SAML, SCIM, data residency, Atlassian Access controls, 99.95% SLA, rather than letting the rep default to Premium. Most Fortune 500 buyers legitimately need Enterprise capabilities; starting the conversation there unlocks deal-desk authority that Premium negotiations do not access.

04, Negotiate Data Center migration incentives

If you are a Confluence Data Center customer committing to migrate to Cloud Enterprise, Atlassian has migration incentives that are not advertised in standard pricing pages. Cloud migration credits, extended trial windows on Cloud Enterprise, dual-running periods at discounted DC maintenance, and committed Cloud Enterprise discounts for the migration cohort. Structure the migration as a formal commitment with dates, and request the full incentive package in writing. The effective 3-year cost with migration incentives is often 30 to 40% lower than staying on DC renewal.

05, Cap annual renewal uplift and protect against list-price changes

Atlassian's standard renewal uplift is 5 to 10% on Cloud subscription pricing. Cap at lower of US CPI or 3%, but also insist on list-price-change protection for the committed term. The specific clause: "Effective per-user pricing for the committed term shall not increase based on changes to Atlassian published list pricing. Renewal pricing calculated off the agreement's effective per-user rate, not the then-current list." Without this clause, Atlassian can and will raise list between year one and year three, and the year-four renewal will price off the higher list.

06, Structure Atlassian Together bundles with deactivation rights

Atlassian Together bundles combine Jira, Confluence, Loom, and Rovo at compound discount. Commit to Together only if you will deploy Jira, Confluence, and at least one additional component at material scale. Structure each component with deployment milestones and deactivation rights if adoption stalls, with bundle discount on remaining components preserved. Otherwise the bundle discount funds shelfware on products the organization will not use.

07, Time to Atlassian's fiscal Q4 close

Atlassian's fiscal year ends June 30. Q4 runs April, May, and June, with the deepest discount window in the last two weeks of June. Atlassian is a public company and deal-desk behavior reflects public-market bookings discipline. Start negotiation 120 days before your target close, finalize terms by early June, and close on June 15 to 30. Customer-originated deals closing in Q4 routinely see 5 to 10 points of incremental discount over the same proposal closed in Q1 or Q2.

Typical Discount Ranges: What Comparable Companies Achieve

These ranges reflect Atlassian / Confluence deals benchmarked across 2024 to 2026. "Achievable with leverage" assumes strategic deal-desk escalation, written Microsoft Loop or Notion proposals, Together bundling or Cloud migration commitments, and fiscal Q4 close.

Deal Profile	Typical Discount	Achievable With Leverage	Notes
Confluence Cloud Standard, "Atlassian doesn't discount, our pricing is published." First-line defense from standard reps. Counter: "Published pricing applies to self-serve. This is a Fortune 500 strategic decision across Jira and Confluence with multi-year commitment. Please escalate to strategic deal desk for commercial review." This statement alone unlocks the escalation that standard reps will not volunteer.

"Cloud Premium is the right tier for your organization." Tier-down positioning to protect Enterprise discount authority. Counter: "Our requirements include multiple instances, SAML with SCIM, data residency, 99.95% SLA, and Atlassian Access controls. Those capabilities require Enterprise tier. Please price Enterprise with strategic deal-desk authority."

"Atlassian Together requires you to commit to all four products." Bundle push. Counter: "Together bundles should reflect products we will deploy at material scale. We'll commit to Jira, Confluence, and one additional component with deployment milestones and deactivation rights. Price the bundle accordingly. Otherwise we'll commit standalone and evaluate Loom and Rovo separately."

"We can't protect against list-price changes, that's a company-wide policy." Revenue-protection positioning. Counter: "Every multi-year SaaS contract at our company has list-price-change protection for the committed term. If Atlassian is unwilling, we'll reduce commitment duration to 12 months and re-evaluate annually, with Microsoft Loop, Notion Enterprise, and Guru included in the re-evaluation." The short-term alternative plus competitive threat usually unlocks the protection.

"Data Center renewal pricing is standard." Defensive revenue. Counter: "DC renewal at current pricing doesn't reflect your strategic priority of migrating customers to Cloud. Let's structure a DC-to-Cloud Enterprise migration with committed dates in exchange for migration incentives and a committed Cloud Enterprise discount for the migration cohort." Atlassian's strategic priority is Cloud migration; this framing unlocks authority DC-only negotiations never access.

Get a 48-hour Atlassian benchmark

We compare your Atlassian proposal line-by-line against benchmarked deals. Confluence Cloud Enterprise discount tier, Together bundle economics, DC migration incentives, list-price protection, and renewal protections, quantified.

Contract Language That Protects You at Renewal

Discount depth disappears at renewal without structural protections. These clauses should appear in every Atlassian / Confluence Enterprise agreement.

Uplift Cap

Annual renewal uplift capped at lower of US CPI or 3%, applied to effective per-user rates. Cap applies to all existing and future Together bundle components.

List-Price Change Protection

User Growth Pricing

User expansion priced at the same discount tier as base commitment. Published per-user rates for each tier in the order form. Automatic re-tiering into higher commitment bands at the same effective rate.

Together Bundle Deactivation Rights

Right to deactivate Together bundle components (Loom, Rovo, Atlas) that slip adoption milestones without penalty, with Jira plus Confluence discount preserved at the original Together tier.

Data Residency and Sovereign Cloud Guarantees

Data residency commitments (US, EU, AU, SG, DE, CA) locked for the committed term with no unilateral changes. SLA credits for data-sovereignty incidents.

Migration Assistance for Cloud Transition

For DC-to-Cloud migrations, Atlassian-funded migration tooling support, dual-running period at discounted DC maintenance (90 to 180 days), and committed Cloud Enterprise discount for the migration cohort locked for 3 years.

SLA Credit Scaling

SLA credits scale with severity and duration of service incidents. Cloud Enterprise 99.95% SLA with credit aggregation across the renewal cycle. Three P1 availability incidents in a 12-month rolling window trigger termination right without penalty.

Non-Renewal Notice Window

60 days' notice to non-renew, effective on delivery. Auto-renewal only at the same discount tier and commitment structure, never at a reset list rate.