I kept applying to accelerators until I asked a better question

For a long time, applying to startup accelerators felt like a completely normal habit.

If you are an eager builder working on software, the logic seems obvious: you build prototypes on nights and weekends, an application window opens, and you submit your project. If you get rejected, you shrug, keep writing code, and apply again to the next cohort.

By early 2025, I had applied to Antler Singapore approximately twice before.

Those earlier applications had not made it very far. I had never reached a partner or interview stage, and I did not think much of it. Rejection felt like part of the background noise of trying to build things on the internet.

Then, in late April 2025, an email landed in my inbox:

The email invited me to a 30-minute interview with Rufus to move forward in the selection process. The residency was less than a month away, and I needed to pick a slot within three days.

I went into that interview thinking about how to get accepted.

I came out of it thinking about something much deeper: whether I was even building the kind of company that belonged in a venture-backed portfolio.

I used to apply anyway

When you are starting out as a founder, accelerators look like the universal gatekeepers of progress.

You read about demo days, venture rounds, and founder cohorts, and it is easy to assume that getting accepted into a reputable program is the official moment a project turns into a real company.

Because of that assumption, my default reaction whenever an application opened was simple: why not apply?

There was no downside. Submitting a form took an evening. If the committee liked the project, you got resources, mentorship, and a potential cheque. If they passed, you lost nothing except a few hours of typing.

What I did not understand at the time was that accelerators and venture funds are not generic test centers giving out grades on your work ethic.

They are investment businesses with specific economic constraints. They are looking for very particular founder traits and company profiles that match their fund model.

Going through the interview was the first time I felt that distinction in person.

The interview was not about my app

When I joined the call, I expected a standard product pitch.

I had prepared to explain what the product did, walk through the user flow, talk about the features I had built, and describe my technical stack. At the time, the project I had applied with was a very early social application, conceptually similar to a microblogging platform.

What surprised me was how little of the conversation focused on that specific product.

At least in my experience of the call, the evaluation seemed much more interested in how I thought than in hearing a rehearsed deck. Rather than digging into my user interface or UI design, the interviewer presented me with a hypothetical problem around scaling and business execution, testing how I would break down an unfamiliar challenge in real time.

That approach matches Antler's broader "Day Zero" and founder-first philosophy.

Because Antler often backs founders at the pre-idea or inception stage, their selection model is designed to evaluate raw founder characteristics, such as structured problem-solving, resilience, and communication, rather than whatever prototype an applicant happened to upload that week.

The idea might change ten times during a residency. The person has to carry the company regardless of the pivot.

I was not particularly good at that style of interview

Looking back candidly, I did not perform especially well.

Rapid-fire, verbal case breakdown under interview pressure does not play to my natural strengths.

When I work on a problem, I tend to do my best thinking asynchronously. I like sitting with a codebase, pulling apart edge cases over days, testing assumptions against real user behavior, and building deep, localized domain context. When you put me on a live video call and ask me to architect a multi-variable business solution on the spot, my answers are slower and less structured than someone trained in consulting or fast verbal debate.

I still do not know which factors mattered most to their final decision:

• maybe I was too slow at articulating my framework;
• maybe my reasoning lacked the executive clarity they look for in early-stage leaders;
• maybe my mental model was too narrow;
• maybe it was just an off day.

The important thing was not diagnosing their exact internal scoring. The important thing was the mirror it held up.

There is a big difference between being able to build a functional piece of software and being able to quickly communicate high-level strategic trade-offs to an investor. That interview showed me a clear dimension where my instincts were unpracticed.

Accelerators are selecting for a specific model

The rejection that followed did not sting the way earlier rejections had.

Instead, it made me step back and examine the venture model itself.

When an accelerator turns down an applicant, it is easy for founders to fall into one of two traps:

1. Defensiveness: "They did not understand what I am building."
2. Despair: "My project is worthless and I should quit."

Neither of those conclusions is useful.

