Private Pilates studio in Bengaluru with full apparatus and one instructor

How I Use AI to Run a Solo Pilates Studio Efficiently

Written by Abdul Kalam, Pilates instructor · For educational purposes only; not medical advice.

Let me begin with what this post is not about.

I do not use AI to plan Pilates lessons, choose exercises, sequence a session, interpret a client's body, or decide how the work should be adapted. I do not use it to diagnose, assess medical suitability, or replace the judgement that belongs to the instructor.

Teaching happens in real time. It depends on what the person in front of me is doing, how the body responds to the exercise, what changed after the previous cue, and what the session requires at that moment. That responsibility remains mine.

This post is about everything around the teaching: the website, the appointment system I built for my studio and later made public, and the technical work required to run a one-person business without letting administration consume the time and attention that belong in the studio.

I run a private, appointment-only studio in Bengaluru. The client roster is deliberately small. There is no administrative team, and there is no scale that makes high recurring costs unimportant. Every system has to justify the money, time, and attention it requires.

That is where AI has made a practical difference.

The Website: Control, Performance, and Cost

When I opened my studio in 2021, I used Squarespace for the website. The annual price began at US$216, with an additional foreign-currency conversion charge of about 3.5%. By the time I left Squarespace in August 2024, the annual price was US$276 before that charge. Later in 2024, I moved to Wix and paid ₹4,500 for a three-year subscription — the equivalent of ₹1,500 a year. Both were capable platforms, but neither gave me the control I wanted over how my studio's website worked.

I kept having to shape the website around the platform's structure, templates and available features. That was the opposite of what I wanted. My broader goal was to control the digital infrastructure my studio depends on — the website, its code, hosting and deployment — while keeping the recurring costs proportionate to a small business. I wanted the freedom to build what the studio needed and maintain it on my terms.

I have a background in software development. I understood the kind of system I wanted, but building and refining it alone while teaching full time would have taken more time than I could reasonably give it.

I used AI as a development assistant while building the present website in HTML, CSS, and JavaScript on a Node.js server. I defined the requirements, reviewed the code, tested the implementation, corrected what did not work, and remained responsible for the final system. AI accelerated parts of the development process; it did not remove the need for technical judgement.

AI also helped me research the available infrastructure and work through the Git setup, including my GitHub repository and the deployment environment on MilesWeb. I can now make changes to the website or appointment application through the same version-controlled workflow. That makes maintaining the studio's digital systems much more straightforward.

On 9 November 2026, a Lighthouse audit of the studio homepage returned scores of 100 in Performance, Accessibility, Best Practices, and SEO on desktop. A separate mobile run returned 97 in Performance and 100 in the other three categories. These figures describe those particular tests; they are not a promise that every future run will produce identical results. The site also performed substantially better than the previous versions in my own testing. I chose hosting in India partly to avoid unnecessary network distance for the people most likely to visit it.

Desktop Lighthouse results: Performance 100, Accessibility 100, Best Practices 100, SEO 100
Desktop audit · 9 November 2026
Mobile Lighthouse results: Performance 97, Accessibility 100, Best Practices 100, SEO 100
Mobile audit · 9 November 2026

The website and appointment application now run on MilesWeb infrastructure. I paid approximately ₹4,000 for a three-year hosting plan, running through 2029 — about ₹1,333 a year when spread across that term. The domain is separate, at roughly ₹1,700–₹1,800 a year. I had to pay for the domain under the earlier platforms too, so I do not count it as a saving.

More importantly, the website now reflects the studio accurately. The pricing, practical limitations, teaching boundaries, photographs, Journal, and consultation process are not being forced into a general-purpose template. They exist because they are relevant to this particular practice.

AppointFrame: Building the Scheduling System I Needed

Booking administration began as a much smaller problem. I needed to confirm appointments and remind clients without writing the same emails over and over. But a reminder system was not enough for the way my studio actually works.

Before building my own system, I used Calendly, which cost US$144 a year plus the foreign-currency conversion charge, and later Zoho Bookings, which cost ₹7,776 a year. I also tried other services. They are good products, but I was again adapting my workflow to the software rather than using software built around the way I operated. The experience was familiar from the website, and it led me towards the same decision: build what I needed and retain control of it.

