FoundrexFoundrex
Case study · Events / B2B SaaS

From event planning to a warm welcome.

A multi-tenant B2B SaaS platform for event registration and communication — rewritten so organizers can plan, publish, sell, and check guests in from one workspace.

Client
EventPartners
Industry
Events / B2B SaaS
Year
2025
Role
Design & Engineering
lifecycle workflows
6
copilot specialist lanes
4
EventPartners dashboard showing active events, setup gaps, and Event Copilot
Overview

Event ops still splinter across tools — until someone drops the ball.

An events / B2B SaaS product needed a platform rewrite so registration and communication could run cleanly as a multi-tenant product. Planning lived in one place, the public site in another, tickets somewhere else, and door staff improvised at check-in.

We rebuilt EventPartners as a single multi-tenant workspace: dashboards for every event, program planning, website and form builders, ticket packages, and live door check-in — with an Event Copilot that drafts launch plans and exception handoffs for human review.

The rewrite keeps the organizer in control. AI specialists prepare the work; humans approve what guests see, what gets sold, and how tricky arrivals are handled at the door.

One workspace · plan, publish, sell, and welcome — multi-tenant by design
6
Lifecycle workflows in one platform
4
Copilot specialist lanes
1
Multi-tenant workspace model
Door
Live check-in with exception paths
EventPartners dashboard with event cards, setup gaps, and Event Copilot
Manage every event in one place.Workspace

A workspace dashboard that surfaces live events, setup gaps (no website yet, no form yet), and an Event Copilot ready to draft the next launch plan.

EventPartners program planner for agenda and setup
Plan the event before it goes public.Agenda

Structure the agenda and setup so planning stays attached to the same event record everything else will use.

Where it was breaking down

Where event platforms usually fall apart.

01
Fragmented tooling

Agenda, website, forms, tickets, and check-in lived in separate tools — so setup gaps only showed up when it was too late.

02
Single-tenant leftovers

The old product couldn't cleanly isolate workspaces, so multi-tenant registration and communication kept bending the architecture.

03
Door-day improvisation

Check-in exceptions had no clear policy path — staff improvised, and organizers lost the thread after the event ended.

How we built it

Rewrite the core. Ship the full event loop.

01
Phase 1
Map the organizer workflow

Turned planning → publish → register → sell → check-in into discrete product surfaces inside one tenant workspace.

02
Phase 2
Multi-tenant foundation

Rebuilt tenancy so events, contacts, forms, and tickets stay scoped to the right workspace.

03
Phase 3
Builders that stay connected

Shipped program, website, form, and ticket builders that share the same event truth — not four disconnected drafts.

04
Phase 4
Door + copilot

Added live check-in with exception handoffs and an Event Copilot that prepares launch plans for human review.

The system

Six surfaces. One event workspace.

Workspace dashboard

See every event at a glance — what's live, what's missing a website or form, and what needs attention next.

Program planning

Build the agenda and setup plan so the event structure is clear before anything goes public.

Website builder

Publish an event site from the same workspace — content stays aligned with registration and tickets.

Registration forms

Capture registrations with forms that match the event, then follow the funnel without leaving the product.

Tickets & packages

Sell admission with packages and availability managed beside the rest of the event setup.

Door check-in + Event Copilot

Scan arrivals in real time, escalate exceptions safely, and draft post-event follow-ups once attendance is final.

What we built

One multi-tenant platform for the whole event.

EventPartners runs planning, publishing, registration, ticketing, and check-in on the same multi-tenant foundation — with an Event Copilot that drafts the next move while organizers stay in the approval loop.

Inside the product

The interface, screen by screen.

Screen 01 · Website builder

Publish the event site from the workspace.

Build and ship the public event website without leaving the platform — content stays tied to registration and tickets.

PublishBrandContent
EventPartners website builder for publishing the event site
Screen 02 · Form builder

Capture registrations that match the event.

Design registration forms in-product so sign-ups, follow-ups, and attendance stay connected to one event.

RegistrationFunnelForms
EventPartners form builder for registrations
Screen 03 · Tickets

Sell admission with clear packages.

Configure tickets and packages alongside the rest of the event setup — commercial readiness without a separate system.

PackagesAvailabilitySales
EventPartners tickets and packages for selling admission
Screen 04 · Check-in

Welcome attendees — and handle exceptions.

Scan codes as people arrive, confirm check-ins instantly, and use Event Copilot for exception handoffs and post-event follow-through.

DoorQRExceptionsFollow-through
EventPartners door check-in with successful scan and Event Copilot
Tech stack

Rebuilt for multi-tenant event ops.

Next.js
Next.js
TypeScript
TypeScript
Node.js
Node.js
PostgreSQL
PostgreSQL
The impact

From scattered tools to one event workspace.

Metric
Before
With EventPartners
Event setup
split across tools
one multi-tenant workspace
Registration & site
disconnected drafts
builders on the same event record
Door day
improvised check-in
live scan + exception handoffs
After the event
attendance details drift
copilot drafts follow-through for review
6
Lifecycle workflows in one platform
4
Copilot specialist lanes
1
Multi-tenant workspace model
Scope of work

What we built

01
Multi-tenant platform rewrite
02
Workspace dashboard & event lifecycle UI
03
Program, website, and registration builders
04
Tickets & packages
05
Door check-in with exception handling
06
Event Copilot (launch plans + follow-through)