Evaluated as a Vendor Before You Are One

• Prepared for one conversation, assessed in another
• Not conservatism, but two scales at once
• The nine dimensions
• The dimension you cannot close yourself
• What the mismatch produces
• The Nordic dimension
• The Structural Response
• Conclusion
• References

Startups prepare to be judged on what makes them different, and are assessed on whether they can be relied upon; both sides then wonder why the conversation went the way it did.

Prepared for one conversation, assessed in another

A founder walking into a first corporate meeting has usually prepared three things: the demo, the pilot metrics, and the reason this approach is better than what the organisation is doing now. All three answer the same question, which is whether the idea is good. The research suggests that this is not the question being asked.

Bridgium’s second research report, From Discovery to Practice, is based on 48 qualitative interviews conducted between September and December 2025: 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 working with them. Its second appendix examines corporate evaluation logic directly, and states the underlying question in a form most founders would not recognise from their own preparation. The core question is less whether the idea is innovative, and more whether the solution can survive, integrate and operate inside the organisation.

The distance between those two questions explains a large share of the collaborations that end politely and without a reason anyone can name. It also explains why the failure rate persists at an organisational level: McKinsey found, across a survey of more than a thousand companies, that fewer than a third had moved beyond the pilot phase in modernising their operations, and that the figure had barely shifted in two years. Evaluation is one of the places where that stalling happens, and it happens early enough that neither side registers it as a decision.

This article sets out the nine dimensions the interviews identify, where the friction sits in each, and which of them a startup can influence. It is written for both sides, because four of the nine are things only the corporate organisation can fix.

Not conservatism, but two scales at once

The founder-side interpretation of a slow evaluation is usually that the organisation is risk-averse. The report describes something more specific. Corporates assess startups through two logics simultaneously: an innovation logic that values novelty, experimentation and emerging potential, and an operational logic that values stability, accountability, continuity and integration. Both are applied to the same company in the same meeting, often by different people, and the second is rarely announced.

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

March’s distinction between exploration and exploitation is the underlying structure: two organisational logics with genuinely different criteria for what counts as a good outcome, coexisting inside the same firm. The problem in corporate and startup evaluation is not that one logic wins, but that both are running and only one has been declared.

The most-cited concern in the interviews is continuity, and it is worth quoting because it is usually heard as an insult and is not one:

“Would you really like to use this technology? What happens if the startup in one year is not existing anymore?”
— Open Innovation Lead · Industrial Technology · Germany

Stinchcombe named the underlying fact sixty years ago as the liability of newness: young organisations fail at higher rates than established ones, because roles are still being invented, routines do not yet exist, and the organisation depends on relationships with people who have no history with it. The evidence has held up across decades of subsequent work. A corporate buyer asking about survival is not expressing distrust of a particular founder. They are pricing a base rate, and the base rate is real.

What makes this hard to answer is that the buyer cannot easily distinguish between startups. Akerlof’s account of quality uncertainty describes what follows: where a buyer cannot verify quality before purchase, they apply an assessment based on the category rather than the case, and the strongest sellers in that category are penalised along with the weakest. A well-capitalised startup with three years of runway and a fragile one look similar from across the table, so both are treated as continuity risks until something in the interaction separates them. What separates them is the subject of the rest of this article.

The nine dimensions

Appendix 2 of the report sets out the evaluation dimensions observed across the interviews, together with the corporate concern behind each and the friction it produces on the startup side. Read as a list, the striking thing is how few of them concern the technology.

Table 1. Corporate evaluation dimensions. Adapted from Bridgium, From Discovery to Practice (2026), Table 7, Appendix 2.

Three of these deserve a closer reading, because they are the ones founders most often misdiagnose.

