The business behind the build.
This client is a leadership coaching company we keep unnamed. Its back office lived in six separate places that didn't talk to each other: scheduling, client files, Zoom session transcripts, email follow-ups, an ICF hour log, and the bookkeeping. The founder was the thing holding all six together by hand. We built one private system that connected them. The clients never logged into anything. They kept getting normal emails from their coach.
The work around the work.
The company ran on six separate back-office systems that never talked to each other: scheduling, client file storage, Zoom transcripts, email follow-ups, the ICF hour log, and the bookkeeping. Each one did its own job fine. Nothing tied them together except the founder.
So the founder was the integration layer. Every session left a trail behind it: a transcript to deal with, a follow-up to write, files to put away, hours to log, books to keep current. That trail got longer with every client, and it piled up fast.
One rule mattered as much as any feature. Clients could never be asked to adopt a portal, an app, or a login. Whatever we built had to be operator-only and invisible from their side. They kept getting normal emails, and everything else happened behind the scenes.
Six systems, zero connections
Scheduling, file storage, transcripts, follow-ups, the ICF hour log, and the bookkeeping each sat in its own place. Keeping them in sync was a manual job that landed entirely on the founder.
Admin that multiplied with every client
Every session spun off its own trail of work: transcript, follow-up, filing, hour logging, bookkeeping. Across the client roster, that trail kept growing.
Clients who should never see software
The company's clients couldn't be asked to log into a portal or learn a tool. The system had to be operator-only and invisible, so all a client ever saw was a normal email.
A system around the way they work.
We built one system the founder ran alone. It plugged into the tools the company already had instead of replacing them, and the rule the whole way through was that clients never see any of it. Here's what it connected.
Built on the scheduling tool they already used
No new calendar to learn. The existing scheduler stayed the front door, and a booking there set the rest of the system in motion.
Zoom transcripts pulled in on their own
Each recorded session's transcript came into the system with no manual export or paste, ready to become a follow-up.
Session notes filed in Dropbox
Each session's summary was saved as a document in that client's Sessions folder in Dropbox, instead of being filed by hand.
Follow-ups that read like a normal email
Clients got an ordinary email from their coach. No portal, no login, no attachment to fetch from some system. That was the entire point of building it operator-only.
An ICF hour log in her own spreadsheet
Sessions went into the ICF spreadsheet she already kept, and the system back-filled 44 past sessions into it.
Bookkeeping from her bank statements
She uploaded a bank or card statement. Claude sorted each line into her chart of accounts, and the system made a profit and loss report for her accountant.
One operator, nothing client-facing
The founder ran the whole thing alone, and it stayed private to the business. From a client's side there was no software at all.
More room for the coaching.
The client workflows came together in one connected system. Six back-office functions ran through one private system with a single operator, and from the client side nothing changed. No portal, no app, no login. Just normal emails from their coach.
back-office tools connected through one system
logins clients ever needed