The work continues after the inquiry
Main Event Co is my DJ and photo-booth business. Operating it gave me direct insight into the work that sits behind an event: checking availability, managing bookings, gathering planning details, coordinating music and timelines, preparing agreements, collecting payments, and keeping track of what is still outstanding.
The website needed to support that broader customer journey. A polished public presence was one part of the problem; the business also needed a practical way to organize the information required to deliver each event.
Finding the bottleneck
Event information becomes harder to manage when each step lives separately. The inquiry, booking, planning details, contract, and payments all refer to the same event, so they need to stay connected as it develops.
Different services also create different requirements. DJ clients need music preferences and an event timeline. Photo-booth clients need design selections. Availability needs to distinguish between DJ service, photo-booth service, and a combined booking. Those operating details shaped the application.
What I built
I built a connected platform with three interfaces: the public website, a client portal, and an administrative back office. The portal also connects photo-booth design selection to the relevant booking, helping keep client choices alongside the rest of the event details.
Public website and inquiries
Service, event, and location pages, availability checking, and inquiry and quote-capture workflows that connect prospective customers to the business.
Booking administration
Tools for leads, clients, bookings, venues, availability, contracts, payments, expenses, and reporting.
Client portal
An invitation-based workspace where clients can access their booking, planning information, agreement, payments, and applicable photo-booth design selections.
Event timeline and music planning
Client tools for building an event timeline and recording must-play, preferred, and do-not-play songs, including Spotify search. Planning information stays attached to the booking.
Contracts
Separate template types for DJ, photo-booth, and combined service, with client signing and supporting email workflows.
Payments
Stripe payment handling connected to booking records, with webhook updates for payment outcomes.
Customer communications
Reusable email templates populated from booking information, with preview and sending tools for event-related messages.
Pricing decision support
A quote tool and forecast view that use historical booking information to surface demand and lead-time considerations. Recommendations support the owner's judgment; they are not a guarantee of pricing performance.
Built for the business and its clients to manage
Administrative controls let the business manage date holds and unavailable dates separately for DJ and photo-booth services, maintain venue and recommended-vendor information, and create, edit, and activate contract templates. These supported updates are stored as application data, so they do not require changing application source files or redeploying the website.
Clients can maintain supported planning details, timeline items, and music requests directly in their portal. That gives them a way to contribute to the event plan while keeping the information attached to the correct booking.
The controls reflect the work people actually need to do. An availability change, a revised contract template, or a new song request can be handled through the appropriate interface. Broader design changes and pricing-model changes can still require development.
What the platform enables
The result is a connected customer and administrative experience extending from initial interest through event preparation. Clients have a dedicated place for their planning and booking information, and the business has tools to manage the records behind each event.
It also brings operating knowledge into the software: service-specific availability, music priorities, contract variations, and event timelines are represented directly in the workflows. Routine maintenance can happen through the administrative interface, and clients can participate in planning through their own workspace.
My contribution
As the business owner and builder, I translated firsthand operating needs into the public website, client portal, administrative interfaces, data relationships, payment and email integrations, and planning tools. That combination of operational experience and implementation shaped the platform around the work of delivering events.