A disclosure before anything else: I built one of these tools. This guide explains why — but it’s a genuine evaluation framework, not a pitch. Apply it honestly and you’ll make a good decision whether or not it leads to GRADR.
Years ago, I ran my own academy. Then I didn’t — for a long time. Not because I’d fallen out of love with jiu-jitsu, but because I’d seen up close just how much running an academy actually takes, and how many moving parts you have to hold together at once.
But the itch never really goes away. Eventually I started thinking seriously about opening another one, and the first thing I did was ask myself what I’d actually need to run it the way I wanted — what would keep students progressing, keep instructors aligned, and keep the admin from swallowing my evenings. The more I thought about it, the longer and more specific that list got.
So I went looking for the BJJ gym management software that would do it. And I couldn’t find it. Plenty of tools could take payments and mark attendance, but none of them were built around the things that actually make a jiu-jitsu academy run. So I built it myself. That’s where GRADR came from — a list of requirements I couldn’t buy.
This guide is that list, turned into something you can use. Because here’s the trap I ran into, and the one you’ll run into too: put any two platforms side by side and their feature lists look almost identical. Attendance — check. Billing — check. Rank tracking — check. On a comparison grid, they’re twins. And that grid is exactly why so many owners choose wrong.
Two tools with identical checklists can produce two completely different academies six months later. The feature list tells you what a tool has; it doesn’t tell you what it was built around — and that’s the only thing that actually matters. Most gym software is built around the transaction: billing is the center of gravity, and a student is an invoice with a name attached. The right software for a jiu-jitsu academy is built around the student — their attendance, their progression, their journey through the art — with the money orbiting that, not the reverse.
That difference never shows up on the grid. So before you compare a single feature, ask the two questions I eventually wished I’d started with. Everything else in this guide hangs off them.
Question 1: Was it built for jiu-jitsu, by people who know jiu-jitsu?
Not “for fitness.” Not “for martial arts.” For jiu-jitsu specifically.
Software companies see a yoga studio, a CrossFit box, and a BJJ academy as the same business: monthly payments, class attendance, card processing. So they build one generic “fitness studio management platform” to serve all three — sometimes relabeled as “martial arts software” or “dojo management software” — and it will tick every box on your list on the surface. A martial-arts skin on a fitness platform doesn’t change what’s underneath.
But the architecture is the credential. A non-grappler can copy the name of a feature — “rank tracking,” “curriculum” — off a screenshot. What he can’t copy is the judgment that put it there in the right shape, because that judgment comes from decades on the mat. As I see it, the people who build your software should understand not only how jiu-jitsu works, but how it needs to be taught. That’s not a marketing line; it changes what the software can actually do, as you’ll see in a moment.
This is the part I was uncompromising about when I built GRADR: if it didn’t handle jiu-jitsu properly — really properly, not “a belt dropdown” properly — there was no reason for it to exist at all.
Question 2: Do the systems actually talk to each other?
This is the one almost nobody asks, and it’s the most important.
The failure mode of generic software isn’t missing features. It’s features that exist as disconnected islands. The yoga-shaped platform might genuinely have attendance tracking — everything you’d expect from martial arts attendance software — and a rank field, and a member portal — three checkmarks on the grid. But they don’t know about each other. Attendance doesn’t feed grading. The schedule doesn’t know what’s being taught. The portal can’t show a student whether he’s on track for his next belt. So you, the owner, end up stitching it all together in your head — which is the exact job you bought software to get rid of.
Your deepest test isn’t “how long is the feature list.” It’s “how many of these features are actually wired together?”
And here’s why the two questions are really one: only someone who knows the game can define the shared language those systems speak. Built-for-BJJ is the precondition that makes the integration possible. Let me show you what that looks like in practice, because it’s the single most useful thing in this guide.
The integration chain: one decision, five faces
Watch how a single owner decision should propagate through the entire academy.
It starts once, at the top: the owner defines his curriculum areas — the positional structure of the game (guard, mount, standup, and so on). One decision.
It wires into the schedule. He builds his timetable out of curriculum blocks, so the calendar doesn’t just say “6pm class,” it says “6pm — guard.” That schedule renders in three places at the same time: the owner’s view, the instructor portal, and the student portal. Everyone knows what’s being taught before they walk in. And accountability is baked in — an instructor can’t quietly drift into teaching whatever he feels like that day, because the schedule committed the class to an area, and students showed up for that area. Owner, instructors, and students are all evolving on the same map at the same time.
It wires into attendance and grading. Every curriculum-block class a student attends logs against that specific area. So a promotion requirement like “10 guard, 10 mount, and 10 standup classes before purple” tallies itself. The grading requirement isn’t a separate spreadsheet you maintain — it fills itself from attendance, which fills itself from the curriculum-blocked schedule, which came from the areas you defined at the start.
It closes the loop at the student. That same data feeds back to the student’s portal, where he sees his own progress — “8 of 10 guard classes” — which is the motivation and retention layer, running off the very same numbers.
One decision — “here are my curriculum areas” — defines the schedule, drives what three different people see, governs what counts toward promotion, and shows the student his own progress. That’s not five features. It’s one feature wearing five faces.
You cannot get this from islands. No amount of bolting yoga features together produces a wire that runs from a schedule block to a belt requirement. That’s the thing only a purpose-built tool delivers, and it’s the thing to test for: pick any two features and ask whether they pass data to each other. Does grading read attendance? Does the schedule know the curriculum? Does the portal show progress toward the next belt? If the answer is no, you’ve found islands.
When the systems do connect like this, they stop being software you think about and become the quiet machinery a thriving academy runs on — what I’ve called the invisible engine behind a successful BJJ academy.
Why a belt dropdown isn’t grading
Grading is where built-for-BJJ stops being a slogan and becomes something you can actually see in the architecture — and it’s the area I know best.
Here’s what real BJJ promotion requires that a “white / blue / purple / brown / black” dropdown fundamentally cannot do:
- It has to be customizable — IBJJF guidelines as a sensible default, but adjustable to your academy.
- It has to gate on sessions attended before a stripe or belt.
- It has to account for time in grade — and time in your system.
- And the one that genuinely can’t be faked: eligibility tied to attendance across specific curriculum areas. The 10-guard-10-mount-10-standup example. That is impossible unless the software already understands the positional structure of jiu-jitsu — it has to know which class was a standup class, tie it to each student’s record, and gate promotion on the distribution across areas. A generic platform can record a belt and maybe count sessions. It can never say “he’s trained plenty, but he’s never once shown up to a standup class, so he’s not ready” — because it has no concept that standup exists.
How a piece of software carves up the jiu-jitsu game tells you instantly whether a grappler designed it. The structure itself is the credential. You can’t fake decades on the mat in the architecture of a curriculum tool.
A scaffold, not a cage. A fair worry here is that structured software means surrendering your own system or your lineage. It’s the opposite. A built-in area system should be fully customizable — use it as-is, build your own from scratch, or take it as a starting point and shape it. The point is to help you build your curriculum faster, not to replace it.
And the philosophy that matters most — requirements are a floor, not a verdict. When you set promotion requirements, you’re forced to codify the standards you’ve carried loosely in your gut for fifteen years. That alone can upgrade your standards, not just organize them. The objection I hear coming — “attendance isn’t ability; you’ve turned a martial art into a loyalty punch card” — answers a question nobody asked. The requirement doesn’t promote the student. It guarantees he was in the room enough times for your eye to land on him. If you and your instructors are any good, those 10 guard classes are 10 opportunities for real teaching to do its work — so by the time the system says he’s eligible, you’ve genuinely seen and coached his guard. The number is the precondition that makes your judgment trustworthy. It also protects against the opposite failure: the student who looks the part but has never been coached through his weak positions. The requirement is the floor. You are still the verdict.
(For the bigger picture on how the belt and stripe system actually works — and how to grade fairly without sliding into “McDojo” territory — see my guide to the BJJ belt system.)
The part the billing-first owner is blind to: retention
Software built around the transaction has a specific blind spot, and it’s an expensive one.
A student-centric tool watches engagement, not just payment. When a student’s attendance starts to drop, it nudges you to make personal contact — before he ghosts. The billing-first platform only tells you someone left when their payment fails. By then it’s not a save, it’s a cancellation. You found out too late by design.
That matters because of the math. A BJJ membership runs roughly $100–$200 a month, and the lifetime value of a student who goes white belt to black belt is on the order of $10,000. Losing one student you could have saved isn’t a $150 problem. So the features that keep people on the mats — a student portal that onboards them into how your academy works, an achievement layer that makes them feel noticed, attendance-based retention alerts — aren’t nice-to-haves. This is where a real martial arts CRM earns its keep: not as a sales database, but as a retention system that flags a fading student while you can still do something about it. It’s the cheapest revenue you’ll ever protect.
The transfer student nobody promoted
Here’s a scene I’ve watched play out many times over 27 years. A student transfers in from another academy — already skilled, often already a blue belt. He trains just as hard and shows up just as consistently as the homegrown student next to him. But he arrived recently, so you have no accumulated history of him in your head.
Promotion time comes. You scan your mental roster, and the homegrown students surface — you’ve got a decade of memory on each of them. The transfer student doesn’t surface. Not because he’s less deserving, but because there’s no record of his deserving anywhere except in his own experience, which you can’t see into. He matched the dedication, matched the attendance, and got passed over anyway.
He doesn’t experience that as an administrative gap. He experiences it as my coach doesn’t see me. He gets discouraged. He quits. And you never learn you lost a good student to a filing error you didn’t know you were making.
A system that logs attendance and area-coverage surfaces the transfer student and the lifer on identical terms — because it reads the record, not the relationship. That’s not bureaucracy. That’s fairness you couldn’t deliver from memory.
The slow burn: find out who touches your money
This is the thing owners under-weight up front and get bitten by a year later. Payment processing.
A lot of what’s sold as martial arts billing software acts as the payment processor itself and takes a transaction fee on top of your monthly software fee — a cut of every payment, every month, forever. Let me be precise, because this is where people get it wrong: a transaction fee is normal. Every processor takes one; that’s unavoidable and fine. The trap is a software company inserting itself as the processor and stacking its own markup above standard processing rates.
Do the math on 80 students at ~$150 a month. A couple of extra percent skimmed off the top is real money walking out the door every month — a cost you agreed to without ever really deciding on it, because it was buried in the signup.
So the buyer’s takeaway is simple: find out who touches your money, and whether they take a cut above standard processing — because that line item compounds. (For what it’s worth, GRADR doesn’t touch your money at all: it integrates Stripe, you use your own Stripe account and keep full control, Stripe takes its standard low fee, and we add no markup on top.)
The five-minute evaluation checklist
If you remember nothing else, run any tool you’re considering through these:
- What was it built around — the transaction, or the student? (Read the marketing. Whose convenience does the product center?)
- Was it built for jiu-jitsu by people who know it? Look at the shape of the grading and curriculum tools. Could a non-grappler have designed this?
- Do the features talk to each other? Pick two — say grading and attendance — and ask the salesperson to show you the data flowing between them. Watch for islands.
- Can it gate promotions on real BJJ criteria — sessions, time in grade, and attendance across curriculum areas — or just store a belt color?
- Will it tell you a student is slipping before they quit, or only when their card declines?
- Who processes your payments, and do they mark up standard rates?
Six questions. They’ll tell you more than any feature grid.
Want to see what “built around the student” actually looks like? Book a GRADR demo and we’ll walk your academy through it — curriculum, scheduling, grading, and retention as one connected system, not six.
Frequently asked questions
Isn’t generic gym software fine for a BJJ academy? It tracks attendance and payments too.
On the surface, yes — and that’s the trap. The features exist as disconnected islands: attendance doesn’t feed grading, the schedule doesn’t know your curriculum, the portal can’t show progress toward a belt. In a BJJ academy those pieces need to be one integrated system, and that’s what generic software can’t deliver no matter how long its feature list.
My fitness platform already has a belt/rank field. Why do I need BJJ-specific grading?
A dropdown records a belt. It can’t gate a promotion on attendance across positional areas — say, 10 guard, 10 mount, and 10 standup classes before purple — because it has no concept that those areas exist. BJJ-specific grading understands the structure of the game; a rank field just stores a label.
Do I have to use the software’s curriculum, or can I use my own?
You should be able to use your own. A good system gives you a built-in framework as a starting scaffold, fully customizable — adopt it, adapt it, or build from scratch. The structure should accelerate your system, not replace it.
Does requirement-based promotion replace my judgment as a coach?
No. Requirements are a floor, not a verdict. They guarantee a student was in the room enough times for your eye to land on him and for your teaching to do its work — then you still make the call. They also protect you from promoting someone who looks the part but has never been coached through his weak positions.
What should I watch out for on pricing?
Find out who processes your payments and whether they take a transaction-fee markup above standard processing rates, on top of the monthly fee. A standard processing fee is normal; a software company inserting itself as the processor and stacking its own cut is the part that quietly compounds.
What’s the single most important thing to evaluate?
Whether the features actually talk to each other. Integration is the one thing only a purpose-built tool delivers — and it’s the thing a feature checklist will never reveal.
Nic Gregoriades is a fourth-degree Brazilian jiu-jitsu black belt and the first person ever to receive a black belt from Roger Gracie. He is the co-founder of the Jiu-Jitsu Brotherhood and the founder of GRADR, gym management software built specifically for BJJ academies. He has trained and coached for more than 27 years across four continents.