2000X / Com2000  /  Insights

What We Look for in Accelerator Applicants

Application season produces the same question every time: what does an accelerator actually want to see? The answer is less mysterious than it looks, and more specific than a good deck.

At 2000X and Com2000, the evaluation starts with three signals. None of them depends on how large the team is or how ambitious the roadmap sounds.

1. A clear reason this needs Web3

The first question is whether the problem genuinely requires a blockchain. A conventional database is often faster, cheaper, and easier to explain. That is not a criticism; it is a filter.

Strong applications can say exactly what changes when the system is trust-minimized, who needs that property, and why existing alternatives fail them. "We are building on Web3" is not an answer. "Counterparties will not accept a centralized ledger for settlement" is.

For real-world asset projects, this question also includes jurisdiction, custody, and reporting. Applicants who understand those constraints impress more than those who treat them as details to solve later.

2. Evidence the team can ship small

Markets change faster than annual plans. The teams that survive are the ones that can release a narrow version, learn from real users, and adjust.

We look for evidence, not promises: a working prototype, a shipped feature, a documented decision that changed after feedback. The scale does not matter. The loop does.

This is where AI changes incubation. A small team can now cover research, documentation, code generation, and community replies that used to require more people. The useful question is no longer team size but leverage.

3. Willingness to work with partners

The most underestimated signal. Early Web3 growth depends on exchanges, auditors, legal counsel, and distribution partners. A team that tries to own every layer will move slowly and exhaust itself.

Co-opetition is not a slogan here. Sharing standards and partner knowledge makes the whole category more credible, and it makes each team easier to work with. Applicants who can describe what they would gladly hand to a partner stand out.

What the application should include

Keep it short and concrete:

  1. The problem and why Web3 is necessary.
  2. What has been shipped so far.
  3. The single hardest partner or compliance question you face.
  4. What you would contribute to the cohort, not only what you need from it.

A specific question is more useful than a broad pitch. It tells us how we can help and whether the team thinks in terms of execution.

After acceptance

The first weeks are spent turning the application into a working plan: which partners to approach, which compliance questions to resolve, and which piece of the product to narrow. AI-assisted research speeds up the routine parts; human judgment still decides the order.

Learn more at https://2000x.net/ and https://com2000.org/. Related initiatives: https://rudao.org/, https://tonytong.cc/, https://hkba.net/.

The Ecosystem RuDao - Confucian Co-opetition Tony Tong Official 2000X AI+Web3 Accelerator Com2000 AI Web4 Incubator Hong Kong Blockchain Association