The AWS Software Path for CROs: What Each Stage Does for Your Pipeline

By Fractivo · November 9, 2026 · 11 min read

AWS can add a route to market alongside the ones you already sell through. It gives you a buying channel many of your customers already use, access to budget they have already committed to AWS, and AWS sellers who already cover many of your target accounts. However, how much of that you can use depends on where your company sits on the AWS Software Path.

Whoever runs your AWS partnership, whether that is a full-time hire, someone doing it part-time or a fractional resource, will usually report progress in AWS program terms. This guide translates each stage into what it means for pipeline, forecast and the investment it takes, for CROs and the people who run their AWS partnership. For the program detail, see our guide to the AWS Software Path in 2026.

The bottom line

• Getting your product approved by AWS pays back first. That is because it covers most of the work needed to sell through AWS Marketplace, which speeds up procurement for customers who already buy through AWS and lets them pay from committed AWS budget where their agreement allows.
• Register deals with AWS from week one. ACE is AWS’s deal registration system. Your team logs an opportunity there so AWS knows about it and can decide whether to help. AWS counts what you log over the last 12 months, so every month you wait pushes back the date you qualify for its co-sell programs.
• Treat ISV Accelerate as a pipeline quota. ISV Accelerate is AWS’s co-sell program. Once you are in, AWS sellers can find you more easily and earn incentives for helping close your deals through AWS Marketplace. To get in, you need 15 qualified deals and 5 live customers logged with AWS in the last 12 months.
• Treat AWS referrals as best case. AWS sellers can refer deals to you only after you reach ACE eligibility, which takes 10 logged deals approved by AWS, and they decide when to engage. Forecast the deals your own team sources.

The AWS terms in this post

• ACE: AWS’s deal registration system. Your team logs opportunities there so AWS knows about them and can decide whether to help.
• ACE eligible: the point where AWS sellers can start referring deals to you, once AWS has approved 10 of your logged deals in the last 12 months.
• Validated: AWS has approved your product. Most of the work overlaps with getting listed on AWS Marketplace.
• Differentiated: you hold an AWS Competency, AWS’s stamp that you are proven in an industry or use case.
• ISV Accelerate: AWS’s co-sell program. Members are easier for AWS sellers to find, and those sellers earn incentives for helping close members’ deals through AWS Marketplace.
• Marketplace private offer: a custom-priced deal your customer buys through AWS Marketplace and pays on their AWS bill.
• For Visibility Only (FVO): a deal logged so AWS knows about it, without asking for help. It does not count toward ISV Accelerate.

What each stage does for your pipeline

AWS’s Software Path has four stages. We add two milestones that sit on top of them, because that is where AWS sellers start to get involved.

Where the effort goes

The heavy lifts are in the middle. Validated takes engineering capacity, and Differentiated takes customer references. Both pay back. However, both also need a named owner and a target date, or they slip behind the product roadmap and the current quarter.

The later stages depend on your pipeline. ACE eligibility and ISV Accelerate are counts of deals registered with AWS. For example, your partner manager, an agent or software that syncs your CRM with ACE might do the registering. The deals still come from your sales pipeline, so reps need to flag the opportunities where AWS is relevant and keep deal details current. Without sales leadership behind it, these stages stall.

AWS lists the benefits on its Specializations and ISV Accelerate pages, and the approval requirements in its Partner Central guide.

Forecasting the AWS motion

AWS-referred deals take time. AWS sellers can only refer deals to you once you reach ACE eligibility, which takes 10 of your own deals registered with AWS and approved in a trailing 12 months. Even so, AWS sellers decide which partners to bring into their accounts and when.

In our experience, year-one AWS revenue comes from deals your own team sources and closes through AWS Marketplace. Then AWS referrals and AWS seller involvement build from there. Therefore, forecast the first, and treat the second as best case until it shows up consistently.

The simplest way to set this up is to split the AWS motion into what your team controls and what AWS decides.

