AWS credits for Founders Inc portfolio companies — the Mansion-resident, consumer-AI, partner-filed Portfolio path most cohorts never run.

IFounders Inc — the Mansion-resident, consumer-AI Bay Area accelerator

Founders Inc occupies an unusual position in the Bay Area accelerator landscape. It is smaller than YC by a factor of 20 to 30 per batch; more concentrated than On Deck Catalyst by a factor of 3 to 5; physically anchored at a single SF residence rather than distributed remote-first; and vertically focused on consumer and AI rather than running a sector-agnostic program. Understanding the structural shape matters because the AWS Activate posture follows directly from it.

Founders Inc was founded by Jake Gibson and a small co-founding team. Jake Gibson came out of NerdWallet, which he co-founded and helped scale during the 2010s before transitioning to investing and accelerator work. The Founders Inc team built the program around a thesis that pre-seed and seed-stage consumer and AI founders benefit disproportionately from physical co-location, sustained mentor density, and a smaller, more concentrated cohort experience than the larger accelerator models provide. The physical anchor for that thesis is the Founders Mansion — a residence in San Francisco where cohort founders relocate for the duration of the program.

The Mansion model is structurally different from the YC cluster (founders live anywhere in or around SF and attend weekly office hours and Tuesday dinners), the Techstars model (founders relocate to the program city for three to four months and work out of a Techstars-provided workspace), the On Deck Catalyst model (remote-first with periodic in-person convenings), and the a16z Speedrun model (LA-based cohort with sustained partner time). The Mansion provides not just a workspace but a residence — founders live in the building, share common spaces, eat meals together, and have ambient access to the Founders Inc partners and to each other at the kind of intensity that only co-residence produces.

The cohort size has varied across cycles. Earlier batches ran in the 8 to 12 company range; more recent batches have run larger, in the 15 to 20 company range, with some cycles structured as concentrated sub-cohorts around specific verticals (consumer AI, gaming, devtools-for-creators, agents). The cohort cycle is approximately 12 weeks, comparable to YC and Speedrun in duration, but the residence-based structure produces a substantially higher hours-of-co-presence figure than non-residence accelerators of similar duration.

The vertical focus is consumer and AI, with AI-native consumer products being the most common acceptance pattern in recent cohorts. The thesis is straightforward: consumer products benefit from rapid user-feedback loops that the Mansion environment accelerates (founders test products on co-residents, on the Founders Inc partners, on the visitor network passing through the Mansion); AI-native consumer products benefit additionally from the technical density (multiple cohort companies share inference infrastructure conversations, prompt-engineering practices, model selection rationales). Games and creator tools also show up in recent cohorts; pure B2B SaaS, enterprise, and fintech show up less often.

The investment structure is standardized at acceptance: approximately $150K to $250K per cohort company at terms set by the program, with Founders Inc as the lead institutional check. The check size is below the $750K Speedrun standardized check and below the $500K YC MFN SAFE, but above the $125K Techstars convertible note + equity standard. The check size reflects the Founders Inc thesis that physical co-residence plus mentor density is the largest leverage point at the formative stage, not the size of the institutional check.

Worth flagging for AWS credit purposes: Founders Inc operates the fund and the program as integrated activities. Unlike On Deck (where the fellowship and the On Deck Founders Fund are structurally distinct entities) or YC (where the YC fund and the accelerator program are integrated but the standing Activate arrangement is at the accelerator-program level), Founders Inc bundles the fund check and the cohort participation as a single offer. The implication: every Founders Inc cohort company has Founders Inc on the cap table; there is no equivalent of the "On Deck fellowship without On Deck Founders Fund investment" pattern. This matters because the cap-table position is the variable AWS reviewers cross-reference in the partner-filed Portfolio application.

IIWhy Founders Inc is NOT in the AWS Activate Portfolio Sub-Program directly

The Portfolio Sub-Program operates by maintaining a list of institutional partners with standing arrangements. YC, Techstars, and 500 Global are in. Antler, On Deck, and Founders Inc are out. For Founders Inc the structural reason is small-cohort volume and a relatively recent fund vintage, not a quality-of-program judgment.

The Portfolio Sub-Program standing arrangement requires both a stable definition of "portfolio company" (which Founders Inc has, because every cohort acceptance comes with the integrated fund check and cap-table position) and a sustained annual volume of those companies sufficient to justify the AWS reviewer planning and the standing-arrangement integration overhead. The annual volume threshold is the structural variable that keeps Founders Inc outside the Sub-Program in 2026: a Founders Inc batch of 15 to 20 companies running roughly twice per year produces 30 to 40 portfolio companies annually, which is below the volume threshold AWS Activate has typically required for standing arrangements (the Sub-Program members typically produce 200+ portfolio companies per year through their cohort cycles).

