Hot CuesAbout Hot Cues
Built by a DJ company, for its own Saturdays first.
Hot Cues is made by Gifted Geeks, an event company that runs real weddings — and runs them on this software. We are customer zero: every feature gets worked at an actual gig before it gets sold to you.
Why that matters
Software built at a desk breaks in a barn. Ours gets to break on us first.
The offline sheet exists because our own venues drop signal. The questionnaire writes itself because our own couples used to answer forty questions in the wrong order. The do-not-play tier exists because somebody requested the one song the couple banned. Every sharp edge on this product was sanded off at a real event — usually the hard way.
The roadmap is public
What's coming, what's being weighed, and — rarer — what we won't build, in the open where you can hold us to it. Read it here.
So is the status page
Deploys and integration health, live, including the parts that aren't configured yet. Software that fails silently isn't honest. See it now.
No testimonials until they're real
You won't find invented review counts or stock-photo crowds here. The photo slots on this site hold our own rooms or nothing.
Be honest about the fit
One DJ with forty Saturdays, or five DJs with two hundred. Same sheet.
Hot Cues is built for the shape most event companies actually are — an owner who still plays, and a bench of people who work for them. What changes is which part of it saves you the most.
- Just youOwner, DJ and office
The win is the week before. The questionnaire writes itself off the timeline, the couple answers in the order their day happens, and the sheet is finished on Tuesday instead of in the car on Saturday.
- Two to fiveYou still play most of them
The win is the ones you don't. The gig across town runs the way you'd run it, and nobody has to ring you during dinner service to ask what comes after the toasts.
- GrowingSeveral out on the same night
The win is that it stays one business. One calendar, one set of assignments, payouts that come off the assignment rather than a spreadsheet, and a venue book everybody adds to.
What this is instead of
- a planner's PDF timeline
- a music app your couples log into separately
- a spreadsheet of who's working what
- the group chat where the changes actually live
- a notes app with the venue's quirks in it
- an invoice written somewhere else again
Six places to look, and not one of them is the sheet you're holding at 6:40. One place — and the sheet is what comes out of it.
The rules we build under
Four promises, each one checkable.
Leaving must be easy
Every plan — Free included — exports everything it ever put in, one click, any time. A tool you can leave is a tool that has to stay good.
Your data is walled off by the database
Company isolation is enforced at the database layer, not just in application code — another company on Hot Cues cannot see your events, clients or money, even if our code has a bad day.
Machines suggest, humans decide
Anything read out of an email, a transcript or a screenshot lands as a pending suggestion a person approves. AI never edits your sheet on its own.
Honest when unconfigured
An integration that isn't set up says so, by name, on the status page — it never pretends, and it never fails silently.