FTR is the gateway to SaaS Co-sell Benefit, transactable Marketplace listings, and the AWS Qualified Software badge. Most ISVs fail the first attempt, not because their product is not ready, but because the process is poorly understood.
We run the full engagement: gap analysis, evidence documentation, ACE prerequisites, and Partner Central submission. Our clients pass on the first submission.
12 to 20 hours · 3 to 6 weeks · $250/hrFTR moves you from a listing in the AWS catalog to a co-sell partner the field team routes deals to.
Signals to buyers and field reps that your product meets AWS architectural and security standards. Appears on your Marketplace listing and in Partner Finder.
FTR is the prerequisite for SaaS Co-sell Benefit enrollment. Without it, AWS field reps cannot formally co-sell your product alongside AWS services.
Transactable Marketplace listings require a passed FTR. It is also a prerequisite for private offers and CPPO channel programs.
FTR status opens access to Migration Acceleration Program funding, Market Development Funds, and POC credits AWS makes available to credentialed ISVs.
Most FTR failures come from documentation gaps, missed ACE prerequisites, or submitting before the pipeline is staged. We eliminate all three.
Most engagements run 12 to 20 hours over 3 to 6 weeks. Scope confirmed after a free discovery call.
AWS uses different checklists for SaaS, AMI, Container, and Professional Services products. We identify the right track, map your current posture against it, and flag every gap before you waste time on the wrong review track.
We work through each requirement with your technical team, identify what evidence exists, what needs documenting, and what gaps require remediation. We prioritize by submission risk so you close high-risk items first.
AWS requires 10 active or closed opportunities in ACE before you can submit an FTR. This catches most ISVs off guard. We audit your pipeline, clean up or submit opportunities to hit the threshold, and run this track in parallel with technical prep.
AWS reviewers evaluate documentation, not intent. We assemble your full evidence package: screenshots, architecture diagrams, security policy excerpts, and written responses, formatted to match what reviewers look for.
We manage the full submission in Partner Central and coordinate with your PDM to flag the review for prioritization. If AWS returns clarifying questions, we handle the response and keep the review moving without bottlenecking your team.
Not every ISV is positioned to start FTR. Here is how to know.
Not ready yet? Our Managed Operations and Strategy Consulting engagements can get you there.
What the self-serve path looks like versus what we do.
| Grnmrk-Guided | DIY / Internal | |
|---|---|---|
| Checklist Selection | ✓ Correct track identified upfront | Often misidentified, costs weeks |
| ACE Prerequisite | ✓ Managed in parallel | Frequently missed until submission |
| Gap Analysis | ✓ Prioritized by submission risk | Manual, no prioritization |
| Evidence Package | ✓ Reviewer-ready format | Often incomplete or mis-formatted |
| Partner Central Submission | ✓ Fully managed | Significant internal time required |
| PDM Coordination | ✓ Proactive | Usually ad hoc and delayed |
| First-Submission Pass Rate | ✓ 100% across client engagements | Industry average requires multiple attempts |
| Total Elapsed Time | 3 to 6 weeks | 3 to 6 months (common) |
What is the AWS Foundational Technical Review?
FTR is an AWS evaluation of your product's architecture, security posture, and operational practices against a defined checklist. Checklist criteria vary by delivery model: SaaS, AMI, or Container. Passing unlocks the Qualified Software badge and SaaS Co-sell Benefit eligibility.
Do I need 10 ACE opportunities before submitting?
Yes. AWS requires at least 10 active or closed opportunities in ACE as a prerequisite. This is the most commonly missed requirement for ISVs attempting FTR without support. We address it as a parallel workstream from day one.
What AWS tier do I need before starting FTR?
Registered tier at minimum, though most ISVs starting FTR are at or working toward Select. The Qualified Software designation, required for SaaS Co-sell Benefit, is available regardless of tier once FTR is passed.
What is the difference between FTR and a Well-Architected Review?
FTR is a mandatory partner credentialing review that evaluates your product against a security and architecture checklist. A Well-Architected Review is a customer-facing service partners run to assess and improve customer workloads. Complementary, not interchangeable.
What happens if AWS sends back remediation requests?
We manage all reviewer communication. If AWS asks for additional evidence or remediation, we coordinate the response and resubmission without creating internal bottlenecks. We build buffer for this in the standard timeline.
Can I run FTR prep alongside my Marketplace listing build?
Yes, and it often makes sense since both require similar product readiness. If you need support on both, our AWS Marketplace engagement can cover Marketplace GTM and FTR prep as a combined scope.
How much does FTR preparation cost?
We bill at $250/hr. Most engagements run 12 to 20 hours, typically $3,000 to $5,000 total. Scope and estimate are confirmed after a free discovery call. No retainer required.
What do I need to have ready before we start?
Access to Partner Central, a technical contact who can address architecture and security questions, and a sense of your current ACE pipeline status. We handle everything else.
30 minutes. We will review your AWS partner status, assess your FTR readiness, and give you a clear scope and timeline.