GoSeedly Boat & Marine Service Kit
A marine service yard does not run on a day. It runs on one season, and the season is the same every year for every boat: it comes out of the water, it gets winterized, it sits somewhere in the yard for months, it gets commissioned in the spring, and it goes back in. In February the question is not what is happening today, it is which of your vessels are still where you put them. Mooring answers that as a band: one row per vessel, twelve months from September to August, five phase blocks, and the storage location code at the row start in monospace, because nobody says "the Beneteau", they say "RACK-B3".
YOUR MOORING SEASON BAND
01 — SEASON BAND
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 / Season bandEvery vessel in the selected pipeline is one row: the recorded storage location code in monospace, the vessel label with its recorded type and length, then a twelve month band from September to August. Phases before the recorded one are solid lime, the recorded phase is a wash carrying a thin marker at today’s position inside it, and later phases are a hairline outline.
02 / Vessel registerEvery vessel grouped by its native pipeline stage, in stage order, with the recorded type, make and model, length, engine label, hull ID reference, owner label, phase and storage code. The stage select beside each row calls your CRM’s own stage mutation under your own roles, and it never touches the recorded phase.
03 / Work ordersEvery recorded work order across the loaded vessels, grouped by the phase it records in season order, with open rows before in progress rows before complete ones. Each row carries the vessel, its storage code, the recorded technician label and the recorded amount reference. A work order in progress or complete requires a technician label.
04 / Storage recordVessels with a recorded storage location code, grouped by the kind the code prefix records: rack, yard row, slip or indoor bay. Each row carries the code, the vessel, the owner label, the recorded in and out dates and the recorded phase. Vessels with no recorded code are listed as unrecorded rather than quietly dropped.
05 / Yard insightsVessel counts by recorded phase and type, the winterization and commissioning checklist completion rates, work order counts by status and by phase, storage counts by location kind, recorded season contract totals grouped by currency, and the two places where records disagree with each other.
06 / Vessel recordThe record editor holds the vessel fields, the storage location code and its dates, the season contract reference, the phase checklist rows and the work orders. Checklist rows and work orders carry stable IDs and are archived, never deleted, so a row somebody ticked and a job a technician did are never erased.
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 eleven fictional vessels covering all five recorded phases and all four storage location kinds, with 50 checklist rows across the winterization and commissioning lists and 10 recorded work orders: five open, two in progress and three complete. One vessel records no storage code and one is recorded in storage with an out date that has already passed, so both observations are visible without editing anything. Example edits stay in the current page’s memory and reset on navigation or reload; sample vessels are never inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
One vessel under service for one season is a native contact-linked opportunity with namespaced vessel type, make and model label, recorded length in whole feet, engine label, hull ID reference, owner label, recorded season phase, storage location code, storage in and out dates, a season contract reference, yard notes, checklist rows and work order rows. Two seasons for the same boat stay independent, and so do two boats belonging to one owner. Other custom fields are preserved.
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 company 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 vessel helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks every field bound and the storage cross-field rules, and compares the current record timestamp and a server-owned revision before saving. Existing checklist rows and work orders cannot disappear from a save: archive and unarchive instead. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A storage location code looks like RACK-B3, YARD-R4, SLIP-12 or BAY-2, and its location kind is derived from the prefix rather than stored, so a code and its kind can never disagree. A code is a label your yard wrote down: the kit holds no yard map, capacity figure, dimensions or occupancy limit, and two vessels recording one code are both listed, because that happens. The season band is a fixed twelve month reading frame, not a schedule the kit maintains, and the recorded phase is always what a person last wrote down. A recorded storage in date needs a recorded code, a recorded out date needs a recorded in date and cannot precede it, and a vessel recorded in the storage phase needs both; commissioning and launch do not, because a boat can arrive in the spring without having wintered with you. Checklist rows belong to the winterization or commissioning list, and the sheet reads whichever list the recorded phase works from. Insights reports how many vessels record a phase that differs from the current month’s phase and how many are recorded in storage past their recorded out date; both are observations that two records disagree, never a claim that work is late, and nothing is corrected automatically. There is no slip or berth management, no parts inventory or supplier catalog, no weather or tide data, no scheduling engine, and no invoicing, payments or owner messaging. A recorded date reserves no lift, bay, slip or technician and creates no calendar entry. Season contract and work order amounts are recorded references, separate from native opportunity value, and totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: saving a vessel record never moves it, and a native stage change never rewrites a recorded phase.
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.
Mooring keeps its marine service navigation across the original yard views and 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.
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.