• Cultural and communication fit is not about likeability. The friction recorded here is that a strong solution can fail because the way it is framed threatens the people whose work it touches. A pitch built on how badly the current process performs is, to the person who designed that process, a proposal to document their failure. The same solution described as removing a constraint they have complained about for years is the identical product with a different receiving audience.
• Predictability is a coordination requirement, not a preference for slowness. An organisation that has to sequence procurement, security review, integration work and user training needs to know when things will arrive. A supplier who adapts the roadmap mid-quarter is not demonstrating agility to that organisation; they are removing its ability to plan around them. Iteration inside an agreed envelope reads completely differently from iteration that moves the envelope.
• Integration readiness is assessed before it can be demonstrated. Nobody can prove they will integrate well until they have integrated. What can be shown is that the question has been thought about: which systems the solution touches, what the support model looks like, what happens at version upgrades. Cohen and Levinthal’s work on absorptive capacity describes the other half of this, which is that the receiving organisation also needs internal capacity to take up external knowledge. Where that capacity is thin, no amount of readiness on the supplier side compensates.

The dimension you cannot close yourself

The ninth dimension is the one that decides most outcomes and is almost never discussed in preparation. The corporate question behind it, as recorded in the report, is whether the internal sponsor can justify supporting this initiative. Not whether the solution is good. Whether defending it is survivable.

This is a career question wearing a procurement costume. The innovation manager who champions an external supplier is taking a position that will be reviewed if anything goes wrong, and reviewed by people applying operational criteria. Kerr’s observation about rewarding one behaviour while hoping for another applies precisely: the sponsor is measured on delivery and risk, and asked to advocate for uncertainty. The friction the report records follows directly. Innovation managers support solutions that later fail at budget or executive approval level, and they are not being insincere when they do it. They are advocating within a limit they have not tested yet.

Weick’s account of sensemaking is useful for what this means in practice. The sponsor is not transmitting facts about a supplier to a committee; they are constructing an account that will hold up when questioned by people with different concerns. A founder who supplies only product arguments has given them raw material for one kind of account. A founder who supplies the continuity evidence, the integration answer, the reference, the compliance position and the named risk mitigation has given them an account that survives the meeting they will not be invited to.

Table 2. Which evaluation dimensions a startup can influence, and how. Dimensions from Bridgium, From Discovery to Practice (2026), Appendix 2; routing by the Bridgium research team.

What the mismatch produces

Four outcomes recur where the two evaluation logics are never separated.

• Legitimacy lost before fit is established. An exploratory solution is measured against mature-vendor criteria and fails them, which it was always going to, before anyone has determined whether the problem and the solution actually match. The report states this directly: collaboration weakens not because the idea lacks value, but because the startup does not yet appear predictable, legible or operationally trustworthy within the corporate system.
• Category pricing instead of case assessment. Where nothing in the interaction distinguishes one early-stage supplier from another, the buyer applies the category assessment. The startups that suffer most from this are the ones that would have survived scrutiny, because they are carrying a discount earned by companies they have never met.
• Sponsors who advocate beyond their limit. Support given in good faith at the innovation-team level is read by the founder as an organisational decision. It is not one, and the distance between the two is invisible until the approval stage, by which point the founder has committed months on the strength of it.
• Feedback that explains nothing. Because the operational logic was never declared, the reasons for a negative decision cannot be stated in terms the founder can act on. The polite version is that it was not the right time. The founder learns nothing, adjusts nothing, and repeats the same approach at the next organisation.

The Nordic dimension

Two regional features intensify the continuity question specifically, and they compound rather than offset each other.

The first is sectoral. Much of Nordic industry sits in energy, manufacturing, infrastructure, mobility and logistics, where assets and systems are held for decades and where regulatory instruments including the EU AI Act and the Digital Operational Resilience Act impose documented obligations on third-party providers. In that setting, the question about whether the supplier will exist in a year is not rhetorical caution. It is a component of an operational risk assessment that extends well past the contract term, and a buyer who skipped it would be doing their job badly. The practical implication for founders is that continuity evidence belongs in the first substantive conversation rather than in the procurement stage, because by procurement it is a hurdle, and early it is a differentiator.

The second is structural and less often stated. Nordic markets are small. The reference cases that would answer the continuity question are held by a limited number of large organisations in each sector, and those organisations require reference cases before engaging. One founder in the study described the resulting dependency plainly:

“External validation and early adoption signals strongly influence credibility. That’s a crucial factor for future fundraising.”
— Startup Founder · AI & Data · Finland

