CRM KitsPersonal trainers
Every session booked. Every pack accounted for.
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.
Two panes. One day.
The 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.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Two-pane trainer desk with a 5 am to 9 pm session rail and a CSS pack depletion list
- Client sheet with the derived pack balance, session log and recorded check-in notes
- Clients, Sessions and Packs views with low-balance ordering
- Training insights drawn from the recorded records in the selected pipeline
- Black and white Rep application frame with the full permission-filtered CRM tools
four pipelines
- New client consultations · 8 stages
- Pack renewals · 7 stages
- Small group training · 7 stages
- Corporate and online clients · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Consultation booking task
- Welcome note
- First session reminder
- Monthly check-in task
- Two sessions remaining follow-up
- Pack renewal task
- Missed session check-in
- Program review note
- Ninety-day milestone note
Inactive until you review and publish them. None send customer messages.
Sample workspace
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.
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
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set business 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 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.
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.
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.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory client records with 75 recorded sessions and nine recorded packs.
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 Personal Training Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
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?
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.
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.
More health, beauty & wellness kits
Browse all 220 kits
