Clear functional fit
Connect your expertise to one work process, user group and intended improvement.
Connect responsibly
Work together without creating a new dependency.
Public organisations must retain control and freedom of choice. Cooperation therefore starts with demonstrable value, interoperability and clear responsibilities — not with reach or sales.
For a sustainable connection
Make the contribution, dependencies and agreements visible.
A functional fit is only the beginning; management, continuity and a workable exit matter too.
Modular and replaceable
Assess interfaces, standards, export and management without promising integration in advance.
Transparent agreements
Discuss ownership, licences, costs, support, security and exit arrangements.
From expertise to connection
Clarify the value and conditions first.
Every next step requires an explicit decision; an initial conversation is not an integration or contract.
-
01
Describe your contribution
Explain the problem you help solve, for which users and with which experience.
-
02
Assess the functional fit
Explore whether your expertise fits an existing module or public case.
-
03
Review the conditions
Discuss architecture, standards, data, accessibility, security, licensing and procurement.
-
04
Test a limited connection
Test only what is needed to assess usefulness, manageability and dependencies.
-
05
Make a follow-up decision
Integration, contracting, listing and scaling each require a new decision.
Clear boundaries
An open ecosystem requires clear boundaries.
Public control, transparency and freedom of choice remain the starting point.
No preferred position
Participation does not guarantee a contract or partner status.
Procurement rules still apply
An exploration does not bypass tendering or procurement requirements.
Share information appropriately
Commercial and confidential information is only shared under suitable agreements.
Public authority remains
The public organisation retains authority over its process, data and decisions.
A workable exit
Continuity, portability and a workable exit are considered in advance.
Frequently asked questions
Before you propose a partnership
How does this differ from the innovator route?
The innovator route tests whether a new proposition works in public practice. The partner route assesses how mature expertise, technology or services could connect responsibly and sustainably.
Will we become an iSyNAPS partner after a conversation?
Not automatically. A conversation only explores the functional fit. Listing, cooperation, procurement and contracting are separate decisions.
What information should we bring?
Describe the concrete contribution, maturity, relevant references, standards and interfaces, data requirements, management model and known dependencies.