Work/Supermomos/Internal tools

Supermomos internal tools: one workspace for the team behind every event.

The CRM, campaign tools, partner revenue and event operations the Supermomos team uses every day, plus an AI that reads every RSVP against the event’s target audience.

ClientSupermomos · US
DomainCommunity · Events · Internal tools
My roleLead Product Designer
Live linkVisit site
Supermomos · Internal tools
At a glance
01

Audience fit (AI)

Fit tags on every RSVP.

02

Sales CRM

People, companies and deals.

03

Speaker database

Find the right speaker.

04

RSVP list

Approve guests in bulk.

05

Email blasts

Emails in four steps.

06

Seating planner

Plan the tables.

07

Cards and expenses

Log spend at the venue.

08

Patron profiles

One view of each partner.

09

Invoices and contracts

Link invoices to events.

Audience fit (AI)Sales CRMSpeaker databaseRSVP listEmail blastsSeating plannerCards and expensesPatron profilesInvoices and contracts

Audience fit (AI)

Hosts describe who the event is for, and every RSVP gets a Good fit, Partial fit or Not a fit tag. The matching facts show as small chips, so hosts approve the right guests faster.

01 / The business problem

Behind every Supermomos dinner sits a small team doing a lot of manual work: qualifying partners, inviting speakers, approving guests, sending emails and keeping receipts.

That work lived across spreadsheets, inboxes and a basic admin panel. Records went out of date, the same person existed twice, and nobody saw an event’s costs until it was over.

The design challenge was to give a small team one connected workspace, fast enough for daily use on a laptop and simple enough to use on a phone at the venue.

The tools follow the work of a dinner from start to finish: a CRM for partners, a speaker database, fit tags on every RSVP, scheduled email blasts, a seating planner, expenses from the venue and invoices linked to events.

User journey

One dinner,
end to end.

One event team member, from qualifying partners to closing the books. Each step moves out of a spreadsheet and into one connected workspace.

1

Qualify

2

Invite

3

Approve

4

Run the night

5

Close out

What they do
Qualifies partners and the companies behind them.
Invites speakers and promotes the event.
Decides which guests get a seat.
Plans the seating and logs spend at the venue.
Matches invoices and contracts to events.
What gets in the way
Records in spreadsheets go out of date, and the same person exists twice.
Easy to invite the same speaker twice or rewrite the same email.
Checking every RSVP against the audience takes time.
Costs stay hidden until the event is over.
Payments live across inboxes and a basic admin panel.
How the design helps
→ In the designSales CRM: one record per person and company, with emails, deals and comments in tabs.
→ In the designSpeaker database ranked by fit with status tabs, and email blasts from one template library.
→ In the designGood fit, Partial fit or Not a fit on every RSVP, with bulk approve, waitlist or decline.
→ In the designSeating planner with a PDF for the venue, and expenses logged on a phone that feed the event P&L.
→ In the designInvoices allocated to events with a progress bar, and events without a contract flagged.
12345
1

Qualify

What they do

Qualifies partners and the companies behind them.

What gets in the way

Records in spreadsheets go out of date, and the same person exists twice.

→ How the design helps

Sales CRM: one record per person and company, with emails, deals and comments in tabs.

2

Invite

What they do

Invites speakers and promotes the event.

What gets in the way

Easy to invite the same speaker twice or rewrite the same email.

→ How the design helps

Speaker database ranked by fit with status tabs, and email blasts from one template library.

3

Approve

What they do

Decides which guests get a seat.

What gets in the way

Checking every RSVP against the audience takes time.

→ How the design helps

Good fit, Partial fit or Not a fit on every RSVP, with bulk approve, waitlist or decline.

4

Run the night

What they do

Plans the seating and logs spend at the venue.

What gets in the way

Costs stay hidden until the event is over.

→ How the design helps

Seating planner with a PDF for the venue, and expenses logged on a phone that feed the event P&L.

5

Close out

What they do

Matches invoices and contracts to events.

What gets in the way

Payments live across inboxes and a basic admin panel.

→ How the design helps

Invoices allocated to events with a progress bar, and events without a contract flagged.

Swipe to follow the journey
02 / What I owned

What I owned.

01

Information architecture for the CRM

Structured people, companies, speakers and partners as linked records with one detail panel and clear sections.

02

Bulk workflows for long lists

Designed filters, multi-select actions and status tabs for RSVP lists, speakers and contacts.

03

Campaigns and email automation

