GoSeedly Swim School Kit
A lane grid for swim schools: the pool's lanes as rows, the day's time as columns, every group class placed by time with its level label, instructor and one mark per seat. Kickboard keeps swimmers, class places, waitlists, make-up credits and the school's own level ladder in one connected workspace, with swimmers kept to a first name and an age band.
YOUR KICKBOARD WORKSPACE
01 — LANES
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 / LanesA class over capacity and the families with an alert lead, then the block and week, day tabs with classes and open seats, the lane grid with places, make-ups and open seats marked, and the roster of the chosen class.
02 / SwimmersEvery swimmer with the school's level label, status and current class places in words, the parent or guardian for minors, and a level change flagged while the swimmer still holds a place in the old level's class.
03 / Make-upsEvery make-up credit with its missed class, expiry and booking, then the classes at the same level label with an open seat before each open credit expires.
04 / LevelsLevels in the order the school recorded them, with swimmers, weekly classes and open seats on separate lines, and every recorded level change with where the swimmer's place is now.
05 / WaitlistWaitlist entries grouped by class, with the class's standing places against capacity and a waiting entry flagged when a seat is open.
06 / TimetableThe week's classes by day with lane, instructor and places against capacity, and the editor for lanes, the level ladder, weekly classes and lesson blocks.
07 / InsightsSwimmers by status, level and age band, seats by class day and recorded block fees, each in its own ledger, with the families behind every count.
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 26 fictional families with 47 swimmers, 45 class places, 5 waitlist entries and 8 make-up credits on a timetable of 5 lanes, 7 levels, 18 weekly classes and 3 blocks. 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 family holds the parent or guardian, contact note and the block fee the office recorded, its swimmers as a first name, age band and the school's level label, class places, waitlist entries, make-up credits with expiry and booking, and an editable family checklist. Lanes, the level ladder, weekly classes with their capacities and the lesson blocks are the school's own timetable record.
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 school 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 family creation, edits, the timetable and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse dates of birth, exact ages, school names, medical details, access codes, logins, payment card numbers and Social Security numbers, require a guardian for swimmers under 18, and check revisions before saving. The native form patterns are built from the same rules. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Everything shown is what the office recorded. The kit does not book classes online, sync calendars, place swimmers, offer waitlist seats or book make-ups for you, track attendance beyond recorded make-up credits, take payments, invoice or calculate fees or instructor pay, assess swimmers or certify levels, or send messages. A level label is the school's own name for a group, not a swimming, water-safety or lifeguard certification. It stores no date of birth, exact age, school name, medical or allergy detail or photograph.
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.
Kickboard keeps its azure lane-rope rail and pale pool-tile canvas across the kit views and the 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.