The difference between being listed on Marketplace and selling through it

One of our customers got listed on AWS Marketplace, announced it, put the badge in their email signatures, and then transacted exactly nothing through it for a year. When we started working with them, the listing came up almost apologetically, the way you'd mention a gym membership. It wasn't a failed project. It was a successful project attached to no motion: everyone had treated "listed" as the goal, and "listed" is not a goal, it's an address.

What finally moved wasn't a better listing. A rep on a slipping deal learned, late, that the buyer had a committed-spend agreement with AWS, an EDP, with a use-it-or-lose-it commitment the buyer was behind on. The rep's deal could be paid for out of money the buyer had already promised to spend. Repackaged as a private offer, the deal stopped being a new line item fighting for budget and became a way for the buyer's cloud team to hit a number they were worried about. Procurement, which had been quoting a monthslong vendor-onboarding process, took weeks instead: AWS was already an approved vendor, and this was just more AWS spend.

That's the entire difference. A listing is you being findable. A transaction is the buyer spending money they've already committed, through paper they've already signed. The first is about you; the second is about them.

Why the confusion persists

Partner tier checklists reward the listing, so the listing gets built. Nothing in the checklist rewards the uncomfortable follow-through: teaching reps to ask, on every enterprise deal, whether the buyer has an EDP and how their commitment burn is tracking. That question feels intrusive until you realize the buyer's cloud team usually wants to route spend through the commitment, and is delighted when a vendor makes it easy. The information asymmetry runs the wrong way: the buyer knows about their commit and doesn't think to mention it; the rep doesn't know to ask.

This is also, unsurprisingly, a data problem wearing a strategy costume, like most of co-sell. "Does this account have an EDP, and is the deal offer-shaped?" is a per-deal fact, and in our product it rides the same rails as every other per-deal fact, surfaced next to the offer workflow from the last post. But you can run the whole motion with no tooling at all: it's one question, asked earlier.

Real numbers

1. 1 year listed, 0 transactions at one customer - a finished listing attached to no motion.
2. Months → weeks through the buyer's procurement once the deal rode existing AWS paper instead of new vendor onboarding.
3. 1 question ("do you have an EDP, and how's the burn?") separating the two states, asked by the rep, early.

Where the humans sit

The motion is carried entirely by two humans talking: your rep and the buyer's cloud owner. Marketplace, the offer, the commit drawdown are plumbing between them. Which means the leverage is in what your reps know to ask, not in what your listing looks like, and the alliance lead's job on this front is closer to teaching than to operations.

Steal this

Audit your open enterprise deals this week with one column added: does the buyer have committed AWS spend, and does anyone on the deal know its burn status? For every yes-and-behind, propose the private offer now; the buyer's own cloud team becomes your closer. If the answer is unknown across the board, that's the actual Marketplace problem, and it costs a training session to fix, not a listing revamp. Being listed made none of this happen. It just made it possible.

Next on this track: the artifact that keeps a partnership honest - the scorecard we generate before every QBR.

---

This post is part of the partner track of How a Tiny Team Ships Like a Big One, a series on how six builders run a production AI company. Building at Aithon - if this is how you want to work, talk to us.