Concurrent Agreements on AWS Marketplace — and Why This Matters

Last week, Amazon Web Services announced a significant update to AWS Marketplace: the ability to support concurrent private offers and agreements.

On the surface, this is a feature release. In reality, it's something more important — it's the outcome of a deliberate, structured listening loop between AWS and the ISVs who rely on Marketplace to run their businesses.

Where This Actually Started: The AWS "Ops Squad"

The need for concurrent agreements didn't emerge from a product roadmap brainstorm. It came from operators.

The "AWS Ops Squad" began as a small group of prominent Marketplace-using ISVs — founders, revenue leaders, marketplace operators — who were deep in the mechanics of private offers, renewals, CPPO, channel motion, and co-sell execution. The goal was simple:

• What works in Marketplace?
• What doesn't?
• What's friction vs. what's intentional design?
• What's misunderstood?
• What would materially improve revenue execution?

Over time, this group expanded globally. What started as a tight feedback loop became a broader, international operator forum.

Importantly, this wasn't just about feature requests. It was about context. Marketplace can sometimes feel rigid — but often that rigidity exists for structural, billing, or compliance reasons. The Ops Squad created a space where AWS could both improve the product where it genuinely needed improvement and explain why certain constraints exist.

Customer-Centric — Even When the "Customer" Is an ISV

In this instance, the Marketplace-using ISVs are the customers. And AWS behaved accordingly.

Customer centricity isn't about slogans — it's about:

• Listening to commercially meaningful friction
• Validating patterns across multiple operators
• Prioritising engineering resources
• Shipping something that removes real-world deal complexity

Concurrent agreements solve a tangible revenue operations problem. They reduce unnecessary friction in structuring deals and allow sellers to operate in a way that reflects how enterprise procurement actually works.

Why This Is Worth Calling Out

It's easy to criticise large corporations. And often, criticism is warranted. But it's equally important to highlight when they get it right.

AWS didn't have to build a structured operator forum. They didn't have to scale it globally. They didn't have to incorporate that feedback into shipped functionality. But they did.

Individuals deserve recognition here — particularly Phil Soane and Wei-Han Chen, who helped champion and operationalise this feedback loop. These kinds of improvements don't happen by accident; they happen because people internally decide that operator feedback matters.

The Bigger Picture

Marketplace is no longer an experimental GTM motion. It's a primary enterprise procurement channel.

As that evolution continues, structured listening mechanisms like the Ops Squad will become even more important. Because the companies building on Marketplace aren't just vendors — they're scaling businesses whose revenue models now depend on it.

Concurrent agreements are a feature. But the process that led to them is the real story. And that's worth recognising.