Why I built TrainBase

I'm a gynecologic oncologist. A couple of years ago I noticed what onboarding actually cost my practice: every time someone new joined, we pulled our best medical assistant, Emily, away from patients for a full week of shadow training. Then she spent the next three months fielding the new hire's questions, usually while rooming a patient or chasing an authorization.

We tried the obvious fix first. We recorded her explaining things and saved the videos to a shared folder. Nobody ever opened it. When a new hire is stuck, she doesn't go digging through files and hoping one is labeled correctly. She asks a person, because a person answers the question she actually has.

So I built something that works the way she already works. Emily records each workflow once, while doing her job. A new hire asks the system what she would have asked Emily, and the answer that used to wait 40 minutes comes back in about 30 seconds, as step-by-step video, at whatever pace she needs, as many times as she needs it. Patient information is removed from every video before anyone sees it, because I would not run software in my own practice that handled that carelessly.

I built it for my practice. I'm offering it to practices like yours because the problem is everywhere, and the solution shouldn't require a software engineer to implement.