I cloned Luma. Then I built GETHRS.
I wanted to build an event product.
Instead of starting from a blank page, I asked myself:
What if I cloned Luma?
So I did.
I studied how Luma handles:
- event creation
- landing pages
- RSVPs
- invitations
- attendees
- event management
- organizer experience
Then I rebuilt core flows from scratch.
Not to create another Luma clone.
To understand what makes an event product work.
That process led me to a different idea:
GETHRS — event management for B2B events.
Luma is great for communities, creators and public events.
But B2B events have different problems:
- attendee relationships matter after event ends
- organizers need CRM, not just guest lists
- companies manage recurring events
- speakers and partners need coordination
- event data should become useful commercial data
So I started changing direction.
The clone became prototype.
The prototype became product.
Now GETHRS is working.
You can see it here:
https://gethrs.app/
I built it because I wanted to answer one question:
Can one person build a focused alternative to a product as polished as Luma?
Next challenge isn't building.
It's getting first users.
I'll share what happens.
The B2B angle seems much stronger than simply being “Luma for businesses.”
What’s the first workflow where early organizers are telling you GETHRS is materially better than their current event stack?
That's exactly the bet. The first workflow where organizers tell us we're materially better is registration-to-CRM.
Today the typical stack looks like: event page on a public platform (or a bare form), attendee list in a spreadsheet, and then someone manually importing it into HubSpot — usually days later, often with the wrong source, sometimes never. For marketing, the event effectively didn't happen.
With GETHRS, the registration form captures the fields that actually matter in B2B (company and role, not just name and email), and every registrant lands in the organizer's HubSpot as a contact + company automatically, with the event as source. No CSV, no cleanup, attribution intact.
So the "aha" isn't the event page itself — it's that the pipeline exists the moment someone registers.
That registration-to-CRM handoff is a much sharper wedge than the event page itself. I’d be interested in digging into how organizers are responding to it. What’s the best email to reach you on?