Built by people who’ve seen both sides of this problem
One of us spent years deploying AI inside one of the world’s largest pharmaceutical companies. One of us spent years working alongside the practitioners who carry the caseloads. We started KnowledgePlane to close the gap between those two worlds.
Why this exists
Healthcare practitioners — SLPs, OTs, PTs, behavioral health therapists — spend a staggering amount of their professional lives on work that isn’t care. Documentation that follows them home. Billing processes that leak revenue quietly. Authorization deadlines that arrive without warning. Progress reports drafted from scratch because there’s no better system.
The AI infrastructure to fix this exists. Enterprise health systems and pharmaceutical companies have had it for years. Private therapy practices haven’t, because the tools are expensive, complex to configure, and built for organizations with IT departments — not for a three-person practice running on Google Workspace and good intentions.
We deploy that infrastructure into small practices. We configure it for the specific way each practice works. We maintain it. That’s the whole business.
Deployed, not self-serve
We configure and run your assistant. There’s no onboarding flow, no product evaluation, no new software to learn. A conversation with us, then it works.
Inside Google Workspace
Your practice already runs on Google Calendar, Drive, and Gmail. Your assistant connects to those directly — no data migration, no new login, no parallel system.
Purpose-built for each discipline
An SLP and an OT have different workflows, CPT codes, and documentation standards. We configure for your specific practice type — not a generic template with your name on it.
The team
Two founders. One builds the technology. One knows the clinical world. Neither of us thinks the problem gets solved by adding another tab to an EHR.
Dan Huston
Co-founder · EngineeringBuilt and deployed AI systems at Bristol Myers Squibb before starting KnowledgePlane. Designed the agent architecture, Google Workspace integration, and the clinical context engine that powers both Practice and School Therapy.
Andrew Huston
Co-founder · Clinical & GTMBrings deep familiarity with how therapy practices actually operate — where time gets lost, where billing breaks down, where the right tool changes someone’s day. Shapes what we build and who we build it with.
How we got here
The origin
Enterprise AI meets a gap in the market
Dan spent years building AI tooling inside Bristol Myers Squibb — agentic systems, workflow automation, context-aware assistants. The architecture worked. He saw that it hadn’t reached healthcare practitioners in private practice, where the need was just as real but the resources weren’t.
School Therapy
Building for school-based therapy teams first
Andrew brought a specific problem: school-based SLPs managing large caseloads under IDEA compliance with no good tools. We built a multi-provider platform for school therapy teams, and that work pushed the technology significantly further than any prior version.
Practice
Bringing the platform to private practices
The same architecture, reoriented toward private practice. Shorter sales cycles. Direct budget authority. ROI that’s immediately measurable. We’re deploying Practice with a small group of practices now, configuring and running it, and building from real usage data.
Want to be one of the first?
We’re taking on a small number of practices to deploy and configure Practice. If yours might be a fit, we’d like to hear about it.
Get in touch