Qualify
Qualifies partners and the companies behind them.
Records in spreadsheets go out of date, and the same person exists twice.
Sales CRM: one record per person and company, with emails, deals and comments in tabs.
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.
Fit tags on every RSVP.
People, companies and deals.
Find the right speaker.
Approve guests in bulk.
Emails in four steps.
Plan the tables.
Log spend at the venue.
One view of each partner.
Link invoices to events.
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.
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.
One event team member, from qualifying partners to closing the books. Each step moves out of a spreadsheet and into one connected workspace.
Runs every dinner with a small team
Up-to-date records, fewer manual steps, and costs visible before the event is over
Qualifies partners and the companies behind them.
Records in spreadsheets go out of date, and the same person exists twice.
Sales CRM: one record per person and company, with emails, deals and comments in tabs.
Invites speakers and promotes the event.
Easy to invite the same speaker twice or rewrite the same email.
Speaker database ranked by fit with status tabs, and email blasts from one template library.
Decides which guests get a seat.
Checking every RSVP against the audience takes time.
Good fit, Partial fit or Not a fit on every RSVP, with bulk approve, waitlist or decline.
Plans the seating and logs spend at the venue.
Costs stay hidden until the event is over.
Seating planner with a PDF for the venue, and expenses logged on a phone that feed the event P&L.
Matches invoices and contracts to events.
Payments live across inboxes and a basic admin panel.
Invoices allocated to events with a progress bar, and events without a contract flagged.
Structured people, companies, speakers and partners as linked records with one detail panel and clear sections.
Designed filters, multi-select actions and status tabs for RSVP lists, speakers and contacts.
Reworked the four-step campaign flow, templates and scheduling, including continuous sends.
Designed the app views for receipts, company cards and the event P&L used on site.
Turned sprint requirements into flows with the CEO and engineers, and reviewed each build before release.
Six examples of how I turned repeated manual work into a few clear steps for the operations and sales team.
The sales team needs one place to see a partner’s company, contacts, open deals and what colleagues already know before they follow up.
Hosts need to find speakers who fit an event, know who has already been contacted, and avoid inviting the same person twice.
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.
Patrons needed to track their commitments, see what they had used and register attendees for upcoming events.
Finance needed to know which events each invoice pays for, and to catch events that were never linked to a contract.
Hosts need to see at a glance which guests match before they approve anyone.
How the event team decides who gets a seat, using Audience fit tags instead of checking every profile by hand.
Flow for: Event teamThe host writes the target audience for the event.
Audience fitEvery RSVP gets a Good fit, Partial fit or Not a fit tag, with the matching facts as chips.
RSVP listPartial fit goes to the waitlist; Not a fit is declined
Partial fit goes to the waitlist; Not a fit is declined
Approve, waitlist or decline many guests at once by status tab.
RSVP listContent, recipients, preview and schedule in four steps.
Email blastsGuest profiles beside each seat, then a PDF for the venue.
Seating planner