How a Ho Chi Minh City strength and rehab coach got one system for the whole business, from the first click on the website to the last rep of the session, in 20 days

Parkes Performance Coaching is a strength, athletic-performance and injury-rehab practice in Ho Chi Minh City, run by Justin Parkes. Until October 2026 it ran on a Wix site, a Google Form, spreadsheets and chat threads. Edge8 replaced all of it with one platform on one database: a public website with a lead-scoring audit, an admin for the business, a coach hub for the training floor, and the PPC Lab, a portal for every student. The first commit was 7 October. Students were training on it by the week of 19 October.

Before the build, the work lived everywhere. Prospects filled in a Google Form. Programmes lived in spreadsheets the client never saw. Session feedback went into chat threads. Progress lived in the coach's head. Nothing connected the website to the intake, the intake to the programme, or the programme to what actually happened in the session.

That is the normal state of a small coaching business, and it caps growth at the owner's memory. Every new coach has to be told the history. Every student who asks "how am I doing?" gets an answer from recall, not record.

PPC had the harder version of the problem: half its clients are rehab cases. Health screening, movement assessment and consent are not optional paperwork, they are the product. The system had to hold health data properly or not at all.

“A coaching business is the purest shape of a Company OS. One person's judgement, applied to a few dozen people, one session at a time. If the system can hold that judgement and hand it back to the coach at the right moment, the coach gets to coach.”

Dave Hajdu, founder, Edge8

No course and no retreat. The coaches learned the system by approving its drafts.

Justin's team did not get a tool and a manual. They got a working system with the AI already inside it, and one rule: nothing reaches a student until a coach says so. Every AI draft sits in a review queue. The coach edits, approves or rewrites, and the record keeps who did what. Three weeks in, the review queue is the training.

1. A front door that qualifies. The new site keeps PPC's black-and-white look. Its main call to action is the Eligibility Audit: five movement questions, sixty seconds, a score. Every result lands in the admin inbox as a lead, with an AI qualifier reading the answers before a human does.
2. Intake that creates the account. A six-step mobile intake captures goals, health history, experience and availability, records versioned consents, and creates the student's portal login on the spot. The Google Form is gone.
3. An admin for the business. Students, coaches, intakes, coach load, inquiries, blog, newsletter and billing in one place. Assigning a coach is one click. A student can have several coaches; each coach sees only their own students.
4. A shared exercise library. 168 exercises, each with difficulty, coaching cues, measurement type and progression rules, organised by movement pattern and session phase. Every plan is built from it.
5. The session loop. Each session owns its plan. A coach builds it by hand or presses Draft with AI, which builds on what was logged last time while progression rules set what is allowed. It never sees the student's name or health history. Every Saturday evening a drafter prepares the coming week. On the floor the coach moves through prep, live session and a one-pass review of sets, effort and notes. On the gym TV the session becomes a full-screen slideshow.
6. The PPC Lab. Each student's home shows the next session, how to get ready, a readiness check, this week's consistency, focus areas with real progress, and tips from their coach. A biometrics hub reads InBody reports, imports WHOOP recovery and sleep, and tracks weight. Session Zero turns the first assessment into a report: video analysis of squat, hinge, push, pull and trunk, each with findings and one focus.
7. Operations and marketing, built in. Packages, billing plans and VAT invoices with PDFs and online signing. A team workboard, time off and expense claims. A blog with SEO, a double opt-in newsletter, broadcasts and a welcome series written in Justin's voice. A monthly recap reports what worked. Ten scheduled jobs run all of it.
8. A coach assistant and a locked health tier. Justin can ask the database in plain English. The assistant can only read, never write, and it cannot see health records at all. Health data sits in its own tier, every read is audited, and files open through short-lived links.

• One record per student instead of four. Website, intake, programme and session history share one database. A new coach reads the history; nobody has to tell it.
• Plans are drafted, not typed. 75 of the 90 exercise prescriptions in the live plans started as an AI draft. Coaches edit and approve; they no longer start from a blank spreadsheet.
• Assessment became a product. 7 Session Zero reports with 14 analysed movement patterns, delivered to the student's portal with video, instead of a verbal debrief.
• The business runs on a schedule. 10 automated jobs, from plan drafts and prep emails to billing renewals and the monthly recap, have run 5,396 times since launch.
• Health data has rules. Versioned consents at intake, a separate health tier, 2,629 audited reads, and an AI assistant that is structurally unable to see it.
• Twenty days. 173 pull requests, 44 database migrations and 143 pages, from an empty repository to students training. 52 million fresh agent tokens against about 30 human hours: the tokens did the volume, the humans did the judgment.

• Where the human sits: why escalation beats approval
• Single source of truth for my company: one database first
• AI Program vs AI Tool: what founders get wrong
• How long does it take to build software with AI? 100 hours

This runs on the same Company OS we install for clients. If you want the people who built it inside your company, talk to us about the roles you actually need.