Switching software is painful and worth doing only when staying is more painful. Here is the honest framework for deciding when, with three signs you should switch and two signs you should wait.
The bias to acknowledge
You'd think a vendor's blog post would say "switch immediately." But schools that switch reactively usually switch again within two years. Schools that switch with a clear reason and a plan usually stay. We'd rather have fewer customers who stay than more who churn.
Three signs you should switch
1. The product blocks a workflow you need
Not "annoys" or "is awkward." Blocks. Examples:
- You can't track BJJ stripes the way your style requires, and it's affecting promotions.
- You can't bill a family across multiple locations, and you have multiple locations.
- Your instructors can't reliably log progress in any reasonable time, and the data is always stale at belt tests.
If your software prevents you from doing your job correctly, the math on switching gets easier. The ongoing cost of the block is usually higher than the one-time cost of migration.
2. The pricing model is misaligned with your growth
Per-student pricing penalizes you for succeeding. Percentage-of-payments pricing scales linearly with your revenue. If your software costs grow faster than your owner take-home, the pricing model is fighting you. That's a switch reason.
3. The team has effectively given up on the system
You can tell by the workarounds. Side spreadsheets, texts about students that should be notes in the system, a group chat that's the real source of truth. When the team has structurally routed around the software, the software is no longer doing its job.
A workaround is information. Five workarounds is a decision.
Two signs you should wait
1. You've never given the current tool a real shot
If you bought it 3 months ago and you're already shopping, the problem might be that you haven't finished onboarding. Most tools have meaningful features you discover in months 4 to 6. Give it at least one full belt-test cycle and one full billing quarter before you decide.
2. You're in a deal-breaking workflow with families now
Mid-belt-test is the wrong time to switch software. So is the week before a billing cycle. If you're in the middle of an operational crunch, fix the crunch first. Pick the next quiet two-week window for the switch.
The cost of switching, honestly
The migration itself is usually about two weeks for most schools. The harder cost is the team's attention. Your front desk has to learn a new tool. Your instructors have to adopt a new workflow. The owner has to be visible during the transition.
A reasonable mental model: assume 4 weeks of partial-attention overhead from when you sign to when the new tool is your real source of truth. If you have a quiet stretch coming up, that's the right window.
The cost of staying, also honestly
The cost of staying compounds. A workflow that frustrates instructors is also slowly losing them. Pricing that grows faster than your business is slowly eating your margin. A tool that doesn't surface at-risk students is slowly losing students. None of this hits in one big bill; it hits as a slow drip.
When you've felt the drip for two consecutive quarters and the workarounds aren't enough anymore, the math has usually tipped.
The decision exercise
Write down three workflows that frustrate your team most. For each, ask: is the current software the cause, or is it a process problem we're blaming on the software? If two of three are software's fault and one is a process problem, you're switching for the right reasons. If it's the other way around, fix the process problem first.