CoachBase
Coach. Manage. Grow.
A coaching app for personal trainers and their clients. Training programmes, meal plans, body measurements and messaging in one place — with health data protected at the database level.
Not in the app stores yet.
Key Features
Write programmes, track them day by day
Assign from a template or write one from scratch. A snapshot is taken the moment a programme is assigned — editing the template later never disturbs a client mid-programme.
A session screen that works in the gym
Set ticking runs against a local draft instead of waiting on the server, so every tap responds instantly even on a weak signal.
A 7,899-item food catalogue
106 curated Turkish entries plus 7,793 USDA records. Search a food and the macros fill themselves in; training-day and rest-day meal plans are written separately.
Read body composition reports from a photo
Photograph an InBody printout and get structured values back. Nothing is saved automatically — you review the preview and confirm it yourself.
Progress photos and measurements
Front, side and back pose timeline, plus height, weight, circumferences, body fat and muscle mass, visceral fat, BMI and basal metabolic rate.
Weekly check-ins and messaging
Sleep, stress, energy and notes, with trainer replies. This is where what the numbers do not say gets caught.
Document-verified trainers
Trainers upload a certificate, diploma and ID, and reach no client data until approved. That check is enforced in the database, not in the interface.
Export your data, delete your account
Both work for real — they are not decorative buttons.
Screenshots
Screenshots are coming soon.
What is CoachBase?
CoachBase is a mobile coaching app that puts personal trainers and their clients on the same data. The trainer writes programmes and follows progress; the client logs training, nutrition and measurements. Both look at the same table — with different permissions.
That distinction matters. CoachBase is not a fitness tracker, it is a coaching relationship app. Writing a calorie counter for one person is easy. Building a system where two people can look at the same health data, with different rights, safely, is hard — and that is where the weight of the product went.
For trainers: scattered tracking in one place
Most trainers today run programmes over WhatsApp, measurements in a notebook and nutrition through screenshots. That system collapses as the client count grows.
In CoachBase a trainer accepts clients, assigns programmes, writes meal plans, reviews measurement and photo history, and replies to weekly check-ins from one place. The dashboard shows client count, pending invitations, workouts completed this week and check-ins awaiting a reply at a glance.
There are two routes for programming: assigning from a template, or writing a custom programme day by day and exercise by exercise. When a programme is assigned a snapshot is taken — so even if the trainer later edits the template, the plan a client is currently working through does not shift under their feet.
For clients: walking into the gym knowing what to do
Opening the app, a client sees today's training day, weekly adherence and a summary of their latest measurements. Tapping start opens the session screen, where weight and reps go in per exercise and per set, and sets are ticked off as they are completed.
The design decision on that screen: set ticking runs against a local draft. Phone in hand, in the gym, on a weak signal, nothing waits on the server.
Against that, the server enforces a date lock: a training day can only be started on the day it was planned for. That rule lives in the database, so there is no way to poke at the app and mark past weeks as done. Adherence only means something on those terms.
Trainer verification: the product's most important decision
A system where anyone can claim to be a trainer and reach people's health data is a data-leak machine.
In CoachBase a trainer's account starts as pending. They upload a certificate, diploma and ID; the documents are held in private storage and reviewed by an administrator. Until approved, they reach no client data at all.
The critical part is where that check lives: in the database, not the interface. Every trainer action passes a database-level approval check, so bypassing the app screen and calling the API directly gets you nowhere.
AI does the boring job, not the coaching
A client picks up an InBody printout at the gym: body fat, muscle mass, visceral fat, basal metabolic rate, segmental analysis. Entering that by hand means 15–20 fields, which in practice nobody does.
In CoachBase you photograph the report, the values come back structured, and they are shown on screen as a preview. Three design decisions matter here:
- Nothing is saved automatically. Optical reading makes mistakes, and silently recording a wrong body fat percentage is not acceptable. The user confirms.
- It is optional. Skip it and your photo is never sent anywhere; you enter the values by hand.
- It is quota-limited. Every user has a bounded number of reads.
There is no "AI coach" here. Programming, nutrition advice and the decision stay with people. The AI only reads numbers off a piece of paper and types them into a form.
How health data is treated
The product idea is not novel — there are plenty of coaching apps. What separates this one is how the data is treated.
Most small apps handling health data do authorisation in the interface and leave the backend open. CoachBase does the opposite: whatever the screen says, the database holds the door.
- A client sees only their own data
- A trainer sees only the data of clients they are actively linked to
- Access ends the instant a relationship is archived
- An unapproved trainer reaches no client data at all
Photos sit in private storage and are served through short-lived signed links, so nobody can reach someone else's file. Session tokens live in the iOS Keychain or Android Keystore rather than in plain text, so a lost phone does not hand over a readable token.
Much of this model came out of a full security audit: 23 findings, 20 of them closed. Among them were serious gaps — trainer approval existing only in the interface, archived trainers keeping their access, and account deletion being absent entirely.
Who it is for
- Personal trainers hitting the limits of WhatsApp and spreadsheets as their client count grows
- Online coaches who never see their clients in person and therefore have to look at the data
- Coaches running training and nutrition together who would rather not juggle two tools
- Clients who want to walk into the gym knowing what to do, and to see their own progress
Where it stands today
CoachBase is in development. Working: authentication, invitations and referral codes, trainer document verification, measurements and report scanning, progress photos, programme templates and custom programmes, workout tracking, nutrition and the food catalogue, meal plans, weekly check-ins, real-time messaging, reminders, data export and account deletion, and the admin panel.
Still to come before release: binding legal texts, payments, two-factor authentication and remote error monitoring.
The app is not in the stores yet. Join the waitlist and you will hear first when it ships.
Frequently Asked Questions
- When will CoachBase launch?
- The app is in development. The core features work; what remains before release is finalising the legal texts and going through store review. Join the waitlist and you will hear the launch date first.
- How do I register as a trainer?
- After signing up you upload your certificate, diploma and ID. Once the documents are reviewed and approved, your trainer dashboard opens. Until then you have no access to any client data — that is the safeguard protecting clients' health information.
- How does a client connect to a trainer?
- Two ways. Your trainer sends an invitation to your email address and you register through the link, or you enter your trainer's permanent referral code during signup or afterwards.
- Can my trainer see all of my data?
- Your trainer sees your data only while actively linked to you. The moment you end the relationship their access stops — progress photos included. This rule is enforced at the database level, not in the app screen.
- Is the report scanning feature mandatory?
- No. If you do not use it your photo is never sent anywhere and you enter the values by hand. Even when you do use it, nothing is saved automatically — you have to review the preview and confirm.
- Where is my data stored?
- The database is in Frankfurt, inside the European Union. Photos are held in private storage and served only through short-lived signed links. Session tokens are kept in the iOS Keychain or Android Keystore rather than in plain text on the device.
- Can I delete my account and my data?
- Yes. You can permanently delete your account from inside the app, and export all of your data beforehand. If you cannot reach the app, the account deletion page explains how to request it.