Skip to content
View packages

CRM KitsMartial arts schools

Every student on the ladder.

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.

Ladder in the GoSeedly Martial Arts School Kit with fictional sample records

Read the whole school in one column.

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.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • 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 pipelines

  • Student journey · 8 stages
  • Trials and intros · 7 stages
  • Rank testing · 7 stages
  • Programs and camps · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • 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

Inactive until you review and publish them. None send customer messages.

Forms and documents

  • Trial class request
  • New student enrollment details
  • Test day feedback
  • Rank requirements sheet
  • Test day candidate list
  • Promotion record

Editable native forms and document templates. Forms collect information for staff review.

Sample workspace

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 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
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set school 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 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.

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.

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.

Four optional pipeline templates and nine inactive workflow drafts. 39 fictional in-memory records.

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 Martial Arts School Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

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?

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.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.