Most AWS partners running a co-sell motion through ACE describe the same experience. They submit opportunities. PDM conversations happen. Some deals close. But the motion doesn’t compound the way it was supposed to — more ACE activity doesn’t produce proportionally more pipeline, PDM relationships that took a year to build produce inconsistent results, and when a PDM moves to a new role, the motion partially resets.
This is true for AWS consulting partners (SIs) and SaaS ISVs alike. The mechanics differ, but the frustration is identical. And the reason is the same: most partners are running co-sell without understanding that it is two fundamentally different motions operating under one program name.
The root cause isn’t ACE. It’s treating co-sell as one motion when it’s two.
Co-sell in ACE runs on two distinct tracks. Understanding which one you’re operating in changes everything about what good execution looks like.
The first is AO — an AWS-Originated Opportunity. AWS finds the account and refers it to a partner. The PDM is making a selection: which partner in my book is the right one for this customer, right now? The evaluation criteria are capability-based — competencies, specializations, certifications, regional fit, delivery track record. The partner who gets the referral is the one whose profile most credibly matches what the customer needs.
The second is PO — a Partner-Originated Opportunity. The partner finds the account and submits it to ACE, asking AWS to help accelerate. The PDM is making a different judgment: is this a real opportunity? Does this partner genuinely know this account? Are they bringing me something worth my time, or are they submitting accounts from a filtered list with no real relationship behind them? The evaluation criteria are not capability-based. They are relationship- and intelligence-based. The PDM wants to know that the partner has done the work — that there’s a real conversation underway, a real stakeholder who is receptive, a real account situation that makes this the right moment.
Most partners collapse these two motions into one and try to fix both with the same lever. For AO, they add competencies. For PO, they also add competencies — because the competency logic worked for AO and they assume it transfers. It doesn’t. The PDM evaluating a PO isn’t looking at the partner’s certification profile. She’s asking whether the partner has earned the right to bring this account.
Every submission is a credibility transaction — and most partners are in deficit
ACE submissions are not free. Each one is a withdrawal from or a deposit into a credibility account the partner has been building with the PDM over time.
A well-researched PO submission — an account where the partner has a real conversation underway, genuine stakeholder intelligence, and a specific timing reason to bring this to ACE now — is a deposit. The PDM receives something she can act on, champions it successfully, and updates her mental model of this partner as someone worth prioritizing.
A generic submission — an account pulled from an ICP filter with no stakeholder relationship, no specific account context, no timing reason — is a withdrawal. The PDM has to investigate whether this is even a real opportunity. She can’t champion it because there’s nothing specific to champion. She marks it pending and moves to the partners who brought her something actionable.
After enough withdrawals, the erosion is not subtle. The PDM takes meetings less frequently. Emails get slower responses. When a relevant account does come across her desk, the partner she thinks of is the one who consistently brings her clean, specific, actionable intelligence — not the one whose submissions consistently require her to do the work the partner should have done. That credibility gap takes real time to rebuild, even after the partner’s submission quality improves.
An SI submitting fifteen generic ACE opportunities in a quarter is not running a co-sell motion at scale. They are running fifteen credibility withdrawals simultaneously. The math on that is not good.
PDM dependency fills the gap that genuine prospect intelligence should fill
The second symptom follows from the first. When the partner isn’t generating real prospect relationships and real account intelligence, the PDM becomes the substitute. The motion shifts to: stay top of mind, show up at partner events, get regular syncs, and hope the PDM thinks of you when she hears of an account that might fit.
This produces results sometimes. A warm referral from a well-maintained PDM relationship closes real deals. That is not the issue. The issue is what the motion depends on and whether it compounds.
Relationship-dependent co-sell doesn’t improve with the partner’s own growth. A new competency, a sharper offering, a new vertical specialization — none of these are automatically visible to a PDM who is managing dozens of partners and can only invest attention in the ones actively bringing her intelligence. The motion is entirely dependent on the PDM’s bandwidth and memory, both of which are finite. And when the PDM rotates to a new role — which is a regular feature of the program, not an exception — the institutional knowledge resets. The new PDM knows nothing about the partner. The trust-building starts over.
PDM dependency is what fills the gap when the partner doesn’t have a systematic way to develop genuine prospect intelligence and genuine stakeholder relationships. It’s a workaround, not a motion. And like all workarounds, it costs more over time than addressing the root cause would have.
What the co-sell motion looks like when intelligence and relationships feed it
The fix looks different depending on which motion you’re in.
For AO flow, the question is whether AWS recognizes the partner as the right fit when relevant accounts come across the PDM’s desk. This is where competency attainment and specialization genuinely matter — they are the signal AWS uses to select which partner gets the referral. An AWS SI that has attained the Data & Analytics competency, built a delivery track record in migration programs, and maintained clean account performance in ACE becomes a natural candidate when a PDM is looking for a migration-capable partner for a specific account. The intelligence that matters here is about the partner’s own capability positioning, not the end account.
For PO flow, the question is whether the partner genuinely knows the account they’re submitting. This is where prospect intelligence and real stakeholder engagement are the differentiators — not competency profiles.
Consider an SI that has been doing outreach to companies in active MAP qualification phases — companies publicly signaling they are committing to an AWS migration program. The SI has had real conversations: a cloud infrastructure lead who is evaluating implementation partners for phase two of a migration, a specific decision timeline tied to MAP funding deployment windows, a genuine sense of what the account needs and when. That SI submits this to ACE as a PO with specific context: the account name, the stakeholder they’ve been talking to, the phase the account is in, and the specific timing window. The PDM receives something she can act on. She can warm-introduce the SI to her contact at the account, add the partner’s credibility to the deal, and help accelerate what already has human momentum.
For an ISV, the same logic applies with different account dynamics. An ISV in ISV Accelerate has been doing targeted outreach to companies whose AWS workloads are scaling into compliance territory — growing data environments approaching a SOC 2 audit, regulated verticals where FedRAMP readiness is becoming a contractual requirement. The ISV has had a genuine product conversation with a security architect at one of those accounts. The architect has evaluated the Marketplace listing, asked technical questions, and expressed real interest. The ISV submits this to ACE: the account, the stakeholder relationship, the compliance trigger, the product conversation underway. The PDM can champion an opportunity that already has a real relationship behind it.
In both cases, the PDM isn’t being asked to manufacture momentum. She’s being asked to amplify momentum that the partner has already started building through genuine prospect engagement. That is a fundamentally different ask from “here is an account we’d like you to help us get into.”
Co-sell is an amplifier, not a channel. It amplifies whatever you bring to it — including a vague offering.
When the partner brings research-grounded account intelligence and a genuine stakeholder relationship, co-sell amplifies a deal that is already in motion. When the partner brings a filtered list and a vague pitch, co-sell amplifies the noise that wasn’t converting before ACE was added.
A GTM Intelligence Layer specialized for the AWS ecosystem changes what the partner is able to bring to both motions. For AO flow, it sharpens the offering and the competency positioning that determines which accounts AWS routes to the partner. For PO flow, it supports the outreach and research that builds genuine prospect relationships — the email and LinkedIn execution that turns a researched account into a real stakeholder conversation, the ecosystem intelligence that identifies which accounts are in motion and why right now. Gil, Wyra’s AI agent for the AWS ecosystem, surfaces account situations tied to AWS program mechanics and connects them to the partner’s specific offering. The research that makes an ACE submission genuine gets done before the submission is written. Human review and judgment stay in the loop throughout: the team validates what surfaces, the partner owns the stakeholder relationship, and the PDM is handed something worth championing.
The counterargument worth naming
The honest objection: “ACE is working for us — we close co-sell deals.”
Yes. Co-sell deals close even on generic PO submissions. A PDM occasionally champions a deal without deep account context because she knows the account from her own relationship with the customer. A referral lands because the partner’s competency profile matched a PDM’s memory of a relevant account.
The question is whether this is a motion or a series of transactions. A motion improves with repetition. Genuine stakeholder relationships deepen. Research compounds. PDM credibility builds because the submissions are consistently worth acting on. Transactions produce variable results, depend on PDM attention that can’t be planned, and don’t improve when the partner gets better. The partners whose co-sell pipeline is growing quarter over quarter are not the ones closing the most individual transactions. They are the ones who have built a motion — PO submissions that consistently reflect real account intelligence and real stakeholder engagement, AO profile positioning that consistently attracts the right referrals.
Co-sell compounds when both motions are fed correctly
The AWS partner program is genuinely powerful. The PDM network, the account intelligence AWS holds, the AO referral flow, the MAP funding infrastructure, the Marketplace transaction layer — these create real acceleration for partners who bring the right input to each motion.
What most partners are missing is not access to the program. They have the access. What they’re missing is the upstream work that makes the program work in both directions: AO competency positioning that makes AWS want to route relevant accounts to them, and PO submission quality that comes from genuine stakeholder relationships and real account intelligence rather than a filtered list.
That is the motion that compounds. Credibility builds because the submissions are consistently actionable. Referrals increase because the competency profile is consistently well-matched. Stakeholder relationships deepen because the outreach that produces them is grounded in research, not hope. And the PDM — even a new one who doesn’t know the partner yet — receives enough specific, genuine account intelligence in the first few submissions to decide this partner is worth investing in.