Evaluating the Impact Projects Accelerator 2.0: A Founder’s Due Diligence Framework

The Impact Projects Accelerator 2.0 in Ukraine has opened applications, according to a September 21 fundsforNGOs listing. The confirmed surface: a program name, a "2.0" iteration tag implying a prior cohort, and a Ukraine geography flag. The hidden surface: no deadline, no cohort size, no equity terms, no duration, no sector filter, no funding amount.

For ClimateTech founders scanning the market, the bottleneck is not the application form. It is the absence of parameters required to size the trade.

What fundsforNGOs actually publishes

One verified data point: the iteration marker. Every other input sits below the public line. The listing mirrors an aggregator pattern — index, do not validate. fundsforNGOs reproduces titles submitted from outside sources. Treat the entry as a pointer to an external system, not as a program specification.

The diligence load therefore transfers to the applicant. Before founder-hours are spent on a written submission, the underlying program must surface its terms in writing. A real accelerator will publish, or supply on request, the following:

1. Cohort size and selection ratio.

2. Weekly founder time requirement and total program length.

3. Equity taken, if any, and at what valuation cap.

4. Grant, stipend, or cash component, currency, and disbursement schedule.

5. Sector and geography eligibility — confirm the Ukraine focus and any ClimateTech fit.

6. Mentor network and follow-on investor map.

7. Reporting cadence and KPIs the program tracks.

8. Outcomes from Accelerator 1.0: companies funded, capital raised, exits or pivots.

Items 1 through 6 govern burn rate and runway drag. Items 7 and 8 govern the program's credibility as a signal in your investor deck.

The unit-economics framing

A ClimateTech founder applying without items 1 through 4 locked is running blind on capital and time allocation. Applying without item 8 is running blind on track record. An aggregator listing supplies neither input.

If the program is genuine, these parameters exist in a partner deck, a PDF, or behind an email gate. The task is to extract them in plain text before the application form opens.

Binary checklist before submit

• Seven of the eight parameters verified in writing → proceed with the application.
• Five or fewer verified → request the missing terms first. Do not write the application.

States between the two are noise. The equation does not balance on partial inputs.