How to Build a CRM for a Kids Activity Centre in Saudi Arabia (Arabic-First, With Parent Accounts)
Kids activity centres are everywhere in Saudi cities now: football and swimming academies, robotics and coding clubs, Quran and Arabic classes, art studios, gymnastics, summer and Ramadan camps. Most of them start the sa
Kids activity centres are everywhere in Saudi cities now: football and swimming academies, robotics and coding clubs, Quran and Arabic classes, art studios, gymnastics, summer and Ramadan camps. Most of them start the same way. Enrolments arrive on WhatsApp, the schedule lives in a spreadsheet, payments are tracked by whoever took the transfer, and the parent group chat is the "system".
That works for thirty children. At two hundred, across two branches and three age groups, it starts to cost money: missed renewals, siblings billed twice, a coach who doesn't know a child has an allergy, and an owner who can't answer "how many children did we lose after the trial class?"
This guide walks through building a simple CRM for a kids activity centre, Arabic first, with accounts for parents. I'll use Mythex, an AI app builder made in Dubai where I work, for the build steps, but the list of what to track and the order to build it in is useful whatever tool you pick.
What a kids activity centre actually needs to track
A CRM for a children's club is not a sales pipeline. The "customer" is a parent, the person attending is a child, and most of the value is in the relationship over months. Before building anything, agree on these records:
- Families. One parent account can have several children. Siblings share a phone number, an address and often a discount.
- Children. Name in Arabic and English, date of birth (age groups change every September), medical notes and allergies, who is allowed to collect them, photo consent.
- Programmes and groups. "Swimming, level 2, girls, 6ā8 years, Sunday and Tuesday, 4:30 pm, Al Malqa branch." Each group has a coach, a capacity and a term.
- Enrolments. Which child is in which group for which term, with a status: trial, active, paused, finished.
- Attendance. Per session, marked by the coach on a phone.
- Payments. What each family owes per term, what they paid, and how (mada, transfer, cash). You don't need full accounting here, just a clear "paid / due / overdue".
- Leads. Parents who asked about a trial and never booked. This is the list most centres never look at.
Write these on one page with the names your staff actually use. If you call them "levels" and not "groups", the app should too.
Why Arabic-first matters here
Parents in Saudi Arabia will mostly read Arabic. Coaches may be Saudi, Egyptian, Filipino or British, so the staff side often needs English too. Decide this up front:
- Parent screens: Arabic by default, right-to-left, with a switch to English.
- Staff screens: bilingual, so a coach can switch to the language they read fastest.
- Messages to parents: Arabic, with names written the way the family wrote them.
Mythex builds apps fully in Arabic, with right-to-left layouts, when you ask for it, so you can describe the app in Arabic or English and say which language each side uses.
Step 1: Start with the family and child records
Don't start with the dashboard. Start with the data, because everything else hangs off it. The first prompt I'd type:
Build a CRM for a kids activity centre in Riyadh. The app is Arabic-first with a switch to English, right-to-left by default. Store families (parent name, phone, email, district) and children (name in Arabic and English, date of birth, gender, medical notes, allergies, authorised pickup people, photo consent). One family can have several children. Staff see a searchable list of families and can open a family to see its children. Use a real database.
Check the preview on your phone. Add two real families (with permission) or two made-up ones that look like real cases: a family with three children, a child with a severe allergy. If the screens don't match how your reception works, say so in plain words: "Show the allergy in red at the top of the child's page."
Step 2: Programmes, groups and enrolment
Next, the timetable and who's in it:
Add programmes and groups. A programme is an activity (swimming, football, robotics). A group belongs to a programme and has a level, age range, gender, branch, coach, days and time, capacity and term dates. Staff can enrol a child in a group with a status: trial, active, paused or finished. Warn if a group is full or the child is outside the age range. Show each group's list of children with their allergies visible to the coach.
The age check sounds small. It saves the argument at the pool when a seven-year-old ends up in the 9ā12 group.
Step 3: Attendance on the coach's phone
Coaches won't open a laptop by the pool. Give them one screen:
Add a coach view. A coach signs in and sees only today's groups. Tapping a group shows the children with large tick boxes for present or absent, and the child's allergy and pickup notes. Save attendance per session. Owners can see attendance by group and month.
Then ask for one useful alert: "List children who missed three sessions in a row so the centre can call the parent." That list is where retention is won.
Step 4: Payments per term, without pretending to be accounting software
Add term fees. Each enrolment has a fee for the term. Record payments with amount, date and method (mada, bank transfer, cash). Apply a sibling discount of 10% to the second and later children in the same family. Show each family's balance: paid, due or overdue. Give the owner a list of overdue families with phone numbers.
If you want parents to pay online, ask Mythex to connect a payment provider that supports mada. You sign up with the provider yourself and add your own keys; the app uses them. Your accountant still does the books and your ZATCA e-invoicing stays in the tool you already use for it. This screen is only there so reception knows who has paid.
Step 5: A parent account
This is what parents notice:
Add parent accounts. A parent signs in with their email and sees only their own children: groups, schedule, attendance, balance due, and a form to update medical notes, allergies and authorised pickup people. Every change a parent makes is logged with the time. The parent side is Arabic by default.
Sign-in for your parents is built into your app with your database, separate from anyone's Mythex account. If you'd rather parents sign in with a code sent to their phone, that needs an SMS provider you sign up with yourself. Test it with two parent accounts and make sure one parent can never see the other family. That check is worth doing by hand every time you change the app.
Step 6: Leads and trial classes
Add a lead list. A public form (Arabic first) lets a parent request a trial class: parent name, phone, child's age, activity and preferred branch. Leads have a status: new, contacted, trial booked, joined, not interested. Show the owner how many leads became active enrolments each month, by activity.
Now you can answer the question you couldn't before: which activities turn trials into enrolments, and which ones lose families after the first visit.
What the centre ends up with
After those six steps, the centre has one place for families, children, groups, attendance, fees and leads, with:
- A Postgres database behind it, so the data is in proper tables rather than a fragile sheet.
- Parent and coach accounts with separate views.
- Its own web address, and on Mythex Pro its own domain (for example
app.yourcentre.sa). - On Pro, the same app sent as an Android app (Google Play internal testing) and an iPhone app (TestFlight), which parents tend to prefer over a link.
Honest limits
- Children's data is sensitive. Collect only what you need, limit medical notes to the staff who need them, and check your obligations under Saudi Arabia's Personal Data Protection Law. If your data must be hosted inside the Kingdom, confirm where any tool hosts it before you start; that may rule some tools out, including the hosted route described here.
- It's a CRM, not a full school system. If you need grading, transport routes or government reporting, a dedicated school or academy product may fit better.
- Someone has to own it. Pick the person who will make small changes (a new branch, a new programme each summer) before you build.
- Read the Arabic once. The builder writes the labels, but a fluent person should check every parent-facing word, especially medical and consent wording.
For teams
If the owner, a branch manager and an admin will all work on the app, keep it in a shared team workspace rather than one person's account. On Mythex that's the Business plan, from $50/month: a shared workspace, roles (admin, editor, viewer), members-only apps that only signed-in colleagues can open, and Google Workspace sign-in with your company domain. More ideas for club and youth programme software are on our youth club software page, and plans are on the pricing page.
Start smaller than you think
The centres that get value from a CRM start with one branch and one programme, run it for a term, and then add the rest. Build the family and child records this week, put attendance on the coaches' phones next week, and leave payments and leads until the first two are part of the routine. A simple system people actually use beats a complete one nobody opens.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes ā full credit and traffic to the original publisher.