A belt ladder built from your own ranks. Dojo stacks every recorded rank from white at the foot to black at the top, puts each student in their band with stripe pips and a readiness meter, and keeps the next test day beside it.
Each recorded rank is a band with its belt colour as a small swatch at the left edge, its own stripe, class and week minimums, and its students as chips. The side column carries the next recorded test day and its candidates.
Counts by readiness state, each opening the students behind the number: test ready, stripes outstanding, classes outstanding, weeks outstanding, absences and trials.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Student journey · 8 stages
Trials and intros · 7 stages
Rank testing · 7 stages
Programs and camps · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Trial class booking
Trial follow-up
Enrollment welcome
First stripe note
Absence check-in
Test readiness review
Test day reminder
Promotion note
Annual re-enrollment review
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
Explore 39 fictional records: 32 enrolled students across ten ranks and five programs, plus 7 trials in progress. Sample edits stay in memory and reset on navigation or reload.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry to the final handoff.
Editable native forms and document templates give your team a practical starting point.
01 / INTAKE & FOLLOW-UP
Three ready-to-edit forms.
Trial class request
New student enrollment details
Test day feedback
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
02 / WORKING DOCUMENTS
Three reusable templates.
Rank requirements sheet
Test day candidate list
Promotion record
Open each template in Documents and complete it for the actual job or visit.
03 / THE NEXT STEP
Checklists alongside the work.
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
Your workspace. Your starting point. Your code to edit.
One contact-linked student record holds the student label, age band label, program, guardian label, start date, current rank, rank start date, stripes earned, classes since promotion, last class date, trial state and date, an optional tuition reference, and stable rows for promotions, recorded classes, non-medical staff notes and a checklist. The rank list and the test day list are the kit’s own per-workspace records, each behind a server-owned revision.
Ladder operating view
Students operating view
Test days operating view
Attendance operating view
Trials operating view
Programs operating view
Insights operating view
An editable per-workspace rank list and test day list, each with a server-owned revision
Three native form drafts and three editable document templates
Editable per-student checklists and preserved row history
Four optional pipeline templates and nine inactive workflow drafts
39 fictional in-memory records
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
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.
03
Set up your own team.
Edit school name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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 record creation, edits, the rank and test day lists, and resource setup. They preserve native account permissions, unrelated custom fields and row history, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Test readiness is derived from values the school records: stripes earned against that rank’s recorded stripes, classes since promotion against its recorded minimum classes, and weeks at rank against its recorded minimum weeks. The kit is not a class scheduling or booking engine, an attendance kiosk or check-in system, a billing or tuition processor, a messaging tool, or a curriculum. A promotion row is the school’s own record, not an accredited grade from any federation. There is no field for a date of birth, a medical condition, an allergy, an injury or a photograph, and guardians are recorded as labels only.
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.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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.
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
Good questions. Clear answers.
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?+
Dojo keeps its black rail and application frame across the kit views and 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.
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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
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.