The organisation

Ventures & incubation

How a tested solution becomes a venture: the shared stack every founder draws on, what the incubation record looks like, and the ownership claims the academy does not make.

Version 4.1.0 Published 27 August 2026 Updated 3 September 2026

Where entrepreneurship sits

Entrepreneurship is not an end-stage programme. It is a networked support system embedded across the whole journey.

Exposure events, bootcamps, labs, maker training, volunteer programmes and funding connections are all inputs into entrepreneurship rather than separate programmes that happen to sit near it. The venture track names and strengthens that system; it does not bolt entrepreneurship onto the end of something else. That framing is what the entrepreneurial ecosystems literature would predict: the surrounding conditions produce entrepreneurial activity, not any single module delivered into a vacuum[34, 35].

Practically, support comes in two shapes, and both belong in the record.

Direct support

Funding facilitation, equipment and tool access, mentorship, incubation.

Indirect support

Matchmaking: connecting founders to external funders, networks, volunteers and experts, and linking local makers to opportunities elsewhere.

The second is the less visible half. The academy works as an intermediary in an innovation ecosystem, not only as a direct provider, and the asset that compounds over time is the network, not any single programme.

The shared stack

A founder does not receive a programme. They draw on a standing set of assets that everybody else is drawing on at the same time.

AssetWhat it does in incubation
The workshop floorWhere challenge-based learning and prototyping happen.
Mentors and trainersCoaching and domain expertise, increasingly from alumni.
The funder and partner networkMatchmaking, external funding, links beyond the region.
Seed capital instrumentsA startup challenge with a capped award, and incubator seed grants.
ReplicationThe mechanism that takes the whole stack to another community.
Alumni and the ventures the pathway producedProof, role models, and inputs back into the system as mentors and partners.

The founder funnel

One end-to-end view, with the condition that has to be true before each step becomes the next one.

StageWhat happensGate to the next
Maker educationFoundational mindset and skills.Curiosity, and base competence.
DiscoveryExposure, bootcamps, first projects.The learner opts into the journey.
Labs and challenge-based learningTake on a real local challenge on the floor.A tested prototype.
Grassroots innovationPrototype becomes a validated local solution.Tested prototype, plus community demand, plus a committed team.
Domain expertise and a first versionDesign thinking, business modelling, storytelling.A working first version and a venture concept.
IncubationSeed funding, mentorship, workspace, network.Launched, with revenue and impact being tracked.
SustainingThe venture keeps trading; alumni return as mentors; the model replicates.Loops back into the stack.

The step from a tested prototype into venture work is the best documented transition in the record. The step after it, from a first version to a launched venture, is the one whose conversion rate cannot yet be computed, so no rate is published.

What gets incubated

The incubation record is not technology-led

In the best-documented incubation cohort, eleven ideas were supported. Eight were agriculture, food or materials businesses, and exactly one was digital: spice, mushrooms, handicrafts from upcycled glass, aloe vera and peanuts. This is from an organisation that also runs a software floor and an artificial-intelligence curriculum.

That is what the community-origin test produces. The problems that pass it are the ones a Batticaloa community actually has, and the binding constraint in this region is livelihood rather than skill. Any mismatch is between the incubation record and the way the work gets described, not between the record and the mission.

Two rules follow. The incubation here is not described as tech or deep-tech. And the software floor's project list is not used as evidence of what gets incubated, because that is client service work: a different activity with a different output. Whether later cohorts have the same shape is not known, because their sector mix has never been counted, and it should not be assumed in either direction.

What is owned, and what is not

A page of logos under a heading implies ownership that usually is not there, so the position is set out explicitly.

  • The ventures are not described as a portfolio. That word claims ownership, assembled out of a list of roles, and a role does not add up to ownership. They are ventures the pathway produced.
  • A venture that separates from the academy is independent by default. Only the venture leaves; a lab never becomes a subsidiary.
  • A company founded by an alumnus after they left is theirs. It is not counted and not listed here. The credit belongs to the venture that person built while they were here.
  • An organisation a co-founder ran before the academy existed is a related party, never independent validation of this work.
  • No headline count of ventures is published. A count needs a stated role and a stated population it is counted from. Until both exist, the number would mean nothing.

Reporting all three outcomes

Credibility here comes from the second and third rows, not the first.

CategoryWhat it looks likeWhy it is reported
Success Business started, revenue, work created, sustained production, community impact. Proof of possibility.
Partial Prototype built but not scaled; funding paused; used locally but never commercialised. Realism, and depth. Most real outcomes live here.
Failure Abandoned; funding not sustained; a mismatch between training and the local economy; the learner left. Credibility. These are constraints discovered during implementation.

The literature is clear that making on its own fosters only some entrepreneurial capability and needs explicit programmes and incubation layered on it[6, 32, 36]. That is a design instruction, and it is the reason this stage exists at all rather than being left to happen.

The academy was incubated too

DreamSpace Academy is on the receiving end of the mechanism it now operates. It was founded through an incubation programme run by another organisation: a short structured programme ending in a pitch, a soft loan rather than a grant, and a centre set up as a social enterprise run by a local entrepreneur rather than as a branch office, with the entrepreneur left owning it.

That matches the definition of an impact venture used here, described by somebody else before it was written down: something that came out of a real community context, with a credible path to paying for itself, which could not have got there unaided at the start.

What it does not license

The resemblance is structural. Nobody has said the copy was deliberate, so there is no claim to be replicating what was done here. There is no claim to have finished that graduation. And no figures are attached to it.