When Program Design Becomes Value
The positive average for startup accelerators hides a design problem: a program's features do not produce value independently of the venture and the ecosystem around it. This chapter examines cohort size, duration, services, sponsorship, venture size, and institutional setting as parts of one operating system. The practical judgment is not which feature is “best,” but what each feature enables, what it costs, and whether a particular venture can use it before the program ends.
The meta-analysis is useful here because its high heterogeneity invites a closer look at moderators. Its subgroup results do not amount to controlled experiments on program design, and some groups are small. They are signals about where the relationship between participation and performance changes—not universal specifications for building an accelerator.
The design trade-offs inside a cohort
Cohort size: network density versus individual attention
The cohort is the accelerator's central interface. It determines how many founders can learn from one another, how widely introductions can travel, and how much mentoring attention must be shared. A small batch makes individualized support easier in principle. A large batch can create more peer connections, more varied experience, and a larger pool of potential collaborators. Neither effect is automatic: a large group can become anonymous, while a small group can lack the knowledge or network diversity needed for a difficult problem.
In the meta-analysis, studies of cohorts with at least 50 ventures have a positive mean effect of r = 0.187. The subgroup with fewer than 50 ventures is not statistically significant, and the difference between the two cohort-size groups is significant. This result runs against the simple expectation that smaller groups must work better because each founder receives more attention. The authors suggest that peer effects, knowledge exchange, collaboration, and the pressure created by competition may outweigh the loss of individualized support in larger cohorts.
That interpretation is plausible, but the result does not prove that increasing a batch to 50 or more will improve a program. The subgroup estimate is still a correlation across studies. Large cohorts may differ from small ones in unmeasured ways: they may have stronger brands, more capital, broader networks, or different admission standards. A large group can also require a different support architecture. If mentor access, feedback channels, and peer matching remain unchanged while the cohort expands, the interface may overload even if the average result in the literature is positive.
The design question is therefore about the division of labor between the cohort and the program staff. If peer learning is expected to carry more of the load, founders need enough shared vocabulary and a reason to exchange useful information. If mentors are expected to compensate for cohort scale, the program needs a way to route specialized advice rather than offering the same conversations to everyone. Cohort size changes where value is produced; it does not determine whether value is produced.
Duration: time to act versus intensity of pressure
Time affects a different part of the mechanism.