GoSeedly Bus Tour Operations Kit
A departure board for coach tour and group charter operators: each departure with its pickup route stop by stop, a manifest kept as head counts with a lead booker, boarding counted at each pickup, the coach and driver recorded for it, the fares each lead booker owes and a trip log once the coach is back. Stepwell never stores passenger names, dates of birth, ID numbers or health details.
YOUR STEPWELL WORKSPACE
01 — DEPARTURES
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 / DeparturesDepartures with booked seats over the recorded seat count, a pickup still planned within two days, no driver within three days or a balance past its due date lead. Then the board shows today and the next six days by time, each departure with its pickup route as a line of stops and a manifest block of seats booked, confirmed, held and boarded.
02 / PickupsA route sheet for each departure in the next 14 days with each stop's time and status and the parties boarding there as lead booker and seats, then pickup points with departures and seats in separate columns.
03 / ManifestsOne manifest per departure: lead booker, group, pickup, seats, party status and boarding status, with seats by status in the footer. No passenger names, dates of birth or health details.
04 / CoachesDepartures in the next 14 days grouped by coach label, then each driver with their departures. Coach and driver entries are labels the office typed.
05 / FaresBalances past their due date, balances still open, paid fares and fares by departure. Money only, as the office recorded it.
06 / Trip logDeparted and returned departures with seats booked, seats boarded, miles recorded and checklist progress in separate columns, then cancelled departures.
07 / InsightsDepartures by status, seats booked by kind of tour, parties by boarding status, pickups by status, miles by coach and fares by payment status. Departures, seats, miles and dollars are never added together.
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 10 fictional departures: six scheduled, one departed, two returned and one cancelled, with 18 pickups and 25 booking parties kept as head counts. 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 departure holds the tour name and kind, the organizer and destination, departure and return dates and times, the coach label and recorded seat count, driver and guide, the status, the manifest close date and recorded miles, pickups with time, order and status, booking parties with a lead booker, seats, boarded count, fare, payment and balance due date, 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 departure creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, logins, card and ID numbers, dates of birth, passenger name lists and health details, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Stepwell records what the office planned, booked, confirmed, counted and was paid. It makes no DOT, FMCSA, safety, insurance or on-time claim, does not check driver hours, vehicle records or coach conflicts, and does not plan routes, track vehicles, sell seats or take payments. It is not a passenger list: passenger names, dates of birth, passport and ID numbers, health and mobility details, card numbers, Social Security numbers, and depot or gate codes and passwords are refused in recorded text and in the native form drafts, while tour codes, booking references and coach numbers are kept.
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.
Stepwell keeps its warm-grey route 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.