The Altera Sport fitness studio moved from an off-the-shelf booking service to its own CRM. A trained AI developer agent, built right into the admin panel, keeps improving it. The owner and front-desk staff describe a change in plain words and attach a screenshot. A couple of minutes later they get a finished change and a plain-language report. There are no programmers in this loop. In the first two days the owner gave the agent 14 tasks. Each took the agent between 44 seconds and 3 minutes.
Turnkey setup — ₽99,000, incl. 5% VAT. We train the agent on your company's knowledge base and your staff to work with it.
Altera Sport is a fitness studio in Saint Petersburg: personal training, EMS, massage, group classes. Our agents had already built the studio's website, Yandex Direct advertising, online payments and end-to-end analytics — that's CASE 03. Bookings, clients and payroll, however, lived in DIKIDI, a popular cloud booking service.
The team was used to it but kept hitting things no boxed product will ever have: payroll by the studio's own schemes, seat limits per room, split sessions for two, a multi-service visit on one receipt, its own online booking on the website and all client data in its own database. Every such detail is custom work for one client. No boxed service will do it, and ordering it from programmers is slow and expensive.
The solution: build the studio's own CRM that feels as familiar as the old system, and give the owner a tool to keep improving it without programmers.
| What | Before | Now |
|---|---|---|
| System | A subscription cloud service, the same for everyone | The studio's own CRM: code, data and rules belong to the studio |
| A change is needed | A request to support — maybe some day | A task in the Change Center — done in minutes |
| How to explain it | Spec, calls, emails with a developer | Plain words + a screenshot, like in a messenger |
| Cost | Developer hours, prepayment, rough estimates | The cost of every task is in the table: ₽76–197 for a typical change |
| Control | You find out once it's already live | “Accept” and “Send back” buttons on every task |
| Client data | On someone else's servers | In the studio's database, with backups |
The owner recorded the old system's screen for 21 minutes, saying out loud what the new one must do. The agent transcribed it, went through it screen by screen and produced a 67-item spec with 35 screenshots and an acceptance checklist.
Booking journal, clients, memberships and gift certificates, sales and receipts, finances by account, payroll by scheme, goods, access rights for six roles, client import, Google Calendar sync.
The owner asked for everything to look exactly like the old system so the front desk wouldn't need retraining. Booking colours, payment windows and payroll tabs mirror the familiar screens.
The studio's own booking page with strict rules: only the trainer's shifts, room limits, 15-minute steps. Requests go straight to Telegram, MAX and email.
The front desk sent five video notes and a voice message in Telegram. The agent transcribed them, found the cause of each of the 9 issues in the code and fixed them all in one evening.
A tab in the CRM header. A task goes straight to the agent, without us in the loop. The agent makes the change on a test copy, checks it and reports back. The team accepts the work or sends it back.
The Change Center is a single page inside the admin panel. It's used by the owner and front-desk staff, not programmers: they have no terminal, no code and no server access.
What to change and how it should be. A screenshot goes right into the field — Ctrl+V or drag and drop.
The queue is checked every 5 minutes. The agent reads the task and the screenshot, finds the right place in the code and makes the change. It then checks 20 key screens and deploys the change to a test copy of the site.
Not “patched a function” but “open the journal — non-working hours are grey now”. Next to it: working time, tokens and cost.
Not happy? Write what to redo and attach a screenshot. The task goes back to the queue, the agent finishes it, and the cost of the rework adds up in the same row.
Below are eight of the fourteen tasks the studio owner gave the agent in the first two days, translated from Russian. The task is as the owner wrote it, the result is a shortened version of the agent's report. Time is the agent's net working time, cost is from the meter in the studio's admin panel (AI work plus specialist oversight).
#55 · 28.09 · 13:20 → 13:23
“In ‘Payroll calculation’ keep only the staff who are on the schedule for the current day.”
Done: the list shows only staff with a shift on the chosen day, week or month. A note at the bottom says how many are hidden, with a “show all” link. 1 min 4 s · ₽117
#56 · 28.09 · 13:41 → 13:45
“On pressing ‘Complete sale’ the data is reset. The system asks to enter the service again.”
Done: the cause was a full room, and the explanation was hidden behind the window. The window no longer clears, and the reason is shown in red at the top. 1 min 41 s · ₽195
#57 · 28.09 · 13:58 → 14:01
“Add a button that goes to sales so we can sell products quickly.”
Done: a “Sell a product” button in the journal and in the booking window. The client from the booking fills in automatically. 53 s · ₽108
#58 · 28.09 · 14:01 → 14:03
“Add a ‘booking history’ button that shows all of the client's past bookings.”
Done: a button with the visit count on the booking card. It opens every past booking with its status, plus the client's visits from the old system. 1 min 26 s · ₽158
#64 · 29.09 · 14:09 → 14:10
“When dragging a booking with the mouse it should follow it, moving up and down visibly through time.”
Done: a copy of the booking follows the mouse in 5-minute steps and shows the new start–end time. It can also move into another trainer's column. 1 min 20 s · ₽97
#65 · 29.09 · 14:35 → 14:43
“Mark a trainer's non-working time in grey. And start the schedule not at 08:00 but when the staff start working.”
Done: hours outside the shift are hatched grey. The day grid starts with the first shift and ends with the last. 2 min 34 s · ₽149
#68 · 29.09 · 14:55 → 14:57
“Show every service and product that pay was accrued for, and how much for each.”
Done: a “What was accrued for” block: each service and product with date, price and the staff member's share, bonuses and penalties, with a total. 1 min 24 s · ₽156
#69 · 29.09 · 15:17 → 15:19
“When a booking is deleted the journal shouldn't scroll back to the start, and the calendar and day's finances should stay pinned.”
Done: the journal remembers the open time of day through any action and when switching days. The calendar and finances stay in place. 2 min 14 s · ₽187
For comparison: with a contractor each such change means a request, an estimate, a queue and at least one billed developer hour. Here the owner set 14 tasks in two days between other work and accepted them the same day.
The main fear — “what if it breaks everything” — is handled by how the process is built, not by trusting a neural network. The rules live in the system that launches the agent. The task text is data, not commands: writing “delete the database” in a task does nothing.
The developer agent didn't arrive in an empty room. Around the CRM runs the marketing our agents built and manage. It all lives in the same admin panel and can be improved through the same Change Center.
Direct: search, ad network, Maps. UTM tags on every campaign.
A form, the “Find your trainer” quiz or online booking. A notification in Telegram, MAX and email within seconds.
A booking in the CRM journal, a receipt, a card payment via an SMS link.
“Came” and “Paid” go to Metrica, and the bidding strategy learns from real sales.
You don't get “access to a neural network” — you get a trained developer on staff. It knows your code, your rules and your language. It lives in your admin panel and follows the rules we set up together.
| Stage | What we do |
|---|---|
| Project study | The agent studies the code of your website, admin panel or CRM. We work out how it's built and where the weak spots are. |
| Knowledge base | We load everything the company knows: rules, price lists, instructions, past specs, correspondence with developers. The agent understands why things are built the way they are. |
| Test copy | We set up a copy of the site where the agent edits and checks. The live site isn't touched until you accept. |
| Change Center | We build into your admin panel a task form with screenshots, statuses, time, tokens and cost, plus accept and rework buttons. |
| Rules and safety | What the agent may and may not do, backups, screen checks, rollback, per-task limits. |
| Staff training | We show how to phrase tasks and accept work, and record a video guide for new staff. |
| Support | Two weeks on call: we fine-tune the rules on your team's first real tasks. |
EXAMPLE: ALTERA SPORT FITNESS STUDIO CRM · 69 TASKS
Not for everyday changes. The owner and front desk set tasks in plain words. Complex decisions, architecture and large modules we take on as a separate project.
A change first lands on the test copy. A backup is made before deploying and screens are checked after. Not happy — “Send back”; something broke — rollback in a minute.
Any, as long as you have the source: PHP, WordPress, 1C-Bitrix, Laravel, Node.js, Python, static sites. We check the stack in a free review.
It depends on the scope. At the fitness studio a typical change costs ₽76–197. The table shows each task's cost: agent time, tokens used and the total.
Where it is now — on your server. The agent doesn't export the client base and can't see passwords or payment keys.
Usually 1–2 weeks: project study, test copy, Change Center, rules and team training. Then two weeks of support.
We start with a free review: we look at your website or system, tell you whether the agent fits and show what your Change Center will look like.
A trained developer agent in your admin panel: staff write a task, the agent does it in minutes, you accept the result.
I want this agent