Rejected by an accelerator? What to do in the next 90 days.
A practical plan for the three months after a no from Y Combinator or another program: what to learn, what to build and when to ask again.
An accelerator rejection feels like a verdict on the company. It is usually a judgment made quickly, on thin evidence, by people choosing a small number of companies from many. The next 90 days decide whether it becomes a setback or a turning point.
First, what a rejection is
Selective programs say no to most applicants. That is how they work, not a special statement about you. Some explain their decisions: Y Combinator’s application page says that if it declines an application, it will explain why. Many programs say nothing at all.
A first no is also far from final. Y Combinator’s own FAQ says that in a typical batch about half the companies applied more than once before being accepted, and it encourages founders who were turned down to apply again.
Either way, the rejection is information about how one group of people read your application at one moment. Our essay Rejection is data. It is not destiny. sets out a simple way to sort it: was it a weakness in the company, a mismatch with the program, a timing problem, or a failure of imagination on their side? The plan below assumes you start by being honest about which.
Days 1–14: read the no properly
Give yourself a day. Then write down, in one page, what you think the rejection was about. If you received a reason, copy it in word for word. If you did not, list the three things a sceptical reader would most likely doubt about your application.
Then test that list against people who know the company. Ask two or three users and one person who has built a company before: “If you had to bet against us, what would you bet on?” Their answers are usually more useful than the rejection itself.
Finally, reread your application as if you were the reader. Was it specific about what exists today? Did it show evidence or only describe intentions? Founders often discover that the application undersold what they had actually done.
Days 15–30: choose three tests
Turn the doubts into tests. Each should be small enough to finish within the quarter and clear enough that you will know the result. For example:
- If the doubt is demand: get ten target users to try the product and record what they do in the second week, not just the first.
- If the doubt is willingness to pay: ask for money, even a small amount, from a defined group, and count who says yes.
- If the doubt is the team: close the gap you are weakest on, whether that means a co-founder conversation, a first hire or a skill you learn yourself.
- If the doubt is the market: talk to enough buyers to put a defensible number on how many there are and what they spend today.
Write the three tests down with a date next to each. This becomes your plan and, later, the strongest part of your next application.
Days 31–75: build evidence, not a better pitch
This is the long middle, and the place where founders most often drift. It is tempting to spend it improving the deck, collecting advisors or entering competitions. Some of that is fine. Most of the time should go to the tests.
Keep a short weekly log: what you shipped, who you spoke to, what changed. It takes ten minutes and does two jobs. It keeps you honest about whether the company is moving, and it gives you a record you can show. Evidence of movement over a few months is one of the hardest things for any reader to ignore; it is one of the five things we look for.
If a test fails, treat it as a result. A clear negative result in week six is far better than an ambiguous one in week twelve. Some ideas should change. Changing because the evidence says so is a strength, and it reads that way to experienced selectors.
Days 76–90: decide where to go next
By now you know more than you did when you applied. Use it to decide on the next step, rather than defaulting to the same application.
Reapply if the program fits and your evidence has clearly changed. Lead with what is different since last time. John O’Nolan’s essay “A decade after being rejected by YC” is a reminder that one decision does not settle the story.
Apply elsewhere if the rejection was a mismatch. Programs differ a great deal in stage, sector, location and what they offer. Our guide to alternatives to Y Combinator sets out how to compare them using each program’s own pages.
Go straight to investors if the company has outgrown the need for a program. That needs introductions; our guide to getting investor introductions at pre-seed explains how to earn them.
You are not the only one
Rejection by accelerators is common enough that founders have built projects around it. Rejected By YC is a weekly audio show of interviews with founders YC turned down. ReverseYC is a public collection of YC-rejected startups with evidence of what they did next; its rejections are self-reported and it is not affiliated with YC. Neither is connected to Rejected Club. Both are useful company in the first few weeks.
Where Rejected Club fits
Rejected Club reads applications for evidence, not pedigree. You do not need a rejection story to apply, and a rejection is never the qualification. If the 90 days have left you with a company that is moving, a clear sense of what is weak and evidence you can show, apply. How selection works explains what happens next.
Sources
- Y Combinator: Apply to YC
- Y Combinator: FAQ
- John O’Nolan: A decade after being rejected by YC
- Rejected By YC (Substack)
- ReverseYC on Product Hunt
Pages read in November 2026. Programs change their terms; check each source before you rely on it.
Search wider. Judge deeper. Build earlier.