One event on the surface, five products underneath.

An "event platform" is never one product.

Each unit was a full product with its own users, its own jobs and its own best-in-class competitor: the email engine competed with dedicated marketing tools, registration & ticketing with ticketing platforms, the webpage builder with site builders, and sessions and exhibitor management with specialist event software.

But the customer doesn't buy five products. They buy one event that has to go right, and they feel every seam: a registration that doesn't show up in the email audience, a session change that doesn't update the event page. The job was to run five products like a portfolio and ship them like one.

Run it like a portfolio. Ship it like one product.

• Gave every unit a clear owner: each PM on the team owned a unit end-to-end, its users, its metrics, its backlog, instead of everyone owning everything and no one owning anything.
• Played editor on the roadmap, not author: PMs brought the bets, I sequenced them across units against revenue, retention and what enterprise deals actually needed next.
• Protected the shared spine: one contact and registration data model, consistent patterns across builders and dashboards, so five units never felt like five tools.
• Was the tie-breaker: when units competed for the same engineers or the same release window, the call got made quickly and with reasons attached.
• Grew the team, not just the product: coached 3–4 PMs through discovery, specs and stakeholder fights, growing them from feature owners into unit owners.

A platform that scaled with the business, and a team that ran it.

The platform carried Hubilo's events and webinars at enterprise scale, every email send, registration, event page, session and expo booth, and became the foundation the Webinar+ pivot launched from. Just as durable: a team of PMs who could each run their unit without me in the room.