The problem

By 2025 the academy worked. My calendar did not.

I coached from 17:30 to 21:30 after a full office day. Payments were chased over WhatsApp. Renewals lived in my head. Every new student cost twenty minutes of messages. Every missed payment meant an awkward chat at the worst hour.

You can run a padel academy from your phone. I did it for years. That model has a ceiling, and the ceiling was me. If I stopped, the business stopped with me.

I wanted a business that charges, reminds, answers and sells while I am on court, or out of town entirely.

I looked for a tool built for how an academy actually works. Groups capped at four players. Class packs. Monthly renewals. Make-up sessions. International players who fly in for a week and train twice a day. Nothing fit. So I built it.

The system

Fourteen months building it on my own, in the gaps between classes. The result is one place where the academy's website, every student's record, billing and invoicing all live together. No patchwork of separate tools. The details underneath are not the interesting part. What is interesting is what stopped depending on me.

Every interested family moves on its own through a short process, from the first message to enrolment, with a note on how real the interest is and what to do next. The WhatsApp inbox lives inside the same panel, with the full history of every contact. That panel also holds the accounts and the invoicing, down to the cent, so nothing slips through.

An assistant answers WhatsApp on its own. It resolves questions, offers time slots and prepares enrolments. One rule sits above all of it: it never sends anything without permission. Every reply waits for my approval on Telegram first, and I clear it from my phone in ten seconds.

Payments carry a security signature that cannot be faked. If something breaks mid-charge, the system does not improvise: it stops and flags it before it duplicates or loses anything. Getting into the panel takes two steps of verification.

Student data protection does not depend on my memory. The system itself deletes what is due to go, on schedule, and keeps a record. Other automatic tasks handle class reminders, charges, chasing missed payments and calendar sync.

The real test came in July 2026. Three camps in Russia and a course for 17 coaches with live translation. Two weeks away. The academy kept charging, reminding and answering without me. In September the 2026-27 season opened across two venues, and I did not need to be there for it.

What went wrong

There is a design detail in there called gold. It is green. The brand green ended up labelled with the wrong name, and fixing it never became urgent. It is still that way, noted as unfinished business. Every time I see it I remember that perfection does not pay invoices.

For a while, the internal notes behind the project were lying. They went stale, I chose not to keep them current, and the truth moved somewhere else that actually gets updated. Working alone, keeping two versions of the same truth was the most expensive lie of all.

The first automatic payment alerts failed silently. A retry could duplicate a charge. A dropped connection could leave one half-done. Today the system will not move forward if something does not add up: it stops and flags it instead of risking bad data. It took real scares to learn to distrust anything arriving from outside.

And the bot. The first version sounded like a machine and offered things it should not have. The Telegram approval gate was not the original plan. It was the fix. I gave up full automation and got something better. Nothing goes out under my name without my eyes on it.

The CRM runs the daily operation. I run the method. That split is the product.