Mini Swimming: AMES's First Live Tenant

Mini Swimming was the first live tenant on AMES.

That matters because this was never just a demo project or a proof-of-concept on fake data. It was a real swim school with real families, real bookings, real payments, and real operational pressure. If the platform could handle Mini Swimming, it could handle the kind of complexity activity businesses deal with every day.

---

Why Mini Swimming Was the Right First Live Tenant

Mini Swimming is not a small pilot programme.

It is a large, multi-site operation with:

• 16,052 active members
• 156 classes per week
• 13,150+ bookings processed through the platform
• A team that needed bookings, payments, communication, and attendance to work together

That scale made it the right test case. The product had to work in the real world, not just in a staged demo.

---

What They Were Running Before AMES

Like many growing activity providers, Mini Swimming had built its operation out of separate tools.

Before AMES, the team was juggling:

• Spreadsheets for class and roster management
• Separate payment workflows
• Email and message threads for parent communication
• Paper attendance sheets poolside
• Shared folders for documents and records

None of those tools were terrible on their own. The problem was that they did not act like one system.

That meant more manual work, more copying and pasting, and more chances for things to fall between the cracks.

---

What Changed When AMES Went Live

AMES gave Mini Swimming one connected platform for the work that had previously been split across several systems.

That changed the day-to-day flow in a few important ways.

Bookings became self-serve

Parents could find available classes, book, change, or cancel without the team needing to handle every request manually.

That reduced the constant back-and-forth that eats into the day.

Payments became visible

Instead of chasing separate payment records, the team could see payment status in the same place as bookings and account data.

That made it easier to understand what had been paid, what was due, and where follow-up was needed.

Attendance became digital

Poolside attendance no longer needed to rely on paper sheets that had to be collected, transcribed, and reconciled later.

Parent communication became structured

Messages, updates, and important account information lived in the same system instead of being scattered across inboxes and chat threads.

---

What We Learned From the First Live Tenant

The first live tenant is where software gets honest.

Mini Swimming showed us a few things very clearly:

1. Real operations reveal edge cases

A demo environment is clean. Real life is not.

Once a real swim school starts using the platform, you find the awkward cases:

• Class changes
• Payment edge cases
• Family account complexity
• Communication timing issues
• Progress visibility questions

Those are exactly the cases the product needs to handle well.

2. Parent experience is part of the product

If parents cannot see information clearly, the office team ends up translating everything.

Mini Swimming reinforced that the family-facing experience is not an add-on. It is a core part of how the system works.

3. Visibility creates confidence

When bookings, payments, attendance, and communication live together, the business becomes easier to understand.

That is good for operators, and it is good for parents too.

---

The Results

Mini Swimming did not just help prove the platform.

The move to AMES delivered measurable gains:

• 12 hours saved per week in admin time
• 85% fewer booking phone calls
• 90% reduction in overdue payment noise
• Faster rebooking when spaces opened up

Those numbers matter because they show the platform was not just functional. It made the business easier to run.

---

Why This Case Study Matters Beyond One Tenant

Mini Swimming is the first live tenant, but it is not a one-off story.

The lesson is broader:

• Activity businesses need connected workflows
• Parent communication needs to be simple
• Payments and bookings should not live in different silos
• Admin time should go down as the business grows, not up

That is why the first live tenant was such an important milestone. It proved that AMES could support a real business with real operational demands.

---

The Bottom Line

Mini Swimming is more than the first customer story on AMES.

It is the proof that the platform works in production, at scale, with real families and real operational pressure.

That is why we keep referring back to it. Not because it is a nice anecdote, but because it is the clearest demonstration that AMES was built with an actual activity business, not just around one.

If you want the simple version: Mini Swimming was the first live tenant, and the platform had to earn its place there.

It did.