The structural reason is therefore administrative rather than reputational. AWS Activate reviewers in the partner-mediated path consistently recognize the Founders Inc name, the Jake Gibson institutional background, and the Mansion-resident cohort signal. The recognition is real and supports the partner-filed Portfolio application meaningfully. What is missing is the standing arrangement that would make the eligibility verification automatic and the approval threshold standing — instead, the partner provides the institutional verification in the ACE narrative and the reviewer interprets the layered signal manually.

The practical consequence: the partner-filed Portfolio approval for a Founders Inc cohort company lands at $50K to $75K rather than the $75K to $100K range YC and Techstars companies hit. The $25K gap reflects the standing-arrangement deficit. The approval probability is also slightly lower than the Sub-Program member baseline — CloudRoute observes approximately 70 to 78 percent approval at the upper end of the $50K to $75K range for well-prepared Founders Inc applications, vs 85 percent for YC and approximately 75 to 80 percent for Techstars. The gap closes meaningfully when the application is filed by a partner with prior Founders Inc submission experience.

What Founders Inc has instead of the standing arrangement is a set of working partner relationships that have built up since the program launched. Partners with prior Founders Inc cohort submissions know the cap-table format, the typical post-cohort co-investor pattern, the consumer-AI Bedrock POC scoping conventions, and the Mansion-resident operational timing. The first-time partner submitting a Founders Inc application takes longer because the reviewer pattern recognition is absent; the experienced partner files more efficiently and lands approvals at the upper end of the range more consistently.

The Mansion residence itself does not change the credit ceiling. Some Founders Inc cohort founders assume that the physical presence at the Mansion is somehow itself a credit-application signal worth naming in the ACE submission. It is not. AWS reviewers do not weight physical co-residence as a separate variable; the variables that matter are the institutional cap-table position (Founders Inc as the named investor), the post-cohort co-investor signal (if any), the use case quality, the projected AWS consumption, and the partner attestation. The Mansion is operationally useful for the cohort experience but informationally neutral for the credit application.

Worth flagging: the Founders Inc cohort experience does often produce a faster post-cohort co-investor pipeline than non-residence cohorts of similar duration, because the Mansion creates ambient access to visiting investors, partner network referrals, and inter-cohort introductions. The faster co-investor pipeline is the indirect Mansion benefit for credit purposes — not because the residence itself signals, but because the residence produces follow-on raises faster, and the follow-on raise is the layered institutional signal that pushes the partner-filed Portfolio toward the upper end of the range.

IIIThe Mansion-resident operational pattern — what it means for credit-application timing

The Founders Inc cohort experience is anchored by the physical relocation to the Founders Mansion in San Francisco. Founders move in for the duration of the program, share common spaces, and have sustained access to the Founders Inc partners and visiting investors. The operational shape affects when the credit-application clock starts and how the cohort window maps onto the credit-filing window.

The Mansion is a residence in San Francisco that Founders Inc operates as the physical anchor for each cohort. Founders relocate from wherever they previously lived (Bay Area locals sublet or maintain their primary residence; remote founders fly in and move into the Mansion for the cohort duration). The residence provides bedrooms for cohort founders, shared common spaces for cohort programming, meeting rooms for partner office hours and investor meetings, and informal social spaces (kitchen, lounges, outdoor areas) where the ambient density that the program is built around plays out.

The Mansion-resident pattern produces a higher hours-of-co-presence figure than non-residence accelerators of comparable duration. A YC founder at a comparable point in the YC batch interacts with other YC founders at office hours, dinners, and ad-hoc meetings — perhaps 15 to 25 hours per week of YC-related co-presence. A Speedrun founder in LA has higher co-presence given the in-residence nature of the cohort programming. A Founders Inc founder living at the Mansion has co-presence at the residence-level intensity: 50+ hours per week of incidental co-presence with cohort peers and Founders Inc partners, with the structured programming layered on top.

The credit-application timing implication is that the Founders Inc cohort window is a continuous, sustained engagement rather than a series of weekly touchpoints. The discovery call with the CloudRoute-routed partner can be slotted into the Mansion calendar at almost any point in the cohort, and the partner can engage with the founder in-person at the Mansion when needed (most CloudRoute partners with prior Founders Inc track records have physically visited the Mansion during prior engagements). The 30-minute discovery call, the ~45 minutes of founder document preparation, and the 18 to 25 day partner-filed Portfolio window all map cleanly onto the cohort calendar without requiring the founder to context-switch out of the Mansion environment.

