GoSeedly Music & Artist Tour Management Kit
A tour book for artist managers and tour offices: the next fourteen days as a road, one row per day, with each show's city, venue, load-in, doors and set times and its advance in words, and beside it the drives, flights, hotels and crew calls for that day. Roadbook keeps tours, venue advances, travel legs, crew calls and settlements for several artists in one connected workspace, and it records guarantees and settlements as the office typed them, never as a calculation.
YOUR ROADBOOK WORKSPACE
01 — ITINERARY
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 / ItineraryA needs-attention strip, then fourteen days on a road line: each confirmed show or hold with its city, venue, load-in, doors and set, and beside it the drives with their miles, the flights with their numbers, the hotel confirmation labels and the crew calls. Advances still open near the show, legs not booked, calls not confirmed, holds past their date and shows with no settlement lead.
02 / ToursOpen tours in date order with their stage read from the recorded shows (routing, confirmed, on the road or settling), the first and last show, confirmed shows and holds, and the next show, then tours wrapped or cancelled in the last 60 days.
03 / AdvancesConfirmed shows in the next 30 days with the advance in words (not sent, sent or confirmed) and the load-in, doors and set times each venue gave, then every hold still waiting on a confirmation.
04 / TravelLegs still to book first, then booked legs for the next three weeks and legs done in the last two, each with its time labels, the flight number or hotel confirmation label as typed, and miles on drive and bus legs only.
05 / Crew callsCrew calls still to confirm, then every call in the next three weeks, kept as a role and a call time. People stay in your contacts; passport numbers and dates of birth are refused.
06 / SettlementsShows played with no settlement recorded first, then settlements recorded in the last 60 days with the deal as recorded, the recorded guarantee and the settled amount, then the deal terms for the confirmed shows ahead.
07 / InsightsTours by stage and kind, stops by status, advances for the shows ahead, travel legs by mode and status, crew calls by status, road miles by tour and recorded guarantees and settlements by tour. Shows, miles, days 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 9 fictional tours for one management office: seven open (one routing, three confirmed, two on the road and one settling), one wrapped and one cancelled, with 33 stops, 20 travel legs, 10 crew calls and 81 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 tour holds the artist, the tour kind, the tour manager and agent, the inquiry, wrap and cancel dates, plus every stop with its city, venue, load-in, doors and set times, advance, deal as recorded, recorded guarantee and settlement, every travel leg with its flight number or confirmation label and miles on road legs, every crew call as a role and a call time, 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 tour creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep flight numbers and confirmation labels exactly as typed, refuse access codes, passwords, passport numbers, dates of birth, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Roadbook records what the tour office routed, held, confirmed, advanced, booked, called and settled. Guarantees, door splits and settlements are amounts and terms as recorded; Roadbook calculates no split, checks no contract, takes no payment and makes no tax, accounting, licensing, visa or insurance statement. It does not route tours, contact venues, book travel, track flights, sell tickets, send reminders or messages or collect signatures. Stage door, green room, hotel room and gate codes, Wi-Fi and app passwords, passport, visa and known traveler numbers, dates of birth, 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.
Roadbook keeps its white header and slate road strip 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.