Skip to content
Coach Sheet

Why Your Client Data Should Live in Your Drive, Not the Vendor's Cloud

When a coaching SaaS holds your client history, you're paying rent on your own work. Here's the argument working trainers gave us in our research, and what changes when the data lives in your Drive instead.

By Coach Sheet team · Software builders, not coaches Updated 1 source cited

TL;DR

When you cancel Trainerize, TrueCoach, HubFit, or Everfit, you lose access to your client history. Workouts, measurements, progress photos, all gated behind a subscription you no longer pay. Coach Sheet is built differently: your client data lives in your own Google Drive folder from day one. We host the menu bar, not the data. Cancel us, you keep everything.

What “data ownership” means concretely

Working coaches we interviewed brought this up consistently. Not as a philosophical concern but as a specific operational fear:

  • A client returns 18 months after their first program. The coach wants to see what they did last time. Data’s behind a paywall. Pay or restart from scratch.
  • The coach decides to switch tools. Migration support is patchy; the export is incomplete or formatted unhelpfully.
  • The vendor changes pricing or policy. The coach doesn’t agree but is stuck because moving 50 clients of history elsewhere takes weeks.

These aren’t hypotheticals. They were direct quotes from 28 trainer interviews we ran in late 2025.

How Coach Sheet handles this differently

Every Coach Sheet client file lives at:

[Your Google Drive]/Coaching/Clients/#1 ClientName/
                                      ├── Profile sheet
                                      ├── Workout Plan sheet
                                      ├── Lifting Records sheet
                                      ├── Measurements sheet
                                      └── Photos folder

This is your folder. Your Drive. The structure mirrors what working trainers (like the Bulgarian coach whose screenshot informed our design) build manually anyway. Coach Sheet adds a menu bar and automation on top of these files; it does not replace or remote-host them.

Cancel Coach Sheet at any time:

  • The Apps Script menu disappears
  • Save Week stops working
  • The client-facing PWA link expires (clients lose mobile access)

What stays:

  • Every spreadsheet, with all formulas intact
  • Every photo and measurement
  • Every workout history row
  • Editable in regular Google Sheets

You can keep coaching from raw Sheets if you want. You can re-subscribe later and pick up where you left off. You can export everything to CSV in 30 seconds. The data is structurally yours because it sits in your Drive, not because we’ve granted you a permission to it.

Why incumbents don’t do this

The cynical answer is lock-in. Vendor revenue depends on switching costs. If your client history is portable, you’re a flight risk every renewal.

The less cynical answer is product complexity. Building on a customer’s filesystem (Google Drive) constrains your architecture. Most coaching SaaS chose a hosted database for performance and control. Fair engineering trade-off, except the cost lands on the customer at cancellation time.

We made the opposite trade-off: accept the architectural constraints (Apps Script execution quotas, Sheets API rate limits, slightly slower load times) in exchange for an honest data ownership story. Some workflows aren’t possible with this model. Real-time multi-coach editing on the same client, for instance, runs into Sheets concurrency limits. We accept those gaps.

What this means for your coaching business

Three concrete implications:

Pricing power stays with you. When the next coaching SaaS doubles its prices, you’re not trapped. Cancel and your data’s already where it should be. We’ve priced Coach Sheet at $15 flat partly because we know you can leave cleanly; the price has to be defensible on its own merits, not on switching costs.

Long-tail client relationships are easier. A returning client from two years ago, your old program is right there in their folder. No paywall, no re-onboarding from scratch. The 18-month returnee is one of the highest-LTV client patterns in coaching; lock-in tools make this awkward.

You can extend the system yourself. Apps Script is open. If you want a custom report, a specific calculation, an integration with your CRM, you can write it. We ship the defaults; the ceiling is whatever you can write in Apps Script.

The practical migration story

Coaches switching from Trainerize/TrueCoach to Coach Sheet typically follow this pattern:

  1. Export from current vendor (CSV download, varies by vendor)
  2. Run Coach Sheet’s onboarding wizard for each client (3 minutes per)
  3. Paste imported workout history into the appropriate Workout Plan rows
  4. Start the next mesocycle in Coach Sheet, leave the old subscription active for 30 days as a backup
  5. Cancel the old subscription once you’re confident

For 50 clients, this is one Saturday afternoon. We have a migration guide for Trainerize specifically covering the export format mappings.

What we do host

To be transparent: we do host a few things on our servers.

  • The PWA client-facing app (the URL clients use to log workouts on mobile)
  • Authentication tokens for secure client URLs
  • Marketing website (this site)
  • Apps Script source code (you install it from us into your Drive)

None of these contain client coaching data. The PWA reads from your Drive in real-time when a client opens their workout; it doesn’t store a copy. The auth tokens are random strings, not personally identifying data.

If you cancel and want to verify nothing of yours stays on our servers, request a deletion email. We confirm token revocation in writing within 24 hours.

The argument in one sentence

Either your client data lives in your Drive (Coach Sheet) or in someone else’s database (everywhere else). The first arrangement gives you negotiating power forever. The second gives the vendor power forever.

Sources

  1. [1]