Built from the work
behind the transition.
Five years inside behavioral health — case manager first, then a director role — followed by building a tool around the operational gaps that kept repeating. This is where Teryli came from, in the founder’s own words.
The work mattered. The tools around it didn't keep up.
The origin
I spent five years inside behavioral health, first as a case manager, later in a director role. Across teams, I kept seeing transition work scattered across spreadsheets, inboxes, text threads, contact lists, EHR task queues, and memory. Teryli grew from trying to give that operational work a clearer place to live.
Both sides of the same problem
As a case manager, I built my own systems just to stay organized: tracking aftercare plans, program contacts, referral options, write-ups, follow-ups, and due dates so nothing slipped while I focused on the people in front of me.
So nothing slipped · His first pipeline
And somehow, becoming the reminder system.
When I moved into leadership, the problem multiplied. Supporting a team meant weekly one-on-ones, reviewing caseloads, helping staff ask the right questions in their meetings — and becoming the reminder system. Your note is due. The follow-up call is this week. The thirty-day review is coming up. Somehow while keeping visibility across all of it.
There has to be a better way to keep this work current, visible, and consistent.
And the same question kept coming back.
Owner · Due · Visible to the team
Five years isn’t a lifetime. It was enough to see the pattern.
Built close to the work
I worked the handoff from more than one role: first carrying the follow-up myself, then helping a team stay current across cases, programs, and deadlines. That gave me a practical view of where good work gets harder than it should.
The honest limitI’m not claiming a lifetime of authority or that software can solve placement judgment. I am claiming direct experience with the operational gap, and a responsibility to build around it honestly.
“Program criteria, referral status, ownership, and follow-up still scatter across systems and memory. The next step should stay visible after the call ends.”
What the name means.
People ask what Teryli means. It’s a coined name — you won’t find it in a dictionary. It stands for the thing I kept reaching for and never had: one place where operational transition work stays current, due follow-up stays visible, and the people doing the work and the people leading it can review the same recorded picture.
The product comes from those years: what it tracks, what it surfaces, and the boundaries it needs to keep. Built by someone who did the work, for the people still doing it.
A coined name · The thing the field kept reaching for
The call ends. The next step should not disappear.
Bring a de-identified workflow. We will show where the operational handoff may fit; do not send PHI or client details.