The before — every event rebuilt from scratch.
Events are bursty and detail-dense, and Lumen reassembled each one across five tools. “The inquiry was in the CRM, the proposal in a design tool, the contract in DocuSign, the deposit in Stripe, and staffing in a spreadsheet,” says Priya Anand, Founder. “Every event was re-keyed four times before anyone lifted a tray.”
Deposits slipped because the contract and the payment lived apart, and staffing the night-of meant cross-referencing a spreadsheet against a calendar against a group chat.
$920/month across five tools. Events re-keyed four times before execution. Late deposits from contracts disconnected from payments.
The switch — the event becomes the record.
Lumen built one event record holding the proposal, contract, deposit schedule, and staffing, and migrated its active calendar first. Proposals now reuse past events as templates.
“Building a proposal used to be a half-day,” Anand says. “Now it’s an hour because last summer’s wedding is right there to start from. Same record, new date.”
What got replaced
| Old tool | Replaced by Mewayz module | Monthly saving |
|---|---|---|
| Event CRM | CRM & Leads | $160 |
| Proposal builder | Proposals & Quotes | $120 |
| DocuSign | Contracts & e-Signatures | $140 |
| Stripe Billing add-on | Deposits & Payments | $120 |
| Staffing spreadsheet + tool | Scheduling & Staffing | $130 |
| Total old stack | Mewayz Business | save $920/mo |
The unlock — one record per event.
With the full event lifecycle unified, the team stopped rebuilding and started reusing:
- Proposals template from past events — same record, new date
- Contracts and deposit schedules attach to the event automatically
- Signing the contract triggers the deposit request
- Day-of staffing reads from the same record as the booking
When signing the contract is what triggers the deposit request, payment stops being a separate task someone has to remember. The workflow collects on its own.
The new normal — more events, same team.
“We booked a third more events this season without adding coordinators,” Anand says. “The capacity was always there — it was just buried in re-keying. One record per event set it free.”