Ecosystems — Subirachs Ventures —
The market map problem
Ask for a scouting exercise on a technology category and you will get a landscape: dozens of logos arranged into segments. It looks like progress. It rarely produces one.
The reason is that a landscape answers 'who exists' when the organisation needed to answer 'who could we work with, on what, starting when'. Those are different questions, and only the second one leads anywhere.
Anchor scouting to a problem statement
Effective scouting begins with a written problem statement drafted with the operating team that owns the problem, not the innovation team. It states what is currently done, what is unsatisfactory about it, what constraints any alternative must respect, and what a better outcome would look like in measurable terms.
That document is what makes a shortlist credible. It also does something less obvious: it forces the organisation to establish whether the problem is real and owned before spending anyone's time on the market.
- The operating problem, in the operating team's own words
- How it is handled today, and what that costs
- Hard constraints: data, regulatory, procurement, integration
- What a successful pilot would demonstrate
- Who inside the organisation would sponsor it
Qualify on collaboration readiness, not just technology
A startup can have exactly the right product and still be the wrong partner. Corporate collaboration demands things early companies often cannot supply: security review responses, reference architecture, insurance, contractual terms, a support commitment, and the patience to work through a procurement cycle.
Screening for this early is a kindness to both sides. It avoids a nine-month process that ends in a legal impasse, and it lets the corporate team focus on companies where a pilot could realistically become a contract.
It also changes the shortlist. The best-known company in a category is not always the one that can move; sometimes a smaller team with an enterprise-ready posture is the better match.
Design the collaboration, not just the introduction
Matching is where most scouting programmes stop, and it is exactly where the work should intensify. A useful match comes with a proposed shape: what the pilot would test, over what period, with what data, at whose cost, and what happens if it works.
Setting that out before the first meeting removes the ambiguity that kills corporate-startup collaborations. Both sides know what they are being asked to commit to, and the conversation moves quickly to whether the fit is real.
It also protects the startup. Early companies cannot afford open-ended exploratory engagements with large organisations, and a programme that repeatedly asks them to is not building an ecosystem, it is consuming one.
Treat the ecosystem as a relationship, not a funnel
Organisations that scout well are known in the ecosystems they scout from. They give founders straight answers, decide quickly, and are honest when a fit does not exist. That reputation is what gets them early access to the next cohort of companies.
Organisations that treat scouting as a funnel get one round of goodwill. After that, the good teams stop returning calls, and the programme is left with whoever is still available.
Ecosystem development is the long game underneath scouting: the relationships, the visibility and the credibility that determine what you get shown before anyone else.