The Mansion-resident pattern also affects the entity-formation timing. Founders Inc cohort companies are typically already incorporated at cohort entry (incorporation is a prerequisite for receiving the Founders Inc check), so the AWS account setup conversation does not face the pre-incorporation gotcha that some Antler-style residency programs face. The AWS account can be set up under the company name from day one of the cohort, and the self-serve $5K Activate Founders application can be filed in the first week using the entity account rather than a placeholder or personal account.

Worth knowing: the partner-filed Portfolio application clock can start in cohort week 1. The cleanest operational pattern is to submit the CloudRoute inquiry within the first two weeks of cohort entry, get routed to a Founders Inc-familiar partner within 24 hours, hold the discovery call in cohort week 2 or 3 (in-person at the Mansion if the partner is Bay Area-based), and file the partner-filed Portfolio + Build for Startups + Bedrock POC stack by cohort week 4. Credits land by cohort week 7, available throughout the second half of the cohort and into the post-cohort window.

IVThe realistic Founders Inc credit stack in 2026

The full stack reaches $100K–$130K via self-serve Activate Founders + partner-filed Portfolio + Build for Startups + Bedrock POC. The Founders Inc institutional signal supports the upper end of the partner-filed range when the cap-table position is presented cleanly; the consumer-AI vertical focus supports the upper end of the Bedrock POC typical range.

VWhy the consumer-AI vertical focus aligns with Bedrock POC scoring

Founders Inc cohorts have skewed heavily toward consumer and AI-native verticals in recent batches. The vertical focus aligns cleanly with the Bedrock POC scoring criteria, which means the partner-filed Bedrock POC application for Founders Inc cohort companies tends to read more naturally to AWS reviewers than the same application for a generalist accelerator cohort company.

Bedrock POC applications are scored against four primary criteria: foundation model selection rationale (which model, why), evaluation methodology (how is output quality measured, by whom, with what scoring rubric), budget projection (expected inference token consumption and dollar cost over the POC window), and post-POC roadmap (what happens after the POC, how does the workload transition to production scale). Consumer-AI products map cleanly onto each of the four criteria: the foundation model selection conversation is product-centric (Claude Sonnet 4 for production chat, Claude Haiku for routing and classification, Nova Lite for cost-optimized high-volume paths); the evaluation methodology is end-user-centric (human raters scoring response quality, retention impact metrics, session-level engagement signals); the budget projection scales with user count and session counts; the post-POC roadmap is the launch path.

Founders Inc consumer-AI cohort companies typically arrive at the partner discovery call with the foundation model selection conversation partially worked through — the cohort programming has covered Bedrock model availability, the cohort peer companies have shared notes on Claude Sonnet 4 vs OpenAI direct vs Anthropic direct API access tradeoffs, and the founder is positioned to articulate a defensible model selection rationale by cohort week 4. The partner-filed Bedrock POC application benefits from this prep work — the founder time on application drafting is lower, the application content is sharper, and the reviewer reads the application as well-prepared rather than speculative.

The evaluation methodology section is where the cohort-context advantage compounds further. Consumer-AI products in the Founders Inc cohort have access to in-Mansion user testing (cohort peers and Founders Inc partners as initial test users), which makes the evaluation harness for the POC application concrete — the founder can describe an actual evaluation pipeline with a specific scoring rubric, real test users, and a measurable response-quality signal. The reviewer reads this as production-ready evaluation methodology rather than hypothetical, which calibrates the approval toward the upper end of the typical range.

For Bedrock POC applications targeting the $50K upper tier, the budget projection section is the most carefully reviewed. Consumer-AI Founders Inc cohort companies projecting inference consumption tied to specific user-count trajectories (with the user-count trajectories anchored to cohort-week beta testing, post-cohort launch plans, and 60-day post-launch retention assumptions) support the $50K tier more naturally than applications projecting consumption based on speculative usage assumptions. The Mansion-period beta testing supplies the concrete user-count anchor.

Worth flagging: the consumer-AI vertical alignment does not automatically push every Founders Inc Bedrock POC application to the $50K tier. The $50K tier requires application-quality work that founders consistently underestimate — the difference between a $25K-tier and a $50K-tier application is approximately 4 to 6 hours of focused drafting on the application paperwork plus partner advisory time on the architectural depth section. CloudRoute partners handling Founders Inc submissions typically pre-flag which applications are realistically targeting the $50K tier during the discovery call and scope the founder time investment accordingly.

VIFounders Inc vs Y Combinator — smaller, more concentrated, consumer-AI-focused

