From 45 minutes of admin to one phone call
Kixx wanted every child with a birthday to be offered a free football session to share with two friends: more than 800 birthdays a month across 241 venues, without hiring an admin team to run it.
The Mission
Kixx wanted every child with a birthday to be offered a free football session to share with two friends, so that happy families bring new families into the club. With more than 800 birthdays a month across 241 venues, they needed to do it without hiring an admin team to run it.
The Outcome
A birthday treat system built around a single phone call. A team member agrees the date with the parent, or offers a few dates after a voicemail. The parent confirms on their phone and shares an invite on WhatsApp. Friends register themselves, places close when the session is full, and the local franchisee is told automatically. Built and launched in one week.
The Impact
- Each treat now takes one phone call, down from 30–60 minutes of chasing, phoning, re-keying and emailing. [TODO: admin time saved, measured]
- The treat can go to every birthday, not just the few the office had time for.
- Launched inside the winter window, when referrals matter most.
- [TODO: treats booked]
- [TODO: friends registered]
- [TODO: families who joined]
The goal
Kixx coaches children's football across the UK through a network of franchisees, with over 10,000 members at 241 venues. Their best source of new families is the families they already have, and a birthday is the perfect excuse for a recommendation: the birthday child invites two friends to a free session, and those friends' parents see Kixx for themselves.
Kixx already ran birthday treats, but every one was handled by hand. A form went out, then the office took over: chasing parents, phone calls, liaising with franchisees, keying details into their CRM, and emailing the franchisee at the end. That came to 30 to 60 minutes of admin for every birthday.
At more than 800 birthdays a month, offering a treat to everyone would have meant at least 400 to 800 hours of admin every month. That's a team of people, not a side job.
Then there was the timing. Winter is football's quiet season: parents are slow to sign up for outdoor sessions in the cold and wet, so recommendations from existing members count for more than ever. Kixx wanted the treat running within a week to catch that window.
The gap
Kixx came with a clear idea and a plan: a team member rings the parent and offers the treat, emails a form, then produces something the parent can share with two other parents, and someone ties the three families together by hand. It was a sensible plan for the tools they knew. What they didn't know was how much of it a system could do for them.
So before designing anything, I asked the admin team to write out their current process, step by step, exactly as they did it. That changed the project. Instead of "build us a form", the question became: which of these steps really needs a person?
The answer was one. Kixx's team likes speaking to parents in person, so we kept the call. Everything after the call became the system's job. If the parent picks up, the date is agreed there and then, and the parent receives a link with their booking already filled in, ready to confirm. They choose whether to bring one friend or two, and get an invite link to share. Each friend's parent registers through that link, and all three families end up on a single booking.
Halfway through the build, the team mentioned something that wasn't in the brief: most calls end in a voicemail. Under the old process, every voicemail meant more chasing. So we added a second way to prepare a booking. The caller picks a few dates that work for the venue, the parent chooses one on their phone, and they carry straight on to inviting their friends. Nobody in the office has to touch it again.
The rest of the work went on the things that would otherwise land back on the admin team's desk:
- No overbooking. Once the friends' places are taken, the invite closes by itself, and it reopens if a friend drops out. If two parents try for the last place at the same moment, only one gets it.
- The franchisee hears automatically. When a session fills, the local franchisee gets the details by email, so the coach knows who's coming. They don't need a login, and they never see a child's medical information.
- Children's data is treated with care. Medical and emergency details are encrypted and visible only to named staff, every view is logged, and they're deleted 30 days after the session. Each parent's consent is recorded against the exact wording they agreed to.
- One page per birthday. Staff see everything about a booking in one place, without chasing anyone for it.
- Kixx owns the words. All the wording and photos live in their Wagtail admin, so they can change them without calling a developer.
The hardest part wasn't the software. Sending WhatsApp messages from a business means Meta has to verify the business and approve every message template, word by word, and that process doesn't care about your deadline. We wrote the templates to Meta's rules, kept email running underneath as a safety net, and got the parent's message approved in time for launch. [TODO: confirm]
The gamble
All of this rested on one decision that Kixx had to make.
Kixx had never sent a WhatsApp message. Email was what they knew. But the treat only works if the birthday parent can get the invite to two other parents, and when we talked it through, the problem was obvious: parents don't have each other's email addresses any more. Email is for work. What they all have is WhatsApp.
Not everyone was convinced. "Does everyone have WhatsApp?" was a fair question from a team that cares about not leaving families out. Kixx weighed it up and backed WhatsApp, on one condition: nobody gets stuck. So the parent's link arrives by WhatsApp with an email copy as backup, and the invite page lets them share by WhatsApp, copy the link, or use their phone's own share menu.
“[TODO: testimonial from Kixx]”
The rollout and the gain
The birthday treat went live in the week of 20 November 2026, one week after we started and right at the start of the winter window.
For Kixx's admin team, a birthday treat is now one phone call. Everything that used to fill the next 30 to 60 minutes (the chasing, the re-keying, the emails to franchisees) happens by itself. That's what makes it possible to offer a treat to every child with a birthday, not just the ones the office had time for.
[TODO: first results, e.g. "In its first two weeks, X treats were booked, Y friends registered and Z new families joined." Add treats booked, friends registered, families who joined and admin time saved.]
We're already working on what's next. Soon the person who made the call will see whether the parent's WhatsApp was delivered and read, so a missed message gets a follow-up instead of silence. Then we'll take the remaining office jobs off the team's plate one by one.
Have a process that only works because someone does it by hand?
Let's talk about which steps really need a person.
Get in touch