GoSeedly Gymnastics & Cheer Gym Kit
A roster grid for gymnastics and cheer gyms: the gym's levels and teams as rows, the weekdays as columns and every class as a tile with its recorded seats drawn as pips, beside a meet calendar with entry deadlines. Roundoff keeps athletes, class seats, waitlists, meet entries and families in one connected workspace, with athletes kept to a first name and an age band.
YOUR ROUNDOFF WORKSPACE
01 — ROSTER
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 / RosterHouseholds with an alert lead, then the roster grid: each class a tile with its time, coach, area and seat pips, a class past its recorded seats or with an open seat and a waitlist flagged in words, and the meet calendar with entry deadlines beside it.
02 / AthletesEvery athlete with program, level and team labels, status, class seats and waitlist positions in words, meets ahead and the parent or guardian for minors, alerted rows first.
03 / ClassesOne card per class grouped by program with a seat meter in athlete counts, the roster in seat order and the waitlist in request order, plus the class editor.
04 / WaitlistEvery waitlist request with its position, request date and the seats open in that class now. A position that matches an open seat leads; a full class stays neutral.
05 / MeetsOne section per meet, upcoming first, with host and location labels, the entry deadline, counts by entry state and every entry, plus the meet editor.
06 / FamiliesEvery household with the guardian and relation, how to reach them, athletes, seats held, recorded monthly tuition in its own column and checklist progress.
07 / InsightsAthletes by program and age band, seats by class, meet entries by state and recorded monthly tuition, each in its own ledger, with the households 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 37 fictional households with 58 athletes, 14 weekly classes holding 68 seats, 3 waitlist requests, 4 meets and 37 meet entries. 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 household holds the parent or guardian, contact note and recorded monthly tuition, its athletes as a first name, age band, program and the gym's own level and team labels, class seats and waitlist requests with their dates, meet entries with reply dates and an editable household checklist. Classes with their recorded seats and the meet calendar are the gym's own 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 gym 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 household creation, edits, classes and meets, and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse dates of birth, exact ages, school names, injury and medical details, body measurements, access codes, passwords, payment card numbers and Social Security numbers, require a guardian for athletes 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 enroll or register anyone online, sync calendars, place athletes in classes, move anyone off a waitlist, track attendance, take payments, invoice or charge late fees, register meet entries with a host or governing body, keep scores, evaluate skills, certify levels, make safety or supervision claims or send messages. Levels and team names are the gym's own labels. It stores no date of birth, exact age, school name, injury, medical or allergy detail, body measurement 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.
Roundoff keeps its dark spruce rail and cool 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.