partner center
Co-creation isn't a consultancy buzzword here. It's the way the platform becomes smarter.
section b
A platform for the public sector has value only when it is aligned with the needs of the organisations that use it and with the dynamics of their domain. That cannot be delivered. That you build together.
Partner organisations are not clients purchasing software. They are co-architects who build the fabric with us — sources, taxonomies, context, interpretation. The platform therefore becomes richer for each new partner than for the previous one. And existing partners benefit automatically from the growing intelligence. That's not coincidental. It's the business model.
Partnership is about the Murmur engine — the underlying intelligence that takes a different form per challenge, from the mature UrbanStakes platform to lighter knowledge and research forms — not about a single product. If you recognise the Murmur approach in your own domain, that is the basis to build together.
section c
| Standard SaaS relationship | Murmur relationship |
|---|---|
| Vendor → client (transaction) | Co-architects (committed together) |
| Implementation = "setup" | Onboarding = "domain codification" |
| Roadmap with the vendor | Roadmap governance shared |
| Data = client-owned, we deliver the tool | Data = partner-owned, we deliver the fabric |
| Support = ticket system | Support = dialogue with domain knowledge on both sides |
| Success = retention, expansion | Success = impact in the domain |
section d
How the tenth partner benefits from the first nine.
Every partner brings something in:
The platform aggregates this with strict respect for ownership and sensitivity (see Trust Center) into a fabric that is richer for each next partner.
The tenth partner gets a 10× richer platform than the first.
And existing partners benefit automatically from the growing intelligence. That's why "collective intelligence" is not a marketing claim — it's the business model.
section e
Three organisations building the fabric with us.
Brengt sources, casework, anti-discrimination taxonomy.
Ontvangt trend visibility ahead of governance questions, evidence for policy conversations.
Brengt network of experts, professionals and domain specialists.
Ontvangt trainings fed by current events — a living curriculum, not a static programme.
Brengt local traction, network activation, implementation capacity.
Ontvangt impact portfolio and systems-thinking platform for public-sector work.
Existing partners benefit automatically from the growing intelligence — each new contribution enriches the fabric for all.
section f
Pricing
No per-seat licenses. The pricing model rewards participation, not usage. Basic membership grants access to the platform, own tenant and all core features. Core commitment is a multi-year partnership with a seat on the Partner Council. Differentiation not by user count, but by scale of contribution and domain complexity.
Data & IP
You retain all rights to your data. Jointly developed taxonomies and patterns are 'common' — CC-BY-SA-like, within Murmur | Works. Available to all partners in the network, not to outsiders. No training-data extraction for commercial models. Anonymous aggregates only with explicit partner opt-in.
Roadmap
Quarterly Partner Council — partners co-decide on the next features. Prioritisation on societal impact, not ARR growth. Transparent changelog: who asked what, what was built, what was not — and why.
Onboarding
Duration: six to eight weeks, not one to two. Content: shared taxonomy workshop, source curation, context annotation, role definition. Output: not just a working system but a documented domain model that stays yours. Team: Murmur engineer, Murmur domain curator and one or two practitioners from your side.
section g
Step 1 — Exploratory call
What you bring in, what you receive. No commitment.
Step 2 — Fit analysis
We draft a short analysis: does your domain fit the current fabric? Which sources would we curate? Which taxonomy do you bring?
Step 3 — Contract conversation
Partnership agreement including data rules, IP arrangements, commitment level and pricing.
Step 4 — Onboarding
Domain codification. End: working platform + documented domain model.
Step 5 — Partner Council seat
The Partner Council is informal — an advisory board that meets roughly once per quarter. Partners co-decide on the roadmap.
section h
section i
Thinking about becoming a co-architect? Let's schedule an exploratory conversation — we walk through what you would bring in and what you would receive. No scripted pitch.
Discuss partnership