In European EdTech, the stretch many companies are now navigating is the distance between the product that built the user base and the product that sustains it. A K-12 platform that grew on teacher word-of-mouth is being asked to behave like an enterprise-procured tool, a higher-ed courseware company that built itself around individual learners is being asked to defend institutional contracts, and a workforce-learning platform that lived inside L&D budgets is being asked to translate completion data into productivity numbers a CFO will recognise.

None of those transitions are technological. They tend to be commercial, organisational and evidential, and they pull the company into territory it was not originally built to operate in.

Most of what determines whether a company makes that translation tends to live outside the product team. Building an evidence base that survives an institutional procurement review is closer to clinical trial design than to product analytics; integrating with the system of record is a multi-quarter, multi-stakeholder commitment most product roadmaps were not built for; and pricing for outcomes rather than engagement requires a contract structure and a customer-success function that look almost nothing like the freemium funnel that got the company to its first ten thousand users.

Each is a serious organisational shift on its own. Together they tend to require a company to operate in two registers at once, the old one it grew up in and the new one its survival depends on, before the team is fully equipped for either.

The work we are typically asked to do in this sector sits exactly in that double-register window. It usually runs over horizons long enough for an institutional procurement cycle to complete, an evidence study to read out, or a customer-success motion to start showing in renewal numbers, because the changes that matter here rarely show up in a single quarter.

The starting point of most useful conversations is which of those organisational shifts is closest to becoming a binding constraint on the next stage of growth, rather than which feature gets built next.