One chamber. One system it owns.
Membership was spread across GlueUp, Stripe and GoHighLevel. The first job was one chamber-owned database. Then a suite built on it.
- Client
- MOVE Chamber
- Built
- Public site, member portal, staff console and conference tools
- Owned by
- MOVE Chamber
First, the records.
Then the tools.
Membership lived across three tools. I started with one database in the chamber’s name.
Each new piece cost less than the one before because the data underneath was right.
in MOVE’s name
- Public site
- Member portal
- Staff console
- Conference site
- Ticketing
- Door check-in
- Payments
- Advocacy tools
What got built
The public site.
The public site is one piece of the suite built on MOVE’s own database.
The public website, built on the chamber’s system. The member portal.
The member portal includes AI-drafted listings. Staff publish their own changes.
The member portal’s sign-in screen. Conference, tickets and the door.
The suite also includes the conference site, ticketing and door check-in, alongside payments, email and advocacy tools.
The conference website on a phone.
Staff publish
their own changes.
The public site, member portal, staff console and conference tools sit on the chamber’s own database.
Needs a fact: the recurring task that disappeared, and where that staff time went instead.