First, put the left column in your operating plan with owners and dates. Then keep the right column out of commit until it has delivered for two or three consecutive quarters.

AWS says the same about its own sellers: a complete, specific deal record improves the odds of an AWS seller getting involved, and does not guarantee it (AWS co-sell engagement). In other words, meeting a program requirement makes you eligible, and AWS still decides how it engages on each deal.

Run it like a quota

AWS’s later milestones are deal counts over a trailing 12 months. Broken down by month, they become a pace your sales managers can inspect in the weekly pipeline review.

• ACE eligibility: 10 logged deals approved by AWS, or about one a month.
• ISV Accelerate, qualified deals: 15 logged with AWS, excluding FVO, or one to two a month.
• ISV Accelerate, live customers: 5 deals live on AWS through ACE or Marketplace private offers, excluding FVO, or one roughly every 10 weeks.
• ISV Accelerate, revenue: at least USD 2,000 in AWS-recognized revenue when you enroll.

For most sales teams the volume is modest. However, the harder part is keeping it steady. The counts roll, so deals registered more than 12 months ago drop off. As a result, a strong quarter followed by a quiet one can leave you below the threshold a year later.

How AWS counts a deal

AWS’s definitions differ from your CRM’s in ways that move these numbers.

A live deal means the customer is using the product on AWS. AWS counts an opportunity as launched once billing or usage begins. Your CRM, by contrast, counts it at signature. The gap is your time to go live, and a deal signed late in the 12-month window may miss the count.

Awareness-only registrations do not count. In ACE, reps can flag a deal For Visibility Only (FVO), which tells AWS about it without asking for co-sell help. AWS leaves these out of the ISV Accelerate counts. Therefore, check how many of your registrations carry that flag.

A qualified deal means the customer has confirmed the opportunity. AWS expects you to have confirmed the need, the requirements and the decision-makers with the customer. If the deal would not make your own pipeline review, it should not be in the count.

The QBR slide

These metrics fit on one slide and show whether the AWS motion is on track:

1. Software Path stage and approval renewal date. AWS’s product approval lasts two years, so plan the renewal ahead of the deadline.
2. AWS-approved deal registrations, trailing 12 months, against the 10 needed for ACE eligibility.
3. Qualified deals registered with AWS, excluding FVO, trailing 12 months, against the 15 ISV Accelerate requires.
4. Live deals or Marketplace private offers, trailing 12 months, against the 5 ISV Accelerate requires.
5. Pipeline that can close through AWS Marketplace, the line that shows whether the motion is producing revenue.

The first four track program progress. The fifth, however, is the one your board will ask about. Our post on where AWS revenue starts covers how to track AWS seller involvement and win rates alongside it.

Where AWS motions lose quarters

We see the same patterns across the software companies we work with. Each one costs at least a quarter, and each one is avoidable.

Product approval waits on engineering. AWS returns a decision in minutes. The prep, a Marketplace listing, proof the product runs on AWS and usage tracking, competes with the roadmap. As a result, without an engineering owner and a date, it slips every sprint.

Deals never leave the CRM. Teams hold off registering deals with AWS until they feel ready, and the 12-month clock runs without them. In fact, you can start registering the week you join.

Every deal is registered as awareness-only. It feels low-risk. However, it keeps your ISV Accelerate count at zero.

Time to go live is left out of the plan. Deals sign at the end of the window, customers go live the next quarter, and you miss the live-deal threshold by one or two.

The Competency is picked for the logo. A Competency outside the segments where you already win is hard to evidence and adds little pipeline. Instead, pick the one your buyers will recognize, and bring sales in early to secure references.

AWS referrals are built into the plan too early. Referrals only become possible after ACE eligibility. Counting on them in year one sets up a miss the program did not cause.

Fractivo’s take

If we were running revenue at a software company starting on the Software Path, this is the order we would work in:

