Anakut, or how to standardize a business that resists standardization

The context

Sarin is a sports and nutrition coach in Switzerland. His business doesn't fit any software on the market. He was running his entire operation by hand, and the bigger his client base grew, the more his improvised system cracked everywhere.

The real problems

• Clients booked without knowing when the coach was actually available, which created constant scheduling conflicts.
• Tracking payments was a nightmare: who paid, who didn't, which session, which package. Everything relied on memory and scattered notes.
• The core of the business wasn't managed anywhere: weight-loss tracking, personalized challenges, medical records. Yet that's exactly what makes a coach's value.
• A Swiss client handling health data must comply with the nLPD and the RGPD. There was nothing. It was a legal risk as much as an operational headache.

Our approach

We didn't start by coding. We started by understanding the coaching business: how Sarin really works, how he builds a challenge, how he tracks weight loss, where the implicit rules that no one had ever written down live. Standardizing a business like coaching is hard precisely because much of it sits in the practitioner's head. Our job was to challenge him, model his rules, and turn them into a coherent system.

What we built

A platform that manages his entire client base: the coach's real availability with booking aligned to it, payment and package tracking, weight-loss tracking and personalized challenges, medical records, all of it nLPD and RGPD compliant.

Stack: PHP, Laravel, Vue.js, n8n (automation)

The result

Sarin now manages his entire client base from a single platform. Since launch, his client base has grown by 25%.