Event intake
Host details, taste, requests, moments, references, and comments arrive in one structured place.
Platform
Event music planning software for real DJ workflows.
Build timelines, collect host music input, manage special moments, generate playlist drafts, resolve provider metadata, and export DJ-ready event packs.
Features
A complete music planning surface for the work before the event.
Emppo connects the host portal, event timeline, DJ ownership, playlist preparation, AI assistance, provider metadata, and exports into one calm preparation flow.
Timeline ownership
Assign DJs to the event and to the exact sections they are responsible for.
Music workspace
Build block playlists, must-play lists, do-not-play lists, and special moment songs.
Export layer
Create event packs and ordered playlist exports for provider and DJ software workflows.
How it works
One event record. Every decision connected.
The platform is built around the actual sequence of event preparation: collect, plan, prepare, export. Nothing here is generic CRM filler.
Collect the event information that usually gets scattered.
A host portal turns loose messages into structured event details, music taste, must-play ideas, do-not-play notes, playlist references, moment suggestions, and timeline comments.
- Tokenized host portal
- Saved intake
- Host comments become tasks
Plan the night by timeline, not by a single playlist.
Each event is organized around timeline blocks and special moments, so ceremony music, dinner music, party energy, and finale songs stay separated and owned.
- Timeline templates
- Block-level DJ ownership
- Moment suggestions
Prepare playlists with AI assistance, but keep the DJ in control.
Generate drafts, ask for edits, select moment suggestions, lock important songs, and decide whether AI output replaces or appends to the current playlist.
- Locked tracks protected
- Append or replace flows
- Credit-aware AI jobs
Export the plan in the formats DJs actually use.
Event details and playlists can leave the workspace as print/PDF, CSV, provider playlists, M3U, Rekordbox, Serato, and Traktor-oriented files.
- Print/PDF and CSV
- Spotify and Apple Music
- M3U and DJ software exports
Workspace model
Separate access for DJs, agencies, and hosts.
The product treats DJs as independent professionals, agencies as workspaces, and hosts as event-only collaborators.
Solo DJs
Plan independent events, keep credits and billing separate, and export DJ-ready packs from one workspace.
Agencies
Track active events, DJ slots, assignments, preparation status, team access, and export readiness.
Hosts
Submit music information for one event without seeing internal notes, billing, workspace settings, or team pages.
Exports
Everything leaves the system cleanly.
Music planning only matters if the DJ can take the plan into the booth, the provider account, or the software workflow they already use.
Event pack
- Printable plan
- Details CSV
- Timeline and moment summary
- Host-visible and internal notes
Provider playlists
- Spotify export
- Apple Music export
- Cached provider metadata
- Unresolved track handling
DJ software
- M3U playlist files
- Rekordbox-oriented export
- Serato-oriented export
- Traktor-oriented export
Local readiness
- Mock AI mode
- Mock billing mode
- Mock Spotify and Apple flows
- Database queue support
Guardrails
Professional by design. Narrow by choice.
Workspace ownership
Events, credits, billing, exports, limits, and permissions resolve through the workspace that owns the event.
Permission boundaries
A DJ sees the work they are assigned to. A host sees only one portal. AI keys and provider tokens stay server-side.
Focused scope
The MVP stays centered on collaborative music planning, not contracts, invoices, payroll, marketplace, or a public event directory.
FAQ
Platform questions, answered.
It explains the full product surface: workspaces, host portal, AI, providers, exports, and boundaries.