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

Rackspace Technology Pricing 2026: What

Rackspace Technology pricing 2026: managed cloud, private cloud, and hyperscale markup economics, discount benchmarks, and negotiation tactics from $2.1B+.

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.

Infrastructure and operations. Rackspace Technology is lift-and-shift territory. The migration is the workload and the workload is the consumption, which makes this the shortest line between a renewal date and a funded cloud pursuit.

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
Google Cloud
Google Cloud carries the commitment as committed-use discounts and a negotiated spend agreement. Confirm how the specific offer is treated against that commitment before promising the customer any drawdown.
Google Cloud co-sell Google Cloud Partner Advantage

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

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

Key points

Managed AWS (Rackspace's flagship offering, approximately 45% of revenue) carries a service markup of roughly 12-18% on underlying AWS consumption at Aviator tier, stepping to 18-22% at Navigator tier with deeper operational coverage.
Managed Azure carries similar 12-22% markup depending on service tier.
Managed Google Cloud markups run 14-20%.
Private cloud (VMware-based and OpenStack-based) is priced as a fully-loaded per-GB and per-vCPU monthly rate that bundles compute, storage, networking, and management into a single managed price, typically $0.04-$0.09 per vCPU-hour plus $0.08-$0.18 per GB storage-month depending on SLA tier.
Dedicated hosting follows a traditional physical server lease model with rates from $400-$2,400 per server-month depending on specifications.
Median Fortune 1000 Rackspace Technology spend is approximately $1.4M annually, with managed hyperscale representing roughly 65% of the revenue mix, private cloud another 18%, and dedicated managed hosting plus cybersecurity services the remaining balance.
Aviator tier covers foundational managed services (monitoring, incident response, patching, backup) at 12-18% service markup on underlying AWS consumption plus platform service fee.
Navigator tier adds DevOps automation, SRE practice, cost optimization, and architectural consultation at 18-22% markup plus higher platform fee.
Pricing structure parallels managed AWS: 12-22% service markup on underlying Azure consumption plus platform fee tier.
Service markup runs 14-20% on underlying GCP consumption plus platform fee.

Rackspace Technology Pricing Model Explained

Rackspace operates a two-layer pricing model that procurement teams routinely conflate, to their cost. The first layer is the underlying consumption AWS, Azure, or Google Cloud infrastructure billed via Rackspace as the reseller of record. The second layer is the Rackspace service value a combination of markup percentage on the underlying consumption plus a platform service fee tier that depends on environment complexity, service level (Aviator, Navigator, or custom enterprise tiers), ticket volume expectations, and response SLA commitments. The underlying consumption typically passes through at hyperscale list pricing, with Rackspace capturing the Enterprise Discount Program (EDP) economics on the AWS side and Enterprise Agreement economics on the Azure side. That means Rackspace can pass through some of the EDP discount to customers, or capture it as margin, and this is frequently not transparent in standard pricing proposals.

Managed AWS (Rackspace's flagship offering, approximately 45% of revenue) carries a service markup of roughly 12-18% on underlying AWS consumption at Aviator tier, stepping to 18-22% at Navigator tier with deeper operational coverage. Managed Azure carries similar 12-22% markup depending on service tier. Managed Google Cloud markups run 14-20%. Private cloud (VMware-based and OpenStack-based) is priced as a fully-loaded per-GB and per-vCPU monthly rate that bundles compute, storage, networking, and management into a single managed price, typically $0.04-$0.09 per vCPU-hour plus $0.08-$0.18 per GB storage-month depending on SLA tier. Dedicated hosting follows a traditional physical server lease model with rates from $400-$2,400 per server-month depending on specifications.

The second commercial construct to understand is platform service fees fixed monthly fees that cover 24/7 monitoring, incident response, patching, backup management, and tier-specific operational support. Platform service fees typically scale with environment size: small environments (under $25K monthly hyperscale spend) at $3,500-$8,500 monthly platform fee, medium environments ($25K-$100K hyperscale spend) at $8,500-$22,000 monthly, large environments ($100K-$500K hyperscale spend) at $22,000-$65,000 monthly, and strategic environments above $500K monthly hyperscale spend at custom platform fees typically $65,000-$180,000 monthly depending on complexity and coverage scope.

How Rackspace Captures Hyperscale Economics

Rackspace is an AWS Premier Tier Services Partner and Azure Expert MSP with substantial aggregated hyperscale commit across its customer base. This aggregation produces meaningful Enterprise Discount Program savings that Rackspace captures, and can choose to pass through to customers, partially pass through, or retain entirely as margin. The key negotiation point: demand transparency on hyperscale pricing pass-through. Best-in-class Rackspace contracts include line-item transparency showing underlying AWS or Azure list pricing, any EDP or EA discount applied, and the Rackspace service markup applied separately. Worst-in-class contracts blend everything into a single "managed hyperscale" line item where the customer cannot distinguish between infrastructure cost and service cost.

What Enterprises Actually Pay for Rackspace Technology

These 2026 figures reflect negotiated annual Rackspace Technology spend across 38+ benchmarked enterprise deployments. "Typical" reflects median deal economics with modest competitive pressure; "Strong Leverage" assumes written RFP responses from Accenture, DXC, Kyndryl, Capgemini, or direct-to-hyperscale plus private cloud alternatives.

Deployment Profile	Primary Services	Typical Annual Spend (Negotiated)	With Strong Leverage
Small managed hyperscale	Managed AWS or Azure, single region	$180K to $650K	$145K to $500K
Medium managed multicloud	Managed AWS + Azure, multi-region	$650K to $2.4M	$520K to $1.9M
Large managed multicloud + private	Full stack including VMware private cloud	$2.4M to $8.5M	$1.9M to $6.4M
Strategic enterprise multicloud	Dedicated teams + cybersecurity + SRE	$8.5M to $22M	$6.8M to $17M
Private cloud only (VMware)	Dedicated private cloud environment	$300K to $4.2M	$245K to $3.3M
Managed hyperscale markup	Aviator tier on AWS/Azure	12 to 18% markup	8 to 12% markup
Managed hyperscale markup	Navigator tier on AWS/Azure	18 to 22% markup	14 to 18% markup

Median Fortune 1000 Rackspace Technology spend is approximately $1.4M annually, with managed hyperscale representing roughly 65% of the revenue mix, private cloud another 18%, and dedicated managed hosting plus cybersecurity services the remaining balance. The primary driver of variance is service tier and environment complexity. For comparative context, see our AWS pricing guide, Microsoft Azure pricing guide, and IBM Cloud pricing guide.

Rackspace Discount Benchmarks, What Is Achievable?

Rackspace's negotiable levers sit almost entirely on the service layer: markup percentage, platform service fee tier, minimum commit thresholds, ticket-volume caps, and professional services pooled hours. The underlying hyperscale consumption pricing is largely dictated by AWS or Azure list with Rackspace choosing how much EDP or EA discount to pass through. Procurement teams that optimize only on the underlying hyperscale pricing frequently leave substantial savings on the table at the service layer.

Discount Mechanism	Typical Depth	With Strong Leverage	Notes
Service markup reduction (Aviator)	2 to 5 points	4 to 7 points	List 12-18% to negotiated 8-13%
Service markup reduction (Navigator)	3 to 6 points	5 to 9 points	List 18-22% to negotiated 13-17%
Platform fee tier discount	12 to 22%	20 to 32%	On fixed monthly platform fees
Hyperscale EDP pass-through	3 to 8%	8 to 14%	Demand line-item transparency
3-year commitment (vs 1-year)	8 to 14%	14 to 20%	Only if workload stability supports
Competitive RFP uplift	6 to 12%	12 to 22%	Accenture/DXC/Kyndryl bids critical
Private cloud overage elimination	3 to 8%	8 to 14%	Right-size committed capacity to actual usage
Professional services pooled hours	15 to 25%	25 to 38%	On hourly PS rates via prepaid pools

The three credible competitive alternatives Rackspace commercial teams model against: direct-to-hyperscale with internal cloud engineering (eliminates markup and platform fees entirely if internal capability exists), tier-1 systems integrators (Accenture, DXC Technology, Kyndryl, Capgemini, TCS, Infosys, Wipro) offering similar managed multicloud services at comparable or tighter economics on large deals, and niche managed services specialists (Mission Cloud, 2nd Watch, Cloudreach, Ensono, Presidio) with focused AWS or Azure expertise often at lower service markup than Rackspace.

Rackspace Pricing by Service Portfolio

Managed AWS (Aviator and Navigator Tiers)

Rackspace's flagship offering. Aviator tier covers foundational managed services (monitoring, incident response, patching, backup) at 12-18% service markup on underlying AWS consumption plus platform service fee. Navigator tier adds DevOps automation, SRE practice, cost optimization, and architectural consultation at 18-22% markup plus higher platform fee. For large environments, custom enterprise tiers bundle dedicated Rackspace engineering teams. Negotiate transparent AWS EDP pass-through, markup floor commitments, and ticket-volume tier thresholds.

Managed Azure

Rackspace is one of the few Azure Expert MSPs with multi-regional Azure managed services delivery. Pricing structure parallels managed AWS: 12-22% service markup on underlying Azure consumption plus platform fee tier. Rackspace captures Microsoft Enterprise Agreement economics via Microsoft channel and passes through partially. Negotiate Azure Enterprise Agreement pass-through transparency and MACC (Microsoft Azure Consumption Commitment) crediting mechanics.

Managed Google Cloud

Smaller revenue line than managed AWS or Azure. Service markup runs 14-20% on underlying GCP consumption plus platform fee. Google Cloud Premier Partner economics passed through at Rackspace discretion. For Google Cloud-committed enterprises, Rackspace is a credible managed services option but competitive offerings from SADA Systems, Onix, and Cloudreach frequently carry tighter markup.

Private Cloud (VMware-based)

Rackspace Private Cloud Powered by VMware is priced as fully-loaded monthly rates bundling compute, storage, networking, VMware license, and management. Pricing typically $0.04-$0.09 per vCPU-hour plus $0.08-$0.18 per GB storage-month depending on SLA tier, with minimum commit thresholds. The Broadcom VMware acquisition has pushed VMware licensing costs materially higher in 2025-2026, affecting Rackspace's private cloud economics. Negotiate transparent VMware license pass-through, minimum commit flexibility on workload migration, and 30-day workload-portability provisions.

Dedicated Hosting and Colocation

Legacy dedicated hosting and colocation revenue line. Physical server leases $400-$2,400 per server-month depending on specifications. Colocation rack pricing $600-$1,800 per rack-month plus power. This segment is declining as workloads migrate to hyperscale, but remains material for regulated industries requiring dedicated physical isolation. Negotiate aggressively, Rackspace is motivated to retain dedicated hosting customers through hyperscale migration commitments.

Managed Security and Compliance

Rackspace Elastic Engineering for Security and Managed Detection and Response (MDR) services. Pricing ranges $8-$28 per endpoint per month plus SIEM platform fees. Competitive benchmark against CrowdStrike Falcon, Palo Alto Networks, and Splunk economics.

Benchmark Rackspace against direct hyperscale + SI alternatives

See how your Rackspace service markup and platform fees compare against direct-to-hyperscale plus internal cloud engineering, Accenture, DXC Technology, and Kyndryl managed services economics. 24-hour benchmark across 38+ comparable deployments.

Common Rackspace Contract Traps to Watch For

Auto-Renewal With 60-90 Day Notice Clauses

Default Rackspace contracts include auto-renewal provisions requiring 60-90 day written notice to cancel. Missing the notice window extends the contract for another full term, typically at escalated platform service fees. Procurement teams routinely discover they missed the notice window only after receiving the renewal invoice. Negotiate 30-day renewal notice or explicit opt-in renewal requiring written confirmation from customer signatory.

Hyperscale Markup Applied to Reserved Instance Purchases

A non-obvious cost driver: when customers commit to Reserved Instances or Savings Plans on the underlying AWS or Azure, Rackspace typically applies its service markup to the RI or Savings Plan price, not just to on-demand usage. This means the discount savings from RI coverage flow partially to Rackspace as additional margin. Negotiate markup structure that applies only to variable consumption, not to pre-purchased RI or Savings Plan capacity.

Ticket-Based Professional Services Billing

Beyond platform service fees, Rackspace bills professional services hours against tickets and change requests. Without a ticket-volume cap or pooled hours structure, professional services billing can exceed scoped hours by 30-60% annually. Negotiate pooled hours structure with rollover provisions or ticket-volume caps with transparent overage pricing.

Private Cloud Minimum Commit Stranded Capacity

Private cloud contracts include minimum commit thresholds (typically $8K-$45K monthly depending on environment size). As workloads migrate to hyperscale, customers routinely find themselves paying for stranded private cloud capacity they no longer need. Negotiate workload-portability provisions allowing private cloud commit to convert to managed hyperscale commit without penalty, or mid-term commit reduction rights at 10-15% reduction fee.

Rackspace Renewal Pricing: What Changes and What Does Not

Rackspace renewal behavior is less predictable than hyperscale-native renewals because of the service layer dynamics. The platform service fee tier and markup percentages are the primary renewal levers.

What changes at renewal: Platform service fees typically increase 5-9% annually absent negotiation, citing "operational cost inflation" or "service enhancement." Hyperscale pass-through discount rates reset to then-current Rackspace commercial terms, which may be materially different from the terms at original sale. Ticket-volume thresholds and professional services hour pools often reset to standard tiers rather than negotiated levels. Private cloud pricing adjusts based on Rackspace's underlying cost inputs, particularly VMware licensing following the Broadcom acquisition.

What does not change without leverage: Service markup percentages rarely decrease at renewal absent competitive pressure. Auto-renewal clauses extend unchanged. Platform service fee tier does not step down automatically even if environment has shrunk. Professional services rates carry forward at list absent renegotiation.

What changes with leverage: Written RFP responses from tier-1 systems integrators (Accenture, DXC, Kyndryl, Capgemini) at renewal initiation routinely unlock 6-12% incremental service layer savings. Direct-to-hyperscale viability assessments including internal cloud engineering build-out cost modeling position the customer to exit if Rackspace does not compete meaningfully. Multi-year commit in exchange for markup floor and platform fee cap provides renewal-price certainty.