GoSeedly Personal Training Kit
Start the day with the clock and the balances. Rep puts today’s recorded sessions on a vertical rail from 5 am to 9 pm beside a pack depletion list, so the next hour and the client about to run out of sessions sit on one screen.
YOUR REP TRAINER DESK
01 — TRAINER DESK
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 / Trainer deskThe left pane is the session rail: sixteen hour rows from 5 am to 9 pm, with each recorded session on the selected day sitting at its recorded start time under the client name and program label. The right pane is the pack depletion list, one row per recorded pack.
02 / Client sheetSelecting a pack row opens the client sheet: the recorded goal, program, trainer and start date, the pack size with its derived used and remaining counts, the recorded price reference, the session log and the recorded check-in notes.
03 / ClientsOne table of contact-linked client records with the recorded goal, program label, trainer label, start date and pack, the derived used and remaining counts, and the next booked date. Filter by recorded program.
04 / SessionsRecorded sessions grouped by date with their recorded start time, duration, client, trainer label and focus label. Record a session complete from the row, and read archived rows under their own heading where they count toward nothing.
05 / PacksEvery recorded pack sorted low balance first, each with its depletion bar, recorded size, derived used and remaining counts, recorded purchased date, recorded price reference and next booked date.
06 / InsightsClient counts by recorded program, the recorded completion rate with its stated denominator, the recorded pack totals against the sessions still remaining, and recorded price references grouped by currency.
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 ten fictional client records with nine recorded packs, three of them low balance and one recorded fully used, 75 recorded sessions including eight on the workspace day across two trainer labels, and seven recorded check-in notes. Example edits stay in the current page’s memory and reset on navigation or reload; sample clients 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 training client is a native contact-linked opportunity with namespaced details: goal label, program label, trainer label, start date, pack size, pack purchased date, an optional pack price reference in integer minor units, session rows with a date, start time, duration, focus label and completed flag, and check-in rows with a date and a note. Used and remaining session counts are derived from the recorded pack size and the session log, never stored, so no number on screen can contradict the log.
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 Rep helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, and compares both the record timestamp and a server-owned revision before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts stay optional.
A recorded session is a row your team typed. It reserves nothing, creates no native Calendar appointment, checks no availability, prevents no double booking and cancels nothing, and the recorded completed flag is never verified against a clock, a door or a device. The recorded pack price is a reference, separate from opportunity value: nothing here charges a card, issues an invoice or recognizes revenue. Recording a new pack purchased date is how a new pack starts, because a completed session dated before it stops counting. A pack recorded over its own size reports the overage rather than zero. The program and focus labels are labels: there is no exercise library, no set or rep model, no nutrition record and no wearable integration. A recorded goal label is a sentence a trainer wrote, not a clinical record. The pipeline stage stays the native CRM’s, moved through its own mutation and its own permission.
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.
Rep keeps its training navigation across the original views and the native CRM modules. Full CRM tools stay available inside 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.