Founders Inc and YC sit on opposite ends of the Bay Area accelerator concentration spectrum. YC runs the largest accelerator program in the world by batch volume; Founders Inc runs one of the smaller concentrated programs. The credit-application implications follow the structural differences directly.

YC batches are 200 to 300+ companies; Founders Inc batches are 15 to 20 companies. The 15x scale difference shapes everything downstream: YC operates a standing AWS Activate Portfolio Sub-Program arrangement that automates eligibility verification for the full batch; Founders Inc operates partner-filed Portfolio applications individually, with the partner providing the institutional verification that the standing arrangement would otherwise provide automatically. The standing arrangement is what produces YC's $75K to $100K Portfolio ceiling vs Founders Inc's $50K to $75K Portfolio ceiling — the $25K gap reflects the manual-verification overhead built into the partner-intermediated path.

YC operates as a sector-agnostic program — every YC batch includes enterprise SaaS, fintech, biotech, devtools, consumer, AI, and a long tail of other verticals. The sector-agnostic shape supports the standing arrangement because the portfolio definition is bounded and stable across cycles regardless of vertical mix. Founders Inc operates as a consumer-and-AI-focused program with concentrated vertical exposure. The vertical concentration is a strength for the cohort experience (cohort peers share more in common, the mentor network is sector-specific) but does not by itself unlock Sub-Program standing — the volume threshold matters more than the vertical concentration.

YC's check is the $500K MFN SAFE delivered as part of the batch acceptance. Founders Inc's check is the standardized $150K to $250K delivered at acceptance. The check size ratio (YC ~2.5x Founders Inc) reflects different program theses: YC operates at scale with the batch model leveraging the YC network; Founders Inc operates at concentrated depth with the Mansion model leveraging co-residence. The check size affects the Portfolio award calibration only modestly — AWS reviewers weight the institutional check size as one input among several, with brand quality and projected consumption more heavily weighted.

YC's physical anchor is the YC office and the Tuesday dinners; founders live anywhere in or around the Bay Area. Founders Inc's physical anchor is the Mansion; founders live in the residence. The physical model affects the operational shape of the partner discovery call (in-person availability at the Mansion is reliable for Founders Inc; in-person availability for YC founders is variable based on where the founder lives) but does not affect the credit ceiling itself.

YC's post-batch demo day produces a concentrated raise window where most YC batch companies close seed rounds within 60 days of demo day. Founders Inc's post-cohort raise pipeline is more distributed — some cohort companies close follow-on rounds during the cohort itself (the Mansion-resident ambient access to visiting investors compresses the raise timeline), some close shortly after cohort completion, and some build for longer before raising. The distribution affects the timing of the partner-filed Portfolio application: for YC the cleanest timing is around demo-day-period when the seed round is closing; for Founders Inc the cleanest timing is whenever the cap-table position is most fully built (which can be cohort week 4 if a fast co-investor closes early, or post-cohort if the raise builds more slowly).

Net realistic stack comparison: YC non-AI companies land $125K to $150K; Founders Inc cohort companies land $100K to $130K. The $25K gap is the Sub-Program-membership gap. For AI-native cohort companies, both can reach the upper Bedrock POC tier — YC AI cohort companies land $150K+ when the Bedrock POC approves at $50K; Founders Inc consumer-AI cohort companies land $130K+ on the same Bedrock POC approval. Both programs feed into the Generative AI Accelerator pipeline; YC has higher Accelerator acceptance rates (~15 to 20 percent for YC AI cohort companies vs ~8 to 12 percent for Founders Inc consumer-AI cohort companies), driven by the YC accelerator-class signal weighting that the Accelerator reviewer pool applies.

VIIFounders Inc vs On Deck — physical residence + investment vs remote fellowship

Founders Inc and On Deck represent two distinct accelerator-program theses. Founders Inc bundles physical residence with an integrated investment check at acceptance; On Deck runs a remote-first fellowship model with separate investment from the On Deck Founders Fund at selective participation. The credit-application mechanics differ accordingly.

On Deck pre-2023 ran a community-first fellowship model with large cohorts (600 to 800 ODF fellows per cycle at the 2021 peak) and selective On Deck Founders Fund investment in a subset of fellows. Post-2023 the restructure moved On Deck toward smaller, more focused programs anchored by On Deck Catalyst — closer to a traditional accelerator format than the early fellowship model. Across both pre- and post-restructure periods, On Deck has remained remote-first with periodic in-person convenings rather than physical residence.

