What to Ask a Corporate Before You Commit

• The year before the pilot
• Not closed doors, but missing predictability
• Entry: what to establish before you invest the year
• The pilot: what to establish before the free PoC
• What unanswered questions produce
• The Nordic dimension
• The Structural Response
• Conclusion
• References

Corporate interest is easy to obtain and difficult to read, and the difference between an opportunity with a pathway and one without is usually visible in the first few conversations, if the right things are asked.

The year before the pilot

For a company with fewer than twenty people, a corporate conversation is not a sales opportunity in any ordinary sense. It is an allocation decision. Meetings, workshops, security questionnaires, technical reviews and unpaid proofs of concept consume the scarcest resource a young company has, which is the founder’s own time, and they do so months before anyone can say whether the effort will lead to a purchase. McKinsey has described the resulting condition in industrial settings as pilot purgatory: organisations accumulate promising experiments while very few of them reach production scale. Seen from the corporate side this is an efficiency problem. Seen from the founder’s side it is a survival problem.

Bridgium’s second research report, From Discovery to Practice, examines how corporate and startup collaboration develops in practice and where it loses momentum. It is based on 48 qualitative interviews: 28 with innovation leaders and senior practitioners in large Nordic and European corporations, and 20 with founders and senior representatives of startups and SMEs already engaged in corporate collaboration. The interviews were conducted between September and December 2025 and ran for roughly thirty to sixty minutes each, following a shared guide.

The founders in that sample do not describe corporate collaboration as a mistake. They describe it as expensive and slow in ways that are only partly avoidable. One founder put the arithmetic plainly:

“We spend about a year on research and exploration — not only to approve the PoC, but to build connections. It is a loss of time, but still the only working model.”
— Startup Founder · B2B HR-Tech · Finland

Two things are worth noticing in that sentence. The first is that the year is not wasted on nothing: it buys connections, and connections are what make the next conversation possible. The second is that the founder calls it a loss anyway, because the year buys connections rather than a decision. The practical question for any founder is therefore not how to avoid the exploration period, but how to tell early which corporate conversations have a decision at the end of them.

This article sets out what the research suggests you can establish, and how to read the answers. It is drawn from two sections of the report that address founders directly: section 5.8 on the Entry stage and section 6.9 on the pilot stage.

Not closed doors, but missing predictability

The familiar explanation for slow corporate collaboration is that large organisations are closed, risk-averse or indifferent to outsiders. The interviews do not support that reading. Corporations in the sample were actively looking for external solutions, running challenge programmes, scouting at scale and funding innovation units to do it. What they were not doing, in most cases, was making their own decision logic legible to the people they invited in.

The report names the recurring pattern as an expectation paradox: corporates search for novelty but evaluate predictability, while startups seek fast validation but must prove reliability and operational fit. Both sides are behaving rationally. A corporation that has invited an unproven supplier into a production environment will assess it against the standards it applies to suppliers, because those standards exist to protect continuity. A founder who needs a reference case within two quarters will push for speed, because the funding round depends on it. The friction is structural rather than personal, and it does not resolve itself through better rapport.

What makes the paradox harder to manage is that corporate needs are often only partially communicated. One respondent described the sequence from the supplier side:

“Corporates… don’t really tell you about their problems… only when you are already in.”
— Sales Leader · IT Services · Finland

So the founder adapts a solution to an organisation they only partly understand, while the organisation evaluates that solution without fully exposing its constraints, priorities or adoption logic. Neither party is withholding information out of bad faith. Confidentiality, internal politics and simple lack of a written answer all contribute.

The report uses the term transparency in a specific and limited sense that is useful here. Transparency is the visibility of innovation needs, collaboration stages, entry points, decision criteria, decision-makers and next steps. It does not mean full disclosure of confidential strategic information. It means enough clarity for relevant actors to understand how to engage. Framed that way, transparency is not something a founder has to wait for. Most of it can be established by asking, and the quality of the answer is itself the signal.

There is an older idea underneath this. March distinguished exploration from exploitation as two different organisational logics with different criteria for success, and the difficulty in corporate and startup pilots is that the two are frequently applied to the same activity at the same time. A pilot framed as exploration by one party and assessed as exploitation by the other will disappoint both. Establishing which logic is in force is the single most useful thing a founder can do early.

