$500K is the upper-tier Generative AI Accelerator award — granted to roughly 10% of accepted cohort startups, typically Series-A AI companies with tier-1 VC backing and demonstrated commercial trajectory. It is also reachable through two structurally distinct paths: Y Combinator AI cohort stacks combining standard credits with accelerator follow-on, and large-MAP migration engagements layered with Portfolio and Bedrock POC. The honest framing: $500K is rare outside the competitive accelerator path. This page walks through who actually gets it, the tranching mechanics across the six-month accelerator window, and what $500K realistically funds for an AI startup running at production scale.
$300K is the median Generative AI Accelerator award; $500K is the upper-tier exception. The difference is not just $200K of credits — it reflects a different selection process, a different recipient profile, and a different commitment expectation from AWS.
The Generative AI Accelerator cohort selection produces a distribution of awards. Looking across the public cohorts, roughly 15% of selected startups receive the $200K floor, 30% land at $250K–$300K, 40% receive the $300K median, 10% receive the upper-tier $400K–$500K, and 5% reach the $500K–$1M ceiling. The $500K tier is the practical boundary between "median accepted startup" and "cohort highlight."
The $500K recipient profile is consistent across cohorts. The pattern: Series-A AI native company (typically $10M–$30M raised in the priced round), tier-1 VC backing (a16z, Sequoia, Founders Fund, Benchmark, Index Ventures, Greylock), founders with prior credibility (PhD from a notable ML lab, former senior ML role at OpenAI / Anthropic / DeepMind / Google Brain / Meta AI, or prior exit), demonstrated user traction at scale ($100K+ MRR or 50K+ active users), and an AI use case where the unit economics translate clearly into substantial Bedrock consumption (10M+ tokens/day projected within 12 months).
AWS's economic logic for the $500K tier is straightforward. The Generative AI Accelerator is a customer-acquisition mechanism for Bedrock. The standout cohort startups are the ones AWS most wants to retain as Bedrock customers post-credits, both for the direct consumption revenue and for the reference-customer value. The $500K award is calibrated to materially shift the inference-provider decision for companies that have the demonstrated trajectory to become substantial Bedrock customers within 24–36 months. A $300K award shifts the decision; a $500K award removes financial friction entirely while signaling AWS's commitment to the relationship.
The $500K tier is rare outside the accelerator path for a related reason. Standard Activate-family stacking (Portfolio + Build for Startups + Bedrock POC) caps at roughly $150K — three layers, each with its own credit ceiling. Adding MAP credits at substantial migration scope can push the position to $200K–$300K. To reach $500K through pure stacking without the accelerator layer requires either (a) an exceptionally large migration scope ($1M+ total migration cost, returning $300K+ of MAP credits at the Migrate-phase 50% rate), (b) substantial Build for AWS partner-labor funding in a vertical where AWS has active budgets (FinTech compliance, HealthTech HIPAA, MediaTech transcoding), or (c) some combination of multiple stacked layers including all of the above. The pure-stack $500K path exists but is operationally heavier than the accelerator path.
Each path has its own selection mechanic, eligibility profile, and timeline. The accelerator upper-tier is the cleanest if you fit the profile. The YC AI cohort stack is the standard pattern for Y Combinator alumni with AI batches. The large-migration stack is the route for migration-heavy companies that are not AI-first.
Across CloudRoute's routed engagements with companies that have reached the $500K credit position, the distribution is roughly: 55% via the upper-tier Generative AI Accelerator path, 25% via the YC AI cohort stack pattern, 20% via the large-migration stack. The accelerator path dominates because it is the cleanest single-mechanism path; the other two require multiple parallel applications and longer wall-clock timelines.
The mechanism: direct acceptance into the Generative AI Accelerator at the upper-cohort tier. Same application process as the median $300K tier — application form at aws.amazon.com/startups/programs/generative-ai, screening on eligibility, 30-minute interview with a Bedrock team member, final selection at the quarterly cohort meeting. The upper-tier designation is made by AWS during selection, not by the applicant.
Eligibility filter for the upper-tier vs the median: the eligibility criteria for entering the cohort are identical — AI-first product, pre-Series-B funding, Bedrock commitment, 90-day onboarding willingness. The differentiator for the upper-tier award is the selection committee's assessment of the company's trajectory. The factors that push selection toward the upper-tier: tier-1 VC backing (institutional signal), demonstrated user traction at meaningful scale (commercial signal), AI use case with clear unit economics translating to substantial projected Bedrock consumption (Bedrock-commitment signal), and team credibility (execution signal).
Tranching: the $500K upper-tier award is structured across three tranches matched to the accelerator milestones. First tranche of approximately $165K issues at cohort acceptance. Second tranche of approximately $165K issues at the 60-day milestone — Bedrock POC running in production with measurable workload. Third tranche of approximately $165K issues at the 120-day milestone — clear commercial outcome attached to the Bedrock workload (user adoption, revenue lift, cost reduction, or a similar concrete metric).
Timeline: from application to first-tranche credits, 60–90 days for accepted startups. Full $500K landing in account by month 6 of the accelerator window. Application windows are quarterly; the next cohort review is the next opportunity if you miss the current window.
Risk profile: high variance. The application is competitive (roughly 5% cohort acceptance rate); within the accepted set, the upper-tier designation is competitive again (roughly 10% of accepted startups). The cumulative probability of reaching the upper-tier award through a single application is approximately 0.5%. The path is the cleanest in mechanic but the most selective in outcome.
The mechanism: the Y Combinator AI batches (W24, S24, W25 in particular) had elevated acceptance rates into the Generative AI Accelerator follow-on. The composition is: standing Activate Founders ($5K, via YC partnership), partner-filed Activate Portfolio ($100K once incorporated and funded by YC), Bedrock POC ($25K), plus the Generative AI Accelerator follow-on at $300K–$500K depending on cohort tier. Total: $430K–$630K, with $500K being a common middle position.
Eligibility profile: Y Combinator alumni from AI-heavy batches, post-Demo Day with the standard $500K YC SAFE plus typically a priced seed round of $2M–$10M closed. The YC alumnus signal carries meaningful weight in the Generative AI Accelerator selection — AWS values the institutional filter and the cohort-level commercial trajectory data.
Why the YC cohort stack reaches $500K with median rather than upper-tier accelerator acceptance: the standing Activate base ($5K Founders + $100K Portfolio + $25K Bedrock POC = $130K) plus a median $300K accelerator award reaches $430K. With an additional $25K Build for Startups layer for a distinct AI-adjacent project (a data pipeline, an evaluation harness, an internal tooling layer), the position reaches $455K. With AWS account-team-driven additional credit on top (sometimes $50K of discretionary additional credits for promising YC AI startups based on AWS account team advocacy), the position can reach $500K–$550K. The path does not require upper-tier accelerator acceptance — it stacks the median accelerator with the standard YC-eligible Activate layers to reach the $500K position.
Timeline: Activate Founders + Portfolio + Bedrock POC arrive within 21 days of partner filing. The Generative AI Accelerator timeline is the binding constraint — 60–90 days to first tranche, 6 months for full release. The full $500K position is in-account by month 6–7 of the engagement.
Risk profile: moderate. The Activate layers approve at the standard ~80% rate per layer; the YC institutional signal pushes accelerator acceptance probability above the base 5%. Across CloudRoute's routed YC AI cohort engagements, accelerator acceptance rates have been approximately 15%–20% — meaningfully higher than the global cohort average. The composite path probability to $500K is roughly 8%–12%.
The mechanism: substantial migration scope where MAP credits cover the bulk of the position. The composition is Activate Portfolio ($100K), Build for Startups ($25K for a discrete non-overlapping project), Bedrock POC ($25K), and MAP credits at $300K–$350K from a $1M+ total migration cost. Total: $450K–$500K.
Eligibility profile: Series-A late-stage or Series-B startup migrating off substantial source-platform spend — typically Heroku Enterprise at $20K+/month, GCP at $30K+/month, Azure at $30K+/month, or on-prem datacenters at $25K+/month. Total migration cost projection of $1M+ including engineering labor, partner-labor, parallel-run cost, and data transfer. Post-migration AWS spend projection at $25K+/month.
Why this path reaches $500K but the standard MAP path tops at $200K–$300K: MAP credit issuance is calibrated to the migration scope. The $200K page tier reflects $400K–$500K total migration cost (Mobilize at ~$100K tagged consumption, Migrate at ~$150K tagged consumption, summing to ~$75K–$125K of MAP credits). The $500K tier reflects substantially larger migration — Mobilize at $300K+ tagged consumption and Migrate at $500K+ tagged consumption, returning $200K–$300K of MAP credits. The size threshold is real: $1M total migration cost is qualitatively different from $400K total migration cost in MAP credit issuance.
Timeline: Portfolio + Build for Startups + Bedrock POC arrive within 18–21 days of partner filing. MAP credits trickle across the migration phases — Assess ($25K) at week 4, Mobilize ($75K) at week 14, Migrate ($200K) at week 28. Full $500K position is in-account by month 7 of the engagement. The MAP credit window roughly matches the accelerator path window despite the different mechanic.
Risk profile: lower variance than the accelerator path but operationally heavier. Activate layers approve at ~80%/layer; MAP credit issuance is tagging-discipline-dependent rather than acceptance-rate-dependent. The dominant risk is forfeiting MAP credits to tagging drift across a long migration — a poorly-tagged Migrate phase can forfeit $50K–$100K. The cumulative probability of reaching the full $500K is roughly 50%–60% on this path with disciplined tagging, lower without.
AWS does not publish the upper-tier selection criteria. Looking across publicly-disclosed upper-tier recipients and CloudRoute's routed engagements where the upper-tier was awarded, a consistent set of signals emerges. These are not requirements — they are correlations from the observable cohort data.
The upper-tier designation is made by the Generative AI Accelerator selection committee at the cohort meeting. The committee includes Bedrock product leadership, AWS Startup team leadership, and sometimes guest reviewers from the broader AI infrastructure organization. The committee reviews each accepted startup's materials and assigns the award tier — floor, lower-median, median, upper-median, or ceiling — based on the projected commercial trajectory and the strategic value to AWS of the Bedrock relationship.
The signals that consistently appear in upper-tier selections cluster into four categories: institutional signal (tier-1 VC backing as a validation proxy), traction signal (demonstrated user adoption or revenue at scale), commitment signal (concrete Bedrock production usage already underway or unambiguously committed), and team signal (founder credibility from prior roles or technical achievements). Companies that present strongly across three or four of these categories tend to land in the upper tier; companies that present strongly in one or two land in the median tier.
The upper-tier recipients consistently have tier-1 VC backing. The relevant VCs in 2026 are a16z, Sequoia, Founders Fund, Benchmark, Index Ventures, Greylock, Accel, Khosla Ventures, and a handful of others with consistent AI portfolio presence. The signal is two-fold: the VC has independently validated the company through their diligence process, and the VC will support follow-on investment if the AI use case scales. AWS treats the tier-1 VC presence as institutional validation that reduces the company-specific risk in the credit decision.
Notable: the VC signal is necessary but not sufficient. Many tier-1-backed AI startups land at the median rather than the upper tier — the VC backing is a baseline that opens the upper-tier conversation, not a guarantee of it. The combination of VC backing plus the other signals is what drives upper-tier designation.
The upper-tier recipients have moved past the "prototype with promising metrics" stage. The traction signal is typically one of: $100K+ MRR demonstrated for at least one quarter; 50K+ weekly active users in a consumer or prosumer product; substantial enterprise contracts signed and live (typically 5+ enterprise customers each at $50K+ ARR); or a comparable concrete metric demonstrating that the product has crossed early-stage validation.
The traction signal is what differentiates the upper-tier from the median. The median tier includes many credible pre-revenue or low-revenue AI startups with strong teams and clear use cases. The upper-tier requires the additional evidence that the use case has translated into observable adoption — which then translates into the projected Bedrock consumption that justifies the larger award.
The upper-tier recipients commonly have Bedrock production usage already underway at the time of application. This is not a requirement — startups currently using OpenAI or Anthropic API can apply with a credible migration plan. But upper-tier designation is more often awarded to startups with concrete Bedrock usage demonstrating that the commitment is real and operational.
For startups currently on OpenAI or Anthropic API, the path to upper-tier eligibility is typically: file a partner-led Bedrock POC ($10K–$50K) before the accelerator application, run the POC for 60–90 days to establish concrete Bedrock production usage, then apply to the accelerator with the POC data as evidence. CloudRoute partners often advise this sequence for AI-native startups planning to apply to upper tiers.
The upper-tier recipients consistently have founders with technical credibility. The common backgrounds: PhD from a notable ML lab (Stanford AI Lab, MIT CSAIL, CMU MLD, Berkeley BAIR, UToronto/Vector Institute), former senior ML role at OpenAI / Anthropic / DeepMind / Google Brain / Meta AI / xAI, prior exits or notable open-source contributions in the AI space. The team signal is read as an indicator of execution capability — the founders can translate the AI use case into production reality.
The team signal is the most subjective of the four categories and the least determinative. Many strong founders without classical credentials land in the upper tier based on traction and institutional signals alone. The team signal is best understood as one of four contributing factors rather than a gatekeeping requirement.
The upper-tier $500K does not arrive as a single credit balance. It arrives in three tranches matched to the accelerator program milestones. Understanding the tranching mechanic avoids the founder pattern of planning consumption against $500K from day one.
AWS designed the tranched issuance to align credit deployment with milestone completion. The economic logic is clear: front-loading the full $500K at acceptance would mean companies that abandon the accelerator commitments still keep the full balance. Tranching ties credit issuance to demonstrated progress — Bedrock production usage at 60 days, commercial outcome at 120 days. The mechanic protects AWS's investment while still subsidizing the work that completes.
For the company, the tranching shape determines when consumption can ramp. The first tranche ($165K) is available from day 1 of cohort acceptance. The Bedrock POC and supporting infrastructure can be funded through the first tranche through approximately month 4 of the accelerator window at a sustained $40K/month consumption rate. The second tranche ($165K) arrives at the 60-day milestone, replenishing the balance and supporting continued consumption through month 8. The third tranche ($165K) arrives at the 120-day milestone, supporting consumption through month 12 and beyond.
When issued: at cohort acceptance, typically within 2 weeks of the cohort meeting. The credit balance appears in the AWS billing console as a promotional credit balance with a 24-month validity window.
What it funds: the first 4–5 months of accelerator-window consumption at typical AI-startup scale. For a company running Bedrock at $25K/month plus supporting infrastructure at $15K/month, the first tranche funds approximately 4 months of consumption.
The milestone expectation: the company is expected to begin the Bedrock production deployment immediately. The 60-day milestone (Bedrock-in-production) is the gating event for the second tranche; companies that delay starting the Bedrock work risk missing the milestone and forfeiting the second tranche.
When issued: at completion of the 60-day milestone. AWS's Bedrock team reviews the company's Bedrock deployment status; if Bedrock is running in production with a measurable workload, the second tranche issues within 2 weeks of milestone verification.
What "Bedrock in production" means: at minimum, Bedrock inference calls are serving real user traffic (not just internal evaluation). The workload size is not the primary metric — the criticality is. A small workload serving real customers at low volume passes the milestone; an extensive internal evaluation suite serving no customers does not.
The failure mode: companies that treat the 60-day milestone as a soft deadline often miss it. The Bedrock team verification is not lenient — production traffic is the bar. Companies that miss the 60-day milestone forfeit the second tranche entirely, capping the credit position at the first $165K rather than receiving $330K. CloudRoute partners advise that the Bedrock POC begin within 2 weeks of acceptance to provide buffer for the 60-day verification.
When issued: at completion of the 120-day milestone. AWS's Generative AI Accelerator team reviews the company's commercial outcome documentation; if a clear commercial outcome is attached to the Bedrock workload, the third tranche issues within 2 weeks of milestone verification.
What "commercial outcome" means: a documented metric showing that the Bedrock workload has produced commercial value. Acceptable metrics include user adoption (a Bedrock-powered feature reaching N users), revenue lift (a Bedrock workload contributing to documented revenue), cost reduction (Bedrock replacing previously paid inference at documented savings), or product expansion (Bedrock enabling a new product line at documented adoption). The metric must be verifiable by the AWS team — vague trajectory claims do not pass.
The strategic implication: the third tranche is the easiest milestone to miss for early-stage startups. The 120-day window is short for some commercial outcomes to materialize. Companies that plan for the third tranche typically scope the Bedrock workload to an existing high-value flow rather than a new flow that needs to grow into commercial value within the window. The pattern: take an existing flow that has demonstrated user adoption, move its inference to Bedrock, document the cost reduction or user-adoption continuity, and submit that as the commercial outcome.
The Y Combinator AI batches (W24, S24, W25) produced a distinct pattern in the Generative AI Accelerator data: elevated acceptance rates, faster wall-clock timelines, and consistent reach to the $500K position through stacked composition rather than upper-tier accelerator acceptance.
YC's value to AWS in the accelerator decision is multi-faceted. YC alumni carry institutional validation comparable to tier-1 VC backing — the YC partnership has been a reliable filter for high-growth startups since 2005. AWS's Generative AI Accelerator team has internal data showing that YC AI batches produced disproportionate share of long-term Bedrock customers post-accelerator. The acceptance bias is the rational result.
The stack composition for YC AI alumni differs from the standard pattern in two ways. First, the standing Activate Founders ($5K) is available immediately on incorporation and YC funding — there is no application barrier for the YC layer. Second, the partner-filed Portfolio application is typically approved at the $100K tier rather than the smaller tiers, because YC alumni present strong post-Demo Day fundraise trajectories that justify the higher Portfolio tier.
The composite stack reaches $500K through layering rather than through a single $500K award. The standing Activate Founders ($5K) plus partner-filed Portfolio ($100K) plus Bedrock POC ($25K) plus the Generative AI Accelerator follow-on at median $300K reaches $430K. Adding a Build for Startups layer ($25K) for a discrete project — a data pipeline, an evaluation harness, an internal tooling layer — pushes the position to $455K. Account-team-driven additional credit (sometimes $25K–$50K of discretionary credit for promising YC AI startups, based on AWS account team advocacy and YC partnership memos) can push the position to $480K–$525K. The full $500K is the practical sum of the layered approach.
The W24 batch coincided with the formal launch of the Generative AI Accelerator program; AWS and YC negotiated an informal commitment to evaluate YC AI batch alumni at elevated priority. The W24 batch produced multiple Generative AI Accelerator acceptances out of approximately 25 AI-focused W24 startups — a meaningfully higher rate than the global ~5% cohort average.
The S24 and W25 batches continued the pattern but with slightly normalized acceptance rates as the accelerator program broadened its non-YC sourcing. The current 2026 cohort selection treats YC AI batch alumni as a strong positive signal but no longer as an effectively-guaranteed accept.
For founders in YC AI batches considering the accelerator, the practical implication: file the accelerator application as soon as the cohort window opens post-Demo Day. The YC alumnus signal is strongest in the first cohort window following Demo Day; the signal weakens as the company moves further into Series-A territory and the institutional differentiation narrows.
YC alumni typically execute the stack composition in the following sequence. Week 1 post-Demo Day — partner match through CloudRoute or direct partner relationship. Week 2 — partner files Activate Portfolio ACE record. Week 3 — Portfolio approved, $100K in account. Week 4 — partner files Build for Startups and Bedrock POC applications. Week 5 — Build and Bedrock POC approved, additional $50K in account. Week 6 — submit Generative AI Accelerator application to AWS. Week 10–14 — accelerator selection process. Week 14–16 — cohort acceptance, first tranche of $165K issued. Total $315K in account by week 16. Subsequent tranches at week 24 (second $165K) and week 32 (third $165K), bringing the total to $480K–$500K depending on Build for Startups tier and any account-team-driven additional credit.
The sequence is operationally clean because the Activate layers can be filed in parallel with the accelerator application — they do not conflict, and they front-load the credit position while the accelerator selection runs. By the time the accelerator first tranche issues, the company is already operating against $130K of Activate-stack credit; the accelerator credits extend rather than initiate the AWS engagement.
For migration-heavy companies, $500K is reachable through scale rather than through accelerator selection. The MAP layer dominates the composition at this scale, with Portfolio, Build for Startups, and Bedrock POC contributing the remaining ~$150K. The path is the standard $200K-tier mechanism applied to a substantially larger migration scope.
The size threshold for the $500K migration path is qualitative. Roughly: total migration cost projection of $1M or more, source platform spend at $25K/month or more, post-migration AWS spend projection at $25K/month or more, and a migration timeline of 9–12 months end-to-end. These are not strict criteria — they are the consistent profile across CloudRoute's routed engagements that reached the $500K credit position through the migration path.
The MAP composition at this scale reflects substantial Mobilize and Migrate phases. Mobilize at $300K+ tagged consumption returns approximately $75K of MAP credits (25% rate). Migrate at $500K+ tagged consumption returns approximately $250K of MAP credits (50% rate). Plus the MAP Assess phase contributing approximately $25K at completion. Total MAP: approximately $350K. Layered with Portfolio ($100K), Build for Startups ($25K), and Bedrock POC ($25K), the composition reaches approximately $500K.
The substantial migration projects that reach this tier consistently fit one of three source-platform profiles. Heroku Enterprise at $25K+/month bills, where the company has hit Heroku Postgres scale limits or unfavorable Heroku unit economics. GCP at $30K+/month bills, where the company is migrating off Vertex AI or GKE for regulatory, vendor-consolidation, or pricing reasons. On-prem datacenters at $25K+/month operational cost, where the company is exiting datacenter contracts in favor of public cloud. Azure migrations at this scale are less common in CloudRoute's routing data but follow the same composition pattern.
The tagging discipline that determines MAP credit issuance becomes operationally critical at the $500K scale. At the $200K tier, sloppy tagging forfeits $30K–$50K. At the $500K tier, sloppy tagging can forfeit $100K–$150K because the absolute MAP phase consumption is larger. The same percentage drift translates into larger absolute credit loss.
CloudRoute Migration Competency Partners filing $500K-tier MAP engagements install the tagging convention before the first Mobilize resource is created. AWS Config rules enforce tag compliance; Service Catalog products bake tags into provisioning templates; Terraform modules include tags as required parameters; pull request review checks for tag compliance. The discipline is operational, not technical — the partner enforces convention rather than fixing problems retrospectively.
The full $500K migration path lands in approximately 7 months — Portfolio + Build + Bedrock POC within 18–21 days, MAP Assess at week 4, MAP Mobilize at week 14, MAP Migrate at week 28. This roughly matches the accelerator path timeline (full $500K landing in account by month 6–7 across the three tranches).
The timeline match is not coincidental. AWS calibrated both programs to issue credits across the same approximate 6-month window. The economic logic is that 6 months is sufficient for a startup to demonstrate substantial AWS commitment without requiring the multi-year commitments that EDP contracts handle separately. For founders, the implication: the choice between the accelerator path and the migration path is determined by company profile (AI-native vs migration-heavy), not by timeline preference — both paths take roughly the same wall-clock time to full release.
The $500K credit position is enough to fund a fully production-scale AI startup's AWS consumption for 18–24 months. The distribution skews toward Bedrock inference and supporting infrastructure, with the proportions reflecting the AI-native usage pattern rather than typical SaaS.
For an AI-native startup operating at typical Series-A production scale, the monthly AWS burn falls in the $20K–$25K range. Bedrock inference is the dominant line item, supporting infrastructure (vector search, compute orchestration, storage) absorbs the rest. The $500K credit position covers 18–24 months of this sustained burn rate.
For startups at smaller scale (pre-traction or early-traction Series-A), the burn might be $10K–$15K/month, and the $500K position covers 30+ months. For startups at larger scale (late Series-A approaching Series-B), the burn might be $35K+/month, and the $500K position covers 12–14 months before credits begin to deplete.
Not every AI startup reaches $500K. The selection mechanics across all three paths filter aggressively. Here is the honest framing of who realistically reaches the position, drawn from CloudRoute's routed engagement data and publicly-disclosed cohort data.
The $500K position is structurally rare. Across CloudRoute's 2025 and early 2026 routing data, approximately 4% of routed AI-native engagements reached the $500K credit position; approximately 2% of routed migration-heavy engagements reached $500K through the MAP path. The combined position represents the upper boundary of what is realistic through stacked Activate-family and accelerator mechanisms.
For founders evaluating whether to pursue the $500K position, the honest framing is: assess fit against the recipient profile before committing to the application timeline. The accelerator path requires the four signal categories (institutional, traction, commitment, team) at strong levels — startups missing two or more categories typically land at the $300K median or below. The migration path requires the substantial migration scope ($1M+) and operational tagging discipline — startups below the migration threshold cap at the $200K–$300K tier regardless of effort.
Each path has its own mechanic, eligibility profile, and risk shape.
| Variable | Upper-tier Accelerator | YC AI cohort stack | Large-migration stack |
|---|---|---|---|
| Mechanism | Single competitive selection (cohort + tier) | Stacked Activate layers + median accelerator | Stacked Activate layers + MAP-heavy migration |
| Eligibility filter | Series-A AI; tier-1 VCs; demonstrated traction; team signal | YC AI batch alumnus; standard Activate eligibility | Series-A late / Series-B; $1M+ migration scope |
| Composite probability | ~0.5% (5% cohort × 10% upper-tier) | ~8%–12% (elevated YC acceptance + standard stack) | ~50%–60% (with disciplined MAP tagging) |
| Time-to-balance (full $500K) | ~6 months across three tranches | ~7 months (Activate in 21 days; accelerator across 6 months) | ~7 months (Activate in 21 days; MAP across phases) |
| Partner role | Advisory only on accelerator; partner-filed for Activate base if YC | Files Activate ACE records; advises accelerator app | Files Portfolio ACE + runs MAP engagement (partner-led) |
| Primary risk | Selection rejection or median-tier designation | Accelerator rejection (Activate layers still land) | Tagging drift forfeiting MAP credits |
| Best for | AI-native Series-A with all four signals strong | YC AI batch alumni post-Demo Day | Migration-heavy Series-B with substantial source-platform spend |
| Composition shape | $500K single award, three tranches | $5K + $100K + $25K + $25K + $300K = ~$455K (median accelerator); to $500K with Build or account-team additional | $100K + $25K + $25K + ~$350K MAP = ~$500K |
Situation: AI-native legal-tech, Y Combinator W24 batch alumni, post-Demo Day priced Series-A at $18M raised, a16z + Sequoia co-led. Product is a Bedrock-powered legal research and document analysis platform serving mid-market law firms. Current state at inquiry: ~$120K MRR demonstrated for two quarters, 22 mid-market law firm customers each at $4K–$8K MRR, OpenAI GPT-4 inference at the application layer with a stated commitment to migrate to Bedrock for cost and data-residency reasons. 18 engineers, founding team includes a former Anthropic research engineer and a former Stripe staff engineer. Currently on AWS for storage and compute but minimal Bedrock usage at the time of inquiry.
What CloudRoute did: Routed within 17 hours to a CloudRoute partner with Bedrock production-deployment experience and prior YC alumni engagement history. Discovery call covered the four-path stacking strategy. Activate Founders ($5K) already in account from YC partnership. Partner filed Activate Portfolio ACE on day 3 ($100K against the post-migration Bedrock + supporting infrastructure consumption projection of $22K/month). Partner filed Bedrock POC ($25K) on day 5 to fund the OpenAI-to-Bedrock migration POC. Partner filed Build for Startups ($25K) on day 6 for a discrete evaluation harness project that did not overlap with the Portfolio scope. All Activate layers approved and in account by day 22 — total $155K. Partner advised on Generative AI Accelerator application scoping and projected Bedrock consumption section. Founder submitted accelerator application on day 25; accelerator cohort acceptance arrived day 87 with upper-tier designation ($500K cohort award, tranched). First tranche of $165K issued at acceptance. Bedrock POC migrated 60% of OpenAI inference traffic to Claude Sonnet on Bedrock by day 60 of the accelerator window; second tranche of $165K issued at the 60-day milestone. Bedrock-powered document analysis flow demonstrated 23% cost reduction vs OpenAI baseline; commercial outcome documented and submitted; third tranche of $165K issued at the 120-day milestone.
Outcome: Total credit position: approximately $650K. Activate base ($5K + $100K + $25K + $25K = $155K) plus Generative AI Accelerator upper-tier ($165K + $165K + $165K = $495K) summing to $650K across the engagement window. The combined position covers approximately 24–30 months of sustained Bedrock + supporting infrastructure consumption at the company's projected scale. Migration off OpenAI completed by month 4 of the accelerator window; full Bedrock primacy by month 6. EDP conversation opened with AWS account team in month 5 for a multi-year committed-spend contract beginning when the credit balance starts depleting (projected month 18 of the accelerator window).
engagement window: ~6 months · founder time: ~30 hours total · credits secured: ~$650K (Activate base $155K + Accelerator upper-tier $495K) · cost to customer: $0
CloudRoute routes AI-native Series-A and YC AI cohort startups to partners filing the multi-layer Activate stack and advising on Generative AI Accelerator application scoping. For migration-heavy companies, partners file Portfolio and run the MAP engagement that reaches the $500K position through migration scale.