There is a comfortable story founders tell about accelerators, which is that you join one, absorb some mentorship, and emerge with a warm introduction to money. The version we lived through was less comfortable and more useful. The programme did not give us investor-readiness; it gated it. Readiness was a state you were only granted after clearing a stack of separate thresholds, each with its own definition of done, and the programme simply would not treat you as ready-to-pitch until every one of them was cleared. This note is about that gating, written from the product side. It is not an account of what we built during the six months, which we have described elsewhere; it is an account of what the readiness process itself demanded of us while we were building, and why the demand turned out to be worth more than any individual lesson inside it.
The shape is easy to state and harder to live. The programme ran six months. Graduation required completing at least 80% of more than 100 hours of interactive curriculum. It required attending five of the six two-hour mastermind sessions. Reaching the investor-relations stage for a Pre-Seed company required a floor of pitch work: a minimum of two pitch-deck reviews and two coaching workshops, one pitched to three minutes and one to nine, so you were rehearsed for both the elevator and the room. And it required passing a pre-IR audit whose most quietly ruthless line item was a honed elevator pitch of 60 to 80 words. None of these is exotic on its own. What makes them a gauntlet is that they are joined by AND. Clearing three of the four does not make you three-quarters ready. It makes you not ready, with a good excuse.
Gating is a schedule you did not set yourself
The reason gating works as a forcing function is that founders are extremely good at deferring exactly the work these gates measure. Curriculum hours, rehearsed pitches, a disciplined word count on the story: all of it is the kind of task that feels safe to push a week because the product is on fire this week, and the product is always on fire. Left to our own prioritisation we would have shipped model improvements and let the fundraising narrative stay a rough draft until it was urgent, which is to say until it was too late to be good. The gate removes that option. It converts a soft intention into a hard due date that someone other than us is enforcing, and it does so far enough ahead of the actual investor conversations that there is still time to be bad at the pitch, get told, and fix it.
This is the part the empirical work on accelerators actually supports. Gonzalez-Uribe and Leatherbee found that it was the schooling component of acceleration, not the capital by itself, that moved subsequent venture performance [2], which is the case for treating a curriculum gate as more than box-ticking. Hallen, Cohen, and Bingham make the broader argument that what an accelerator does is compress and schedule intense consultation and pressure rather than deliver any one magic input [3]. From the inside, that is exactly what the gating felt like: not a body of secret knowledge, but a calendar we could not renegotiate, imposed on the founder work we would otherwise have starved.
The gates run in parallel with the build, and that is the whole point
The tempting misreading is that the readiness gauntlet is a phase, something you do after the product is far enough along. It is not, and treating it that way is how startups arrive at demo day with a strong demo and an unrehearsed story. Every one of these gates runs concurrently with the engineering that does not pause for them. We were training models, iterating on the digitisation pipeline, and handling the ordinary chaos of a small team the entire time the curriculum clock, the mastermind attendance count, and the pitch-review floor were also ticking. The gauntlet is a demand on the founders' attention that is levied on top of the build, not carved out of it.
The exhibit below is that parallelism made literal. Four lanes are the readiness gates, each with its sourced threshold; a fifth lane underneath is the product build, running the full six months without interruption. Drag the week lever and each gate clears when its threshold is met, but the verdict on the right stays dark until all four have cleared at once. That single lit state is the argument: readiness is the conjunction, and the conjunction has to be assembled while the product lane keeps moving.
The mastermind gate is a good illustration of why the parallel structure matters. Five of six two-hour sessions is not a heavy time cost in the abstract, twelve hours across half a year. But those sessions land on a monthly cadence, which means the only way to clear the gate is to keep showing up on the programme's schedule rather than your own, month after month, while the sprint you care about is mid-flight. The gate is cheap in total hours and expensive in the specific thing it demands: that you protect a recurring slot for the founder work no matter what the build is doing that week.
The pre-IR audit is where padding goes to die
Of the four gates, the pre-IR audit taught us the most, and the line that did it was the 60 to 80 word elevator pitch. A word ceiling is a brutal editor. You cannot hide a fuzzy value proposition inside 70 words; there is no room for the qualifying clause, the second use case, or the adjective doing the work a fact should do. Getting under the ceiling forced a decision we had been avoiding, which was what the single most important sentence about the company actually was. Everything that survived the cut was load-bearing. Everything we lost, we did not miss. The audit was not testing whether we could talk about the product. It was testing whether we could stop.
That is the general character of a good readiness gate: it does not reward effort, it rewards a specific finished state, and the state is defined tightly enough that you cannot fake your way past it with volume. Two pitch-deck reviews is a floor precisely because one review lets you rationalise the feedback away and a floor of two makes you show that you changed something. The three-minute and nine-minute coaching formats exist because investors ask for the story at both lengths and a founder who is only rehearsed at one will improvise the other badly. The gate encodes the real conditions of the room.
What the gauntlet is actually for
The honest summary is that the accelerator did not make us investor-ready in the sense of teaching us a thing we did not know. Most of the individual lessons were things a diligent founder could have read. What it did was refuse to let us call ourselves ready until we had, in parallel with building the product, done the founder work we would have deferred, at a standard we would not have set for ourselves, on a schedule we did not control. The gating is the product. The curriculum, the masterminds, the reviews, and the audit are the four hard edges of a single forcing function whose job is to make sure that when a startup finally stands in front of capital, the readiness is real and not asserted. The accelerator is, in the taxonomy Cohen and Hochberg set out, a fixed-term cohort programme ending in a pitch [1]; the gauntlet is what turns that fixed term into pressure that lands.
Limitations
This is one cohort's experience of one programme's gates, read as a forcing function, and it should not be mistaken for a general claim about accelerators. The thresholds we describe are the real requirements we cleared, but which gates matter most is a property of a specific programme and a specific stage; a later-stage company or a different programme would face a different stack. The empirical work we lean on establishes that the curriculum component and the scheduled-pressure mechanism carry real weight on average [2] [3], not that they helped our company in particular, which is an anecdote and not evidence. The exhibit's per-gate due weeks are an illustrative scheduling assumption used to animate the parallelism; the thresholds, the programme length, the session hours, the coaching-pitch lengths, and the mentorship and mentor-introduction figures are the sourced facts, but the exact week each gate falls due varied in practice. And clearing the gauntlet is a readiness condition, not an outcome. Being investor-ready by these gates says nothing about whether the round closes, which depends on the market, the product, and a great deal that no accelerator schedule can gate.
References
[1] Cohen, S., and Hochberg, Y. V. Accelerating Startups: The Seed Accelerator Phenomenon (2014). SSRN working paper. The definition of the accelerator as a fixed-term, cohort-based programme of education and mentorship culminating in a public pitch event. https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2418000
[2] Gonzalez-Uribe, J., and Leatherbee, M. The Effects of Business Accelerators on Venture Performance: Evidence from Start-Up Chile. The Review of Financial Studies 31(4) (2018), pp. 1566-1603. The finding that the schooling or curriculum component, not the cash alone, is what moves subsequent venture performance. https://academic.oup.com/rfs/article/31/4/1566/4104616
[3] Hallen, B. L., Cohen, S. L., and Bingham, C. B. Do Accelerators Work? If So, How? Organization Science 31(2) (2020), pp. 378-414. The argument that the mechanism is intense, time-compressed, scheduled consultation and pressure rather than any single input. https://pubsonline.informs.org/doi/10.1287/orsc.2019.1304
