Most partners who tell me their AWS co-sell motion "isn't working" don't actually have a co-sell motion. They have a sell motion, with AWS cast as an extra distribution channel they're hoping to activate.

While that distinction sounds pedantic, it's definitely not. It's the entire reason so many partnerships stall at exactly the same point: the partner shows up asking AWS to sell their product, and AWS, quite reasonably, declines to do that.

What Most Partners Are Actually Asking For

Strip away the ACE submissions, the Better Together stories, the enablement sessions, and look at what's actually being requested of the AWS AM in most partner interactions. It's some version of: "Please introduce us to your customers." "Please mention us when it's relevant." "Please help us close this deal."

Every one of those is a one-way ask. It treats the AWS seller as a bigger, better-connected version of a reseller or an affiliate for new leads. And AWS sellers can smell that framing immediately, because they get it from hundreds of partners throughout the year. There's nothing in it for them beyond goodwill, and goodwill doesn't survive a busy quarter.

But more than being an unwelcome ask, it's structurally the wrong ask, because that's not what an AWS AM's job actually is, and more importantly, it's not what they're incentivised on. A reseller or an affiliate is compensated, in some form, for the leads or introductions they generate. An AWS AM isn't. They're measured on consumption and deal progression inside their own patch, not on how many partner introductions they've made this quarter.

That gap matters more than most partners realise, because it means the whole model breaks even in the best-case scenario. Say you find the one AM who genuinely likes your product, believes in the story, and goes out of their way to make introductions anyway. For as long as that one person is willing to spend their own time and social capital doing something their job doesn't reward, it's great. But that doesn't scale, because nothing about the arrangement transfers to the next AM, the next territory, or the same AM after they get a new manager, a new quota, or simply get busy. Instead of building a motion you've found a favour, being extended by someone whose comp plan gives them no reason to keep extending it.

This is why so many co-sell relationships die after the kickoff call, and it's also why the ones that seem to work often turn out to be riding on exactly one generous AM, right up until that AM moves on. Not because the partner did anything wrong exactly, but because the ask was never mutual, and the person being asked was never actually set up to say yes to it repeatedly.

Co-Sell Means Something Was Supposed to Flow Both Ways

The word "co" isn't decorative. It means the AWS seller has a reason to bring you into a deal that has nothing to do with liking you, and everything to do with what happens to their own number if they do.

There are really only two questions that matter here:

Does your product solve a real problem for an AWS customer? Not "are you cloud native," not "are you aligned with AWS's strategic priorities". Does an actual customer, in an actual deployment, get measurably better outcomes because your product exists alongside AWS services. This is the half most partners get right, or at least think about. It's the Better Together story, and I've written about how to build one properly before.

Does bringing you in help the AWS seller move their own deal forward? This is the half almost nobody thinks about, and it's the one that actually determines whether an AM picks up the phone. AWS sellers are measured on consumption, on deal velocity, on closing what's already in their pipeline. If your product helps them get an existing deal over the line faster, whether it's de-risking a migration, unblocking a stalled workload or giving them a wedge into a wider account, then you've given them a reason to act that has nothing to do with charity.

Most partners have an answer to question one. Almost none have a real answer to question two. And a co-sell motion built entirely on question one isn't a co-sell motion. It's a hope that a customer-value story is persuasive enough to overcome the fact that you're asking the seller to do work for you with no corresponding upside for them.

Why This Gets Missed So Often

Partly, it's because question one is the comfortable one to answer. It's about your product, which you know intimately. Question two is about someone else's incentives, their pipeline, their quota — territory most partnerships teams have never actually had to think about, because they've never sat on the AWS side of the table.

Partly, it's because the language of the ecosystem encourages the confusion. "Co-sell" gets used so loosely, in ACE, in AWS's own documentation, in every partner enablement deck including some of my own. It's easy to absorb it as a synonym for "AWS helps me sell," without ever registering that the word is asking you to bring something to the table too.

And partly, it's structural. Building a genuine answer to question two requires understanding how an AWS seller's deal actually accelerates when you're in it — their internal targets, their existing pipeline pressure, what a stalled deal looks like from their side. That's a harder, slower thing to build than a slide that says "we complement EKS." It requires actual visibility into how AWS reps operate, not just conviction that your product is good.

What a Genuinely Mutual Motion Looks Like

If you want a co-sell motion that survives past the first kickoff call, it needs to be built so both halves are visible, provable, and repeatable — not just asserted in a deck once and forgotten.

For the customer-value half: Can you point to a specific, named deployment where your product measurably improved an AWS outcome? Was it more consumption, faster time-to-value, reduced churn risk? Is that story written in the customer's language, not your product's feature list, so an AM can repeat it on a call without a technical deep dive?

For the seller-value half, which is the one worth actually sitting with: Where in an AWS seller's typical deal does friction usually show up, and does your product remove that friction? Can you show a case where bringing you in accelerated an AWS deal that was already stalling, rather than just added a nice-to-have, but actually moved the timeline? Would an AM walking into their next 1:1 with their manager have something genuinely good to say about why they brought you in, beyond "the partner asked nicely"?

If you can't answer that second set with something concrete, you don't yet have a co-sell motion. You have a partner-value motion, which is a perfectly reasonable thing to have, but it will keep getting treated by AWS sellers as exactly what it is: a favour being requested, not a trade being offered.

The Bottom Line

The partnerships that actually work aren't the ones with the best Better Together deck. They're the ones where an AWS seller can articulate, unprompted, what's in it for them to bring you into a deal. If the honest answer to "why would an AM prioritise us" is "because our product is good and we asked," that's not co-sell. That's outbound with extra steps.

Before your next AWS conversation, don't ask "how do we get AWS to sell for us." Ask "what does an AWS seller's deal look like better because we're in it." If you can't answer that second question as clearly as the first, that's the gap to close.

Tip of the Week

Take your current Better Together story and read it back looking only for the seller's incentive, not the customer's benefit. If every sentence is about the customer and none of it is about what changes for the AWS seller's own deal or quota, you've written half a story and are wondering why it isn't landing.

One to Read: Go back to Week 13 (What Strong Better Together Stories Look Like). Notice that every example there — Coveo, Armis, SUSE Rancher — ties back to AWS consumption growth, which is exactly the seller-side incentive most partners skip. That was always the real reason those stories worked.