RUNEM exists because the people who run clubs deserve to spend their time on their club and their members, not on spreadsheets, bank transfers and chasing renewals.
Most clubs are kept going by a handful of volunteers giving up their evenings. Too much of that time disappears into membership admin: rebuilding spreadsheets each season, reconciling bank transfers, chasing people to renew, and keeping member details accurate and GDPR-safe across half a dozen places.
The big "free" platforms help, but they are built for sport in general, not for the way your club actually works, and your money and data live inside their system. RUNEM is different. A simple 1% platform fee and nothing else from us, no monthly charge and no contract, and your own Stripe so the money lands in your club's bank. And for running and athletics clubs, it understands first claim, second claim and England Athletics registration out of the box.
RUNEM is built by Ryan McLeod of RyanDesign, the studio behind Race Calendar. Ryan is not only a developer, he has spent his life in the sport: a former GB international and twice British Half Marathon Champion, in 2014 and 2015. He stepped away for health reasons, came back to marathon running, and finished London 2026 in 2:19 as first V40.
He documents the comeback as Fast Forties on YouTube and Instagram. That matters because RUNEM is built by someone who lives in the running world, not a software company guessing at it. Memberships are the start; race entries come next.
RUNEM was built with running clubs in mind, hand in hand with a real UK running club as its founding member, so every feature is tested against how a club actually operates, not how we imagine one might. The same tools now work just as well for clubs in any sport. If something does not save a volunteer time, it does not make the cut.
We are onboarding founding clubs now and would love to hear from you.
We use a few essential cookies to make RUNEM work. With your permission we also use Google Analytics to understand how the site is used. See our cookie policy.