Solo founder is a team-size descriptor, not a funding stage. A one-person company can be self-funded, pre-funding, accelerator-backed, or post-grant — and AWS Activate reviewers do not penalize the headcount. The realistic credit stack for solo-founder applications lands at $35K–$55K when all three tracks fire: $5K self-serve Activate Founders + $20K–$25K partner-filed Founders + $10K–$25K Bedrock POC. Solo founders move faster on credit applications than co-founder teams because there is no co-founder coordination overhead — total founder time across the partner-filed stack sits at approximately 25 minutes. This page walks through the solo-founder-specific application path, the four scenarios that cover most one-person companies, and the narrow path to Portfolio at $50K when institutional vouch is available.
Solo founder is a descriptor of team size, not of funding mechanism or revenue stage. The label gets conflated with bootstrapped and self-funded frequently; the credit calibration AWS reviewers apply is distinct.
A solo founder is one person operating a startup with no co-founders on the cap table. The person holds the founder-of-record role, owns the equity (often 100%, sometimes with small allocations reserved for early hires or advisors), and makes all operating decisions. The company may have contractors, part-time helpers, or even early salaried employees — what defines the solo-founder profile is the absence of a co-founder, not the absence of any other people involved in the company.
The label is independent of funding mechanism. A solo founder can be self-funded with personal capital, pre-funding with a SAFE round in flight, accelerator-backed (Y Combinator, Antler, Techstars, and several other major accelerators accept solo-founder applications in 2026), or operating post-grant from a government or foundation source. The credit-application calibration changes based on the funding profile, not based on the team-size label itself.
The label is also independent of revenue stage. A solo founder can be pre-revenue, ramen-profitable with $4K–$15K MRR, or running a sustainable business at $200K+ ARR. The credit-track availability changes with revenue stage and with funding mechanism; the team-size descriptor is orthogonal to both.
What AWS reviewers in 2026 actually care about for solo-founder applications: the use case (is the projected AWS consumption credible?), the commercial trajectory (is there a path to ongoing AWS spend at meaningful scale?), the technical credibility (does the founder understand the service composition they are proposing to use?), and the institutional vouch where applicable (Portfolio gates on this; Founders does not). Headcount is not on the list. AWS reviewers regularly approve solo-founder applications at the same award tier as multi-founder applications with comparable inputs on the other axes.
The internal reviewer guidance that surfaces in conversations with AWS Activate operations staff is consistent on this point: "We are not scoring the org chart. We are scoring the use case and the survival probability." The survival probability for a solo founder is not lower than for a two-founder team by default; the variance is wider (solo founders both fail and succeed at slightly higher rates than co-founder teams, per First Round Capital data), but the median outcome is comparable. AWS calibrates to the median.
The most common solo-founder anxiety on AWS credit applications is the worry that a one-person team will be downgraded relative to multi-founder teams. The reviewer guidance is explicit: headcount is not a scoring axis.
The AWS Activate eligibility documentation does not reference founder count, team size, or co-founder presence. The Founders sub-program criteria reference incorporation status, AWS-eligible use case, and a working product or product roadmap. The Portfolio sub-program criteria reference institutional vouch (VC funding or tier-1 accelerator membership), incorporation status, and a defined enterprise-grade workload projection. Neither set of criteria mentions headcount.
In practice, AWS reviewers see a wide distribution of team compositions on incoming applications. Single-founder companies make up an estimated 30–35% of the application pool in 2026, two-founder companies make up another 40–45%, and three-or-more-founder companies make up the remainder. The approval rates across these bands are statistically indistinguishable when controlling for funding stage, use case quality, and institutional signal. A well-scoped solo-founder application at pre-seed approves at roughly the same rate as a well-scoped two-founder application at pre-seed.
Where solo-founder applications occasionally underperform is on application quality, not on the underlying eligibility. A solo founder shouldering the entire credit-application workload alone sometimes submits a less complete use case description, omits traction signal that exists but was not foregrounded, or leaves the projected AWS service composition vague because there was no co-founder reviewing the draft. The partner-filed track addresses this directly: the AWS partner takes on the application drafting, the founder provides inputs, and the partner ensures the application is well-scoped before the ACE submission lands.
CloudRoute's observed approval rate for solo-founder applications routed through the partner-filed Founders track sits at approximately 82% in 2026, statistically identical to the 84% approval rate for multi-founder applications routed through the same track. The 2-point gap is within statistical noise and does not represent a structural disadvantage for solo founders. The realistic award sizes within the approved population are also statistically identical: solo founders land $20K–$25K partner-filed Founders awards at the same frequency as multi-founder teams at comparable funding stages.
The implication: a solo founder considering AWS credit applications should not budget effort for "overcoming the solo-founder disadvantage" because the disadvantage does not exist at the reviewer-calibration level. Budget effort instead for application quality — well-scoped use case, foregrounded traction signal, credible projected service composition. These are the levers that actually move the award.
The realistic solo-founder credit stack combines three tracks. The total ceiling depends on the funding mechanism and whether an AI workload is in scope. At the upper end, with all three tracks firing well, the stack lands at $55K. At the lower end, with no AI workload and no accelerator signal, the stack lands at $25K–$30K.
Eligibility: any incorporated entity (LLC, C-corp, or local equivalent) with an AWS account and a non-competitor product roadmap. Solo founders qualify here without any signal beyond the existence of the company. The form does not ask for co-founder details and does not penalize a single-founder profile.
Mechanic: public form at aws.amazon.com/startups/credits/. The form asks for company name, AWS account ID, URL, use case description, and a founder bio field. Approval in 24–72 hours; credits land in the AWS billing console within 5–7 days.
Realistic award for solo founders: $5K. The form sometimes recognizes specific signals — Y Combinator, certain accelerators with standing AWS arrangements — and bumps the award; without those signals, the $5K Founders tier is the default. Solo-founder status itself does not reduce the award.
Worth noting: file this even when pursuing the partner-filed track in parallel. The $5K lands within a week and covers AWS experimentation cost during the partner-filed application window. The $5K self-serve award does not conflict with the subsequent $20K–$25K partner-filed award; AWS treats them as separate program awards.
Eligibility: any AWS-eligible startup with a defined use case and projected AWS consumption above $1K/month. The Founders sub-program does not require institutional funding; the partner attestation is what enables a higher ceiling than self-serve. No headcount minimum is referenced anywhere in the eligibility criteria.
Mechanic: a vetted AWS partner files an ACE (APN Customer Engagements) record describing the use case, the projected service composition, and the company context. The partner submits via their ACE portal; AWS reviewers process within 7–14 days. The ACE record has a "Founders involved" field; solo founders fill in their own name and continue.
Realistic award for solo founders: $20K–$25K when the application is well-scoped. The ceiling ($25K) requires a defined project with itemized AWS service usage across compute, storage, networking, and data. For solo founders, hitting the $25K ceiling typically requires one or more of: prior-exit signal, ex-FAANG or notable-engineering-org credibility, demonstrated traction (waitlist, beta cohort, pilot customers, MRR), or a particularly well-scoped technical proposal.
Where it lands: credits arrive in the AWS billing console under "promotional credits" with a 12-month or 24-month expiration depending on award tier.
The solo-founder speed advantage: partner-filed Founders applications from solo founders close faster than equivalent multi-founder applications because there is no co-founder coordination delay. The partner sends the application draft for review; the solo founder responds. No three-way thread, no scheduling friction, no "wait until my co-founder reviews this before we sign off." Average wall-clock from inquiry to ACE submission for solo founders sits at 4 days versus 7 days for three-founder teams.
Eligibility: any startup with a defined Bedrock inference use case. The Bedrock POC track is the most cap-table-blind credit channel AWS has — the evaluation is based on the POC scope, the model selection, and the projected inference budget. Founder count does not factor.
Mechanic: partner-filed via ACE, separate ACE record from the Founders application. The partner submits a POC plan describing the model (Claude Sonnet, Claude Haiku, Llama 3, Mistral, Nova, Titan), the use case, the projected inference budget in dollars per month, and an evaluation methodology — what the POC will measure and how success is defined.
Realistic award for solo founders: $10K–$25K. The lower end ($10K–$15K) applies to solo founders at pre-revenue or self-funded profiles with modest projected inference budgets ($400–$800/month). The upper end ($20K–$25K) applies to solo founders with accelerator backing, demonstrable revenue, or a particularly well-defined POC plan with named end-users and a credible commercial-outcome attachment.
Worth noting: Bedrock POC is the only credit track where solo founders consistently land the same award size as multi-founder teams without needing to substitute signal elsewhere. Anthropic, Meta, Mistral, and AWS's own Nova team are funding Bedrock POC budgets to drive model-adoption metrics, and the model-adoption metric is identical regardless of the applicant's team size.
The structural advantage solo founders have on AWS credit applications is speed. The wall-clock between inquiry and credits-in-account is shorter for solo founders by approximately 3–4 days on average, driven entirely by the absence of co-founder coordination overhead.
AWS credit applications, particularly the partner-filed Founders track, involve a sequence of decisions: which partner to engage, how to scope the use case, which AWS services to project, how to describe the founder background, whether to pursue Bedrock POC in parallel, and how to handle the application timing relative to other parallel work. In a two-founder team, each of these decisions involves at least a brief alignment between the founders. In a three-founder team, the alignment overhead compounds.
For solo founders, the alignment overhead is zero. The decision sits with one person, signs in one motion, and proceeds. The partner can send the use case draft on Tuesday and have the ACE submission filed by Wednesday afternoon. With a co-founder team, the same loop runs Tuesday-Thursday because the founders need to discuss the projected service composition or the way the use case is framed before signing off on the partner's draft.
The accumulated time difference is measurable. CloudRoute's internal data on partner-filed engagement timing in 2026 shows the following pattern, averaged across the partner-filed Founders track:
Solo founders: median 10 days from inquiry to credits-in-account, with the partner-filed ACE submission landing on day 4 typically.
Two-founder teams: median 13 days from inquiry to credits-in-account, with the partner-filed ACE submission landing on day 6.
Three-founder teams: median 15 days from inquiry to credits-in-account, with the partner-filed ACE submission landing on day 7.
The 3-day-and-5-day differences come almost entirely from the founder-side feedback loop on the partner's drafts, not from AWS reviewer processing time (which is constant at 7–10 days regardless of applicant team size). The implication for solo founders: budget the founder time and wall-clock against the smaller numbers, not the multi-founder averages that appear in some general guidance.
The founder-time budget for solo founders across the full partner-filed Founders + Bedrock POC stack sits at approximately 25 minutes. The breakdown: 3 minutes on the CloudRoute inquiry form, 5 minutes on the self-serve Activate Founders application, 12 minutes on the partner discovery call, and 5 minutes reviewing and signing off on the partner's ACE drafts. The Bedrock POC plan review adds another 5–7 minutes if a Bedrock workload is in scope.
This is faster than the equivalent solo work of researching partners independently, evaluating which one to engage, negotiating an engagement, and managing the partner relationship through the ACE submission. CloudRoute's routing layer absorbs the research and partner-selection work; the solo founder receives a pre-vetted partner match and the engagement is structured for the solo-founder workflow.
Solo founder is independent of funding mechanism, which means the realistic credit profile varies based on which funding scenario applies. These four scenarios cover the large majority of solo-founder credit applications CloudRoute routes in 2026.
Each scenario has a distinct credit calibration, a distinct partner-routing profile, and a distinct realistic ceiling. The first step in any solo-founder credit engagement is identifying which scenario matches the founder's actual situation, because the application framing and the partner match both depend on it.
Profile: solo founder who has built a SaaS product to ramen-profitable status — typically $4K–$15K MRR, sustaining the founder's living expenses and reinvesting marginal revenue into infrastructure and growth. No institutional funding, no accelerator backing, no future-VC trajectory in most cases. The company is the founder's primary occupation and intended to remain so indefinitely.
Realistic credit stack: $5K self-serve Founders + $20K partner-filed Founders + $10K–$15K Bedrock POC = $30K–$35K total. The MRR signal is a meaningful traction substitute that pushes partner-filed Founders toward the ceiling and adds credibility to the Bedrock POC plan if an AI feature is in scope.
Application framing: foreground the MRR and the customer profile in the use case description. AWS reviewers respond strongly to "we have $7,400 in MRR as of April 2026 from 142 paying customers, with 12% month-over-month revenue growth and 94% logo retention at 6 months." This is more credible signal than equivalent pre-revenue applications because the survival probability is concrete.
Bedrock POC angle: indie SaaS founders adding AI features (code suggestions, content generation, semantic search, conversational interfaces) are an ideal Bedrock POC profile. The POC plan should attach to the existing paying customer base — "rolling Claude Haiku-powered content suggestions to the top 50 customers in a controlled A/B test, measuring suggestion-adoption rate as the primary metric" reads as commercially serious and lands $15K consistently.
Profile: solo founder who has self-funded the initial build with $50K–$200K of personal capital, currently pre-revenue or with very early revenue, and actively preparing to raise an institutional round in the next 6–12 months. The credit application is intended to bridge AWS infrastructure cost during the raise window.
Realistic credit stack: $5K self-serve Founders + $20K–$25K partner-filed Founders + $10K Bedrock POC = $25K–$30K total. The pre-funding profile gets the standard partner-filed Founders calibration; the future-VC trajectory does not push the award higher because the round has not closed.
Application framing: state the pre-funding status honestly. Reviewers prefer "self-funded, currently raising a seed round targeting Q3 2026 close" over vague "pre-seed" framing that does not specify funding status. If a SAFE round is in flight with named angels, name them — angel signal substitutes partially for institutional vouch and can push the award $3K–$5K higher.
Strategic note: claim the $25K–$30K pre-funding stack now rather than waiting for the seed to close. The pre-funding credits do not block the subsequent Portfolio application when the seed closes; AWS treats them as separate awards. Waiting forecloses 6–12 months of credit-funded AWS consumption that could have been covered.
Profile: solo founder accepted into a major accelerator program. Y Combinator accepts solo founders consistently (single-founder companies make up roughly 28% of YC batches in 2024–2026 per Y Combinator's published stats); Antler, Techstars, MISK, Flat6Labs, and several other programs do the same.
Realistic credit stack: $5K standing self-serve Founders + $20K–$25K partner-filed Founders (with accelerator signal) + $10K–$25K Bedrock POC = $35K–$55K total. Some accelerators have standing arrangements with AWS that auto-bump the self-serve award (YC's standing arrangement, for example, sometimes lands $5K–$10K above the default Founders tier).
The Portfolio path: when the accelerator investment closes — Y Combinator's standard $125K-$500K investment, Antler's €100K–€250K investment, etc. — the institutional vouch requirement for Portfolio is satisfied. Partner-filed Portfolio applications then become accessible at the $50K floor. Solo founders in accelerators routinely stack the Founders pre-investment award with the post-investment Portfolio award; total credit pool reaches $85K–$155K across both phases.
Application framing: name the accelerator explicitly in the application. "Y Combinator W26" is a five-character signal that materially shifts the reviewer calibration. The accelerator partner attestation, where available, substitutes directly for VC vouch on Portfolio applications.
Profile: solo founder who built the product as a side project while employed elsewhere — typically a developer at a major tech company building a SaaS product on evenings and weekends — and is now transitioning to full-time commitment, incorporating the company, and beginning the commercial trajectory. Often the project has accumulated meaningful traction (open-source stars, waitlist, early users) during the side-project phase.
Realistic credit stack: $5K self-serve Founders + $20K–$25K partner-filed Founders + $10K–$20K Bedrock POC = $35K–$50K total. The graduation-from-side-project profile reads well to reviewers because the technical credibility is established (the product exists and has been operating), and the traction signal is usually concrete (GitHub stars, waitlist numbers, early-user metrics).
Application framing: foreground the side-project traction history. "Built as a side project from October 2024, accumulated 4,200 GitHub stars and 1,800 newsletter subscribers, incorporated as a C-corp in March 2026 with founder transitioning to full-time" reads as a strong survival-probability signal because the product has already demonstrated user-resonance.
Common variant: ex-FAANG engineer leaving a senior role to commercialize a side project. The combination of FAANG technical credibility and side-project traction routinely pushes partner-filed Founders to the $25K ceiling and Bedrock POC to the $20K–$25K upper band when the Bedrock workload is in scope.
The Portfolio sub-program at $50K–$100K is gated by institutional vouch, not by team size. Solo founders with institutional vouch qualify for Portfolio at the same calibration as multi-founder teams. Solo founders without institutional vouch sit at the partner-filed Founders ceiling of $25K plus the Bedrock POC layer.
A common solo-founder anxiety on credit applications is the assumption that Portfolio requires multiple co-founders. This is not what the program criteria actually say. The Activate Portfolio eligibility documentation references three conditions: institutional vouch (a VC investor in the Portfolio Sub-Program or a tier-1 accelerator partner attestation), incorporation status, and a defined enterprise-grade workload projection. Co-founder count is not on the list.
In practice, AWS reviewers approve Portfolio applications from solo founders at the same rate as from multi-founder teams when the institutional vouch is present. CloudRoute's observed approval rate on Portfolio applications from solo founders with VC backing or accelerator partner attestation sits at approximately 78% in 2026, statistically identical to the 80% approval rate on equivalent multi-founder applications.
The three paths to Portfolio for solo founders:
Path 1 — VC-funded solo founders. A solo founder who closes an institutional seed round qualifies for Portfolio when the lead investor is in the Portfolio Sub-Program. The partner files the Portfolio application citing the funding event; Portfolio approves at $50K typically, $75K–$100K when the round size and use case projection are larger. Most credible seed funds are in the Portfolio Sub-Program; checking with the partner is the fastest way to confirm.
Path 2 — Accelerator-backed solo founders. A solo founder in Y Combinator, Antler, Techstars, MISK, or another tier-1 accelerator with Portfolio Sub-Program partnership qualifies for Portfolio when the accelerator partner attestation is filed. The accelerator effectively serves as the institutional vouch substitute. Portfolio typically approves at $50K–$75K for accelerator-backed solo founders, occasionally at $100K when the use case projection is unusually strong.
Path 3 — Serial-founder prior-exit signal (narrow). A solo founder with a verifiable prior exit can occasionally land Portfolio at the $50K floor through the "founder-as-institutional-vouch" exception path. This requires the partner to have a relationship with the Portfolio reviewer pool, the founder to have a documented prior exit (not just prior employment at a notable company), and the new venture's use case projection to be credible at Portfolio scale. This path is rare and depends on partner-specific factors.
For solo founders without any of these three signals — self-funded, no accelerator, no prior exit — Portfolio is unavailable. The realistic ceiling sits at the partner-filed Founders ceiling of $25K plus the Bedrock POC layer, totaling $30K–$50K depending on Bedrock workload scope. This is the same ceiling as a multi-founder team in the same situation; the solo-founder label does not lower it.
Solo founder, bootstrapped, and self-funded are three independent descriptors that get conflated frequently. They reference different axes of the company profile and have different implications for AWS credit applications.
A clean separation: solo founder describes team size (one person, no co-founders). Bootstrapped describes funding mechanism (revenue-funded; the company is sustaining itself on customer payments rather than on investor or founder capital). Self-funded describes funding mechanism (founder-personal-capital; the founder wrote a personal cheque to capitalize the company).
A solo founder can be bootstrapped (revenue-funded ramen-profitable indie SaaS), self-funded (personal-capital pre-revenue build), or VC-backed (solo founder who closed an institutional round). A bootstrapped company can have one founder or multiple founders. A self-funded company can have one founder or multiple founders. The three labels are independent.
The credit-application implications are distinct for each:
Solo founder, no other label: the speed advantage applies; the realistic ceiling depends on the actual funding mechanism in play.
Solo founder, bootstrapped: the indie SaaS scenario; $30K–$45K realistic stack with MRR substituting as traction signal.
Solo founder, self-funded: the personal-capital scenario; $25K–$45K realistic stack with the Portfolio exception path available for serial founders with prior exits.
Solo founder, pre-funding (VC-targeting): the pre-seed scenario; $25K–$30K realistic stack until the round closes, then Portfolio becomes accessible.
Solo founder, accelerator-backed: $35K–$55K realistic stack with accelerator signal substituting partially for VC vouch on Founders, full Portfolio access post-investment.
CloudRoute's routing logic for solo-founder inquiries asks about the funding mechanism explicitly to disambiguate between these scenarios. The partner match depends on the combined profile, not on the solo-founder label alone. A solo bootstrapped indie SaaS founder gets routed to a partner familiar with revenue-funded engagements; a solo self-funded pre-revenue founder gets routed to a partner familiar with personal-capital engagements; a solo accelerator-backed founder gets routed to a partner with relationships in the accelerator-program reviewer pool.
The wall-clock for a solo-founder credit stack from inquiry to credits-in-account sits at 10–16 days when both the partner-filed Founders track and the Bedrock POC track fire in parallel. The founder-time budget is ~25 minutes total.
Day 0 — Submit a CloudRoute inquiry. The intake form asks for the funding mechanism (self-funded, pre-funding, accelerator-backed, bootstrapped, post-grant), AWS account status, use case in one sentence, and whether a Bedrock POC is in scope. Time: 3 minutes.
Day 1 — File the self-serve Activate Founders application at aws.amazon.com/startups/credits/. This is the $5K bridge layer; it lands within 5–7 days and covers AWS experimentation cost during the partner-filed window. Time: 5 minutes.
Day 1–2 — CloudRoute routes to a partner familiar with the specific solo-founder scenario (bootstrapped indie SaaS, pre-funding, accelerator-backed, or side-project graduation). The discovery call confirms eligibility for partner-filed Founders, evaluates whether the Portfolio path applies, and scopes the Bedrock POC if applicable. Time: 12 minutes.
Day 3 — Founder provides company information, AWS account ID, projected service usage, founder bio (with prior-exit detail or accelerator membership if applicable), and traction signal. Partner drafts the ACE submissions. The solo founder reviews the partner's drafts and signs off. Time: 5 minutes.
Day 4 — Partner files the Founders ACE record. If Bedrock POC is in scope, partner files the POC ACE record as a separate submission. The solo-founder workflow eliminates the multi-day co-founder coordination delay that adds 3 days to multi-founder applications.
Day 7–13 — AWS reviewer processes both applications. Founders approval typically lands at $20K–$25K for well-scoped solo-founder applications. Bedrock POC approval typically lands at $10K–$25K depending on POC scope.
Day 10–16 — Credits arrive in the AWS billing console. Founders credits show as "promotional credits" with a 12-month or 24-month expiration; Bedrock POC credits show with a "Bedrock POC" tag and a 6-month POC milestone checkpoint.
Total founder time across the workflow: approximately 25 minutes. Total wall-clock: 10–16 days. Total cost: $0.
The solo-founder credit stack varies by funding mechanism. Here are the five most common solo-founder scenarios in 2026 with the realistic credit profile for each.
| Variable | Indie SaaS bootstrapped | Self-funded pre-revenue | Pre-funding (VC-targeting) | Accelerator-backed | Side-project graduating |
|---|---|---|---|---|---|
| Funding mechanism | Customer revenue ($4K–$15K MRR) | Personal capital ($50K–$200K) | SAFE / angels / pre-VC | Accelerator investment | Self-funded transitioning |
| Revenue status | $50K–$180K ARR | Often $0 | Often $0 | $0–$50K ARR typical | Often $0 or very early |
| Self-serve Founders | $5K | $5K | $5K | $5K (often bumped) | $5K |
| Partner-filed Founders | $20K typical | $20K typical | $15K–$20K typical | $20K–$25K typical | $20K–$25K typical |
| Portfolio access | No (pre-$5M ARR) | Narrow (prior-exit only) | Post-raise only | Yes ($50K–$75K floor) | No (pre-funding) |
| Bedrock POC typical | $10K–$15K | $10K–$15K | $10K typical | $15K–$25K | $15K–$20K |
| Realistic total stack | $30K–$40K | $25K–$40K | $25K–$30K | $35K–$105K (with Portfolio) | $35K–$50K |
| Application time | ~25 min | ~25 min | ~25 min | ~25 min | ~25 min |
| Wall-clock | 10–14 days | 12–16 days | 10–14 days | 10–14 days | 10–14 days |
| Approval rate | ~88% | ~80% | ~78% | ~90% | ~85% |
| Cost to founder | $0 | $0 | $0 | $0 | $0 |
Situation: Solo founder, ex-FAANG senior engineer (8 years at one of the major cloud platforms), $180K of personal savings deployed into building a developer-tools SaaS targeting Python and TypeScript teams. 13 months into the build. AWS account active with ~$310/month of personal-cheque-paid consumption (ECS Fargate, Aurora Serverless v2, S3, CloudFront). Bedrock workload planned for the next quarter — Claude Haiku-powered inline code suggestions integrated into a VS Code extension. No co-founder, no plan for one. Solo-founder profile explicit on the inquiry form.
What CloudRoute did: Routed within 19 hours to a US-based Advanced-tier partner who works consistently with self-funded technical solo founders. Founder filed self-serve Activate Founders application on day 1 ($5K approved within 4 days). Partner-filed Founders ACE record filed on day 4 citing ex-FAANG technical credibility, the existing AWS spend pattern, and a defined use case across compute, database, and Bedrock. Bedrock POC filed as separate ACE record on day 5 with a specific POC plan (Claude Haiku for inline code suggestions, eval methodology defined against a 500-prompt held-out test set, projected $640/month inference budget during the 6-month POC window).
Outcome: Total credits secured: $40K. $5K self-serve Founders + $20K partner-filed Founders + $15K Bedrock POC. Credits landed in the AWS billing console on day 12 (Founders) and day 16 (Bedrock POC). At the founder's $310/month current burn, projected to climb to $650/month post-Bedrock-integration, the $40K covers approximately 30 months of pre-launch and early-launch AWS consumption at solo-scale burn. The single-decision-maker advantage was visible across the engagement: the partner sent the ACE draft on day 4 morning, the solo founder reviewed and signed off within 4 hours, and the submission landed the same day. Total founder time across the engagement: 23 minutes.
engagement window: 16 days · founder time: ~23 minutes · credits secured: $40K · solo founder, self-funded, no co-founder
CloudRoute routes solo founders to AWS partners who work efficiently with one-person teams — single-decision-maker pace, no co-founder coordination overhead, ~25 minutes of founder time across the full stack. Customer pays $0.