The AWS Opportunity Quality Score: How to Climb From 50 to 75

By Fractivo · · 9 min read

On June 16, 2026, AWS changed how every co-sell deal gets treated. Every opportunity submitted through ACE in AWS Partner Central now gets qualified by an agent the moment you submit it. The agent assigns an AWS Opportunity Quality Score out of 100 and matches the deal to one of three co-sell motions. Better still, AWS sellers see the same score you do.

Most early commentary focused on avoiding a bad score. That part is relatively easy. The harder question is what happens in the middle of the range, where most legitimate deals land. Typically, a score around 50 means your submission is clean. Getting AWS to lean in takes more than that.

This guide covers what AWS shipped, how the score works according to AWS, and the approach Fractivo uses with clients to move opportunities from the 50s toward 75.

What AWS shipped in June 2026

The launch built on the Partner Central agents AWS introduced in March 2026. According to the AWS announcement, it added three things.

First, partners can submit marketing and sales leads into Partner Central and get propensity insights back. In addition, the system scores how likely each lead is to convert. It also flags which leads qualify for programs, funding and specific sales motions.

Second, every opportunity submitted through ACE (APN Customer Engagements, where you register co-sell deals) gets real-time agent support. You can describe a deal in plain language, upload meeting notes or a proposal, or clone an existing opportunity. The agent then fills in fields, checks details and suggests next steps.

Third, every opportunity gets an AWS Opportunity Quality Score and a co-sell motion.

How the AWS Opportunity Quality Score works

AWS explains the score in its Partner Central Sales Guide. In short, the score measures the quality and completeness of your submission. It appears as a number out of 100, with a trend showing whether it is improving, declining or unchanged. Any edit to a scored field triggers a rescore, and a rescore can move the number down as well as up.

The four scored components

AWS names four components:

  1. Customer Business Problem Completeness. This is the primary driver. It covers the customer’s specific situation, why they must act now, how they will evaluate and decide, quantified outcomes, named contacts and the competitive landscape.
  2. Next Steps. A concrete action with a deliverable, a date, an owner and a named customer contact.
  3. Partner Primary Need from AWS. A precise ask, such as Technical Consultation, Architectural Validation, Pricing Assistance or Business Presentation. AWS notes that “Deal Support” on its own counts as general support and earns no credit.
  4. Solution and AWS Products. Your registered solution, plus the AWS services the customer is adopting.

However, AWS keeps the weights confidential. It also says it will update the model as it collects more data, so expect the score to change over time.

The three co-sell motions

Each opportunity lands in one motion:

  • AWS Field-engaged. The opportunity is matched with an AWS sales team for direct collaboration.
  • Agent-engaged. The agent qualifies the deal and recommends how to strengthen it. As it improves, it can move to Field-engaged.
  • Partner-led. You own and drive the deal with agent support. No AWS seller is assigned, and AWS accepts your updates immediately.

What the AWS Opportunity Quality Score does and doesn’t decide

The AWS Opportunity Quality Score is the part you control. However, AWS assigns the motion based on the score and on the opportunity’s strategic importance. AWS determines strategic importance from the partner, the customer and the products involved. As a result, two opportunities with the same score can land in different motions.

AWS is direct about this: a higher score “increases the likelihood of AWS Field engagement but does not guarantee it.” AWS sellers prioritize by motion first, then by score within the motion. In other words, AWS decides which deals its sellers work. Your job is to give every deal the strongest possible case.

The stakes are real. AWS cites a 2024 Canalys report finding that 65% of partners saw higher close rates and 54% saw larger deals from co-selling with AWS.

Why the AWS Opportunity Quality Score matters to sellers

Fractivo’s founder spent close to six years inside AWS, on the ISV team and in the startup segment. So we read this launch the way an AWS seller does. Which deals get my time?

For years, co-sell quality lived in the heads of AWS sellers and a few alliance leads. You knew a deal was strong when the right person told you so. That made co-sell slow and relationship-dependent. It also left good deals sitting in the queue, because nobody had written them up in a form AWS could act on.

Today, the AWS Opportunity Quality Score makes that judgment visible and consistent. AWS sellers have limited time to chase vague submissions. A strong score signals the deal is real and ready, so it becomes easier for a seller to justify the time. Of course, relationships still matter. Now, though, they need a deal record the system can read behind them.

Where partners lose points

The gaps we see in partner pipelines are consistent:

  • Next steps are blank, or the same sentence appears on every opportunity.
  • Estimated revenue is a placeholder from three months ago.
  • The description talks about the partner’s product instead of the customer’s problem.
  • AWS services go untagged, or the record lists the services the partner’s product runs on instead of the ones the customer is adopting.
  • The wrong person sits on the record, so the agent’s recommendations go to someone who never reads them.