Entry: what to establish before you invest the year

At the Entry stage the report’s finding for founders is that active exploration is necessary but should not become endless searching inside unclear corporate systems. The recommendation is to qualify the opportunity early, and it comes down to four things.

Who owns the problem, who decides, and what budget logic shapes continuation. An innovation unit is frequently the door rather than the owner. It can convene, fund a small experiment and advocate internally, but the problem itself usually belongs to a business unit with an operating budget, and that unit is where continuation is decided. A conversation in which no one outside the innovation team can be named is a conversation with a sponsor and no owner.

Whether the corporate is exploring or ready to implement, and how IP is treated. These are separate questions that behave as one, because both are about what the engagement is for. Co-exploration and ready-to-integrate procurement have different timelines, different evaluation criteria and different implications for what you disclose. The report is explicit that it does not examine legal mechanisms in detail, but it treats IP clarity as a condition for fair collaboration, because early dialogue often requires sharing ideas, assumptions and technical logic.

What counts as success at the next stage, and who funds it. Success at the current stage is usually easy to agree. Success at the next one is where the money is, and where most conversations turn out to be undefined. If nobody can describe what would have to be true for the solution to move forward, and from which budget, the pilot has no destination.

Translation of the solution into business, operational and integration terms. This is the one item on the list that is work rather than a question. Corporates in the sample assess not only innovation potential but reliability, continuity, compliance awareness and the capacity to operate inside existing systems. A solution described only in technical or product terms leaves the receiving organisation to do that translation, and in practice it usually does not.

The value of asking is not only in the content of the reply. It is in whether a reply exists at all, and how quickly it arrives. The table below sets out how to read the answers.

Table 1. Entry-stage qualification questions and how to read the answers. Questions from Bridgium, From Discovery to Practice (2026), section 5.8; interpretation by the Bridgium research team.

The pilot: what to establish before the free PoC

Pilots, proofs of concept, prototypes and MVPs are described in the report as exploratory validation environments, where both sides test assumptions, refine problem and solution fit and assess operational relevance before implementation decisions are made. That is the intention. The structural tension is that startups approach pilots as iterative learning environments while corporates approach them through governance and operational logic, expecting measurable outcomes, compliance alignment, implementation readiness and reduced risk. One respondent named the consequence from inside the procurement function:

“We tend to evaluate startups as if they were already established vendors.”
— Procurement Lead · Telecommunications · Sweden

This is worth reading carefully, because it is not a complaint about startups. It is a description of an evaluation habit that a mature purchasing organisation applies by default. The exploratory solution loses legitimacy before the problem and solution fit has been developed, not because anyone decided it should, but because no one specified a different standard.

At this stage the report sets out five things for founders to clarify: what the pilot is expected to prove, whether the engagement is a free PoC, a paid pilot or a pathway toward funded implementation, who owns the problem and who decides, gives feedback and funds the next step, what remains protected during co-exploration and what happens if the corporate later builds internally or works with another vendor, and what counts as success at the next stage and what conditions shape continuation.

The second of these deserves particular attention, because free proofs of concept are not irrational for founders. They are a considered trade:

“A free pilot in a corporate environment gives us the opportunity to test and pivot. Only from inside can we understand the real needs and issues. Second, we need references and use cases to approach VCs.”
— Startup Founder · B2B HR-Tech · Finland

Blau’s account of social exchange is useful for reading this. Unpaid work creates an obligation only where both parties recognise it as an exchange with a return. Where the return is undefined, the same work reads as a free service, and the relationship it builds is weaker rather than stronger. A free PoC with an agreed output, an agreed end point and a named next decision is an exchange. A free PoC without them is a subsidy. The difference is not in the effort but in what was established before it started.

Table 2. Engagement modes at the pilot stage. Derived from Bridgium, From Discovery to Practice (2026), sections 6.1, 6.9 and 7.

What unanswered questions produce

The questions above are not administrative. Each one, left unanswered, produces a specific and observable outcome in the interviews.

Unbounded exploration. Where no end point is defined, discovery extends until one side stops answering. This is the mechanism behind the year that founders describe. It is not caused by corporate slowness alone but by the absence of an agreed terminal condition on either side.