There are seven distinct credit tracks across the AWS Activate, Bedrock POC, Build for Startups, MAP, and Generative AI Accelerator programs. Each has a different timeline — from 24 hours for self-serve Builders to 90 days for the Generative AI Accelerator cohort selection. This page is the single reference for what wall-clock to expect, what drives the spread within each track, and the hour-by-hour breakdown of a typical engagement.
Most published "AWS credit timeline" content collapses everything into a single number. The honest answer is that there are seven distinct tracks, each with its own application form, reviewer queue, and approval cadence. Knowing which track you are filing decides the timeline you should expect.
The tracks are not interchangeable. A founder filing $5K Founders self-serve and a founder filing $100K Portfolio partner-attested are interacting with completely different parts of AWS. The Founders self-serve track runs through an automated eligibility-check pipeline; the Portfolio track runs through a human partner-development manager (PDM) who reads the ACE record and writes a recommendation. These are different systems with different SLAs.
The seven tracks, in order of typical wall-clock from fastest to slowest, are: Activate Builders self-serve (24 hours), Activate Founders self-serve (3–7 days), partner-filed Founders (10–14 days), Activate Portfolio (11–18 days), Build for Startups (12–17 days), Bedrock POC (14–21 days), MAP Assess phase (14–21 days), and the Generative AI Accelerator (60–90 days). Each track produces a credit balance in a different way and is reviewed by a different team inside AWS.
Wall-clock: 24 hours from form submission to credit balance in account.
Mechanic: automated eligibility check. The form asks four questions (company name, URL, AWS account ID, brief description). The pipeline validates the email domain matches the company URL, runs a quick AWS account existence check, and issues the $1K credit balance within 24 hours. No human review.
What drives the spread: there is almost no spread on this track because there is no queue. Submissions filed at peak times (US business hours) can take up to 24 hours; submissions filed during low-traffic windows can land within 4–8 hours. The 24-hour figure is the documented SLA.
Wall-clock: 3–7 days from form submission to credit balance in account.
Mechanic: light human review. The Founders self-serve form is not fully automated — an AWS Activate reviewer (separate from the partner-development team) reads the application, verifies the company exists, and issues the $5K credit balance. The review is a sanity check rather than a discretionary judgment.
What drives the 4-day spread: reviewer queue assignment is the main variable. Applications filed on Monday tend to clear by Wednesday or Thursday; applications filed on Friday tend to clear by the following Tuesday or Wednesday because the weekend stalls the queue. Country/region also matters — US applications clear fastest because the reviewers cluster in US business hours.
Wall-clock: 10–14 days from partner ACE submission to credit balance in account.
Mechanic: the partner files an ACE record on your behalf. The PDM reviewer reads the record, verifies the company, confirms the partner's standing, and issues the credit. This is slower than self-serve Founders because the PDM queue runs slower than the Activate self-serve queue.
What drives the 4-day spread: partner ACE submission velocity (how fast the partner files the record after your discovery call), reviewer queue depth (varies week to week), and whether the partner asks clarifying questions before submission (faster) or submits and then handles clarifications during review (slower).
Wall-clock: 11–18 days from partner ACE submission to credit balance in account.
Mechanic: the partner files an ACE record requesting from the Portfolio pool. The PDM reviewer evaluates the use case, the projected AWS consumption, and the institutional vouch (either the VC has Portfolio Sub-Program access or the partner attestation substitutes). For Portfolio specifically, the reviewer also checks projected spend against industry benchmarks for the company's stage.
What drives the 7-day spread: existing AWS account consumption history (faster — the reviewer can verify the projected spend against actual usage), use-case clarity in the ACE record (faster — the reviewer doesn't have to write back for clarification), partner's ACE submission velocity (faster — the partner files on the same day rather than batching with other submissions), reviewer batch assignment timing (variable — some weeks have backed-up queues), and whether the company is institutionally funded with a recognizable VC (faster verification).
Wall-clock: 12–17 days from partner ACE submission to credit balance in account.
Mechanic: the partner files a Build for Startups ACE record describing a discrete, scoped project — not the company's general infrastructure. The PDM reviewer checks for use-case overlap with any Portfolio application filed by the same company, validates the project scope, and issues the $25K Build for Startups credit.
What drives the 5-day spread: the cross-application overlap check adds time — if the reviewer flags potential overlap with Portfolio, they may write back for clarification. Clear, distinct project scope speeds the timeline; vague or overlapping scope extends it. Filing Build for Startups simultaneously with Portfolio (rather than sequentially) is faster because the reviewer processes both records as a coordinated stack.
Wall-clock: 14–21 days from partner ACE submission to credit balance in account.
Mechanic: the partner files a Bedrock POC ACE record describing an AI use case, the chosen Bedrock model, an evaluation methodology, and a projected inference budget. The record routes to the Bedrock POC review queue, which is staffed by a smaller team than the general Portfolio queue — that staffing differential is the structural reason this track runs 3–7 days slower than Portfolio.
What drives the 7-day spread: the POC plan quality is the dominant factor. A POC plan with a concrete use case ("customer-support agent using Claude Sonnet 4 with N=500 weekly eval examples against a held-out test set") clears the queue in 14 days. A vague POC plan ("we want to use AI for some features") triggers reviewer clarifying questions and extends to 21 days. Bedrock POC plan revisions add 3–7 days when they happen mid-review.
Wall-clock: 14–21 days from partner-filed MAP record to Assess-phase credit availability.
Mechanic: the partner files a MAP engagement record under the Migration Acceleration Program. The Assess phase is the first of three phases (Assess → Mobilize → Migrate). The Assess-phase credits fund the migration sizing and planning work — typically $5K–$25K depending on migration scope.
What drives the 7-day spread: MAP records require an itemized source-environment inventory (what you are migrating from), a target AWS architecture (what you are migrating to), and a projected savings model. Complete inventories clear in 14 days; incomplete inventories trigger reviewer write-backs and extend to 21 days. The MAP team also runs slightly slower than the general Portfolio queue because they review migration scope in more detail.
Wall-clock: 60–90 days from application submission to first-tranche credit availability.
Mechanic: not a credit application — a competitive cohort selection. The Generative AI Accelerator runs ~50 startups per quarterly cohort globally. Application window is roughly 30 days. Selection is roughly 30–45 days after the window closes. Onboarding and first-tranche credit issuance is roughly 15 days after selection. Subsequent credit tranches issue across 6–12 months tied to program milestones (use of Bedrock, completion of mentorship modules, joint go-to-market work).
What drives the 30-day spread: cohort timing relative to when you apply. If you apply on day 1 of an application window, your wall-clock is 60–75 days. If you apply on day 28 of a 30-day window, your wall-clock is 30–35 days because most of the cohort review time has already elapsed in parallel with your application. The 60–90 day band reflects mid-window applications.
Every track has a 4–7 day spread inside its window. The spread is not random — it is driven by four reproducible factors that either compress or expand the wall-clock. Knowing which factors apply to your situation lets you predict whether your application lands at the fast end or the slow end of the band.
The Portfolio track illustrates this most clearly. The official 11–18 day window has a 7-day spread. The same partner filing for two different Series-A companies on the same Monday can see one approval land on day 11 and the other land on day 18, and the difference is entirely explained by the four factors below.
If your company has an existing AWS account with 6+ months of consumption history, the reviewer can verify your projected spend against your actual usage. This shortens the timeline by 2–3 days because the reviewer does not need to estimate plausibility from scratch.
New AWS accounts trigger an extra verification step — the reviewer wants to confirm the account belongs to the company described in the ACE record and that the projected spend is realistic for a company at the stated stage. This adds 2–3 days to the timeline.
The compression is most dramatic for Portfolio applications. A Series-A company already running at $4K/month of AWS consumption can land Portfolio in 11 days. A brand-new account asking for $100K of Portfolio credits typically lands in 16–18 days.
The ACE record's use-case description is the reviewer's primary signal. A clear paragraph that names the AWS services in volume, describes the workload concretely, and aligns with the company's public positioning clears the queue without reviewer write-backs.
A vague use-case description ("we use AWS for our infrastructure") triggers reviewer clarifying questions. Each write-back round adds 2–4 days. Most engagements with vague descriptions go through 1–2 write-back rounds before approval.
Partners who pre-check the use-case description with the founder before submission generally see 2–3 day faster approvals than partners who submit and handle clarifications during review.
The wall-clock starts when the partner submits the ACE record, not when you have the discovery call. A partner who files within 24 hours of receiving your inputs starts the clock immediately. A partner who batches submissions weekly adds up to 7 days to the wall-clock before the AWS queue even sees the record.
Partner ACE submission velocity is one of the routing criteria CloudRoute uses. Partners with high submission velocity get routed for time-sensitive engagements; partners with batched workflows route for engagements where the founder is comfortable with a slower wall-clock.
Partners with a high ACE approval rate (>70% historically) also tend to see slightly faster reviewer assignments because the PDM team prioritizes their queue. This shortens the timeline by an additional 1–2 days.
Reviewer queues run in batches. The PDM team processes ACE records in waves rather than continuously. The wave cadence varies week to week — typically 2–3 waves per week, with the heaviest wave clearing on Tuesdays and Wednesdays.
An ACE record submitted late Friday tends to wait for the following Tuesday's wave. An ACE record submitted Monday morning catches the same week's Wednesday wave. This timing differential alone accounts for 2–3 days of wall-clock variation.
There is no way to game the wave timing as an applicant — the reviewer queue is opaque to the partner and to the founder. The factor is real but it is essentially noise from your perspective.
A founder filing a $150K stack ($100K Portfolio + $25K Build for Startups + $25K Bedrock POC) does not see credits land on three separate days. The credits all land within the wall-clock of the slowest layer because that is when the engagement is considered complete.
The reality is more nuanced than that. Each ACE record is independently approved by the reviewer, and the credit balance does technically appear in the AWS billing console at three different moments. But for engagement-completion purposes — the moment when the founder treats the credits as "in hand" — the slowest layer drives the timeline.
For the $150K stack, the slowest layer is Bedrock POC at 14–21 days. Portfolio typically approves first (day 11–14), Build for Startups second (day 12–17), and Bedrock POC last (day 14–21). The full $150K is not considered locked-in until the Bedrock POC layer clears.
This matters for planning. A founder budgeting Bedrock POC credit utilization across a 60-day POC window needs to account for the Bedrock POC approval clock starting on day 14–21, not day 0. Most CloudRoute-routed engagements treat day 18 as the realistic planning anchor for the full $150K stack — by then, all three layers have typically cleared.
When a partner-filed Portfolio application is in flight (11–18 day wait), some founders file a self-serve $5K Founders application simultaneously. The $5K lands in 3–7 days while Portfolio processes. This provides experimentation budget during the wait. Note: Portfolio approval supersedes the $5K — once Portfolio lands, the $5K is technically still in the account but functionally moot because Portfolio covers the same use cases. Founders use the $5K window to start spinning up infrastructure during the Portfolio wait rather than waiting until day 18 with nothing.
A founder routed through CloudRoute for a Portfolio application sees the same sequence of events at roughly the same days. The 16-day mark is the median of the 11–18 day band — when the engagement lands at typical pace. Faster engagements (11 days) skip parts of this; slower engagements (18 days) add 2 days of write-back or reviewer queue wait.
This breakdown assumes a Series-A B2B SaaS company, US-East operations, partner with high ACE submission velocity, clear use case, existing AWS account with 6+ months of consumption history. Faster than this is rare; slower than this happens when one of the factors above is missing.
| Day | What happens | Who acts | Wall-clock note |
|---|---|---|---|
| Day 0 | Founder submits CloudRoute inquiry. 3 questions: company name, funding stage, AWS use case (one sentence). | Founder | 3 minutes form time |
| Day 1 | CloudRoute admin reviews inquiry, scores routing eligibility, matches to a vetted partner with Portfolio track record. Calendly link sent. | CloudRoute + Partner | Routing within 24 hours |
| Day 2 | Discovery call (30 minutes). Partner confirms eligibility, walks through what the Portfolio application contains, outlines the projected timeline. Founder decides to proceed. | Partner + Founder | 30 minutes founder time |
| Day 3–4 | Founder fills in the Portfolio worksheet: company info, AWS account ID, deck, use-case paragraph. Partner pre-checks the use-case description for clarity. | Founder + Partner | ~30 minutes founder time across both days |
| Day 5 | Partner files the ACE record on behalf of the founder. ACE submission marks the wall-clock start of the AWS queue. | Partner | Wall-clock starts here |
| Day 6–7 | ACE record sits in the queue. No action from any party. Reviewer batch assignment runs Tuesday/Wednesday for records filed Friday onward. | AWS queue | Queue wait |
| Day 8–10 | Reviewer (Partner Development Manager) is assigned the ACE record. They read the use case, verify the company, check the projected spend against benchmarks. No write-backs needed for a clear application. | AWS Reviewer | Active review |
| Day 11–13 | Reviewer issues the approval recommendation. Internal AWS processing applies the credit to the billing account. | AWS internal | Approval processing |
| Day 14–16 | Credit balance appears in the AWS billing console. Founder receives the AWS confirmation email. Engagement considered complete. | AWS | Credits in account |
The first three days of a CloudRoute-routed engagement happen at a faster cadence than most founders expect. Most of the founder's active work happens in this window — the rest of the 16-day timeline is largely waiting on the AWS queue.
Hour 0 — Founder submits the CloudRoute inquiry form. Three required fields: company name, funding stage, AWS use case in one sentence. Form submission time: 90 seconds.
Hour 0–4 — CloudRoute admin reviews the inquiry. Routing eligibility scoring runs through a checklist: institutional funding status, AWS-eligible use case, region match, stack alignment with available partner specializations. Most inquiries score within 4 hours of submission.
Hour 4–18 — Matched partner receives the routing notification. Partner reviews the inquiry, confirms availability for a discovery call, and sends a Calendly link to the founder. For high-velocity partners (the partners CloudRoute prioritizes for time-sensitive engagements), this happens within 4–8 hours of receiving the routing.
Hour 18–24 — Founder books the discovery call. Most founders book for the next business day; some book same-day if the partner has availability.
Hour 24–48 — Discovery call happens. 30 minutes. Partner confirms eligibility, explains the Portfolio application contents, outlines the timeline. Founder decides whether to proceed (~85% proceed at this point; the 15% who do not generally drop because they realized they want to wait for their next funding round or the stack is materially different from what the credits fund).
Hour 48–72 — Founder receives the Portfolio worksheet from the partner. Fills in company info, AWS account ID, deck, use-case paragraph. Time: 30 minutes. Partner reviews inputs for clarity before submission.
Day 3 onward — Partner submits the ACE record. The AWS queue wall-clock begins here. Founder's active involvement drops to roughly zero until the credits land 11–14 days later.
CloudRoute partners batch their ACE submissions when possible to avoid overlapping with their other PDM-attention requests. The typical pattern is: inquiry on Day 0, discovery on Day 2, founder paperwork on Days 3–4, ACE submission on Day 5. Partners with higher velocity file on Day 3–4. The 1–2 day difference moves the credit landing date from Day 16 to Day 14 — small but reproducible.
The wall-clock is structurally fixed by the reviewer queue, but founder-side and partner-side behaviors reproducibly extend or shorten it. Both lists below come from CloudRoute's routed-engagement data and partner-reported patterns.
Incomplete paperwork from the founder — adds 3–5 days. If the founder takes more than 48 hours to return the Portfolio worksheet, the partner waits. If the founder submits incomplete information (missing AWS account ID, missing deck, vague use-case paragraph), the partner asks for clarification before submitting. Each round of clarification adds 1–2 days.
Reviewer clarifying questions — adds 2–4 days. If the ACE record raises a clarification need (projected spend looks implausible, use case is unclear, institutional vouch is ambiguous), the reviewer writes back to the partner. The partner relays the question to the founder, the founder answers, the partner updates the record. Each write-back round adds 2–4 days.
Partner ACE submission delays — adds 1–3 days. If the partner batches submissions weekly rather than submitting same-day, your record waits in the partner's internal queue before reaching AWS. CloudRoute routes time-sensitive engagements to partners with high submission velocity to avoid this.
Bedrock POC plan revisions — adds 3–7 days. If the reviewer comes back asking for a more specific eval methodology or a revised model selection rationale, the partner and founder have to redraft the POC plan. This is the most common reason a Bedrock POC layer slips from 14 to 21 days.
Cross-application overlap concerns — adds 2–5 days. If the reviewer flags potential overlap between Portfolio and Build for Startups, they pause both applications while clarifying scope. Both end up landing later than they would have individually.
New AWS account verification — adds 2–3 days. Brand-new AWS accounts (no consumption history) get extra verification scrutiny. The reviewer confirms the account belongs to the company described in the ACE record and validates the projected spend against industry benchmarks rather than against actual historical usage.
Existing AWS account with consumption history — shortens by 2–3 days. The reviewer can verify projected spend against actual usage. Companies on AWS for 6+ months at $4K/month consumption clear Portfolio in 11–13 days rather than 16–18.
Partner with high ACE approval rate — shortens by 1–2 days. Partners with >70% historical ACE approval rates see slightly faster reviewer assignments. The PDM team prioritizes their queue because the records tend to be well-prepared.
Single-track application vs stacked — shortens by 2–4 days. Filing only Portfolio (not Portfolio + Build for Startups + Bedrock POC) avoids the cross-application overlap check and the slowest-layer effect. A single Portfolio application can land in 11 days; a $150K stack lands in 18–21 days because Bedrock POC drives the timeline.
Clear, concrete use-case description — shortens by 2–3 days. A use-case paragraph that names AWS services in volume and describes the workload concretely clears the queue without reviewer write-backs. Vague descriptions trigger write-backs and extend the timeline.
Institutionally funded with recognizable VC — shortens by 1–2 days. The reviewer's institutional verification step is faster when the VC is recognizable (tier-1 firms, well-documented funds). For lesser-known investors, the reviewer takes longer to verify; partner attestation helps but does not fully compensate.
Application filed Monday/Tuesday — shortens by 2–3 days vs Friday filings. The reviewer batch wave cadence favors Tuesday/Wednesday clearance. Filing early in the week catches the same-week wave; filing late in the week waits for the following week.
| Track | Wall-clock | Review mechanic | Spread driver | Stack-friendly? |
|---|---|---|---|---|
| Activate Builders (self-serve) | 24 hours | Automated eligibility check | Time-of-day at submission | No (single $1K pool) |
| Activate Founders (self-serve) | 3–7 days | Light human review | Reviewer queue assignment | Yes (bridge during Portfolio wait) |
| Activate Founders (partner-filed) | 10–14 days | PDM human review | Partner velocity + queue depth | Yes (replaces self-serve $5K) |
| Activate Portfolio (partner-filed) | 11–18 days | PDM discretionary review | AWS history + use-case clarity + partner ACE rate | Yes (+$50K via Build + Bedrock POC) |
| Build for Startups | 12–17 days | PDM with overlap check | Cross-application scope clarity | Yes (stacks on Portfolio) |
| Bedrock POC | 14–21 days | Bedrock team POC plan review | POC plan quality + eval methodology | Yes (stacks on Portfolio + Build) |
| MAP Assess phase | 14–21 days | MAP team migration review | Source-environment inventory completeness | Phased (Mobilize 4–8 wk, Migrate 8–24 wk) |
| Generative AI Accelerator | 60–90 days | Competitive cohort selection | Cohort window timing | Mutex with Portfolio in most cases |
The Migration Acceleration Program is the one track where "the timeline" is not a single number — it is three phase timelines that run sequentially across months. The wall-clock for "credits available" depends on which phase you are asking about.
MAP credits issue at each phase milestone, not upfront. A company starting a MAP engagement does not receive the full credit pool on day 14. They receive Assess-phase credits at day 14–21 (typically $5K–$25K for sizing work), Mobilize-phase credits at week 4–8 (typically $25K–$75K for pilot migration), and Migrate-phase credits at week 8–24+ (typically $50K–$200K+ for production cutover).
The phased structure means MAP timelines are inherently longer in calendar terms than single-pool Activate applications, but the credit availability matches the work being done — you do not have unused MAP credits sitting in your account waiting for utilization.
What it funds: migration sizing, source-environment inventory, target AWS architecture planning, total cost of migration modeling.
Typical credit award: $5K–$25K depending on migration scope. Smaller migrations (single application) land at $5K–$10K; larger migrations (multi-application, multi-environment) land at $15K–$25K.
What drives the spread: source-environment inventory completeness. Migrations with complete inventories (asset lists, dependency maps, current monthly costs) clear in 14 days. Incomplete inventories trigger reviewer write-backs and extend to 21 days.
What it funds: pilot migration of 1–2 representative workloads, AWS landing zone setup, IAM and networking baseline, observability instrumentation.
Typical credit award: 25% of projected migration cost, capped per workload. For a $100K total migration, Mobilize credits typically run $25K. For a $500K total migration, Mobilize credits run $125K.
What drives the timeline: the wall-clock here is the actual migration work, not AWS queue time. The 4–8 week range reflects the engineering complexity of the pilot workloads, not a reviewer queue.
What it funds: production cutover of the full migration scope. Application replatforming, data migration, traffic cutover, post-cutover validation.
Typical credit award: 50% of projected migration cost. For a $100K total migration, Migrate credits typically run $50K. For a $500K total migration, Migrate credits run $250K.
What drives the timeline: migration complexity. Lift-and-shift migrations (no application changes) typically complete in 8–12 weeks. Replatforming migrations (containerization, database refactor) typically complete in 12–18 weeks. Refactor migrations (architectural changes) extend to 18–24 weeks or longer.
Founders routinely ask whether the timeline can be compressed. The honest answer is no, not in any direct way. AWS does not respond to "we need credits faster" requests. The timeline is structurally fixed by the partner-development-manager review queue.
The PDM queue is not a customer-facing service. There is no expedited tier, no priority queue, no escalation path that gets your ACE record reviewed faster. AWS does not differentiate ACE records by founder urgency — they differentiate by partner standing, application completeness, and ACE submission date. Founders who ask their partner to "rush AWS" find that the partner cannot, because the partner does not have that lever either.
What founders can do is optimize for the fast end of each band rather than chasing an expedited timeline that does not exist. The four factors that shorten the timeline (existing AWS history, clear use case, high-velocity partner, early-week filing) reproducibly compress the wall-clock by 4–6 days when combined. That is the meaningful lever.
The other workaround is the bridge credit pattern. If a founder needs experimentation budget before the partner-filed credits land, they can file the self-serve $5K Activate Founders application simultaneously with the partner-filed Portfolio engagement. The self-serve credits land in 3–7 days, providing infrastructure budget during the 11–18 day Portfolio wait. This does not accelerate the Portfolio approval, but it solves the underlying problem (need to spin up infrastructure now, cannot wait two weeks).
Asking the partner to escalate to AWS does not shorten the timeline — AWS does not have an escalation path for ACE records. Submitting multiple ACE records with different partners does not shorten the timeline; it creates an opportunity conflict that gets both records rejected. Paying for an expedited tier does not shorten the timeline because no such tier exists. The timeline is what it is.
The Generative AI Accelerator is the one credit track that operates on a quarterly cohort cycle rather than a continuous review queue. Its 60–90 day wall-clock reflects the cohort selection process, not a slow ACE review.
The Accelerator runs roughly four cohorts per year, with each cohort accepting approximately 50 startups globally. The application window for each cohort is typically 30 days. Selection happens roughly 30–45 days after the application window closes. Onboarding and first-tranche credit issuance happens roughly 15 days after selection. Subsequent credit tranches issue across 6–12 months tied to program milestones — use of Bedrock at scale, completion of mentorship modules, joint go-to-market work with the Bedrock team.
The 60–90 day range comes from the timing of your application relative to the cohort window. Apply on day 1 of a 30-day window, and your wall-clock is 60–75 days (30 days of window + 30 days of selection + 15 days of onboarding). Apply on day 28, and your wall-clock is 30–35 days because most of the cohort review has already run in parallel with your application.
For founders who need credits in 14–21 days, the Generative AI Accelerator is not a feasible track. The path forward is to file Portfolio + Build for Startups + Bedrock POC for the standard $150K stack while waiting for the next Accelerator window. If accepted into the Accelerator later, the Accelerator credits typically supersede or supplement the standard stack depending on overlap with already-issued Bedrock POC credits.
For most CloudRoute-routed engagements involving partner-filed Portfolio, Day 18 is the realistic planning anchor. By Day 18, the standard $100K Portfolio engagement has landed, and the $150K stack engagement is nearly complete.
Anchoring on Day 18 rather than the optimistic end of the band (Day 11) avoids the planning trap of building infrastructure plans around a faster-than-typical timeline and then having to delay execution when the credits land later than expected. The optimistic timelines do happen, but they are the bottom of the band, not the median.
For founders who absolutely need infrastructure runway before Day 18, the bridge credit pattern provides 3–7 day cover. Filing the self-serve $5K Founders application simultaneously with the partner-filed Portfolio gives you an active credit balance during the wait. Most founders use the $5K to spin up the AWS account, run initial workload trials, and validate the architecture before the larger credit balance arrives.
For fundraising planning purposes — when a founder is using the credit award as part of their runway calculation for the next round — anchoring on Day 18 also avoids overstating the credit availability date to investors. "Credits in account by mid-month X" is honest if Day 18 of the engagement falls in mid-month X. Saying credits will land in 11 days when the typical engagement runs 16 invites awkward conversations when the timeline slips by a few days.
The most common planning question is: how much longer does the stacked $150K take vs the single-track $100K? Here is the honest comparison.
| Variable | Single $100K Portfolio | $150K stacked | AI Accelerator |
|---|---|---|---|
| Wall-clock | 11–18 days | 14–21 days | 60–90 days |
| Driver of slowest layer | Portfolio reviewer queue | Bedrock POC review queue | Cohort selection cycle |
| Founder time | ~30 minutes | ~70 minutes | Application + interview prep |
| Bridge credit pattern needed? | Optional | Optional but useful | Yes — file standard stack in parallel |
| Planning anchor | Day 16 | Day 18 | ~Day 75 |
| What can slip it later | Reviewer write-backs + new AWS account | Bedrock POC plan revisions | Late cohort window submission |
| What can pull it earlier | Existing AWS history + clear use case | High-velocity partner + clean POC plan | Apply early in cohort window |
| Cost to founder | $0 | $0 | $0 |
Situation: Series-A B2B SaaS with an active product on AWS at $5K/month. Adding a customer-support agent using Claude Sonnet via Bedrock as a distinct workload from the core platform. Wanted to file the full $150K stack — Portfolio for the existing platform, Build for Startups for a separate data-pipeline initiative, Bedrock POC for the customer-support agent. Wanted clear visibility into the timeline because the credits were being reported as part of the runway extension calculation to investors.
What CloudRoute did: Routed within 18 hours to a US-East partner with Portfolio + Bedrock POC track record. Day 0 inquiry, Day 1 routing, Day 2 discovery call, Day 3–4 founder paperwork (worksheet + POC plan + use-case differentiation), Day 5 partner filed all three ACE records simultaneously. Day 8–10 reviewer queue assignment, Day 11–13 Portfolio approved, Day 12–14 Build for Startups approved, Day 14–18 Bedrock POC approved. All three credit balances visible in AWS billing console by Day 18.
Outcome: Total credits applied: $150K. Customer-support agent prototype deployed in week 4 against the Bedrock POC credits. Founder reported the credits to investors with the Day 18 anchor, which was hit exactly. CloudRoute commission paid by partner from AWS engagement funding — customer paid $0.
engagement window: 18 days · founder time: ~9 hours · credits secured: $150K · planning accuracy: Day 18 anchor hit · cost to customer: $0
CloudRoute routes you to a high-velocity partner within 24 hours. Partner files the ACE record, you wait the standard wall-clock, credits land in your billing console at the Day 18 anchor. Customer pays $0.