1. This month: start logging every qualifying deal in ACE, and name an engineering owner and a target date for AWS product approval.
2. Next quarter: get the Marketplace listing live and the product approved, so customers who buy through AWS can buy you that way.
3. The two or three quarters after that: build to 10 AWS-approved deals for ACE eligibility, and pick the Competency that matches the segments where you already win.
4. Then: apply for ISV Accelerate once your pace supports 15 qualified deals and 5 live customers a year.

Each step feeds the next. First, Marketplace and product approval give customers a way to buy through AWS. Next, the deals you log build toward ACE eligibility and ISV Accelerate. Finally, the customers you win become the references a Competency needs.

One view we hold firmly: run the AWS motion as a revenue program, with a quarterly target and an owner who reports into revenue. In our experience, when it sits as a side project it stalls at Validated.

How Fractivo helps

Fractivo is a fractional alliance team for software companies that want AWS to show up in the number. We have helped launch more than 40 ISVs on AWS, register more than 200 AWS co-sell opportunities and unlock more than USD 12 million in AWS Marketplace revenue.

We take the program work off your team so your reps can stay on selling:

• Validated: we scope the AWS approval, get your Marketplace listing and usage tracking live, and manage the review to approval. Your engineering team provides the technical evidence.
• ACE eligible and ISV Accelerate: we set up how deals get logged with AWS, whether by reps, a partner manager or a CRM integration, make sure the details meet AWS’s bar for approval, track the counts against each threshold and prepare the ISV Accelerate application. Your sales team brings the deals.
• Differentiated: we run the Competency from gap analysis to award, including evidence, submission and reviewer follow-up. Your customers and sales team provide the references.

The Docebo case study shows two Competencies taken from gap analysis to approval in 12 weeks. The Defang case study shows a startup moving from a passive Marketplace listing to an active co-sell motion. Both of our core services, AWS Alliance Leadership and AWS Competency Readiness and Validation, are sold as private offers on AWS Marketplace, so you can buy them through your AWS account.

Your next step

Know where you stand before your next QBR. Choose the next step that suits you:

• Request the CRO’s AWS Readiness Checklist. It lists what has to be in place at each stage, with an owner for each, so one review with whoever owns your AWS partnership shows where you are and what is holding back the next stage.
• Book a 30-minute Software Path review. We walk through your current stage, your gap to referrals and ISV Accelerate, and what to fix first, so you leave with a plan to take to your leadership team.

FAQ

What is the AWS Software Path?

It is AWS’s partner track for companies that sell their own software running on or integrated with AWS. AWS tracks four stages in Partner Central: Enrolled, Confirmed, Validated once AWS approves the product, and Differentiated once the company earns an AWS Competency or other Specialization.

Which stage pays back fastest?

Validated. Getting the product approved by AWS takes most of the same work as selling through AWS Marketplace, which opens a faster buying route for customers who already purchase through AWS.

What does it take to qualify for ISV Accelerate?

AWS asks for at least 15 qualified deals and 5 live deals (through ACE or AWS Marketplace private offers) registered in the past 12 months, excluding awareness-only (FVO) registrations. It also requires an AWS-approved product, a generally available Marketplace listing, ACE eligibility, an Amazon Payee Central account, a completed Co-Selling with AWS course and at least USD 2,000 in AWS-recognized revenue at enrollment.

When does AWS count a deal as live?

When billing or usage for the product begins on AWS. That can be weeks after the deal is closed-won in your CRM.

Should we forecast AWS-referred deals?

We advise against it until they arrive consistently. Each stage makes AWS involvement possible. However, AWS decides how it engages on each deal.

Sources

• Request FTR validation in AWS Partner Central
• AWS Foundational Technical Review, updated November 5, 2026
• AWS ISV Accelerate Program, updated November 5, 2026
• AWS Specializations, updated November 5, 2026
• AWS Partner Central Sales Guide: co-sell engagement
• AWS Partner Central API Reference: LifeCycle, for opportunity stage definitions
• AWS Partner Analytics FAQs, for For Visibility Only opportunities
• APN Software Path Partner Handbook and ACE Leads and Opportunities guide (AWS Partner Central sign-in required)