Measure founder progress through learning, applied work and stage-appropriate milestones, using an agreed starting point and review period. Track attendance separately, and distinguish observed business outcomes from the programme’s contribution.
An incubator, accelerator or university enterprise programme can deliver valuable support without every venture raising investment or becoming a company. A founder may validate a customer problem, reject an unsuitable funding route or decide to pause a weak proposition.
The useful question is what changed, which evidence supports the change and what the founder can now decide or do.
What counts as founder progress?
Founder progress is movement towards a credible next decision or milestone for the venture’s stage.
For an early commercial idea, progress might mean testing whether the intended buyer has a meaningful problem. For a company with customers, it might mean understanding a repeatable sales route. For a founder preparing to raise, it might mean resolving a gap between the funding plan and the evidence available.
A completed pitch deck can be evidence of work. It becomes more useful when the founder can explain the investment case, identify its weaknesses and act on the feedback.
Different ventures need different milestones. Counting company formation, fundraising or revenue as the only forms of progress can obscure important decisions earlier in the pathway.
Which programme measures answer which questions?
Use five evidence layers to keep activity, application and outcomes distinct. They are a practical reporting structure, rather than a validated score or a league table for founders.
| Evidence layer | Question | Examples | Limit |
|---|---|---|---|
| Participation | Who accessed the support? | Attendance, office-hours uptake and completion records | Access does not establish learning or application |
| Learning and judgement | What can the founder explain or decide more clearly? | A consistent task, material review or structured reflection | Confidence is distinct from demonstrated knowledge |
| Application | What did the company change or test? | Revised positioning, customer evidence or completed priority work | A completed document alone does not prove commercial usefulness |
| Milestone or pathway decision | What next step became credible? | An agreed milestone, justified pivot/pause/stop or evidence-backed plan | The milestone must fit the company’s stage |
| Downstream outcome | What happened later? | Customers, pilots, grants, investment, revenue or jobs | Multiple causes and different timelines limit attribution |
The layers can tell a useful story together. They should not be compressed into one unexplained score.
The Digital Growth Grant evaluation published in 2025 illustrates why definitions matter. Data-sharing limitations meant the evaluation lacked identifiers needed to assess unique participants’ reach.
Several interactions with one company are different from several companies receiving support. Define the unit before counting it.
How do you agree a useful starting point?
Record the founder’s current constraint, the available evidence and the next decision before selecting a progress measure.
A short starting record can include
- The commercial or financing question.
- The company’s stage and relevant context.
- The evidence already available.
- The next milestone or decision.
- The work needed and who owns it.
- The review date.
“Become investor-ready” is too broad without criteria. A more useful starting point identifies the particular gap, such as an unsupported revenue assumption or a funding request which does not connect to the next company milestone.
My ARU Growth Enterprise Acceleration Programme work used a shared growth structure adapted to founder priorities within the programme calendar. The same distinction matters in evaluation. A shared process can support different company objectives.
Agree the evidence which would demonstrate progress before reviewing the result. If the objective changes, record why. Retrospectively choosing an easier milestone can make a report look stronger while making it less useful.
Which KPIs should a programme team track?
Choose a small set of measures the team can define, collect and interpret consistently. Every percentage needs a denominator and a timeframe.
| Measure | Definition | Reporting safeguard |
|---|---|---|
| Engagement | Participants using the agreed intervention divided by eligible invited participants during the review period | Define eligibility and distinguish unique participants from repeat visits |
| Priority action completion | Agreed actions completed divided by actions due by the review date | Include overdue work and record changed actions |
| Milestone attainment | Ventures meeting their agreed milestone divided by ventures with a milestone due in the review period | Separate pathway decisions unless the decision itself was the agreed milestone |
| Pathway clarity | Reviewed ventures with an evidence-backed next-step rationale divided by ventures reviewed | State the assessment criteria and acknowledge judgement |
| Learning or confidence | Change using the same task or questionnaire before and after support | Separate self-report from demonstrated learning and report missing paired responses |
Counts often matter as much as percentages in a small cohort. State how many founders were eligible, how many responded and how many have evidence available.
A progress report should also explain unresolved work. A stalled action may reflect unsuitable advice, missing access, insufficient time or a genuine change in priorities. The reason helps the team decide what to do next.
How should progress differ across a mixed-stage cohort?
Keep the reporting structure consistent while allowing different milestones.
| Venture context | Possible milestone | Suitable evidence |
|---|---|---|
| Early customer discovery | Test a defined customer/problem assumption | Interview notes, observed patterns and a decision about the next test |
| Research translation | Clarify an adoption pathway or unresolved feasibility question | Evidence reviewed, a specialist contribution where needed and a documented next step |
| Initial commercial traction | Test a specific sales or positioning hypothesis | Customer responses, pipeline evidence and a comparison with the starting assumption |
| Fundraising preparation | Address a defined investment-case gap | Revised materials, supporting assumptions and a clear explanation of remaining uncertainty |
These are possible measures, not promised results or a substitute for domain expertise.
Clinical, regulatory, scientific and legal decisions require the appropriate specialists. Commercial support can help founders connect those constraints to priorities and financing choices, without replacing specialist judgement.
How do you report pivot, pause or stop decisions?
Explain the decision, the evidence and the implications. A stopped project is not automatically success or failure.
An informed stop can preserve resources when a core assumption is weak. A premature stop can also reflect incomplete evidence or a barrier which suitable support could resolve.
Record what the founder investigated, what remains uncertain and why the selected pathway is reasonable. If further work could change the decision, make the condition explicit.
This is particularly important for early research-led ventures. Company formation and fundraising should follow a credible development path, rather than become the measure which every participant is pushed to achieve.
What can you fairly attribute to founder support?
Separate three claims.
Observed change describes what happened. A company revised its proposition, secured a pilot or raised investment.
Plausible contribution explains how a specific intervention may have helped, supported by the founder’s work, timing and other evidence.
Causal impact requires a credible approach to estimating what would have happened without the intervention.
A workshop followed by an investment round does not establish the workshop caused the raise.
The LORCA evaluation published in 2023 cautioned against attributing observed differences in equity raised to the programme. It identified limitations involving data, comparison groups and the time available to observe impacts.
This does not make routine programme reporting pointless. It means the claim should match the evidence. A proportionate progress record can describe delivery, application and next decisions without presenting itself as an independent impact evaluation.
How do you gather evidence without creating excessive administration?
Use work the founder already needs to produce. A revised proposition, customer-learning record or financial assumption can support both the company’s next step and a programme review.
Keep a short record of the starting question, agreed action, evidence, decision and next owner. Agree who maintains it and when it will be reviewed.
Questionnaires have a role. They can show how participants describe their learning, confidence or experience. They should sit alongside work and decision evidence, rather than replace it.
Define access and confidentiality before gathering materials. A small-cohort summary can identify a company even when its name is removed. Ask permission for public examples and collect only the information the evaluation needs.
Treat missing responses as missing evidence. Avoid assuming founders who stop responding made no progress or excluding them from the report without explanation.
What might an honest founder-progress summary look like?
Illustrative scenario, not a client result. Eight ventures agree a priority action due at the end of a four-week review period.
Six provide evidence of completing the action. One reports a delay while waiting for access to a potential customer. One does not provide a review response.
The action-completion record is six of eight, or 75%, for the specified review period. The report explains the delayed action and missing response. It does not count six responses as the whole cohort or label every completed action a commercial outcome.
For one venture, customer feedback weakens the original proposition. The founder decides to test a different buyer segment.
The summary records the evidence and revised hypothesis. It treats the pivot as a pathway decision, rather than silently counting it as achievement of the original milestone. If a pathway decision was the original agreed milestone, the team can assess it against those criteria.
A concise programme summary can then show
- The question or starting gap.
- The support delivered.
- The work completed and evidence reviewed.
- The decision or milestone status.
- Missing evidence and unresolved constraints.
- The next action and owner.
The report is useful because it makes the next decision clearer, rather than because every line is positive.
How does Lucy connect support to company milestones?
My Incubator Partnerships service connects commercial and fundraising support with your cohort’s stage and programme priorities.
Workshops include preparation, milestone-linked homework, one submission per company, one feedback round and pre/post questionnaires. Group office hours and optional private clinics help founders work through the questions arising from application.
The scope remains bounded. Monthly programme-lead check-ins and progress summaries are included in Entrepreneur in Residence + Clinics. Programme-wide impact evaluation and unlimited reporting are not part of every package.
If you are deciding which format fits your cohort, read Workshop, office hours or private clinics for your founder cohort?.