Founders Inc has always operated the physical-residence model. The Mansion is the program anchor, the check is integrated with cohort acceptance, and the cohort size has stayed small enough to support the residence model (which by itself caps batch size at the number of founders the Mansion can house plus reasonable common-space density). The structural differences mean Founders Inc has not faced the same restructure pressure On Deck went through — the program has scaled by adjusting cohort frequency and cohort size within the residence constraint rather than by adding parallel fellowship verticals.

For AWS credit purposes both programs share the same Portfolio Sub-Program structural position: neither is a standing-arrangement member, both run through the partner-filed Portfolio path via ACE, and both face the $50K to $75K partner-filed Portfolio ceiling vs the $75K to $100K YC and Techstars range. The credit-application mechanics, however, differ meaningfully because of the program-structure differences.

On Deck cohort companies face the pre-fellowship vs post-fellowship distinction: during the fellowship the partner-filed Portfolio path is structurally available but lands at the lower end of the range or sometimes downgrades, because the post-fellowship institutional seed round is what layers in the strongest signal. Post-fellowship the partner-filed Portfolio path opens cleanly at the upper end of the range. The cleanest timing for On Deck is to file post-fellowship when the institutional seed round is closing.

Founders Inc cohort companies do not face the same pre-cohort vs post-cohort distinction because the Founders Inc check is integrated with cohort acceptance — the institutional cap-table position is established from day one of the cohort, and the partner-filed Portfolio application can be filed during the cohort with the Founders Inc check as the named institutional signal. The post-cohort co-investor (if any) layers additional signal but is not strictly required for the partner-filed application to land at the upper end of the range. The cleanest timing for Founders Inc is to file in cohort week 4 to 6, with credits landing by cohort week 7 to 9 and available throughout the second half of the cohort.

Net stack comparison: Founders Inc $100K to $130K; On Deck $95K to $130K post-fellowship, $25K to $45K pre/during fellowship. The post-fellowship On Deck ceiling matches the Founders Inc ceiling because both face the same Sub-Program-membership gap. The pre-fellowship On Deck ceiling is lower because On Deck has no equivalent of the Founders Inc integrated check — the pre-fellowship On Deck founder lacks the institutional cap-table position that the Founders Inc cohort founder has from day one.

For consumer-AI focus: Founders Inc is explicitly vertical-focused on consumer and AI; On Deck AI was a focused fellowship pre-restructure and the post-restructure Catalyst cohorts admit AI-native companies but are not exclusively AI-focused. The vertical-focus alignment with Bedrock POC scoring is similar across the two programs for AI-native cohort companies. The Mansion-resident ambient density gives Founders Inc consumer-AI cohort companies a modest evaluation-methodology advantage in Bedrock POC applications (the in-Mansion user testing concretizes the evaluation rubric), but the structural Bedrock POC ceiling is the same across the two programs.

VIIIThe post-cohort follow-on raise pattern and downstream credit applications

Founders Inc cohort companies typically raise post-cohort follow-on rounds within 6 to 12 months of cohort graduation. The post-cohort raise structure varies more than the Speedrun pattern (which standardizes around a16z-led follow-on) and the YC pattern (which standardizes around demo-day-period seed close), and the variation affects subsequent credit applications.

The Founders Inc post-cohort raise structure takes one of several shapes. The most common pattern: a post-cohort seed round led by a tier-one or tier-two VC with Founders Inc participating to maintain the institutional position. The seed round typically lands in the $1M to $3M range, with the named co-investor varying widely by cohort (recent Founders Inc cohort graduates have raised from Founders Fund, Sequoia, Index, Khosla, Spark Capital, AI Grant, and a long tail of smaller tier-two VCs). A second common pattern: a seed extension led by Founders Inc directly, scaling the institutional position before the priced seed round; this pattern is more common for cohort companies with strong cohort-period traction and selective follow-on raise plans.

A third pattern: the cohort company defers the priced seed round and builds for longer on the cohort check plus revenue or grant funding, raising the priced seed round in the 12 to 18 month post-cohort window with stronger traction signals. This pattern is less common but visible in approximately 15 to 20 percent of Founders Inc cohort graduates based on CloudRoute partner observations.

All three patterns preserve the partner-filed Portfolio eligibility. The Founders Inc cap-table position remains stable through any of the follow-on raise structures, and AWS Activate does not re-verify eligibility during the credit-validity window. The original credit pool from the cohort-period filing remains intact through any follow-on raise within the 12-month validity period.