Fortunately, these are hygiene problems, and they are fixable in an afternoon. Fixing them usually gets a deal to around 50. After that, the agent asks harder questions.

What an AWS Opportunity Quality Score of 50 means

At the low end, the agent flags defects: missing fields, partner-centric descriptions and boilerplate next steps. At 50, the feedback changes character.

For example, we worked a client opportunity through this zone after launch. The client is an AI-first software company early in its AWS partner journey. At 50, the agent 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.

In effect, each of those is a question about whether the deal is real, competitive and moving. At this stage, the agent behaves like a skeptical sales manager in a pipeline review. Satisfying it takes real work with the customer.

How we moved the record toward 75

AWS publishes no threshold for field engagement. In our experience, though, the 70s are where it starts to look realistic. Here is what we changed.

Giving the agent deal substance

Evaluation criteria came from the buyer. Conveniently, the material already sat in our discovery notes. The customer’s leadership needed cost, timeline, effort and available funding offsets before approving the project. We wrote those as evaluation criteria in the customer’s voice. That matches what AWS asks for under the purchase and evaluation process.

We narrowed the AWS ask to one thing. We replaced a general request for support with a single ask tied to a named AWS function and a scheduled milestone. As a result, a seller reading it knows what to do and by when. By contrast, several vague asks stacked together read as no ask at all.

The competitor field got real content. AWS lists the competitive landscape as part of the primary component, and that includes in-house options and the status quo. If naming vendors feels sensitive, ask the customer’s team who they actually see in deals. Where a name is off the table, a category plus the specific market pressure still gives the agent something to work with.

Tightening the record

Next steps became a dated sequence. On its own, a single upcoming meeting reads as a deal with one heartbeat. So we wrote a dated technical session with a named customer contact, the deliverable it feeds, and the target close date behind it. AWS’s guidance matches this: one or two dated actions, each with your owner and a customer contact.

Hygiene fields got a cleanup. First, we tagged the AWS services the customer is adopting, set industry and use case correctly, and made sure estimated revenue was defensible. We also assigned the seller who will act on the agent’s recommendations.

One ceiling turned out to be structural. Sometimes, limits reflect the deal’s maturity. In our client’s case, we suspect the score plateaued until more of the customer’s AWS footprint became verifiable. If your score stalls despite clean fields and real substance, look for a structural gate and plan around it. Fighting the rubric wastes time you could spend on the deal.

Use the agent as a coaching loop

Real-time rescoring changes the cadence of co-sell. It used to be a register-and-wait motion. Now the score moves as your data moves. Therefore, partners who revisit and strengthen records every week will steadily improve their deals’ standing.

In practice, treat the agent as a coach. Submit, read the feedback, improve the record and resubmit. Also, AWS warns that trimming a description can lower the score, because the details it credited disappear. Add detail when you edit.

To bring this into your team’s daily work, connect the agents to your CRM through the MCP server AWS provides. The guidance then shows up where your sellers already work.

Pre-submit checklist

Before you submit, check that the opportunity includes:

  • A description that opens with the customer’s business situation, why they must act now, and the outcome they expect
  • Evaluation criteria in the customer’s voice, with baselines and targets where you know them
  • Named approver and champion at the customer
  • At least one named or category-level competitor, or the status quo
  • One specific AWS ask a named team can act on
  • Your registered solution and the AWS services the customer is adopting
  • The right sales team member on the record
  • One or two dated next steps, each with an owner and a customer contact

Finally, read what the agent says and act on it.

For the groundwork that makes these records possible, read Where AWS Revenue Starts: The Groundwork CROs Can’t Skip. For how co-sell fits your AWS Partner standing, see our guide to AWS Partner tiers in 2026.

FAQ

What is the AWS Opportunity Quality Score?

It is a score from 0 to 100 that AWS assigns to every co-sell opportunity submitted through ACE in AWS Partner Central. It measures the quality and completeness of the submission, and it influences which co-sell motion the deal receives.

Does a high score guarantee AWS will co-sell the deal?

No. AWS says a higher score increases the likelihood of field engagement but does not guarantee it. AWS also weighs the opportunity’s strategic importance, based on the partner, the customer and the products involved.

Can AWS sellers see my score?

Yes. AWS sellers see the same score and submission detail you do, in every motion. In turn, they prioritize by motion first, then by score.

What raises the AWS Opportunity Quality Score the most?

AWS names Customer Business Problem Completeness as the primary driver of the AWS Opportunity Quality Score. A specific description of the customer’s problem, urgency, decision process and competition does more than any other field.

Work with Fractivo

If your ACE records sit in the 50s, the fix usually comes down to giving the agent deal substance it can read. Fractivo reviews co-sell records before submission and helps teams build the habits that keep them current. Talk to us about your pipeline.

Sources

Related posts

All posts · Talk to Fractivo