Sky Events is a DJ and event-entertainment company working in Massachusetts and South Florida. Mitchell co-founded it, which makes this the business we run on our own playbook.
We built two things: the command center the team runs the business from, and the public website that brings the inquiries in.
Business: Sky Events
Industry: DJ and event entertainment
Markets: Massachusetts and South Florida
Our role: Mitchell co-founded the company and built both systems
An events business is a pipeline with a deadline
Every inquiry has a date attached, and every booked event has dozens of small steps that must happen before it. Miss a reply and the date goes to someone else. Miss a planning step and it shows on the night.
The job was to make sure every inquiry gets an answer the same day, and every booking gets its plan without anyone building one by hand.
The command center
The screens come in four groups: the day, the CRM, growth, and knowledge. Follow the tour, or click any screen in the rail.
Today: The page the day starts on: what needs a reply, what is due, and what is coming up, without opening anything else.
KPIs: Every number on one page, each one tagged as measured, estimated, or projected so nobody mistakes a guess for a fact.
Calendar: One month grid with layers for events, leads, tasks, content, and campaigns. Any chip opens its record.
Tasks: Tasks sorted by urgency, with a checkbox to finish them. Booking an event creates its own planning tasks.
Pipeline: A drag-and-drop board. Dropping a lead on Booked creates the event and its full planning checklist automatically.
Leads & Inquiries: Every inquiry with its stage, event details, and the date its next step is due. Search, filter, sort, and export.
Contacts: Clients, prospects, planners, and venues in one list, each with a full activity timeline.
Events: Booked events with their status, package, crew, and a checklist whose due dates count back from the event day.
Payments: Deposits, installments, and final balances per event, so what is due and what is overdue is never a surprise.
Vendors & Partners: Venues, planners, and vendors by market, with an outreach status for each relationship.
Marketing: A campaign calendar for the year, a content calendar, channels and listings, reviews, and the marketing plan itself.
Distribution Map: Every place the business could be listed, by channel type and region, coloured by whether it is listed there yet.
Lead Channels: Each lead channel with its market, audience, priority, status, and cost, so marketing effort goes where it pays.
Knowledge Base: The company's knowledge as files anyone can read and edit in the app. The AI assistants read the same files.
Brand Guide: Logo, tagline, type, and colours on one page. Click a swatch to copy its code.
Claude Instructions: The rules, skills, and runbooks the AI assistants follow, readable by the people they work for.
Settings & Data: Team sign-in, the website inquiry webhook, a full export, and an audit trail of every change: when, who, and what.
The website
A black and gold site organised by service, event type, and region, with the booking form on the pages where people decide.
Home: A video hero, quick answers to the questions couples and planners actually ask, and the booking form on the same page.
Services: Every service page uses one template: who it is for, what is included, how the event flows, and the common questions.
Weddings: An event page built to answer a couple's questions in order: what is offered, what past clients said, and what it looks like.
Mitzvahs: The same structure for mitzvahs, with its own proof and its own questions.
Massachusetts: A regional hub with city pages under it, so the site can be found for a service in a specific town.
South Florida: A second regional hub, built the same way for the second market.
Contact: One inquiry form. It validates the request, emails the team, and confirms to the customer before the thank-you page.
What makes it work
An inquiry creates its own work: Logging an inquiry creates the contact, matched by email so nobody is entered twice, the lead, and a task to reply the same day.
Booking builds the plan: Drag a lead to Booked and the event is created with a full planning checklist. Each step's due date counts back from the event day.
Numbers that say what they are: Every figure on the KPI page is tagged as measured, estimated, or projected.
Gone-quiet detection: Leads that have stopped replying are surfaced, so follow-up doesn't depend on someone remembering.
Live across the team: A change made on one screen appears on everyone else's without a refresh.
A marketing hub: A campaign calendar for the year, a content calendar, a map of every channel by region, and the brand guide.
AI skills that draft: A daily brief, replies to inquiries, proposals, event prep, and content plans are drafted by AI skills. A person reviews and sends.
A webhook for the website: The command center has a secured endpoint ready to receive the website's inquiry form.
A site built to be found: Service pages on one template, regional hubs with city pages beneath them, and structured data on every page.
An audit trail: Every change is recorded: when, who, and what.
How the AI is kept in its lane
AI skills draft and report. A person sends every message.
Payments are recorded by a person, never taken automatically.
Every write is audit-logged, including writes made by an agent.
Under the hood
React
TypeScript
Node.js
PostgreSQL
SQLite for local work
Claude Code skills
Replit
Any business that books work for a date has this shape: an inquiry, a quote, a booking, a plan, a payment. We can build the same pipeline around yours.