Pear VC is the Palo Alto pre-seed firm founded in 2013 by Mar Hershenson and Pejman Nozad. It runs two early-stage programs — the PearX accelerator (roughly 20 companies per batch, ~3% acceptance) and the Pear Garage residency for very early founders. Pear is in the AWS Activate Portfolio Sub-Program as a vouching institution, which means the partner-filed Portfolio path lands at the upper end of the range ($75K–$100K) on the back of a Pear-named ACE record. Combined with the standing $5K Activate Founders credit, Build for Startups (+$25K), and Bedrock POC (+$25K for AI-heavy companies), the realistic Pear stack reaches $130K–$155K. This page walks through Pear's structure, the Stanford-ecosystem pattern that defines most of its portfolio, how the partner-filed mechanic actually fires, and how Pear compares to Y Combinator and Sequoia Arc on credit math.
Pear VC is structurally different from most US accelerator-style funds. The check size is institutional VC, the cohort cadence is accelerator, the founder concentration is closer to a Stanford spin-out program than a generalist pre-seed fund. Understanding the model is the entry point to understanding why the credit signal works the way it does.
Pear VC was founded in 2013 in Palo Alto by Mar Hershenson and Pejman Nozad. Hershenson came from a semiconductor design background — she had founded and exited multiple EDA companies before turning to pre-seed investing — and brought a deeply technical founder filter to the firm. Nozad came from a different angle entirely (the well-known carpet-shop-to-Sand-Hill arc) but had built a substantial angel track record before Pear. The combination of an engineering-founder partner and a network-driven partner shaped the firm's early identity: technical founders, often pre-product, often pre-incorporation, often coming directly from a Stanford lab or PhD program.
The firm now operates two programs in parallel. PearX is the headline accelerator program — roughly 20 companies per batch, two batches a year, with each batch running for around 14 weeks of intensive in-person residency in Palo Alto. Acceptance to PearX runs at roughly 3% of applicants, which is comparable to YC's acceptance rate but with a substantially smaller cohort. Standard PearX check size is $250K for around 5% to 10% equity, with the firm sometimes leading or co-leading larger pre-seed rounds for portfolio companies that need more runway.
Pear Garage is the earlier-stage program — designed for very early founders, sometimes pre-co-founder, sometimes pre-idea. The Garage runs from Pear's Palo Alto office and operates more like a founders-in-residence program than an accelerator. Founders work out of the space, get exposure to the Pear partner team and the firm's deep Stanford and Bay Area technical network, and many of them eventually apply to and join PearX once a real company has come together. Garage and PearX together form a top-of-funnel-to-portfolio pipeline that Pear runs continuously rather than in discrete batches.
The portfolio. The firm's public companies and unicorns include DoorDash (Pear was the first institutional check), Branch (now Branch Insurance, late-stage), Affinity (relationship intelligence, late-stage), Guardant Health (oncology diagnostics, public), Imply (real-time analytics, late-stage), and a long list of more recent AI-era companies in healthcare, developer tools, and B2B SaaS. The concentration model means each portfolio company gets significant partner-level attention; the cohort being ~20 companies means PearX founders have substantially more partner time than a 200-company-cohort YC alum has.
The Stanford-ecosystem pattern is the central operational feature of Pear's founder filter. A majority of PearX founders come out of Stanford — Stanford undergrad, Stanford MS, Stanford PhD, Stanford GSB — and often have prior Stanford lab affiliations or research backgrounds. The firm runs deeply Stanford-rooted recruiting (campus events, lab partnerships, PhD outreach), and the cohort dynamics reflect that concentration. This Stanford pattern is relevant to the credit conversation because Stanford-derived companies tend to have technical-research-heavy use cases at the point of credit application, and the partner-filed narrative writes itself when the founder's background is on the AWS reviewer's desk.
AWS Activate has a Portfolio Sub-Program built around a published list of vouching institutional investors and accelerators. Pear is in that list. The implication for Pear-backed founders is that the partner-filed Portfolio path consistently approves at the upper end of the range, $75K–$100K, with the lower end of the range only appearing in edge cases.
The Portfolio Sub-Program is the standing arrangement between AWS Activate and a specific set of institutional investors. The arrangement works as follows: AWS publishes a list of recognized investors and accelerators; partners filing ACE records can name these institutions as institutional sponsors; AWS reviewers verify the institutional relationship through internal mappings rather than requiring fresh evidence; approval thresholds for portfolio companies of these institutions skew toward the upper end of each ceiling. Pear VC has been a named member of this list for several years, comparable in standing to YC, Techstars, 500 Global, and a few other heavyweights.
What "Pear vouches institutionally" means in practice. When a CloudRoute-routed partner files Portfolio on behalf of a Pear-backed company, the ACE record names Pear VC as the institutional investor. The AWS reviewer cross-references the institution against the Portfolio Sub-Program list, confirms Pear-as-vouch is active, and applies the elevated approval logic that goes with it. The reviewer is not re-doing diligence on the company; the reviewer is calibrating against the AWS Activate playbook for Portfolio Sub-Program investors. Pear-backed applications land $100K Portfolio approvals roughly 80% of the time in CloudRoute data, with the remaining 20% landing $75K when the application has narrow scope or projected consumption is small.
The difference between Pear and a non-Sub-Program seed VC is meaningful. A pre-seed VC outside the Sub-Program may write a $1M seed round into a company but its name on an ACE record does not trigger the elevated approval logic; that company is reviewed against the general partner-filed criteria and tends to land $50K–$75K. Pear-backed companies start from the elevated baseline. The marginal $25K of Portfolio award per application is one of the structural reasons Pear founders should not treat AWS credits as an afterthought.
The PearX-versus-Pear-Garage distinction. PearX-graduated companies have the cleanest partner-filed path — they have an incorporated entity, a clear use case, a Pear check on the cap table, and a position in the Pear announce list that AWS reviewers can cross-reference. Pear Garage founders pre-PearX often do not yet have the entity and check needed for the partner-filed path; for these founders the available path is self-serve Activate Founders ($5K) until the entity is registered and the Pear investment closes. Once PearX selection happens (or once a Pear pre-PearX check closes), the partner-filed Portfolio path opens.
The full Pear stack reaches $130K–$155K via self-serve Founders, partner-filed Portfolio at the upper end of the range, Build for Startups, and Bedrock POC. The Pear institutional signal pushes each application toward the ceiling rather than the floor.
Independent of any Pear or partner-filed activity. Public form at aws.amazon.com/startups/credits/. Approval in 24–72 hours, credits land in 3–7 days. Sufficient for early prototyping; runs out fast once a real production deployment begins. Worth filing in parallel with the partner-filed track because the founder time is five minutes and the credits are usable during the partner-filed application window.
PearX founders typically file self-serve Founders during PearX week one or two against the incorporated PearX entity. Pear Garage founders pre-incorporation can file against a personal AWS account or wait until the PearX entity is registered; the second pattern produces a cleaner credit history but the first pattern is reasonable for prototyping.
This is the workhorse track for Pear-backed companies and the place where the institutional vouch matters most. A CloudRoute-routed AWS partner files an ACE record naming Pear VC as the institutional sponsor and the PearX or Pear-backed entity as the customer. The partner attestation plus the Pear institutional signal triggers the elevated approval logic; Portfolio awards consistently land at the upper end of the range ($75K–$100K), with $100K being the modal outcome.
The $100K-vs-$75K calibration. AWS reviewers calibrate the final award size on projected consumption + institutional signal strength. Pear signal is consistent ($75K floor regardless), but the upward adjustment to $100K depends on the projected workload. A B2B SaaS PearX company projecting $5K–$8K/month of AWS spend over 18 months supports $100K cleanly. A research-heavy or pre-product PearX company with modest near-term spend projections may land $75K. The honest distinction is operational — both outcomes are Pear-elevated.
CloudRoute routes Pear-backed companies specifically to partners with prior PearX or Pear Portfolio approvals. The reviewer pattern recognition compounds: partners with prior Pear submissions are recognized, the institutional verification happens faster, and the upper-end approval is more consistent. Partners new to Pear submissions still land approvals, but the wall-clock can stretch 2–3 days longer and the reviewer scrutiny is marginally higher.
Layers on top of Portfolio when there is a distinct, separable workload. PearX companies frequently have a clearly-scoped second workload that justifies a separate Build for Startups application — a new product line, a healthcare-specific compliance push, a developer-tools API surface, a vertical extension of the main product. Build is workload-driven rather than signal-driven, so the Pear signal does not push the award above $25K, but the ceiling itself is consistently attainable for Pear-backed companies because the workload narratives tend to be technically well-scoped (Stanford-derived founders generally write technically-tight ACE descriptions, which the reviewer reads as a positive scoping signal).
Filed by the same partner alongside the Portfolio submission. The partner files Portfolio + Build for Startups + Bedrock POC as three separate ACE opportunity records in the same business week. Each is reviewed separately; each approval is independent. Build for Startups typically approves at $25K within 14–18 days of filing for Pear-backed applications.
AI-eligible PearX or Pear-backed companies layer Bedrock POC on top. Eligibility: a running or planned workload on Amazon Bedrock (Claude, Llama, Mistral, Titan, Nova). The POC plan needs to be specific — use case, model selection, evaluation methodology, projected inference budget over a defined window.
For non-AI-native Pear-backed companies adding AI features (typical: a B2B SaaS product adding a Claude-powered assistant, a healthcare tools company adding a clinical summarization feature, a developer-tools company adding an inline AI completion), Bedrock POC typically lands $25K. The Pear signal does not raise the Bedrock POC ceiling materially because Bedrock POC reviewers are looking at workload specificity more than institutional signal — but the Pear signal does raise the approval probability into the high-80s.
For AI-native Pear-backed companies — the AI agents companies, the LLM tooling companies, the AI infrastructure companies that PearX has been heavily backing in recent batches — $50K Bedrock POC is achievable when the POC scope and projected inference budget justify it. The pattern: pure-play AI companies projecting $15K+/month of Bedrock inference over the POC window land $50K consistently. The marginal $25K is real money for an AI-native company in the first year of operation.
Bedrock POC credits are earmarked: they fund only Bedrock inference and the directly supporting infrastructure (OpenSearch for vector search, S3 for prompt logs, Lambda for orchestration, Bedrock guardrails). They do not cover general EC2 or RDS.
AI-native PearX companies can also apply to the AWS Generative AI Accelerator. Pear-backed AI companies have a notably higher Accelerator acceptance rate than the general pool because Accelerator reviewers favor brand-strong accelerator and pre-seed backing. PearX acceptance for AI applications runs roughly 12–18% versus the general pool's ~5%. Median Pear-backed Accelerator award lands $300K–$500K; standout applications occasionally hit the $1M ceiling.
The Accelerator path runs in parallel with the partner-filed Portfolio + Build + Bedrock POC stack. CloudRoute partners typically advise PearX AI companies to file the stacked path immediately post-PearX-acceptance and apply to the Accelerator on a 30–60-day later cycle, allowing the Bedrock POC results to provide ammunition for the Accelerator application narrative.
A majority of PearX founders come out of the Stanford ecosystem. The pattern shapes both Pear's portfolio identity and the way AWS reviewers read the partner-filed applications.
The Stanford concentration is not accidental. Hershenson is a Stanford EE PhD alum; the firm has run a deep Stanford recruiting program from year one; the PearX cohorts have skewed heavily toward Stanford founders for over a decade. Public PearX cohort listings show roughly 60–70% Stanford-affiliated founders across recent batches (Stanford undergrad, Stanford MS, Stanford PhD, Stanford GSB, or Stanford lab affiliation). The remaining 30–40% are MIT, Berkeley, CMU, Waterloo, or non-degree-ecosystem founders with strong technical track records.
The implication for credit applications. PearX founders with Stanford research backgrounds tend to have technically dense use cases at the time of credit application — work derived from a Stanford lab, a Stanford PhD thesis, a Stanford CS coursework project that became the company. AWS reviewers reading the ACE description register this technical specificity as a positive scoping signal: the projected workload is specific, the inference patterns are defined, the cloud architecture choices are deliberate rather than handwavy. The reviewer is not running an academic credibility check, but the description quality is consistently higher for Stanford-derived applications, which contributes to the upper-end approval calibration.
There is a secondary pattern worth flagging: Stanford-derived PearX companies often have ongoing research collaborations with Stanford labs that involve data pipelines, model training runs, or evaluation infrastructure on AWS. These collaborations frequently justify the Build for Startups award because the collaboration represents a distinct, separable workload from the core product. The honest scoping (the partner writes the ACE description making clear that the Stanford collaboration is a separate workload) lands the Build for Startups $25K cleanly.
And a tertiary pattern: Stanford-affiliated founders are more likely to be familiar with the Bedrock POC mechanic from the outset because Stanford has been an AWS-heavy research institution for years. The founder typically does not need a primer on Bedrock pricing, model selection, or POC scoping; the partner can move directly to filing rather than running an extended scoping conversation.
The non-Stanford PearX founder. The 30–40% of PearX founders who are not Stanford-affiliated follow the same partner-filed path with the same Pear institutional vouch. The institutional signal does not depend on Stanford affiliation — Pear is the vouching institution, not Stanford. Non-Stanford PearX founders land the same $75K–$100K Portfolio approval cadence, the same Build for Startups $25K, the same Bedrock POC outcomes. The Stanford pattern is a description of the cohort, not a requirement for the credit math.
Pear and YC are the two most common comparisons in Bay Area pre-seed conversations and in founder-level credit math. Both are inside the AWS Activate Portfolio Sub-Program; both consistently land Portfolio at the upper end of the range. The differences are structural — cohort size, check size, focus.
The standing credit. YC has automatic $5K Founders credit issuance integrated with the YC batch list; the credit appears in the founder's AWS account within 24–48 hours of account creation without an application. Pear does not have this automatic-issuance integration — PearX founders use the standard self-serve Founders form like any other Activate Founders applicant. The five-minute application is trivial, but the integration gap is worth flagging because it surprises founders who came in expecting the YC-style auto-flow.
The Portfolio approval ceiling. Both Pear and YC are in the Sub-Program; both consistently land $100K Portfolio. In CloudRoute data, YC-backed Portfolio applications approve at $100K roughly 85% of the time; Pear-backed applications approve at $100K roughly 80% of the time. The 5-point gap is operational rather than structural — YC has slightly more reviewer recognition because the YC volume of applications dwarfs Pear's — but both institutions are firmly in the upper-ceiling tier.
The cohort dynamics. YC runs ~250 companies per batch across two batches a year (~500/year). Pear runs ~20 companies per batch across two PearX batches per year (~40/year). Pear is roughly 10x smaller in throughput. The implication for partner-level attention is real: PearX companies get substantially more partner time than typical YC alumni, which feeds into the operational support quality during the credit application window and beyond.
The check size. YC writes $500K MFN SAFE checks for every batch company at standard terms. Pear writes ~$250K equity checks for PearX (sometimes co-leading larger pre-seed rounds with other firms; sometimes leading $1M–$3M pre-seed rounds). The check size affects projected AWS consumption math marginally — a $500K-funded company at YC supports slightly higher projected spend than a $250K-funded company at Pear — but both land at the $100K Portfolio ceiling routinely because the Sub-Program ceiling is a hard cap that neither institution's check size moves substantially.
The vertical focus. YC is a generalist accelerator (B2B SaaS, consumer, fintech, biotech, hardware, climate, deep tech, AI — the full range). Pear is more concentrated: AI/ML, SaaS, healthcare, developer tools, with occasional consumer or fintech adjacencies. The vertical concentration matters for partner matching — a CloudRoute-routed partner for a Pear-backed healthcare company has prior healthcare-vertical track record and HIPAA-readiness experience, which YC-routed partners do not consistently have.
Net realistic stack. YC non-AI: $125K–$150K. Pear non-AI: $130K–$155K. The Pear stack is marginally higher because the Bedrock POC for non-AI-native Pear companies tends to land at $25K rather than $20K (Pear's healthcare and dev-tools workload narratives are technically specific enough to support the $25K Bedrock POC ceiling more consistently). For AI-native companies, both stacks reach $400K–$650K combined with the Generative AI Accelerator path.
Sequoia Arc is the closest direct comparison to PearX in the Palo Alto pre-seed accelerator landscape. Both run small cohorts; both write meaningful checks; both have institutional vouching power. The credit-mechanic differences are worth understanding for founders deciding between the two or for founders evaluating their existing portfolio status.
Sequoia Arc is the pre-seed accelerator program run by Sequoia Capital. It launched in 2022 and runs roughly 15 companies per batch across the Sequoia US and Sequoia Southeast Asia geographies. Check size is $1M equity for around 6–9% ownership, which is substantially larger than Pear's $250K standard PearX check. The cohort is even more concentrated than Pear's — Sequoia Arc is selectively recruited from the Sequoia partner network rather than from a public application funnel.
On the AWS Activate side: Sequoia Capital is in the Portfolio Sub-Program at the top tier; Sequoia Arc inherits that institutional standing for Arc portfolio companies. Sequoia Arc-backed Portfolio applications approve at $100K consistently — comparable to Pear and YC. The institutional signal is essentially identical at the upper-ceiling level. The differences appear at the margin: Sequoia's broader corporate-cloud relationship with AWS provides slightly faster reviewer cross-referencing, but the practical wall-clock difference is a couple of days at most.
The check-size difference does shift the Portfolio award calibration slightly. A $1M Sequoia Arc check produces a 12-month consumption projection that supports the upper end of the Portfolio ceiling more cleanly than a $250K PearX check. Both land $100K, but the $1M-funded Arc company often has the projection room to argue for additional Build for Startups workloads that the $250K-funded Pear company may not have at the same point.
The honest framing: both Pear and Sequoia Arc are upper-tier vouching institutions in the AWS Activate Portfolio Sub-Program. Founders evaluating the two should make the decision on the dimensions that matter for their company (cohort culture, partner fit, vertical focus, ownership percentage, follow-on dynamics), not on AWS credits. The credit math is functionally equivalent at the upper ceiling.
A note on follow-on dynamics. PearX companies frequently raise seed rounds led by Sequoia, Founders Fund, Lightspeed, or General Catalyst within 12 months post-PearX. Sequoia Arc companies frequently extend within Sequoia (Sequoia leads the seed directly) or raise with adjacent firms. The follow-on signal in subsequent credit applications (when the company eventually re-engages a partner for, say, a Bedrock POC re-up or a Build for Startups extension) is comparable in both cases.
PearX week 1 or 2 (or post-PearX-acceptance) — PearX kickoff. Entity incorporated (typically Delaware C-corp), Pear check landed, AWS account creation in progress. Standard PearX residency is intensive; founders are commonly heads-down on product. Credit timeline runs in parallel.
Day 0 — Submit a CloudRoute inquiry indicating Pear-backed status (PearX batch number, or Pear-Garage-graduated-to-PearX, or Pear pre-PearX check). Provide rough vertical (AI, SaaS, healthcare, dev tools) and target AWS region.
Day 1 — Routed within 24 hours to a partner with prior PearX or Pear-portfolio approvals. CloudRoute matches on Pear track record + vertical (healthcare partners for healthcare PearX companies; AI/ML partners for AI-native; dev-tools partners for dev-tools companies).
Day 2 — Discovery call (30 minutes). Partner scopes Portfolio + Build for Startups + Bedrock POC applicability. Verifies Pear backing through public PearX cohort listings or direct Pear confirmation if needed.
Day 3–5 — Founder provides company info, AWS account ID, use case paragraphs, deck, and PearX cohort details. Self-serve Activate Founders also filed in parallel (5 minutes). ~45 minutes total founder time across all four applications.
Day 6–7 — Partner files three ACE records (Portfolio + Build for Startups + Bedrock POC) within the same business week. Each names Pear VC as the institutional sponsor and PearX cohort as the eligibility evidence.
Day 12–16 — Self-serve Founders approval lands first ($5K). Portfolio approval lands next ($75K–$100K — modal $100K for Pear-backed applications). Build for Startups approval by Day 16–20 ($25K).
Day 18–22 — Bedrock POC approval lands ($25K typical, $50K for AI-native). Full stack visible in AWS Billing dashboard under "promotional credits." $130K–$155K total balance auto-applies against monthly invoice from the next billing cycle.
Optional Day 60+ (AI-native PearX only) — Apply to Generative AI Accelerator. Selection in 60–90 days; additional $200K–$1M for accepted PearX AI applications.
One representative pattern from the recent CloudRoute pipeline. Anonymized to protect company identity, with the numbers presented honestly.
The company. PearX Winter 2026 batch graduate. Two co-founders, both Stanford CS MS alums (one ex-Apple ML, one ex-Notion). Product is an AI-native developer tools company building inline Claude-powered context awareness for codebases — the company sits at the intersection of dev tools and pure-play LLM application infrastructure. Standard PearX check of $250K landed at batch start; two months post-batch, the company closed a $4.5M seed round led by Founders Fund with participation from Pear and a few senior individual operators. Engineering team grew from 2 to 7 across the batch and immediately post-batch.
The credit conversation entry point. The founders had used the standing $5K self-serve Activate Founders credit during PearX (filed via the public form during PearX week 2; landed in 5 days). They were burning through it quickly as the Bedrock inference and the vector-search-heavy retrieval pipeline ramped up. By month 4 of operating the production stack, they were running $4K/month on Bedrock alone, with another $2K/month on the supporting infrastructure (OpenSearch, S3, Lambda, RDS). They submitted a CloudRoute inquiry referencing PearX W26 batch and the AI-native dev-tools positioning.
The routing and scoping. CloudRoute routed within 14 hours to a US-East partner with prior PearX track record (the partner had filed Portfolio for three previous PearX cohorts) and prior dev-tools-vertical work. The partner discovery call was 35 minutes; the partner scoped Portfolio at $100K (Pear vouch + clear projected consumption + Founders Fund seed signal landing concurrent), Build for Startups at $25K (the partner identified the customer-onboarding-and-billing workload as distinct from the core LLM product), and Bedrock POC at $50K (AI-native, projected inference budget over the POC window of around $20K/month, well-scoped evaluation methodology built around the company's existing eval harness).
The filing. Partner filed all three ACE records on Day 6 of the engagement. Founder provided company info, AWS account ID, the seven-paragraph use case description that the partner had co-drafted, the latest deck, and the Pear and Founders Fund confirmations. Total founder time across the engagement: 47 minutes.
The outcome. Portfolio approval landed at $100K on Day 14 (12 business days post-filing). Build for Startups approval landed at $25K on Day 18. Bedrock POC approval landed at $50K on Day 22. Combined stacked credits: $175K (the self-serve $5K had already burned down to roughly $1K by the time the Portfolio replaced it, so the effective additional credit was $174K). The founders also applied to the Generative AI Accelerator on Day 35 of the engagement; selection arrived 81 days later with a $400K Accelerator award (above median for the cohort; tightly-scoped AI commercial trajectory). Combined credit position across stacked + Accelerator: $575K. Total cost to the company: $0.
The honest scoping. The founders did not need any of the credits to keep the lights on — the $4.5M seed round was already closed and the runway was healthy. The credits compressed the cloud spend line item on the next 18 months of P&L by roughly half, which freed up budget for an additional engineering hire that would otherwise have been deferred. The actionable insight: even healthy-runway PearX companies should run the partner-filed path because the math is non-trivial even when liquidity is not the constraint.
What stopping at the self-serve Founders credit vs pursuing the full Pear-vouched path actually costs.
| Variable | Self-serve $5K only | Full Pear stack |
|---|---|---|
| Total credits | $5K | $130K–$155K (non-AI); $330K–$1.15M+ (AI-native with Accelerator) |
| Application time | ~5 min | ~45 min total across four applications |
| Wall-clock to balance | 3–7 days | 18–22 days from inquiry |
| Runway covered | 1–2 months at PearX-stage burn | 14–20 months at post-PearX burn |
| Pear institutional signal | Not invoked | Named on ACE record; triggers upper-ceiling logic |
| Bedrock workload supported | Limited (general pool) | Dedicated Bedrock POC pool ($25K typical, $50K AI-native) |
| Generative AI Accelerator eligibility | Yes (separate path) | Yes; can pursue in parallel |
| Cost to founder | $0 | $0 |
Situation: PearX Winter 2026 batch graduate. AI-native developer tools (inline Claude-powered codebase context). $250K PearX check, $4.5M Founders Fund-led seed closed two months post-batch. Burning $6K/month on Bedrock and supporting infrastructure by month 4. Standing $5K self-serve credit nearly depleted. Engineering team grew from 2 to 7. Wanted to maximize stacked credits and prepare a Generative AI Accelerator application.
What CloudRoute did: Routed within 14 hours to a US-East partner with three prior PearX cohort Portfolio approvals and dev-tools vertical track record. Partner filed Portfolio ($100K, Pear institutional vouch + Founders Fund concurrent seed signal), Build for Startups ($25K for the customer-onboarding-and-billing workload as a distinct project), Bedrock POC ($50K, AI-native with $20K/month projected inference budget and a tight evaluation methodology built around the company's existing eval harness). All three ACE records filed on Day 6.
Outcome: Stacked credits applied within 22 days: $175K total. Generative AI Accelerator application filed on Day 35; acceptance arrived 81 days later with $400K award (above median). Combined credit position: $575K. Total cost: $0. Founder time across all activities: ~47 minutes for the credit applications themselves, plus the 4–6 hours of Accelerator application time.
engagement window: 4 months total · founder time: ~6 hours · credits secured: $575K · cost: $0
CloudRoute routes PearX and Pear-backed companies to AWS partners with prior PearX cohort approvals, matched on vertical (AI, SaaS, healthcare, dev tools). Customer pays $0; AWS funds the engagement.