Live in days, not months
You do not rebuild your club. We move it across and switch it on. Your staff learn it in an afternoon, and your members never get a manual because they never need one.
Four steps, and we do most of them
No rebuild, no six month implementation, no consultant living in your inbox.
- 01
Book a demo
Day oneTwenty minutes on a call. We show Atemi running on a real club and map your plans, classes and sites onto the platform while you watch. You leave with a price and a migration plan, or you leave with neither and no hard feelings.
- 02
We migrate your members
The heavy liftingYour members, plans and mandates move across, with identity deduplication so households and duplicate records get cleaned up on the way in. Nothing is retyped by you, and no payments drop. This is our job, not homework we set you.
- 03
Brand it as yours
An afternoonYour logo, colours, domain and member app. Publish a new website from the builder or keep the one you have. By the end of the day your members would not know there is a platform underneath.
- 04
Go live and grow
From there onCollections run, classes fill, the churn worklist works the room. Turn on CRM, POS, reviews or automations whenever you are ready, not because a contract said so.
The scary part is the part we do
Every club we speak to is afraid of the same thing: moving live mandates without breaking anything. Fair. It is why we scope it before you commit and test it before a single collection runs.
Members and households
Records, contacts, relationships and guardian links, with duplicates merged rather than carried over.
Plans and prices
Your membership structure as it actually is, including the awkward legacy plan you keep meaning to retire.
Direct Debit mandates
Moved with care and tested before a single collection runs. This is the part everyone is afraid of, so it is the part we are slowest and most careful about.
History that matters
Payments, attendance and grading, so day one on Atemi is not year zero for your club.
Software nobody has to be trained on
A club is staffed by coaches and a front desk, not administrators. If a screen needs a manual, we built it wrong.
Staff learn it in an afternoon
The console is shaped like the club, not like a database. A coach opens the register and sees the register. Nobody reads a manual, because nobody ever does.
Members never get instructions
They install the app, their pass is on the home screen, and they book a class in two taps. If a member has to be trained, we designed it wrong.
The console shrinks to fit
Modules you have switched off leave the screen entirely. Your staff see the six things your club does, not the twenty two the platform can do.
Mistakes are hard to make
Roles are enforced on the server, actions are audited, and anything that can block a member has an admin override instead of a dead end.
You change it yourself
Labels, prices, capacities, copy, thresholds. Nothing a member sees is hardcoded, so changing your mind does not mean raising a ticket with us.
It gets out of the way
The whole point is fewer evenings on admin. If the software is the main character in your week, it has failed.
The easiest install your club will ever run
There is no rollout plan for the member side. They install the app, their pass is there, and the front desk stops answering questions it should never have been asked.
Pass on the home screen
Installable and branded to your club. It works with no signal.
Self serve everything
Freeze, change or upgrade without an email chain to your desk.
Two taps to book
Grab a spot, join a waitlist, get auto promoted when one opens.
About switching
Days, not months. Our founding school moved 600 members in a week, and a smaller single site club is usually quicker. The variable is not the software, it is how tangled the data is in the system you are leaving. We tell you which you are on the call, before you commit.
Much less than you are bracing for. The migration is our job: you hand over an export and answer questions about your plans. The parts that need you are the decisions only you can make, like which awkward legacy plan finally gets retired.
No, and this is the part we are most careful about. Mandates move and get tested before any collection runs. We schedule the cutover around your billing dates rather than dropping it on top of them.
No, and most clubs should not. Start with billing and classes, get those boring, then add CRM, reviews or POS once your staff have the basics in their hands. Turning a module on later costs you nothing in rework, because the data is already there.
There is an onboarding walkthrough in the product, and the console is built so the common jobs are the obvious ones. In practice a front desk is comfortable within an afternoon. If a screen needs a training session, that is a bug in our design and we would like to hear about it.
You talk to people who run a club on this platform, not a script. Our founding school is on the same software you are, which is a strong incentive for us to fix things properly.
The demo is on a real club with real workflows, not a slide deck. Bring your worst workflow, the one that eats your Tuesday, and make us show you it working.
Bring us your worst workflow
Book a 20 minute demo. We map your migration on the call and tell you honestly how long it takes.