Dance is a people business.
Parents want to know their child is seen. Students want to feel part of something. Coaches build relationships that software cannot replace.
So the goal of automation should never be to remove people from the experience.
It should remove the repetitive work that prevents your team from spending time with people.
Start with repetitive, rules-based admin
The strongest automation opportunities are usually tasks that happen frequently and follow a predictable rule.
Examples include:
- booking confirmations
- payment receipts
- trial reminders
- pre-class information
- attendance-triggered follow-up
- membership onboarding
- failed-payment reminders
- registration renewals
- internal staff notifications
- class-capacity alerts
- cancellation acknowledgements
These processes do not become more valuable because somebody manually sends them every time.
Keep judgement human
Automation is weaker when context and judgement matter.
A parent raising a sensitive concern should not be pushed through a generic sequence.
A student struggling in class may need a coach to make a thoughtful decision.
A complex billing dispute may need somebody to review the account.
The best operating systems make routine processes automatic while making exceptional cases easier for a human to see and handle.
Design around triggers
A practical way to think about automation is:
When X happens, what should happen next?
When a trial is booked, what information should the parent receive?
When attendance is marked, should a follow-up sequence begin?
When a payment fails, who needs to know?
When a class reaches capacity, should booking close or create a waitlist?
When a student joins, what records, communications and staff actions should happen automatically?
Once you map those triggers, you begin to see the real workflow of the school.
Good automation feels like good service
Customers usually do not care whether an email was manually sent or automatically triggered.
They care whether it was useful, accurate and arrived at the right time.
In fact, automation can improve service because consistency no longer depends on how busy the admin team is that day.
A parent can receive the right information immediately after booking rather than waiting until somebody has time to send it.
Avoid over-automation
Not every possible automation should be built.
If the logic is difficult to explain, if exceptions happen constantly or if an incorrect action would create a significant customer problem, manual review may be better.
Automation should simplify the operation, not make it harder to understand.
The real benefit is capacity
At Urban Motion, the most valuable part of building our own system was not the novelty of automation.
It was getting time back.
Every process the system could handle reliably was one fewer repetitive task competing for attention.
That capacity can then be used for teaching, leadership, programme development, customer relationships and growth.
That is the standard I use when thinking about automation:
Does this remove friction while improving or protecting the customer experience?
If the answer is yes, it is usually worth exploring.