Venture capital operates on power-law economics. A venture fund invests across a portfolio of dozens of early-stage startups, knowing that the vast majority will fail or return modest capital. To generate a return for their limited partners, a small handful of winners must grow exponentially and return the entire value of the fund.

That means an investor is not simply asking:

"Is Kenneth a hardworking builder who can ship a useful app?"

They have to ask:

"If this founder succeeds, does this company have a credible path to becoming a multi-hundred-million-dollar category leader?"

If your product is a neat niche utility, a local business, or a small software tool, it might become a wonderful, profitable bootstrapped business. But it might be completely unsuited to the venture capital asset class.

Selection is an evaluation of fit against an economic model, not a universal stamp on your competence as a creator.

I was trying to build another social network

Once I understood the investor's perspective, I had to look honestly at what I was actually trying to build.

At the time of that application, my project was an early social microblogging product.

Technically, building a social app is fun and relatively straightforward:

• you set up a Postgres database for posts and user profiles;
• you create a timeline query;
• you wire up websockets for live notifications;
• you design a clean mobile feed.

Building the software is the easy part. Building the network is nearly impossible.

Consumer social networks are defined by extreme network effects. A social platform with five active users is essentially broken, no matter how clean the code is. To succeed, you have to solve two brutal problems simultaneously:

1. Distribution liquidity: You need millions of people to show up at the exact same time so the feed feels alive.
2. Switching costs: You have to convince people to abandon platforms where their entire social graph already lives (X, Instagram, TikTok) to post into an empty room.

I was thinking entirely about whether I could write the code and get the first few signups. I was barely thinking about why anyone would stay once the novelty wore off.

The one million dollar thought experiment

To see how naive my approach was, I later ran a simple thought experiment:

Suppose Antler or any other venture fund had written me a cheque for one million dollars on the spot for that social app. Would that money have made me capable of beating an incumbent like X or Threads?

The honest answer is no.

One million dollars would have paid for server bills and bought a few years of personal runway. But capital cannot manufacture a structural reason to win.

Money cannot buy:

• an organic distribution advantage;
• an authentic community wedge;
• a novel consumer behavior that incumbents cannot copy;
• a founder with unique, hard-earned domain insight into the market.

If the underlying premise of a startup relies on hoping that massive paid marketing or sheer effort will overcome incumbent network effects, extra funding just accelerates how quickly you burn cash before reaching the same dead end.

Capital is an amplifier of an existing advantage. It is not an advantage on its own.

The better questions

That realization changed how I evaluate everything I build today.

I used to start every project by asking fundraising questions:

• Can I get into an accelerator?
• Can I raise a pre-seed round?
• Can I convince an investor that this space is exciting?

Now, I try to ask operating questions before I ever write a line of pitch copy:

1. Why this problem? Am I picking something I understand deeply, or am I just copying a popular category?
2. Why me? Do I have an unfair advantage, technical perspective, or distribution channel that makes me suited to solve this?
3. What is the wedge? Can this product start extremely small, deliver intense value to a tiny group of users, and expand without needing ten thousand people online at once?
4. Does this need venture funding? Can I build and operate this profitably on my own first?

If a software product can be developed leanly and generate real revenue without massive upfront infrastructure, staying bootstrapped buys something far more valuable than an early investment cheque:

It buys the time and freedom to figure out whether the product deserves to exist at all.

Picking a game you have some right to win

Applying to Antler Singapore three times did not result in a residency spot or a venture-backed demo day.

What it gave me was much more valuable: it broke the illusion that raising money is equivalent to building a real business.

I still have an enormous amount of respect for the founders and investors who operate in the venture ecosystem. When a massive problem requires deep technical research, specialized hiring, or heavy infrastructure before the first dollar of revenue can be earned, venture capital is an indispensable tool.

But funding is a tool, not validation.

Before asking whether an investor might fund your company, you should probably be able to explain why the company has a reason to win without them.

Back to work.