The platform
What runs underneath the cycle.
The cycle on the home page is the surface of the work. This is the system that runs underneath it, and the principles that hold it together.
Convenor is not a feature collection. It is a single system where every interaction produces structured data, every event makes the next one easier, and the platform becomes more useful with each cycle of use. This page is for the buyer who wants to look beneath the surface before committing.
Each of the seven stages on the home page produces data by simply being used. The architecture below is what turns that data into the strategic intelligence behind every decision.
The architecture
Every interaction is a data point.
The platform never asks for the same information twice. The work itself is what produces the record, and the record is what produces the intelligence.
01 · The work
Everyday actions
Sending an invitation, recording an RSVP, checking a speaker in, capturing a quote. The ordinary motions of running an event.
Becomes raw signal
02 · The record
Structured data, automatically
Each interaction is captured as engagement data, attendance data, response timing, audience composition, return patterns. No separate input step.
Becomes structured record
03 · The intelligence
Recommendations and insight
Over time, the record sharpens the platform's recommendations. When to invite, who to re-engage, how each speaker prefers to be approached. The platform learns alongside you.
Becomes strategic intelligence
The platform's value is not in any single feature. It is in how the features compound across every event you run.
The strategic layer
One quarter, at a glance.
Every event captured cleanly is a small contribution to the strategic intelligence of your organisation. Acceptance rates, audience composition, return rates, all derived automatically from the platform's underlying record. The dashboard is the moment the data becomes useful to your director, your board and your funders.
The dashboard is the natural consequence of the work having been captured cleanly the first time.
The design constraints
Six principles, built into every feature.
These are not beliefs we chose to print on the website. They are the rules we follow in every feature decision. They are what makes the platform feel different from a generic CRM with an event tab bolted on.
Data capture is a byproduct, never a chore.
Every interaction with the platform produces structured data automatically. The speaker accepting is what creates the engagement signal. The attendance check in is what feeds the return rate. We never ask users to enter the same information twice.
The relationship stays human, the admin gets automated.
Convenor does not pretend to be a person. It does not write your invitations or replace the personal contact with senior speakers. What it automates is the part that should never have been a person's job: chasing, formatting, copy pasting, file naming, status tracking.
The platform earns trust before it suggests.
Discovery and recommendations come later, once the platform has accumulated enough data to be genuinely useful. We would rather show nothing than show a wrong recommendation that breaks trust.
Concurrency is the default, not the edge case.
Several events at different stages run at the same time. The interface reflects this. The morning view shows you what is outstanding across all of them, not just one.
The path of least resistance wins.
No team will adopt a platform that asks them to abandon what already works. The starting point is the workflows you already run, in Excel, in shared inboxes, in whichever tools a colleague stitched together three years ago. Where it makes sense we integrate; where import is the right call, our flow auto matches columns, flags duplicates and asks for review only where the data is ambiguous. The platform meets you where you are, ready to use from day one.
Built for European data, by European hands.
Convenor is hosted in the EU and built on a clean GDPR foundation. Consent is captured at every interaction, retention is explicit, and your stakeholders' data stays in jurisdictions you can defend to your board, your funders and your data protection officer.
The same twelve, resolved
What changes when the system runs underneath.
The same twelve frustrations from the home page, met one by one. Not by adding more tools, but by running them all through a single record.
The visibility, the comparability, the credibility, addressed not by another reporting tool, but by data that exists because the work itself produced it.
01 — Coordination
One screen, every event.
The spreadsheet labyrinth becomes a single live view. Invitee lists, RSVPs, speakers and budget all sit in one place, agreeing with each other by default.
02 — Speakers
Speakers confirm themselves.
Each speaker gets a personal portal. They upload their own bio, photo, title and consent. The four to seven email exchanges per speaker collapse into one structured flow.
03 — Invitations
RSVPs land where the work lives.
Replies come back through one channel, structured at source. No reconstruction, no merging from inboxes, no last minute call to count who is actually coming.
04 — Knowledge
Yesterday's event, ready to clone.
Every recurring event keeps its concept, its invitee patterns, its speaker history. The next edition starts with the structure of the last one already in place.
05 — Memory
Soft knowledge made structural.
Who responds, who is reliable, who matters, recorded as part of the workflow rather than someone's inbox. When a colleague leaves, the relationships do not leave with them.
06 — Reporting
The report writes itself.
Attendance, engagement, audience composition, gender balance, sector mix: the data is already structured. The post event report is a click, not a sprint.
07 — Visibility
The whole programme, on one screen.
Every event, every coordinator, every stage of preparation visible from a single view. No more reconstructing the picture across spreadsheets and weekly check ins.
08 — Reporting
Funder reports, evidenced.
Quantified evidence of convening impact, generated from the data the platform already holds. No reconstruction, no gaps, no quiet rounding before submission.
09 — Strategy
The programme that actually ran.
Real time visibility on whether the events that happened reflect the strategic direction. Drift becomes visible early, not in the year end review.
10 — Memory
Relationships held by the institution.
Years of accumulated trust captured as institutional record. When senior staff move on, the relationship history stays. The next generation inherits the work.
11 — Comparability
Quarter on quarter, comparable.
Consistent metrics across every event. Are you reaching new audiences? Is engagement deepening? The questions that used to be unanswerable are now charts.
12 — Credibility
Boardroom answers, evidenced.
Probing questions about programme effectiveness met with structured data, not constructed answers. Confidence in the room because the underlying record is solid.
How adoption actually works
From conversation to independent operation, in four phases.
Convenor is built to be adopted carefully, not flipped on. Each phase exists for a reason. The goal is not speed of installation. It is speed of trust.
Phase one
Conversation
We sit down with you for an hour. We listen to how your team currently runs events, where the friction is, which reports you owe to whom, what your data protection officer asks about. No pitch deck. We are figuring out together whether the platform fits the shape of your work.
Phase two
Setup
We import your existing contacts, configure your event templates, set up your branding, and walk through the data structure with you. Your existing spreadsheets become the seed of your live database. Nothing is rebuilt from scratch.
Phase three
First event
We run an event with you. You drive, we are in the room. Every awkward moment, every "wait, how does this part work", every "I would expect this button to do X" gets noted and addressed. You see the system work end to end before you commit to running it alone.
Phase four
Independent
From the second event onwards, your team runs it. We stay reachable for questions, but the work is yours. The platform is now part of how the team operates, not a thing the team is using on top of how it operates.
Integrations
What the platform connects to today, and what is on the near roadmap.
- ✓ Microsoft 365 calendar & email
- ✓ Google Workspace calendar & email
- ✓ Existing CRM contact import (CSV / Excel)
- ✓ Webform embed for public events
- ○ Salesforce two way sync
- ○ HubSpot two way sync
- ○ Mailchimp / Brevo audience segments
- ○ Power BI / Looker direct connectors
How we work with you
The relationship after setup, in plain terms.
A named contact at Convenor for every customer. A response time we publish and meet. A monthly check in for the first six months, then quarterly. A roadmap that is shaped by actual customer requests, with the next quarter's priorities visible to you.
Your friction with the platform is our roadmap. Your suggestion in March often becomes a feature in May. The platform grows around the people who use it, which means it grows around you.
A closing thought
A platform is a thousand small decisions stacked on top of each other. We have made ours to be reliable, defensible, and quietly serious. The kind of system you can stand behind in a boardroom, leave to a colleague when you are away, and trust to be there when the next event starts.
Convening, made deliberate.
Ready to look at your own work through this lens?
We are running a free founding cohort with a small number of Brussels policy organisations through 2026. The conversation starts with an hour, no slide deck, no commitment.
Start the conversation →