Why local partnership matters in research infrastructure.

The legal layer is local

Academic data carries legal weight. Personal data of researchers and patrons sits under GDPR but also under jurisdictional implementing acts that vary considerably between member states. Records retention rules are set by national archives law. Public-procurement constraints depend on the country’s tendering threshold and on whether the institution counts as a contracting authority. Research-evaluation frameworks — REF in the United Kingdom, M17+ in Czechia, VVOO in Austria — have national specifics that no Brussels-shaped document captures.

A vendor who knows this from a slide deck is not the same as a partner who has filed the forms.

The procurement layer is local

Most European universities and research institutes are public-sector buyers. Their procurement processes are governed by national laws that implement the EU Public Procurement Directive but add country-specific procedures, document templates, and ethics standards. A vendor who arrives without local procurement experience tends to discover, on day forty of a sixty-day tender, that the bid is missing a form the institution’s legal office considers mandatory.

The form is not difficult. It is just specific. A local partner ships it with the proposal.

Onboarding speaks a language

Library staff, researchers and IT teams are most fluent in their working language. They will learn the system faster in that language. They will train each other faster in that language. Their feedback will be more honest, because honesty in a second language tends to round down to politeness.

Documentation, training sessions and the first ninety days of support all happen in the institution’s working language. That is what a local partner brings. It is not something a translated user manual replaces.

Why we don’t direct-sell into thirty countries

Accadema operates a single ecosystem. It does not operate a sales team in every European jurisdiction. The institutions that need the platform live in those jurisdictions. The gap between “we have a product” and “the institution has it running” is bridged by local partners who know the jurisdiction, the language, the procurement office and the people.

The economics are also kinder. A vetted local partner who closes three or four deployments a year and supports them well is a sustainable business in their country. A central sales team trying to do the same across thirty countries is a burnout factory that produces shallow deployments.

What a partner does that a vendor cannot

The short version:

• Sits across the table, not in a video call across two time zones.
• Files the forms the institution’s procurement office expects, in the format they expect.
• Translates the contract, the support agreement and the runbooks — not just literally, but into the institutional vocabulary.
• Knows the funder well enough to anticipate the reporting templates the institution will need.
• Stays, in a way that a project-shaped engagement does not.

None of this is romantic. It is the unglamorous infrastructure of trust, built one filed form at a time.