Skip to content
View packages

CRM KitsRV and trailer service centers

Fourteen days. Six bays.

An RV shop is not limited by calls, it is limited by bay space and by how long a unit sits in one. Bayside draws two weeks across six bays and a yard, with every stay a block as long as the promise somebody made, so the fortnight you have already sold is visible without opening a single record.

Bay timeline in the GoSeedly RV & Trailer Service Kit with fictional sample records

Length of stay, drawn to scale.

Six bays and a yard down the left, fourteen day columns across, and every unit that records an arrival and a bay drawn as a block from its arrival column to its promised column. A navy rule marks today. Each block carries the recorded year and make label and six inspection ticks, filled for each item somebody actually recorded.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Fourteen-day bay timeline across six bays and a yard, with stay blocks drawn to their recorded length
  • CSS warranty pennant, six-tick inspection row and red overdue tail on the blocks themselves
  • Unit sheet with the unit record, the bay assignment, the six-item inspection checklist and the work orders
  • All unit visits, inspection checklists and warranty claim views
  • Service insights drawn from recorded workspace data only
  • Black and navy Bayside application frame with the permission-filtered CRM tools drawer

four pipelines

  • Service and repairs · 7 stages
  • Warranty claims · 8 stages
  • Seasonal prep and winterization · 7 stages
  • Pre-purchase and consignment inspections · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Check-in inspection task
  • Parts wait note
  • Estimate approval follow-up
  • Promised date check task
  • Overdue promise follow-up
  • Warranty claim filed note
  • Claim status check task
  • Ready for pickup task
  • Seasonal prep reminder

Inactive until you review and publish them. None send customer messages.

Sample workspace

Explore twelve fictional unit visits in the separate sample view. All six unit types appear, eleven record a bay and one records an arrival with no bay so the unassigned strip has a row, two record a promised date that has already passed with no release so two red tails are drawn, and four carry warranty work orders across four claim references. Inspection checklists run from zero recorded items to all six. Example edits stay in the current page’s memory and reset on navigation or reload; sample unit visits are never inserted into your CRM.

No sample customers are added to your CRM.

Setup and source

  • Guided setup and compatibility report
  • Private rollback receipt
  • AI-agent guide for customized installations
  • Original editable source, configuration, and tests
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set company name, descriptor, and default pipeline name. Then sign in and check the workflows and permissions your team uses.

Technical details and compatibility

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 RV and trailer service helper is required for connected creation, editing and starter setup. It checks the active account, native permissions and the current record state, preserves unrelated custom fields and unknown values, and invokes the native Seedly mutations inside one transaction. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required.

One unit visit is a native contact-linked opportunity with a namespaced unit type, year and make label, unit length in feet, VIN reference, owner label, bay, arrival date, promised date, released date, a fixed six-key inspection checklist where each item holds a done flag, a date and findings, work orders with stable IDs carrying a status, technician label, warranty flag, claim reference and amount, an optional visit total and notes. The same coach coming back in October is a second visit and a second opportunity, and other custom fields are preserved.

A bay assignment, an arrival date and a promised date are decisions somebody typed. They allocate nothing, reserve nothing, create no native Calendar appointment, send no confirmation and prevent no double-booking; there is no scheduling engine or bay optimization. A block’s length is the recorded arrival day through the recorded promised day inclusive and nothing else. The inspection checklist is six items a technician ticked and dated, not a safety inspection, a roadworthiness certificate or a moisture survey, and an unticked item means nobody recorded it. A warranty flag and a claim reference are words somebody typed, with no manufacturer portal integration, claim filing, authorization lookup or payment. A work order records a label and a status; the kit holds no stock, part number or purchase order. The VIN reference, year and make label and length are staff-entered references, with no VIN decoder or vehicle data service. Overdue means a passed recorded promised date with no recorded release, and a released date requires every work order recorded as done. Recorded amounts are references, separate from native opportunity value, invoices and payments. Empty values read as words, never a dash.

Four optional pipeline templates and nine inactive workflow drafts. Twelve fictional in-memory unit visits with recorded inspection items and work orders.

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.

Get the RV & Trailer Service Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

Already a member? Open your downloads.

Questions

How do I receive the kit?

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.

Does this include Seedly CRM?

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.

Is this one connected workspace?

Bayside keeps its bay timeline navigation across the original RV and trailer service views and the native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. 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.

Can I use it with existing customizations?

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.

Do I have to import all the starter content?

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.

Can I remove the examples and starter content?

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.

Can different subaccounts use different kits?

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.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.