GoSeedly DJ & Event Entertainment Kit
An event calendar for DJ and event entertainment companies: the next four weekends on one screen, with every planning form's status, the night's timeline and the song requests beside each event. Floorfill keeps bookings, planning forms, cue sheets, must-play and do-not-play lists and the DJ schedule in one connected workspace, records songs as titles only, and keeps only the adult booking contact and a head count for school dances, sweet sixteens and quinceañeras.
YOUR FLOORFILL WORKSPACE
01 — CALENDAR
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / CalendarA needs-attention strip, then four weeks of open events by day with the set start and the planning form stage, then next-up cards with the form, the first cues and the requests. Overdue forms, unsent forms close to the date, unlocked timelines, waiting requests and events not wrapped lead.
02 / Planning formsFour columns, form not sent, form out, form returned and timeline locked, with the sent, due, returned and locked dates on every card, soonest event first.
03 / TimelinesEvery upcoming event as a cue sheet in the order of the night, with the time, the moment, the detail, the song as typed and whether the client confirmed it. A last dance after midnight follows the evening.
04 / RequestsMust-play songs, guest requests and the do-not-play list for each upcoming event, each song as the client wrote it with waiting, on the list or declined.
05 / BookingsOpen events by date with the kind, venue, adult booking contact, head count, package, recorded fee and recorded deposit in their own columns, then events wrapped or cancelled in the last 30 days.
06 / DJ scheduleOpen events grouped by DJ with load-in, set times and set length, and each DJ's set hours for the next 30 days, counted in hours only.
07 / InsightsEvents by stage and kind, song requests by kind and status, cues by moment, set hours by DJ, head count by event kind and recorded fees and deposits. Hours, songs, guests and dollars are never added together or drawn on one scale.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore 12 fictional events: ten open (two with the planning form not sent, three out, two returned and three with the timeline locked), one wrapped and one cancelled, with 32 timeline cues, 28 song requests and 84 checklist steps. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
One contact-linked event holds the date, kind, venue label, load-in and set times, the adult booking contact and a head count, the DJ and package, the planning form with its sent, due, returned and locked dates, and the recorded fee and deposit, plus every cue of the night, every song request as a label and an editable checklist.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Edit business name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected event creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep every cue and song label exactly as typed, refuse access codes, logins, card numbers, Social Security numbers, dates of birth and exact ages, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Floorfill records what the office booked, planned, locked and played. Songs are titles typed as labels: it stores, plays, streams and licenses no music. For school dances, sweet sixteens and quinceañeras it keeps only the adult booking contact and a head count, and it refuses dates of birth and exact ages. It makes no insurance, venue, permit or noise claims, holds no dates, sends no reminders or messages and takes no payments. Venue load-in, dock and gate codes, Wi-Fi and app logins and passwords, payment card numbers and Social Security numbers are refused in recorded text and in the native form drafts.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
DEVLAUNCH ALL ACCESS
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Floorfill keeps its graphite channel-strip rail across the kit views and native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.