How incubators actually run programmes, and where each way stops working

What most incubators run today, and it is not a stupid choice. It costs nothing, everyone already knows how to use it, and for a first cohort of fifteen applications it genuinely works.

It stops working at three specific points, and they are worth naming because they arrive in the same order every time. First, evaluation: two reviewers scoring out of ten with no shared rubric produce numbers that look comparable and are not, and nobody notices because the average still computes. Second, document chasing: the state of 'what is still outstanding' lives in your sent folder, so it is only as good as your memory. Third, the audit question: eight months later a funder asks how a cohort was selected and where a specific tranche went, and a spreadsheet has no concept of who changed what, when.

The tell that you have outgrown it is usually not volume. It is the first time somebody asks a question about the past that you cannot answer without reconstructing it.

Outgrowing it does not mean throwing it away. With EcoSync the sheet you keep today imports with its dates, schemes and founders, the portfolio can still be worked on as a sheet - now with a history on every cell - and any tab exports back to Excel.

Airtable, Notion, a project board. A real step up: you get structure, views, and something that looks like a pipeline without writing code.

The limit is that they model records and tasks, not programmes. Weighted multi-evaluator scoring can be faked with formulas until you need the per-evaluator breakdown retained. An external panel member cannot be given access to one programme's applications and nothing else, because permissions are per base or per workspace, not per module and per role. And money is where it gets uncomfortable - tracing a grant from its source, through a programme allocation, to a specific tranche that reached a specific startup, with over-allocation blocked at the point of commitment, is not a thing you configure. It is a thing that is built or is not.

These tools are excellent, and if what you need is a better list, they are the right answer and cheaper than us.

Several products do this, including this one. The category exists because programmes have shapes that general tools do not model: cohorts and batches, an application that moves through states rather than being done or not done, panels who are not staff, funding that arrives in tranches against a sanctioned amount.

The questions worth asking any of us are the same four, and they are more useful than a feature grid: Can an external evaluator be scoped to one programme without a full login? Is the per-evaluator scoring breakdown kept, or averaged away? Can you trace a specific rupee from grant to startup, and is over-allocation blocked where the commitment is made or reconciled afterwards? And can you get your data out - as a feed, not a CSV somebody exports by hand?

Ask us those and we will answer with specifics. Ask anyone else and the answers should be just as concrete.

Common at universities with a software department, and occasionally the right call - if the requirement is genuinely unusual and you have people who will still be there in three years.

The cost that gets underestimated is never the build. It is the second year: the person who wrote it moves on, the scheme rules change, a funder asks for a report the schema does not support, and there is nobody left who wants to own it. If you are going to build, budget for maintenance and a successor rather than for a launch.

Said plainly, because a comparison that finds us best at everything is worth nothing to you.

If you run one cohort a year with a dozen applications, forms and a spreadsheet are genuinely fine and you should keep the money. If what you actually need is a better task board, a general work tool will fit you better and cost less. If your requirement is fund administration - LP reporting, capital calls, cap tables - that is not built here. And if you need a named security certification today, we do not hold SOC 2 or ISO 27001 and will not pretend the roadmap counts.

Where we are a good fit: several programmes running at once, evaluation by people who are not on your staff, money that has to be accounted for to somebody else, and a reporting question that arrives months after the cohort closed.