What Q1 2026 cloud earnings just told every ISV about partner, co-sell, and Marketplace strategy.

On April 29, three earnings reports landed within hours of each other and quietly redrew the map of cloud go-to-market for every software company. AWS posted Q1 2026 revenue of $37.6 billion, up 28% year-over-year, the fastest growth in 15 quarters. Backlog: $364 billion, and that figure excludes a freshly signed Anthropic deal worth more than $100 billion on its own. Microsoft followed with FY26 Q3 revenue of $82.9 billion, Azure up 40%, and a Commercial Remaining Performance Obligation (RPO) of $627 billion. That number nearly doubled year-over-year. Doubled. Google Cloud rounded out the day with $20 billion in quarterly revenue, up 63%, and a backlog that nearly doubled quarter-over-quarter to $462 billion.

Customers have signed contracts for north of $1.4 trillion! in future cloud spend across the three hyperscalers. That money has been promised. It has been budgeted. It now has to be consumed.

If you sell software and you are not thinking carefully about how to position your product against that consumption pressure, you are leaving the largest tailwind in enterprise software history sitting on the table.

The mechanic most ISVs still underestimate

Cloud commits are not simply discount programs. They are use-it-or-lose-it agreements. Customers sign Private Pricing Agreements (PPAs, formerly the AWS Enterprise Discount Program or EDP), Microsoft Azure Consumption Commitments (MACC), and Google Committed Use Discounts (CUD) in exchange for negotiated discounts. In return, they owe the hyperscaler a minimum spend over one to five years.

Every one of those programs allows the customer to draw down a portion (in some cases up to 100%) of the commitment by purchasing third-party software through the cloud provider’s Marketplace. AWS allows up to 25% of an EDP commit to be retired through qualifying Marketplace software purchases. Google’s Channel Private Offers, as of mid-2025, retire 100% of commitment value tied to the negotiated price. Microsoft’s MACC program treats Marketplace purchases as eligible Azure consumption.

Run the math on AWS alone. A reported $364 billion backlog, 25% retirable through Marketplace, implies up to roughly $91 billion of pre-allocated buyer budget that is hunting for ISV products to consume it. That is the procurement pool sitting inside agreements customers have already signed.

If your product is not transactable on the cloud where your customer holds their commit, you are not in a price competition. You are not in a feature competition. You are simply not on the buyer’s procurement list.

Why the acceleration matters more than the size

The headline numbers are dramatic, but the deeper signal is the pace.

Microsoft’s RPO doubled in twelve months. Google’s backlog nearly doubled in one quarter. AWS re-accelerated to a level we have not seen since 2022. The trajectory is not linear, and it is not slowing.

Three things follow from that.

Hyperscaler sellers are under enormous pressure to convert backlog into recognized revenue. They will spend their selling time on partners who help them do that. Co-sell readiness moves from “nice to have” to “the thing that determines whether an Account Executive returns your call.”

The deals are getting larger and more concentrated. AWS confirmed its backlog has “reasonable breadth,” but the Anthropic agreement alone represents a $100 billion line item. When the largest customers commit at this scale, the operational pressure to pull software purchases forward into Marketplace lanes intensifies, especially in years two and three of multi-year agreements where shortfall risk becomes visible.

The AI workloads driving this growth are pulling adjacent ISV demand with them. Data tooling, observability, security, governance, deployment automation, and vertical applications all sit downstream of AI infrastructure spend. If you sell into any of these categories and your buyer is in active AI build-out, the commit-funded purchase window is open right now.

The Fractivo view: three things most ISVs are getting wrong

We work with software companies on AWS Cloud GTM every week, and the same patterns keep surfacing.

1. Listing is treated as a strategy

It is a procurement mechanism. The strategy is the partner motion that drives buyers to use it. We see ISVs invest six months in a listing, launch it, then wait for inbound that never comes. A Marketplace listing with no co-sell motion, no private offer playbook, and no Account Executive relationships produces nothing.

2. The three motions are treated as one

AWS ISV Accelerate, Microsoft Azure IP Co-Sell, and Google Partner Advantage are not interchangeable. They have different revenue thresholds, different validation requirements, different seller engagement models, and different incentive structures. A single multi-cloud playbook will underperform on all three. We map each motion against the buyer base, the Ideal Customer Profile (ICP) geography, and the existing pipeline before recommending where to invest first.

3. Compensation neutrality with the hyperscaler seller is left to chance

When a hyperscaler Account Executive co-sells your deal, they need to know it counts toward their quota the same way a first-party deal would. If your deal does not retire commit cleanly or attach to a Specialization the seller is being measured on, you are asking them to do you a favor on their commission. That math does not work at scale. Structuring deals to align with seller compensation is one of the core coaching tactics we apply with every ISV client.

What to do about it before the quarter closes

If you are an ISV and Q1 2026 earnings just made you question whether your partner strategy is keeping up, three diagnostic questions are worth answering this week.

  1. Are you transactable on the cloud where your largest customers hold their commit? If the answer is no for any of the three hyperscalers where you have meaningful pipeline, that is a procurement gap, not a marketing gap.
  2. Do you have a current view of which active opportunities can be routed through Marketplace as a private offer to retire buyer commit? This is often the fastest path to closing a stalled deal in Q2.
  3. Is your co-sell motion structured around what the hyperscaler seller is being measured on, or around what is convenient for your team? The answer determines whether you get pipeline help, or whether you do not.

Let’s talk

We help software companies build the partner motion that turns these tailwinds into pipeline. If the trillion-dollar backlog story has surfaced gaps in your AWS, Azure, or GCP strategy, we would like to hear what you are working on.

Reach out. We will tell you what we see, where we think the leverage is, and whether we are the right team to help you capture it.


Ryan Vankessel is the founder of Fractivo, an AWS alliance consultancy helping ISVs build, scale, and execute Cloud GTM strategy across AWS, Microsoft, and Google Cloud.

Sources

  • Amazon Q1 2026 Earnings Call Transcript, April 29, 2026: AWS revenue $37.6B, +28% YoY; backlog $364B exclusive of $100B+ Anthropic deal. The Motley Fool | CNBC
  • Microsoft FY26 Q3 Press Release, April 29, 2026: Total revenue $82.9B, Azure +40%, Commercial RPO $627B (+99% YoY). Microsoft Investor Relations | SEC Form 8-K
  • Alphabet Q1 2026 Earnings Release, April 29, 2026: Google Cloud revenue $20.0B, +63% YoY; backlog $462B; ~50% expected to convert to revenue over the next 24 months. SEC Form 8-K | Earnings Call Transcript
  • Google Cloud Marketplace updates: 100% commit drawdown via Channel Private Offers; variable revenue share (1.5% on $10M+ deals, 3% under $1M). ChannelE2E coverage | ERP Today analysis
Share this post

Subscribe to our newsletter

Keep up with the latest blog posts by staying updated. No spamming: we promise.
By clicking Sign Up you’re confirming that you agree with our Terms and Conditions.

Related posts