One Platform. Many Events. Any Sector.
Client
Global B2B Events and Exhibitions Company
Industry
B2B Events / Platform Engineering
Engagement
Greenfield platform development
What This Enabled
A unified platform that could support multiple event formats and sectors while treating users as a shared, continuous base. This enabled cross-event engagement and scalable portfolio growth.
About the Project
Context and Strategy
The client managed a global portfolio of B2B events across sectors such as retail, grocery, and education technology. The portfolio had grown through acquisitions, resulting in a collection of independently built and incompatible platforms.
As the portfolio expanded, this fragmentation became a structural constraint. The situation became more acute when the pandemic forced a rapid shift toward virtual event formats, requiring new capabilities on top of already fragmented systems.
Understanding the Challenges
A Growing Portfolio, a Fragmented Foundation
The core issue was not just fragmentation. Each platform encoded assumptions about a specific event model, making reuse difficult and limiting the ability to evolve the system.
User Duplication
Participants were duplicated across systems, preventing a unified view of users across events. The same person attending multiple events existed as separate records with no shared history.
Operational Debt
Scaling required multiplying specialist headcount due to platform-specific knowledge. Each system demanded engineers familiar with that specific codebase.
Rigid Structures
Supporting new event types required structural code changes instead of configuration. The systems encoded assumptions about a specific event model, making reuse difficult and limiting the ability to evolve the system.
Business Constraint
Fragmented systems limited cross-event engagement, marketing, and portfolio-level insights. The business could not treat its user base as a continuous asset across its portfolio.
How We Approached It
Events as Configurable Variations
We shifted the model from event-specific systems to treating events as configurable variations over a shared core platform. This required clear boundaries between shared capabilities and event-level variability.
Core vs Configuration
Defined a strict boundary between shared capabilities and event-specific behaviour. Registration, matchmaking, meeting booking, and reporting were built once and served every event without forking.
Unified Identity
Introduced a centralised identity layer to enable a single user lifecycle across events. A participant could attend multiple events with a consistent identity and continuous engagement history.
Format Abstraction
Treated virtual events as a variation of the same platform instead of building a separate system. Virtual was built as a configuration layer over the same core, not as a different product.
Modular Design
Built services that could scale independently based on event demand. Matchmaking, registration, and meeting scheduling each scaled without affecting the rest of the platform.
What We Built
A Multi-Tenant Platform for High-Density Events
A multi-tenant platform designed to support high-density B2B interactions across multiple events and sectors, with identity and configuration shared across the full portfolio.
Unified Platform
Registration, onboarding, and catalogue management across all event types and sectors. One codebase, one deployment, serving multiple concurrent events each with its own brand and workflow.
Matchmaking Engine
Algorithmic matching system to score compatibility and enable large-scale meeting scheduling. The core commercial value driver for every B2B event, with configurable parameters per sector and event type.
Unified Identity Layer
Central identity provider enabling cross-event participation. A single user lifecycle across the full event portfolio, making cross-event engagement and portfolio-level insights possible for the first time.
Runtime Configuration
Event branding, workflows, and feature availability driven dynamically without code changes. New events onboarded through configuration alone, with no new code branch or additional specialists required.
Impact
One System. A Different Way to Scale.
The unified platform changed both system operations and how the business could scale its event portfolio.
Platform Consolidation
Multiple format-specific platforms replaced by a single, maintainable system. Engineering effort consolidated into one codebase, one deployment, and one set of operational standards.
User Unification
Enabled a portfolio-level view of users across events for the first time. Participants could engage across the full portfolio with a single, continuous identity rather than separate records per event.
Commercial Leverage
Made cross-event marketing and engagement possible. The client could now treat its user base as a shared asset across the portfolio rather than isolated populations within each event.
Operational Efficiency
New events can now be launched through configuration rather than development. No new code branch, no additional specialists, and no duplicate infrastructure for each event added to the portfolio.
Proven Scale
Facilitated over 9,000 meetings across approximately 10,000 attendees at flagship events. The matchmaking and scheduling engine handled high-density interaction volumes reliably across concurrent events.
Key Insights
Most event platforms fail to scale because they model events correctly but users incorrectly.
Unifying identity across events is what turns a set of systems into a platform. Without a shared user layer, every event is an island and the business loses the compounding value of its full portfolio. Platform consolidation is a configuration problem before it is an engineering one. Identify what truly belongs in the core and make everything else configurable.
Consolidating fragmented platforms or managing complex multi-product engineering?
Get in touch