The downstream credit applications shift in character after the post-cohort raise lands. The Portfolio Sub-Program access remains at the partner-filed $50K to $75K ceiling (no automatic uplift from the follow-on raise), but new credit pools become available: production-scale Bedrock commitments rather than POC-stage scoping, ISV-program enrollment for cohort companies pursuing AWS Marketplace listing, and Build for Startups extensions for newly distinct workloads emerging from the post-raise product expansion. CloudRoute partner relationships with Founders Inc-graduated cohort companies typically continue across the post-cohort raise window, with the initial cohort-period engagement (Portfolio + Build + Bedrock POC) followed by a post-raise engagement (production-scale Bedrock, ISV, Marketplace, additional Build for new workloads).

For consumer-AI Founders Inc cohort companies pursuing the Generative AI Accelerator, the post-cohort raise affects the application timing. The Accelerator application can be filed during the cohort or post-cohort; cohort-period filing accelerates the timeline but the application profile is somewhat thinner without the post-cohort raise signal layered in. The 60 to 90 day Accelerator review window means cohort-period filing produces a decision shortly after cohort completion; post-raise filing produces a stronger application profile but a later decision. CloudRoute partners advise on the timing tradeoff based on the cohort company's specific raise trajectory.

Worth knowing: the post-cohort raise can affect the Bedrock POC scoping window if the post-cohort raise is meaningfully larger than the cohort-period Founders Inc check. A cohort company with the $150K to $250K Founders Inc check and a subsequent $3M seed round may want to refile or extend the Bedrock POC at the post-raise stage with a larger projected inference budget — the partner-filed Bedrock POC is not strictly capped at the cohort-period $25K typical, and at the post-raise stage with stronger projected consumption signals the application can be re-scoped toward the $50K upper tier.

IXThe 25-day Founders Inc credit-application timeline

Cohort week 1 (Mansion move-in) — Cohort company has been accepted into Founders Inc, the standardized $150K to $250K check is on the cap table, the entity AWS account is set up under the company name. Self-serve Activate Founders ($5K) filed against the entity account; credits land in 24 to 48 hours and are immediately usable for prototyping.

Cohort week 1–2 — CloudRoute inquiry submitted indicating Founders Inc cohort participation, current cap table, and product vertical (consumer-AI, games, creator tools, devtools).

Cohort week 2 (Day 1 of partner engagement) — Routed within 24 hours to a partner with prior Founders Inc-application experience, matched on vertical (consumer-AI most common) and on Bay Area presence for in-Mansion discovery call availability.

Cohort week 2 (Day 2) — Discovery call (30 minutes), often in-person at the Mansion. Partner confirms cohort participation, verifies the integrated Founders Inc check on the cap table, scopes Portfolio + Build for Startups + Bedrock POC applicability based on the vertical and the projected AWS consumption.

Cohort week 2–3 — Founder provides company info, AWS account ID, use case paragraphs, deck, Founders Inc cohort confirmation, and cap-table summary. ~45 minutes total founder time.

Cohort week 3 — Partner files three ACE records (Portfolio + Build for Startups + Bedrock POC) within the same business week. Each names Founders Inc as the institutional sponsor and the company as the customer. The Bedrock POC record includes the vertical-specific POC narrative (Claude Sonnet 4 / Claude Haiku model selection rationale, evaluation harness, budget projection, post-POC roadmap).

Cohort week 5–6 — Portfolio approval lands first ($50K to $75K, calibrated against the integrated Founders Inc check plus any post-cohort co-investor signal). Build for Startups by cohort week 6 ($15K to $25K). Bedrock POC by cohort week 7 ($20K to $25K typical, $50K achievable for AI-native applications).

Cohort week 7 — Full stack visible in AWS Billing dashboard under "promotional credits." $100K to $130K total auto-applies against monthly invoice. Stack credits actively consumed throughout the second half of the cohort and into the post-cohort window.

Cohort week 8 onward — Consumer-AI cohort companies pursuing the Generative AI Accelerator submit the Accelerator application with partner advisory support on the architectural depth section. Accelerator review window is 60 to 90 days; decision typically lands at cohort week 12 or shortly post-cohort.

Optional cohort week 12+ (Generative AI Accelerator outcome) — Accepted consumer-AI Founders Inc cohort companies receive Accelerator awards in the $200K to $400K range, layered on top of the standard stack for a combined $300K to $530K position.

XA representative Founders Inc cohort credit-application engagement

A representative anonymized example: a Founders Inc consumer-AI cohort company, two co-founders, building a consumer chat application with generative content as the core product spine. Cohort entry produced a $200K Founders Inc check with the entity already incorporated as a Delaware C-corp; founders relocated to the Mansion at cohort week 1. Pre-cohort the founders had used a personal OpenAI API account for prototyping; the cohort intent was to migrate to a Bedrock-based production inference pipeline with Claude Sonnet 4 as the primary model.

