The AWS Foundational Technical Review (FTR) is the gateway to ISV Accelerate, co-sell priority access, and the Qualified Software badge. Most ISVs fail it the first time — not because their product isn't ready, but because the process itself is poorly understood.
Grnmrk guides you through every step: gap analysis, evidence documentation, ACE pipeline prerequisites, and Partner Central submission. Our clients pass on the first submission.
Engagement runs 12–20 hours · $250/hr · Most clients complete in 3–6 weeks
The FTR isn't a checkbox. It's the credentialing event that moves you from a listing in the AWS catalog to a co-sell partner the field team actually routes deals to.
Signals to AWS buyers and field reps that your product has been reviewed and validated against AWS architectural and security standards. It shows up on your Marketplace listing and in Partner Finder.
ISV Accelerate is the co-sell program. Without passing FTR, you can't enroll. With it, AWS field reps can formally co-sell your product alongside AWS services and earn credit for attaching you.
FTR completion signals to your PDM and the broader AWS field that you're a credible, investment-worthy partner — dramatically increasing the likelihood they route opportunities your way.
FTR status opens the door to Migration Acceleration Program funding, Market Development Funds, and POC credits that AWS makes available to credentialed ISV partners.
Most FTR failures come from documentation gaps, missed prerequisites, or submitting before the ACE pipeline is properly staged. We eliminate all three.
Most FTR engagements run 12–20 hours with a total elapsed timeline of 3–6 weeks depending on your current readiness.
Scope is defined after a free discovery call. No surprises, no bloat.
Not all FTR checklists are the same. AWS uses different evaluation criteria for SaaS, AMI, Container, and Professional Services products. We identify the correct checklist for your delivery model, map your current architecture and security posture against it, and flag every gap before you waste time on the wrong review track.
We work through each checklist requirement with your technical team — identifying what evidence already exists, what needs to be documented, and what gaps require actual remediation before submission. We prioritize by submission risk, not alphabetical order, so you close the highest-risk items first.
AWS requires a minimum of 10 active or closed opportunities in ACE before you can submit an FTR. This catches most ISVs off guard. We assess your current ACE pipeline, submit or clean up existing opportunities to meet the threshold, and ensure the submissions are properly structured to satisfy the prerequisite — running this track in parallel with technical prep.
AWS reviewers are evaluating documentation, not just intent. We assemble your full evidence package — screenshots, architecture diagrams, security policy excerpts, and written responses — formatted to match what reviewers actually look for. We've seen enough failed submissions to know what "good enough" doesn't pass.
We manage the full Partner Central submission — entering all required information, attaching evidence, and coordinating with your AWS PDM to flag the review for prioritization. If AWS comes back with clarifying questions or remediation requests, we manage the response and keep the review moving forward without bottlenecking your team.
Not every ISV is in the right position to start FTR. Here's how to know.
Not ready for FTR yet? Our Managed Services and Strategy Consulting can get you there.
What the self-serve path actually 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, not as a blocker | Frequently missed until submission attempt |
| Gap Analysis | ✓ Prioritized by submission risk | Manual checklist review — no prioritization |
| Evidence Documentation | ✓ Reviewer-ready package | Often incomplete or incorrectly formatted |
| Partner Central Submission | ✓ Fully managed | Requires significant internal time to navigate |
| PDM Coordination | ✓ Proactive — not reactive | Usually ad hoc and delayed |
| First-Submission Pass Rate | ✓ Strong — most clients pass first try | Industry average requires multiple attempts |
| Total Elapsed Time | 3–6 weeks | 3–6 months (commonly) |
What exactly is the AWS Foundational Technical Review?
The FTR is an AWS-led evaluation of your product's architecture, security posture, and operational practices. AWS reviews your submission against a defined checklist — which varies by delivery model (SaaS, AMI, Container) — and grants approval once requirements are met. Passing unlocks the Qualified Software badge and ISV Accelerate enrollment eligibility.
Do I need 10 ACE opportunities before I submit?
Yes. AWS requires at least 10 active or closed opportunities in ACE (AWS Customer Engagements) as a prerequisite to FTR submission. This is one of the most commonly missed requirements for ISVs attempting FTR on their own. We address this as a parallel workstream from day one.
What AWS tier do I need to be at before starting FTR?
You need to be enrolled in the AWS Partner Network at the Registered tier at minimum, but most ISVs starting FTR are at or working toward the Select tier. FTR is a requirement for the Qualified Software designation, which is also needed for ISV Accelerate enrollment regardless of tier.
What's the difference between FTR and the Well-Architected Review?
The FTR is a mandatory partner credentialing review that evaluates your product against a security and architecture checklist. The Well-Architected Review (WAR) is a customer-facing service partners use to assess and improve customer workloads — and it's a co-sell motion in its own right. They're complementary, not interchangeable.
What happens if AWS sends back remediation requests?
We manage all reviewer communication. If AWS asks for additional evidence, clarification, or remediation, we coordinate the response and resubmission without creating internal bottlenecks. This is standard for first-time submissions — we build buffer for it in the timeline.
Can I start FTR prep while also building my Marketplace listing?
Yes, and it often makes sense to run them in parallel since both require similar product readiness. If you need support on both tracks, our Strategy Consulting engagement can cover Marketplace GTM and FTR prep as a combined scope.
How much does FTR preparation with Grnmrk cost?
We bill at $250/hr with most FTR engagements running 12–20 hours — typically $3,000–$5,000 total. Scope and estimate are confirmed after a free discovery call. No retainer required; this is a fixed-scope project engagement.
What do I need to have ready before we start?
Access to Partner Central, a technical contact on your side who can address architecture and security questions, and a rough sense of your current ACE pipeline status. We handle everything else from there.
30 minutes. We'll review your current AWS partner status, assess your FTR readiness, and give you a clear scope and timeline — whether or not you work with us.