A coach with an online course
Her buyers and her contacts were two different people in two different systems.
A Middle Tennessee coach sold an online course through one system and kept her contacts in another, so every buyer had to be entered twice and reconciled by hand. Her whole business now runs from one site over one database, where a student and a contact are one record. She signs in to her desk, builds the course in the same place, and her students sign in to their own side of it.
- The business
- A coach with an online course
- The job
- Her desk, her course workspace and her students, on one site
- What she owns
- The code, the database, and every record in it
She was the reconciliation step, and it ran on her memory
Her course lived in one platform, her contacts lived in another, and the two had never spoken. Someone bought a seat, the course platform knew about it, and her contact list did not. So she opened both, found the new name in one, and typed it into the other.
That works while the numbers are small. It is the kind of task that never announces itself as a problem, because every single instance of it takes ninety seconds.
The question she could not answer without opening two windows
Someone emails asking how far along they are in the course. Answering that means the course platform, for progress, and the contact list, for who they are and what they last talked about.
Two windows, two searches, and a quiet hope that the name is spelled the same way in both.
Every list she pulled was a guess at how well she had kept up. There was no way to ask her own business a question and trust the answer.
The decision that shaped it
One site, two faces, and two front doors that never meet.
The obvious build is a course platform bolted onto a CRM with something syncing between them. Every sync is a thing that drifts, and the day it drifts quietly is the day she stops trusting both of them.
So the site was built with one database underneath and two completely separate ways in. Her side is hers: the desk, the contacts, the course workspace. Her students get their own door into their own pages, with their own sign-in, and the two sessions never touch each other.
That single choice is why a buyer and a contact are the same record now. Nothing syncs, because nothing was ever apart.
What she signs in to now
- Her desk
- Her contacts, her day and her business on one screen. The same place she already worked, with the course sitting inside it instead of beside it.
- The course workspace
- She builds the course herself. Weeks and days, video uploaded straight in, worksheets attached to the day they belong to, a schedule, and a publish button. No developer sits between her and her own material.
- Who has gone quiet
- The screen tells her who joined, how far each person has gotten, and who has stopped opening it. That last one is the whole reason to have the data in the first place.
- Her students, on their own side
- They sign in, see the days that have opened for them, and work through it. Days that have not been released yet show the date they will be, so nobody has to ask.
She stopped being the thing holding it together
She adds nobody by hand. A person who buys is a person in her contacts, immediately, because they were never two records.
Before it went live it was signed into as a real student to check the honest version: six days after enrolling, seven of the twenty days were open and the rest showed the dates they unlock. That was confirmed underneath at the database level too, so the release gate actually refuses the days it says it refuses.
Can a course platform and a CRM be the same system?
Yes, and for a business run by one person it usually should be. The alternative is two products with a sync between them, and a sync is a moving part that fails quietly.
The build that works is one database with two sign-ins on top: the owner on one side, her customers on the other.
Her customer record and her student record become the same row, so progress, purchase history and contact history are one question instead of three.
She paid once, and the code is hers.
It is an asset her business holds, the same way it holds a van or a building. Nobody can end it by raising a price or going out of business, and that is the whole point of building it this way.
Tell me what yours is