The CloudRoute inquiry was submitted at cohort week 1.5 indicating Founders Inc cohort participation, the integrated $200K Founders Inc check on the cap table, the consumer-AI vertical, and the Bedrock migration intent. Routing landed within 18 hours to a Bay Area partner with prior Founders Inc cohort track record and Bedrock POC submission experience for consumer-AI applications. The discovery call was held in-person at the Mansion at cohort day 12, scheduled into a 30-minute slot between cohort programming.

The partner filed three ACE records at cohort week 3: Portfolio ($75K, upper end of the Founders Inc range — supported by the integrated $200K check plus a verbal soft-circle from a tier-two co-investor signaling a follow-on seed extension would land within 60 days), Build for Startups ($25K, distinct workload — a content moderation pipeline separated from the primary generative inference pool), Bedrock POC ($25K typical tier — well-scoped POC with Claude Sonnet 4 for primary chat inference, Claude Haiku for routing and classification, documented evaluation harness with in-Mansion test-user scoring, budget projection scaled against cohort-period beta testing and projected 60-day post-launch user-count trajectories).

Portfolio approval landed at cohort week 5 at the full $75K; Build for Startups at cohort week 6 at $25K; Bedrock POC at cohort week 7 at $25K. Total stacked: $125K. The OpenAI-to-Bedrock production migration completed during cohort weeks 8 to 10 with the AWS partner providing implementation support in parallel with the cohort programming. The post-cohort seed extension closed at cohort week 11 ($1.2M led by the soft-circled tier-two co-investor), bringing the post-extension cap table to Founders Inc + the seed extension lead + two angel co-investors.

The Generative AI Accelerator application was filed at cohort week 6 with partner advisory support; the architectural depth interview reached at cohort week 11; the decision (accepted at $300K) landed at cohort week 14. Combined credit position at 90 days post-cohort-entry: $425K total. Founder time across the full stack + Accelerator application: approximately 12 hours.

This example sits at the upper end of the realistic Founders Inc range for consumer-AI cohort companies; not every cohort company hits the Accelerator acceptance, and not every Portfolio application lands at the $75K upper end. The median Founders Inc cohort company outcome is closer to $100K to $115K (Portfolio at $50K to $65K + Build for Startups at $20K to $25K + Bedrock POC at $20K to $25K) without the Accelerator path. The variance is driven primarily by the application quality, the partner track record on Founders Inc submissions, and the post-cohort co-investor signal strength.

XIWhat Founders Inc cohort founders typically get wrong about AWS credits

