Open innovation: scouting and matchmaking, done with method

Working with startups, universities and technology partners is now part of the mandate of nearly every innovation department. What separates an ecosystem that generates projects from one that only generates contacts is method.

Finding startups is no longer the problem

Specialised databases, accelerators, industry events: filling a list of interesting startups is within reach of any team today. The bottleneck has moved elsewhere, to the ability to connect what the ecosystem offers with a precise internal need. A contact collected at a trade fair, with no need to answer and no evaluation path ahead of it, remains a business card.

This is why many open innovation programmes show activity numbers — startups met, events run, applications received — and few PoCs actually launched. The connections exist, but without a process to take them somewhere they scatter across generic CRMs, inboxes and people's memory.

Everything starts with defining the need

Effective scouting begins inside the company, not outside it. Before looking at the market, needs have to be collected and formalised: interviewing business functions, understanding which problems are mature enough for an experiment, translating them into a question the outside world can answer. A well-formalised need contains at least four elements:

• the problem to solve and the operating context where it appears;
• the technical, regulatory and budget constraints of the experiment;
• the criteria a candidate solution will be judged against;
• the internal sponsor who will own the eventual PoC.

Without this upstream work, scouting looks for "something interesting" and finds a bit of everything. With a defined need, every solution encountered can be measured against a shared yardstick.

Targeted scouting and challenges: two complementary tools

Once the need is defined, there are two routes into the ecosystem. The first is targeted scouting: an active search for solutions, run on qualified sources and guided by the criteria of the need. The second is the challenge, or call for solutions: the need is published, openly or on an invitation basis, and startups, research centres and partners apply.

When to use which

Scouting works when the solution market can be mapped and the need is specific; a challenge works when you want to stay open to unexpected proposals or actively engage a region, a cluster, a community. Many organisations use both on the same need. What matters is that both feed the same evaluation funnel: in blendX, the Challenge module manages calls and applications in a single flow, converging on the same point where scouting leads arrive.

Evaluating against shared criteria

Whether they come from a call or from active search, candidate solutions go through the same funnel: an initial screening to rule out what is off-scope, a comparative analysis against the criteria defined with the need, and a shortlist to explore through meetings and documentation. Structured evaluation protects against a very real risk: choosing on enthusiasm, on the strength of a well-run demo, and discovering the limits once the PoC is already underway. Tools like the blendX Startup Dealflow module exist precisely for this: keeping the funnel in order, with statuses, evaluations and responsibilities tracked.

Matchmaking is a process, not a meeting

Once the shortlist is there, the work changes nature: demand and supply have to be brought together in a way that produces a next step. Those who do matchmaking for a living — innovation hubs, clusters, accelerators — know that most of the value lies in what comes after the introduction: preparing both sides, aligning expectations, setting the goal of the meeting, collecting outcomes and keeping up the follow-up until a decision is reached. The blendX Matchmaking module structures this path, keeping track of who was introduced to whom, on which need and with what outcome.

The end goal remains the PoC: an experiment with a defined scope, budget and success criteria. Every step of the process — from need to challenge, from evaluation to matchmaking — exists to get there with the right premises.

Why a generic CRM is not enough

The temptation to run all of this in the corporate CRM is understandable: the tool is already there and the team knows it. A CRM, however, models commercial relationships — accounts, opportunities, sales pipelines — while open innovation has objects of its own: needs, candidate solutions, evaluations, meetings, PoCs, and many-to-many relationships between demand and supply. Forcing these objects into a CRM means losing precisely the link that gives the process its value, the one between a need and the solutions that address it.

This is why blendX treats the ecosystem as a first-class object: modules such as Innovation Ecosystem, Challenge and Matchmaking share the same data, and a contact born at an event can become an application, then a shortlist entry, then a PoC without ever changing platform. The platform page describes how the modules work together.