CASE STUDY · CRM & AUTOMATION

Event management. Built into HubSpot.

I replaced standalone event software with a custom HubSpot-based system. Registrations, daily check-in and follow-up, connected to the CRM the team already used.

Platform
HubSpot CRM
My role
Architecture & build
Focus
Event operations

Anonymized case study. Company details omitted; visuals use fictional demo data.

01 / Event workspaceDemo preview
Search events or registrations Events 12 active Upcoming Workshop 01 Two days · 146 registrations Workshop 02 Two days · 118 registrations Workshop 03 Two days · 102 registrations Workshop 01 · Event workspace Overview of dates, registrations, and attendance status Overview 2 event days 146 registrations 97 checked in Open event ATTENDEE LIST Name Registration Status Day 1 Name Surname 1 Confirmed Checked in 9:06 AM Name Surname 2 Confirmed Not yet — Name Surname 3 Waitlist → approved Checked in 9:19 AM
Events · dates · registrations01 / 03

One event.
Too many systems.

The website handled the first interaction. A separate event platform managed registrations. HubSpot held the customer relationship. The team had to connect the pieces themselves.

The cost went beyond software subscriptions. Each event brought more exports, manual updates and places where information could fall out of sync.

01 /

Paying for overlap

A separate event platform added recurring costs for workflows that could be brought into the existing CRM.

02 /

Repeating the work

Registration lists, contact details and attendance updates had to move between tools before the team could use them.

03 /

Missing the full picture

Event participation sat apart from the contact record, making follow-up and reporting harder than they needed to be.

Start with the workflow.
Then build the system.

I mapped what the team actually needed to run an event, then built those operations around connected HubSpot records. The interface followed the workflow.

Custom objects Custom properties Record associations Custom UI
01 /

Model the relationships

Events and registrations become structured records linked to existing contacts. Each registration belongs to a person and an event, keeping repeat attendance connected without duplicating the contact.

02 /

Define the right properties

Event dates, registration status and attendance are stored against the relevant records. Clear properties give the interface, workflows and reports the same information to work with.

03 /

Make it practical for the team

A purpose-built interface brings event selection, attendee lookup and check-in into one workflow. Staff can do the job without navigating the underlying CRM structure.

Pick a day.
Find a person.
Check them in.

01

Choose the event and day

Open the event and select the day being managed. The team works from the relevant attendee list.

02

Find the attendee

Look up a registered person and see their registration details in the same interface.

03

Confirm attendance

Check the person in for the selected day. Their status updates in the interface and is saved to the connected CRM record.

04

Keep the whole team in sync

The attendance information is available for follow-up and reporting, without another spreadsheet export.

02 / Attendance & daily check-in Fictional demo data
Workshop 01 · Daily check-in Search attendee name or email Today Day 1 · Session 01 Day 2 · Session 02 AT THE DOOR 97 Checked in so far Attendee list Name Surname 1 Checked in Name Surname 2 Arrived Name Surname 3 Pending Selected attendee Name Surname 1 Registration: Confirmed Seat: Workshop 01 · Day 1 Contact linked in HubSpot Check in attendee View CRM record RESULT New stasus saved to system Updated status synced to CRM.
A simpler check-in: attendee list, selected day, and attendance status.02 / 03

The click is simple.
The rest is connected.

Bringing event data into HubSpot made it possible to connect the operational steps with the communication and reporting around them.

01 /

Registration → connected records

Keep the person, event and registration associated, so later steps use the right context.

02 /

Event details → communication

Use registration status and event information to drive relevant confirmations and reminders.

03 /

Attendance → follow-up & reporting

Use recorded attendance to inform post-event communication and understand participation.

04 /

The outcome

A separate event platform, replaced. Lower software spend. Fewer manual handoffs.

03 / Connected workflowsConceptual demo
Connected workflows. One system. Registration · automation · reporting INPUT Registration New paid attendee Correct event linked Contact associated LOGIC LAYER HubSpot automation Registration updated Status and attendance stay in sync. Emails automated Confirmations and reminders use event data. Reporting connected Attendance and outcomes in one place. OUTPUT Business impact Fewer handoffs Lower software costs Cleaner follow-up
Registration · communication · follow-up · reporting03 / 03
THE OUTCOME

A separate event platform, replaced. Lower software spend. Fewer manual handoffs.

HAVE A SIMILAR CHALLENGE?

Your systems should
work together.

Replacing a tool, connecting data or removing manual work? Let's look at what your team needs and build a simpler way to get it done.