Choosing Incubation Management Software: A Buyer's Guide
The nine questions that separate incubation platforms, why a demo hides most of them, and how to tell whether you need software at all this year.
First, decide whether you need it
The honest starting point, and the one no vendor will lead with.
You do not need incubation management software if all of these are true: you run one cohort a year, applications number in the low dozens, every reviewer is on your staff, you have no physical space to allocate, you disburse no money you must account for, and nobody outside your organisation will ask you to explain a decision.
That is a real situation. Plenty of small university cells are in it. Buy nothing.
What tips it is rarely volume alone. It is usually one of three specific events:
- A reviewer disagreement you could not resolve because the scores were averaged
- A funder asking where a specific amount went, and it taking three days to answer
- A document request that fell through because it lived in one person's sent folder
If one of those has happened, the spreadsheet has stopped working regardless of how many applications you get.
The nine questions
A demo will show you dashboards. These are the questions that actually separate products, and most of them are invisible in a demo unless you ask.
1. Is the per-evaluator scoring breakdown retained, or averaged?
Ask this first. If a system stores only the average score per application, then eight months later, when someone asks why a company was not selected, you cannot answer usefully. The information was destroyed at the moment of submission and no care afterwards recovers it.
Ask to see a scored application from a past round with all evaluators' individual criterion scores visible.
2. Can an external evaluator be scoped to one programme?
Panels include outsiders. They need the applications for one programme and nothing else - not your funding records, not other cohorts, not your startup directory.
If the only option is a full account, you are choosing between an over-permissioned stranger and evaluation by email attachment. Ask what an external evaluator can see, and ask what happens to their access when the programme ends.
3. Can you trace a specific amount from source to the startup that received it?
Not "does it track funding". The chain: this grant, allocated to this programme, committed to this startup, released as this tranche against this milestone.
Ask them to demonstrate it on a real record, backwards: start from a payment and walk up to the source.
4. Is over-allocation blocked at commitment, or reconciled afterwards?
If two programmes can each commit money from the same grant and the total exceeds it, when do you find out? At commitment, or at reconciliation?
At reconciliation means discovering it after a startup has been told the money is coming. This is a control-versus-policy question and vendors answer it very differently.
5. Do document and change requests carry a state?
"We asked them for the incorporation certificate three weeks ago" needs to be visible to your whole team, not just to whoever sent the email. Ask whether a request is a first-class object with an open/closed state, or a note.
6. Can you get your data out yourself?
Ask for an export during evaluation, not after signing. Applications with scores, funding with tranche history, startup records, in a machine-readable format, without raising a ticket.
A vendor who cannot demonstrate this in a trial is telling you something about the eventual exit.
7. What happens to physical space?
If you have desks, cabins, labs or meeting rooms, ask whether they are first-class objects with rates, deposits, recurring charges and approvals - or a text field.
This is the most commonly missing module across the category, and if you run a physical centre it is half your administrative load.
8. Are permissions per person, or per job title?
A finance officer who can see funding but not evaluation. A programme manager for one programme only. Ask how fine the granularity is and whether it is per module.
Role-only permissions force you into over-granting, and over-granting is what makes an access review painful later.
9. What is not built?
Ask directly, and judge the answer more than the content. Every product has gaps. A vendor who names theirs quickly is a vendor whose other claims are worth more.
If the answer is "nothing", you have learned something important about how the rest of the conversation should be weighted.
What a demo hides
Demos are run on clean, prepared data by someone who knows every shortcut. That is not dishonest, but it hides the four things that determine whether you will still like the product in a year:
- The second cohort. Everything works for one programme. Ask to see two running simultaneously, with different forms and different rubrics.
- The messy record. A withdrawn application, a startup that changed its name, a tranche that was partially released. Ask to see one of each.
- The bulk operation. Registering forty startups, exporting everything, emailing a cohort. Ask them to do it live.
- The permission edge. Log in as the external evaluator, in front of you, and show what they can reach.
Ask for a trial with your own data rather than a longer demo. A vendor who will not give you one is answering the question.
Pricing, and the questions under the headline
Whatever the model, establish these four:
- What drives the price - users, startups, programmes, storage, modules?
- What happens when you exceed a limit mid-cohort? Blocked, charged, or a conversation?
- Which modules are included at your tier, and what does adding one cost?
- What does it cost to leave - is there an export fee, and what is the notice period?
The third one is where incubation software differs most between vendors, and the one most likely to produce an unwelcome surprise in year two.
A note on implementation
There are two models and they are genuinely different purchases.
Subscription software is live in days. You configure it yourself. Where it does not do something, it does not do it.
An implementation project is scoped, configured to your process, and takes months. You get something shaped exactly around how your department works, and you pay for that in time and money.
Neither is wrong. Government and large public bodies often have procurement rules that make the second the only available route. What is wrong is buying one while expecting the other.
The scorecard
Take this to every vendor and fill it in during the call:
| Question | Vendor A | Vendor B |
|---|---|---|
| Per-evaluator breakdown retained? | ||
| External evaluator scoped to one programme? | ||
| Source → allocation → startup → tranche traceable? | ||
| Over-allocation blocked at commitment? | ||
| Document requests carry a state? | ||
| Self-service export, demonstrated? | ||
| Space and facilities as real objects? | ||
| Permissions per person and per module? | ||
| What is not built? |
If a vendor cannot answer six of these on the call, they have not run a selection round. That is not disqualifying, but it tells you how much of your process you will be explaining to them.
Where we stand on our own list
It would be evasive not to say. EcoSync answers yes to the first eight, and the ninth is: no learning management system, no fund administration such as LP reporting or capital calls, no SOC 2 or ISO 27001 certification, and no published uptime SLA. If a curriculum is the centre of your programme, or a certification is a procurement requirement, those are real reasons to buy something else - and the comparison pages say which.
Frequently asked questions
- Do we need incubation management software at all?
- Not necessarily. If you run one small cohort a year, all reviewers are your own staff, and nobody outside will ask you to account for a decision or a disbursement, a spreadsheet is genuinely the right answer and you should not buy anything.
- What is the most useful question to ask a vendor?
- Whether the per-evaluator scoring breakdown is retained or averaged. It sounds narrow and it is the fastest way to tell whether a product was built by people who have run a selection round, because averaging is what makes a decision indefensible later.
- How long should implementation take?
- For subscription software, days. If a vendor quotes months for a standard incubation programme, you are buying an implementation project rather than a product - which is a legitimate choice, but a different one, with different costs and a different failure mode.
- What should we check about getting our data out?
- Ask for an export before you sign, not after. Specifically: can you get applications with their scores, funding with its tranche history, and startup records, in a machine-readable format, without asking support. If the answer is a support ticket, factor that into the decision.