Reworked the four-step campaign flow, templates and scheduling, including continuous sends.

04

Event operations on mobile

Designed the app views for receipts, company cards and the event P&L used on site.

05

Requirements and delivery

Turned sprint requirements into flows with the CEO and engineers, and reviewed each build before release.

Guest questionnaire
Internal notes
03 / Selected features

Tools the team
opens every day

Six examples of how I turned repeated manual work into a few clear steps for the operations and sales team.

Feature 01

A sales CRM that keeps every conversation in context

?The challenge

The sales team needs one place to see a partner’s company, contacts, open deals and what colleagues already know before they follow up.

What I designed
  1. 01Kept company details, target audience and active events in a fixed panel beside the record.
  2. 02Grouped emails, transcripts, qualification, contacts and deals into tabs on the same record.
  3. 03Added internal comments that only the team can see, with the author and date on every note.
  4. 04Flagged outdated details and showed who last verified each record and when.
A sales CRM that keeps every conversation in context
Feature 02

Finding and inviting the right speakers

?The challenge

Hosts need to find speakers who fit an event, know who has already been contacted, and avoid inviting the same person twice.

What I designed
  1. 01Ranked speakers with a score and showed past and upcoming events on each row.
  2. 02Added status tabs for not started, email sent, confirmed and declined.
  3. 03Made “checked by team” visible so unverified profiles stand out.
  4. 04Let hosts assign a speaker to an event and send the invite from the same list.
Finding and inviting the right speakers
Feature 03

Email blasts that run on a schedule

?The challenge

The team sends invitations, reminders and follow-ups for every event, and needs to reuse content, target the right guests and send at the right time.

What I designed
  1. 01Split sending into four steps: content, recipients, preview and schedule.
  2. 02Added one-time sends, scheduled sends and continuous automation with an end date.
  3. 03Warned senders when they edit a blast that a colleague created.
  4. 04Added a shared template manager so the team stops rewriting the same email.
Email blasts that run on a schedule
Feature 04

Showing partners what they have used

?The challenge

Patrons needed to track their commitments, see what they had used and register attendees for upcoming events.

What I designed
  1. 01Placed commitments and usage progress beside upcoming events, so partners check both in one view.
  2. 02Showed used and remaining events within each commitment, with the discount applied.
  3. 03Added an Add attendees action on each upcoming event.
  4. 04Kept a public link so partners can share the profile with their own team.
Showing partners what they have used
Feature 05

Allocating invoices to events

?The challenge

Finance needed to know which events each invoice pays for, and to catch events that were never linked to a contract.

What I designed
  1. 01Designed an allocation drawer that shows what is left to allocate as a progress bar.
  2. 02Listed available events with their invoice status, and greyed out the ones already invoiced.
  3. 03Flagged unlinked events with a Link to contract action.
  4. 04Kept allocation internal, so partners never see reconciliation notes.
Allocating invoices to events
Feature 06

A fit tag on every RSVP

?The challenge

Hosts need to see at a glance which guests match before they approve anyone.

What I designed
  1. 01Added a fit tag beside each guest: Good fit, Partial fit or Not a fit.
  2. 02Showed the matching facts as small chips, such as role, industry and funding stage.
  3. 03Added an empty state that invites hosts to add a target audience first.
  4. 04Kept approve and decline where hosts already use them.
A fit tag on every RSVP
User flow

From an RSVP
to an approved guest.

How the event team decides who gets a seat, using Audience fit tags instead of checking every profile by hand.

Flow for: Event team
StartStep on a screenDecisionDone

Describe who the event is for

Start

The host writes the target audience for the event.

Audience fit
1

RSVPs come in

Every RSVP gets a Good fit, Partial fit or Not a fit tag, with the matching facts as chips.

RSVP list

Good fit?

No

Partial fit goes to the waitlist; Not a fit is declined

No

Partial fit goes to the waitlist; Not a fit is declined

Yes
2

Approve in bulk

Approve, waitlist or decline many guests at once by status tab.

RSVP list
3

Email the approved guests

Content, recipients, preview and schedule in four steps.

Email blasts

Plan the tables

Done

Guest profiles beside each seat, then a PDF for the venue.

Seating planner

From scattered spreadsheets to one workspace the whole team uses.

ClientSupermomosMy role · Lead Product Designer
References
  • Edwina Yeo · CEO
  • Zheng Kaizhong · CTO
  • Kien Van Truong · Technical Lead
supermomos