The loop closes on itself: references are needed to gain access, and access is needed to build references. Granovetter’s finding that weak ties carry the information that strong ones do not explains why the loop is broken through networks rather than through better material, and why founders describe a year of relationship-building as the only working model. It also explains why the first corporate reference is worth disproportionately more than the second, and why corporates that run structured entry programmes gain access to companies their competitors cannot see.

The Structural Response

Two responses for each side, because the mismatch is jointly produced.

• For corporates: declare which scale is in force. Stating at the outset whether this is co-exploration or a supplier assessment costs one sentence and removes the largest single source of wasted effort on both sides. A startup told it is being assessed as a supplier can decide whether to compete on those terms. A startup told nothing spends months optimising for the wrong criteria.
• For corporates: give the sponsor a defensible frame, not just a budget. If internal legitimacy decides outcomes, then the organisation that wants external innovation has to make advocacy survivable. That means agreed criteria for exploratory suppliers that differ from mature-vendor criteria, and a named forum where the exception is granted rather than argued for case by case.
• For founders: answer the operational question before it is asked. Continuity, support model, integration approach and compliance position, supplied unprompted in the first weeks. This does not remove the liability of newness, but it moves the assessment from category to case, which is the only movement available.
• For founders: equip the sponsor rather than persuade the room. The meeting that decides the outcome is one the founder does not attend. What travels into it is whatever the sponsor can carry: a written answer to the continuity question, a named reference, an integration outline, a risk mitigation. Product enthusiasm does not travel. Documents do.

Conclusion

The evaluation logic described in this research is not hostile to startups and is not a failure of corporate imagination. It is what an organisation responsible for continuity does when presented with something it cannot yet verify. The founder-side experience of it as unfairness, and the corporate-side experience of it as due diligence, are both accurate descriptions of the same process.

What is avoidable is the concealment. Nine dimensions are being assessed, of which one is the one most founders prepare for. Four of the nine sit inside the corporate organisation and cannot be closed from outside. The single most useful thing either party can do is say which scale is being applied and when, because the cost of the mismatch is paid in months by the smaller company and in missed capability by the larger one.

So the question for whichever side of the table you are on. In your most recent corporate and startup conversation, was it ever stated out loud whether the startup was being explored with or assessed as a supplier?

Appendix 2 of From Discovery to Practice: How Corporate–Startup Collaboration Becomes Usable sets out the full evaluation table and the interview evidence behind it:
bridgium-research.eu/startup-report-2026

References

1. Bridgium Research Team (2026). From Discovery to Practice: How Corporate–Startup Collaboration Becomes Usable. Illarionova N., Verlin K., Verlin A. Report
2. Bridgium Research Team (2026). How Innovation Happens: Insights from Leading Enterprises in Times of Change. Illarionova N., Verlin K., Verlin A. Report
3. Stinchcombe, A. L. (1965). Social Structure and Organizations. In March, J. G. (ed.), Handbook of Organizations. Chicago: Rand McNally, pp. 142–193. Print edition; no stable open link.
4. Akerlof, G. A. (1970). The Market for Lemons: Quality Uncertainty and the Market Mechanism. Quarterly Journal of Economics, 84(3), 488–500. Print edition; no stable open link.
5. March, J. G. (1991). Exploration and Exploitation in Organizational Learning. Organization Science, 2(1), 71–87. JSTOR
6. Kerr, S. (1975). On the Folly of Rewarding A, While Hoping for B. Academy of Management Journal, 18(4), 769–783. JSTOR
7. Cohen, W. M. and Levinthal, D. A. (1990). Absorptive Capacity: A New Perspective on Learning and Innovation. Administrative Science Quarterly, 35(1), 128–152. JSTOR
8. Granovetter, M. S. (1973). The Strength of Weak Ties. American Journal of Sociology, 78(6), 1360–1380. JSTOR
9. Weick, K. E. (1995). Sensemaking in Organizations. Thousand Oaks, CA: Sage. Publisher
10. McKinsey & Company (2020). Breaching the great wall to scale. Read
11. European Commission. Regulatory framework on artificial intelligence (EU AI Act). Read
12. Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA). EUR-Lex