Stage 1 — Launch

AWS Foundational Technical Review

FTR is the gateway to ISV Accelerate — and it trips up more companies than any other step in the AWS partner journey. We help you pass it on the first attempt.

The Problem

FTR Is Harder Than It Looks

The AWS Foundational Technical Review sounds like a standard technical audit. In practice, it requires your product to demonstrate specific architectural patterns across five Well-Architected pillars — and AWS reviewers look at evidence, not promises. Companies that approach FTR without structured preparation consistently fail or spend months in remediation cycles.

The hidden cost isn't just the time lost. While you're stuck in FTR limbo, you're ineligible for ISV Accelerate benefits — including co-sell support, deal registration, and funding programs that your competitors with FTR completed are already using.

Why It Matters

What FTR Unlocks

ISV Accelerate Eligibility

FTR completion is required to enroll in ISV Accelerate — the program that gives you access to dedicated AWS co-sell resources and deal support.

AWS Seller Credibility

AWS account executives are far more willing to co-sell products that have passed FTR. It signals architectural maturity and reduces their risk in recommending you.

Program Tier Progression

FTR is a prerequisite for advancing through AWS partner tiers. Without it, your program status is capped and your access to AWS resources is limited.

Common Mistakes

What Goes Wrong Without Expert Help

Attempting FTR without a gap analysis

Submitting before you understand which pillars you'll fail on guarantees rejection. AWS reviewers flag all gaps simultaneously — making it hard to prioritize remediation.

Conflating "good architecture" with "FTR-compliant architecture"

Your product might be well-built but missing specific AWS service patterns that FTR requires as evidence — like AWS Config rules, CloudTrail logging, or specific IAM practices.

Treating FTR as a one-time event

FTR requirements evolve. Companies that pass and forget often find themselves out of compliance when AWS updates the Well-Architected requirements for Marketplace products.

Not involving engineering early enough

FTR remediation often requires architectural changes that take time to implement and test. Engaging engineering after the business has already committed to a timeline creates pressure and shortcuts.

Our Methodology

How We Guide You Through FTR

1

FTR Readiness Assessment

We run a structured evaluation of your product architecture against current AWS FTR requirements across all five Well-Architected pillars — security, reliability, operational excellence, performance, and cost optimization.

2

Gap Analysis Report

We document every gap with specific remediation guidance, effort estimates, and priority ranking — so engineering knows exactly what to fix and in what order.

3

Remediation Roadmap

We create a phased remediation plan with clear milestones, assigned owners, and a realistic timeline to FTR submission — mapped to your engineering team's capacity.

4

Remediation Support

We work alongside your engineering team during remediation — answering questions, reviewing implementations, and validating that changes satisfy FTR evidence requirements.

5

Evidence Package Preparation

We prepare the evidence package AWS reviewers need — screenshots, configuration exports, policy documents, and architectural diagrams — in the format that minimizes back-and-forth.

6

Submission & Review Management

We submit the FTR on your behalf and manage the AWS reviewer communication through approval — responding to questions and providing clarifications to keep the process moving.

Deliverables

What You Receive

FTR readiness assessment across all five Well-Architected pillars
Detailed gap analysis report with remediation guidance
Prioritized remediation roadmap with timelines
Engineering guidance during remediation
Complete FTR evidence package
FTR submission and review management
FTR approval and ISV Accelerate enrollment guidance
Outcomes

What Success Looks Like

FTR Approved on First Submission

A clean FTR approval with no major reviewer findings — achieved efficiently, without wasted cycles.

ISV Accelerate Enrollment

Full eligibility for ISV Accelerate benefits, co-sell resources, and AWS deal support programs.

Architectural Confidence

A product architecture aligned to AWS best practices — with documentation your team can use for future reviews.

FAQ

Common Questions

It varies significantly based on your current architectural state. Companies with modern, cloud-native architectures can complete remediation in 4–8 weeks. Legacy or on-premises-derived products with significant gaps may take 3–6 months. Our gap analysis gives you a realistic estimate before you commit to a timeline.
Rarely. Most FTR gaps are about missing controls, logging configurations, and operational practices — not fundamental architectural redesign. The most common remediation items involve enabling AWS Config rules, CloudTrail, GuardDuty, and establishing proper IAM boundaries. Major architectural changes are uncommon.
Yes, you can resubmit after addressing the reviewer's findings. There's no limit on resubmissions. However, repeated failures can slow down your relationship with your AWS account team. Our process is specifically designed to avoid this by resolving all gaps before submission.
No. FTR is an AWS-specific architectural review against the AWS Well-Architected Framework. SOC 2 is a third-party security and availability audit. They cover some overlapping areas (particularly security), but they are separate programs with different evidence requirements and reviewers. Having SOC 2 helps with FTR preparation but doesn't substitute for it.

Ready to Pass FTR and Unlock ISV Accelerate?

Start with a FTR readiness assessment. We'll tell you exactly where you stand and what remediation will take.