• Assuming the Mansion residence is itself a credit-application signal — The most common confusion. Cohort founders sometimes assume that the physical residence at the Mansion or the Founders Inc cohort name on the resume is sufficient to support Portfolio Sub-Program direct access. It is not — the Sub-Program standing arrangement does not exist for Founders Inc, and the partner-mediated path requires the institutional cap-table position (the Founders Inc check) as the variable AWS reviewers cross-reference. The Mansion is operationally useful but informationally neutral for the credit application. Fix: lean the partner narrative on the integrated Founders Inc check and the cap-table position, not on the residence.
• Filing self-serve Founders only and never running the partner-filed track — Some Founders Inc cohort founders redeem the $5K self-serve Founders credit during the cohort and never pursue the partner-filed $50K to $75K Portfolio path. The self-serve credit is operationally useful during the partner-filed application window, but it is not the ceiling. The cohort-period partner-filed Portfolio path is the workhorse track and should be initiated within the first two weeks of cohort entry. Fix: submit the CloudRoute inquiry by cohort week 1 to 2.
• Vaguely scoping the Bedrock POC application and downgrading from $50K to $25K — Consumer-AI Founders Inc cohort companies with strong product fundamentals sometimes file Bedrock POC applications that read as speculative rather than production-ready. The $50K upper tier requires application-quality work — specific foundation model selection rationale, named evaluation methodology with concrete test users and scoring rubric, budget projection tied to anchored user-count trajectories, defined post-POC roadmap. The 4 to 6 hours of focused application drafting is the difference between $25K and $50K. Fix: take the application drafting seriously, work with the partner on the architectural depth section, anchor the budget projection to cohort-period beta-testing data.
• Not coordinating the Bedrock POC with the post-cohort raise timing — Some Founders Inc cohort founders file Bedrock POC during the cohort with cohort-period inference budget projections, then close a meaningful follow-on seed extension that changes the consumption profile, but do not re-engage the Bedrock POC application. The partner-filed Bedrock POC is not strictly capped at the cohort-period $25K — post-raise re-scoping with larger projected consumption can push the application toward the $50K upper tier. Fix: re-engage the partner at the post-raise stage if the consumption profile materially changes.
• Underutilizing the cohort-period in-Mansion user testing in the evaluation methodology — The Mansion provides ambient access to cohort peers, Founders Inc partners, and visiting investors as informal test users. This is a meaningful evaluation-methodology advantage for consumer-AI Bedrock POC applications — the founder can describe an actual evaluation pipeline with specific scoring methodology and real test users, which reviewers read as production-ready. Some cohort founders underutilize this by filing Bedrock POC applications with hypothetical evaluation methodologies rather than describing the in-Mansion testing concretely. Fix: write the evaluation methodology section around the in-Mansion testing actually happening.
• Conflating Founders Inc with On Deck Catalyst for credit-application purposes — Some applicants and partners new to Founders Inc conflate the program with On Deck Catalyst because both are non-Sub-Program-member smaller accelerators with similar credit ceilings. The credit ceilings are similar, but the operational structure differs (residence vs remote-first; integrated check vs selective fund), and the partner narrative differs accordingly. Fix: the ACE narrative should specifically name Founders Inc and the integrated $150K to $250K check as the institutional signal, not generalize to "smaller accelerator program."
• Filing through a partner with no Founders Inc track record — Founders Inc applications carry more reviewer scrutiny than YC or Techstars because the institutional verification is partner-mediated rather than standing. Partners with prior Founders Inc submissions land approvals more consistently because the reviewer pattern recognition reduces friction. Partners new to Founders Inc take longer per application and sometimes see downgraded awards. Fix: route through CloudRoute specifically to partners with prior Founders Inc track record.
• Missing the cohort-period Accelerator application timing window — For consumer-AI Founders Inc cohort companies, the Generative AI Accelerator application can be filed during the cohort with the 60 to 90 day review window producing a decision shortly post-cohort. Cohort founders who defer the Accelerator application to post-cohort or who fail to file at all miss the timing window where the cohort signal is freshest. CloudRoute observes approximately 8 to 12 percent Accelerator acceptance for consumer-AI Founders Inc cohort companies — modest but meaningful given the $200K to $400K typical award. Fix: file the Accelerator application by cohort week 6 to 8.
• Treating the partner-filed Portfolio approval as ceiling rather than starting point — The partner-filed Portfolio approval at $50K to $75K is the cohort-period credit-position floor, not the full credit-position trajectory. Post-cohort, additional credit pools become available (production-scale Bedrock commitments, ISV-program enrollment, Marketplace listing support, additional Build for Startups for newly distinct workloads). The cohort-period stack is the foundation; the post-raise extension is the compounding layer. Fix: maintain the partner relationship across the post-cohort window for downstream credit applications.

XIIWhat a CloudRoute-routed AWS partner does for a Founders Inc cohort company

The partner's role for a Founders Inc cohort company is structurally similar to other partner-filed engagements, with three Founders Inc-specific patterns worth flagging.

They file the ACE records — Portfolio, Build for Startups, Bedrock POC — naming Founders Inc as the institutional sponsor and the integrated $150K to $250K cohort check as the institutional cap-table position. Because Founders Inc is not in the standing Portfolio Sub-Program, the partner narrative work matters more than it does for YC or Techstars submissions: the partner explicitly establishes the institutional credibility in the ACE description rather than relying on automated verification.

They vet the use case, Founders Inc context, and post-cohort co-investor pipeline before filing. Founders Inc cohort companies are typically early-stage at the partner-filing moment (cohort week 2 to 3); the partner sanity-checks whether the use case as described matches what the ACE reviewer is going to want to see, and whether the post-cohort co-investor pipeline supports a stronger institutional signal narrative.

They act as the named technical partner on the file. The reviewer cross-references partner history; partners with prior Founders Inc approvals are recognized and the file moves faster. The first-time Founders Inc partner takes longer because the reviewer does not have the pattern recognition.

They provide the actual AWS implementation if you want it — production account setup, IAM and VPC, the migration off whatever pre-cohort infrastructure was used (typically Vercel + Supabase + OpenAI direct for consumer-AI Founders Inc cohort companies; sometimes Render + PlanetScale + Anthropic direct), observability, deployment pipelines, and the production Bedrock setup with proper guardrails. Most Founders Inc cohort companies want this because the cohort window is intense and cloud-engineering bandwidth is limited.

They provide a co-branded readiness assessment — a written document showing the partner-built infrastructure, the trade-offs, what to monitor. This deliverable is useful for incoming investors during post-cohort raise diligence and during the post-raise window when Series-A conversations begin.