GoSeedly Limo & Chauffeur Kit
A reservation board for limo and chauffeur companies: the week's runs by vehicle or by chauffeur, with weddings, airport transfers, proms and corporate travel side by side and double-bookings flagged from the times you recorded. Nameboard keeps the runsheet, reservations with recorded quotes and deposits, flights as typed, event timelines and fleet counts in one connected workspace, and makes no safety, licensing or on-time claim.
YOUR NAMEBOARD WORKSPACE
01 — RESERVATION BOARD
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 / Reservation boardSeven day columns from today with one row per vehicle, or per chauffeur with one click. Each run ticket shows its times, the occasion, the reservation, the chauffeur or car, passengers and the flight on airport runs. A double-booked car or chauffeur, a run with nobody assigned, an airport run with no flight and a past run still marked booked lead the page.
02 / RunsheetPast runs still open, then every date for two weeks in pickup order with pickup, drop-off, flight, vehicle, chauffeur, passengers and hours booked, each in its own column.
03 / ReservationsInquiry, quoted and confirmed lanes with the occasion, event date, party head count, booked runs, next run, the recorded quote and the recorded deposit, then completed and cancelled reservations.
04 / AirportArrivals and departures for the next 30 days with the flight as the client gave it, pickup, drop-off, chauffeur and car, then the last 30 days. Nameboard does not look up flights or delays.
05 / OccasionsEach reservation as a timeline of its runs with times, stops, car and chauffeur. Proms record only the adult who booked and a party head count, never students' names or ages.
06 / FleetVehicles and chauffeurs by label with runs today, runs in the next seven days, the next run and double-booking flags. Counts of runs only.
07 / InsightsReservations by occasion and status, booked runs by kind and by vehicle, recorded quotes and recorded deposits. Hours, passengers 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 11 fictional reservations: nine live (seven confirmed, one quoted, one inquiry), one completed and one cancelled, with 20 runs across six vehicles and five chauffeurs and 88 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 reservation holds its occasion, status, event date, venue, the adult who booked and their role, the party head count, the recorded quote and deposit, plus every run with its kind, date, pickup and end time, vehicle, chauffeur, pickup and drop-off, flight on airport runs, passengers and hours booked, 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 reservation creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep flights exactly as typed, refuse access codes, logins, card numbers, Social Security numbers and ages, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Nameboard records what was booked, assigned, flown and done. It makes no safety, licensing, for-hire or DOT compliance, insurance or on-time statement about any car, chauffeur or run, and it compares only the times you recorded, adding no drive time. It does not track flights, dispatch, route, use GPS, book calendars, bill, take deposits or payments, collect signatures or send messages. For proms only the adult booking contact and a head count are kept. Gate, building, garage, lockbox, door and alarm codes, logins and passwords, payment card numbers, Social Security numbers and ages 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.
Nameboard keeps its tuxedo-black top bar and white name card 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.