In June 2026, AWS changed how every co-sell deal gets treated. Every opportunity submitted through ACE in AWS Partner Central now gets qualified in real time by an agent, assigned an AWS Opportunity Quality Score out of 100, and matched to one of three co-sell motions: AWS Field-engaged, Agent-engaged, or Partner-led. The score determines how much of AWS’s attention your deal earns. AWS sellers see it too.
Most of the early commentary on this launch is about avoiding a terrible score. That advice is easy. Write a real description, fill in the fields, done. The harder question is what happens in the middle of the range, because that is where most legitimate deals will land. A score around 50 means your submission is clean. It takes more than a clean submission to make AWS lean in.
We have been working a real client opportunity through this zone since launch. What follows is the approach we built for the climb toward 75, where AWS field engagement starts to become realistic.
How the AWS Opportunity Quality Score works
Building on the Partner Central agents AWS released in March 2026, every ACE opportunity now gets scored the moment you submit it and rescored continuously as you update it. AWS describes the score as a data-driven indicator of how well your submission aligns with what drives successful co-selling, and it feeds directly into which motion you land in. A strong score can move an Agent-engaged opportunity toward direct AWS sales team collaboration.
The commercial stakes are real. Canalys research cited by AWS found 65% of partners report higher close rates and 54% see larger deals when co-selling with AWS. In other words, the score is now the gate to that engagement.
What an AWS Opportunity Quality Score of 50 means
The agent’s feedback gets more demanding as you climb. At the low end it flags defects: descriptions written from the partner’s point of view, missing fields, boilerplate next steps. In fact, any competent partner ops team can fix those in an afternoon.
At 50, the feedback changes character. On our client’s opportunity, an AI-first software company early in its AWS partner journey, the mid-range feedback asked for four things: sharper evaluation criteria, a narrower AWS ask, named competitors, and a structured customer next step with a contact and a date attached.
Every item on that list is a question about whether the deal is real, competitive, and moving. The agent at 50 behaves like a skeptical sales manager in a pipeline review, and it takes actual work with the customer to satisfy it.
What we changed
Giving the agent deal substance
Evaluation criteria came straight from the buyer. The material already existed in our discovery notes. The customer’s leadership needed cost, timeline, level of effort, and available funding offsets before they could approve the project. Written in the customer’s voice, those became the evaluation criteria on the record: reach the outcome within budget, fit the internal approval window, keep the effort at a level the team can absorb, and apply offsets that reduce net cost. All we did was translate what the buyer had already told us into the structure the agent scores.
We narrowed the AWS ask to one thing. We replaced a general request for AWS support with a single ask tied to a named AWS function and anchored to a scheduled milestone. A seller reading it knows exactly what to do and by when. There will be more asks later, and the record can carry them once the score recalculates. Several vague asks stacked together read as no ask at all.
The competitor field got real substance. The agent’s rubric appears to want at least one proper noun here. If naming vendors feels commercially sensitive, ask the customer’s sales team who they actually see in deals. Reps almost always know. Where a name is genuinely off the table, category-level naming paired with the specific market pressure the customer faces still gives the agent something real to work with. This is the field partners most often leave blank out of caution, and in our experience it carries meaningful points.
Tightening the record
Next steps became a staged sequence. A single upcoming meeting reads as a deal with one heartbeat. We structured the record as a sequence: a dated technical session with a named customer contact, the deliverable that session feeds, and the target close date behind it. As a result, momentum is legible to the agent the same way it is legible to a seller.
Hygiene fields got a cleanup. Tag every AWS service the customer’s platform actually runs. Set industry and use-case tags correctly. Make sure estimated revenue reflects what you can defend in a conversation. And assign the seller who will actually action the agent’s recommendations, because insights route to the person on the record. If that person never logs in, the feedback loop dies and the score sits still.
One ceiling turned out to be structural. Certain constraints are about the deal’s maturity. In our client’s case, the customer has yet to enroll in APN, and we suspect the score has a ceiling until enrollment happens and the AWS footprint becomes verifiable. If your score plateaus despite clean fields and real substance, look for a structural gate and sequence it into the plan. Fighting the rubric wastes cycles you could spend on the deal.
The bigger shift
We have written before about the thesis we took away from AWS Partner Summit Toronto: AWS is moving from presence-based partnering to measured, machine-readable partner impact. The AWS Opportunity Quality Score is the clearest expression of that shift so far. Who you know at AWS matters less every quarter. What earns engagement now is the data you submit, evaluated by an agent, on every deal, in real time.
The mid-range is where that shift bites. Plenty of partners will clean up their submissions, settle at 50, and wonder why AWS field sellers still stay quiet. The partners who treat the agent’s mid-range feedback as a qualification framework and feed it genuine deal substance will find the path to Field-engaged open.
Raising your AWS Opportunity Quality Score: a pre-submit checklist
Check that the opportunity includes a description that opens with the customer’s business situation and desired outcome, evaluation criteria written in the customer’s voice, one narrow AWS ask a specific team can action by a specific date, at least one named or category-level competitor with real competitive context, tagged AWS services and Partner Solutions, the correct sales team member assigned, and staged next steps with named contacts and dates showing the deal’s momentum.
Then read what the agent says and act on it. It is telling you exactly what AWS wants to see.
Fractivo helps ISVs accelerate AWS Competency designations, Marketplace listings, and co-sell motions. If your pipeline is full of opportunities stuck in the middle of the score range, we should talk.