My clients usually work through session packages. One current example is twenty paid sessions with two complimentary sessions. That creates more to manage than a calendar appointment: the package has to be created, appointments have to be linked to it, and the session balance and related communication have to remain organised. I now create a client's package and renew it when necessary. The system handles the booking workflow around it.

I developed my own appointment system for this purpose. I wrote most of the code myself, using plain HTML, JavaScript, Node.js and an SQLite database. What began as software for my studio has also been made publicly available as AppointFrame. The link is there for anyone curious about the system; this article is about why I built and use it.

The software manages client enrolment, instructor and studio availability, session types, packages and appointments. I can repeat a previous week's bookings, schedule a month ahead or set up recurring appointments. There is an instructor-facing interface and a client-facing interface. Clients can make certain bookings and create packages themselves, although those self-service options are deliberately limited.

AppointFrame can also handle multiple instructors and group sessions. Those are capabilities of the software, not a description of my Pilates studio. My own studio still operates with one instructor and one client in each private session.

Communication has changed too. The old process was primarily email-based. Now WhatsApp is central to the appointment workflow. When an appointment is confirmed, both the client and the assigned instructor receive a message. The client receives a reminder twenty-four hours beforehand. If an appointment is cancelled, both sides are informed. I no longer need to manage those routine messages one by one.

AI's contribution was substantial, but specific. It helped me compare software options, research and set up the infrastructure, configure the WhatsApp Business account, work through Meta's utility-message templates, standardise the communications, review code quality, run security checks and investigate faults when something did not behave as expected. I still wrote most of the application, tested what was built and made the final technical decisions. AI reduced the time spent finding answers and resolving problems; it did not build the entire system for me.

The software itself has no scheduling-platform subscription fee. Building it cost me my own time. As a comparison, the three-year Wix plan worked out to ₹1,500 a year, and Zoho Bookings cost ₹7,776 a year: ₹9,276 annually when those costs are spread across the same period. The MilesWeb hosting plan now works out to about ₹1,333 a year. Allowing for the small cost of routine WhatsApp messages, that leaves an annualised saving of approximately ₹7,500. The domain cost exists in either setup and is excluded from this comparison. These are annualised costs, not money recovered from an earlier prepaid subscription.

If I continue with this same studio model, I would be comfortable planning to use AppointFrame for the next ten years. That does not mean the code can be left untouched. Node.js will change, infrastructure will need attention, and Meta may revise its platform requirements. I will have to keep the software compatible. But I do not see a reason to replace the scheduling system simply to continue the same private, package-based business model.

Privacy and Responsibility

Using AI does not remove my responsibility for the systems I choose to use. The studio's privacy obligations still apply, and no tool is given authority to make decisions about a client's health, suitability, instruction, or teaching relationship.

Administrative assistance is useful only when its role remains limited. A generated draft still has to be reviewed. Code still has to be tested. A calculation still has to be checked against the underlying record. A system may reduce repetitive work, but responsibility for what is published, sent, stored, or acted upon remains with me.

Where AI Helps and Where It Stops

The conversation around AI often moves towards either dismissal or exaggeration. Neither is particularly useful.

In my studio, AI does not watch a client move, choose the spring setting or decide whether an exercise is right for that particular session. I make those decisions while I am there, watching the response to the movement and the instruction. If Short Spine needs to wait, if Frog needs more time, or if a cue has not helped, that is for me to recognise and address with the client.

Nor do I outsource the working relationship. The client has to be able to tell me what they feel, ask questions and develop confidence in the work over time. A tool can support the administration of that relationship; it does not take part in the lesson.

What it can do is help me build and maintain the systems around the teaching. In this case, that has meant infrastructure research, development support, troubleshooting, testing and the removal of repetitive administration. The code, the systems and the decisions about using them remain my responsibility.

I did not need AI to make me a better Pilates instructor. I used it to help me build the tools a one-person business needs without handing over the teaching or paying indefinitely for software I could develop and maintain myself. That is where it has made a real difference.

The teaching happens in real time—through what the body is showing in that particular session. No tool changes that. A tool can only reduce how much administration gets in the way of doing the teaching well.