Skip to content
Work

Systems we have shipped with operators.

Each study is the operational problem, the system intervention, the verified result, and the business implication. Numbers appear only when an operator's sourced data backs them, none are published here yet, so none are shown.

Counted from this site, not claimed

0
Solution areas
Each with a page and a diagram
0
Live products
3 in the library
0
Case studies
Problem, system, result, implication
0
Operators listed
Building alongside
0
Workflow stages
Referral source to CRM/EHR sync
0
Engagement phases
Audit to scale
Case 01 / 05
Referral CRM · Census
BedFlow, product site preview
  1. 01 · Operational problem

    Small-to-midsize treatment centers were running referral pipelines on spreadsheets. The EHR was the only “system,” and it was the wrong tool for business development, partner tracking, and openings.

  2. 02 · System intervention

    A specialized referral-partner CRM with pipeline stages, partner records, and authorization tracking designed around treatment BD, not a generic sales CRM and not an EHR clone.

    Scope. Product strategy, referral workflow design, brand and marketing site, partner onboarding, and the operational data model for referrals and openings.

  3. 03 · Verified result

    BedFlow is live as the operational layer for referral partners, pipeline, and related capacity tracking. It is a working product, not a slide. Individual operator results depend on adoption and program mix; we do not publish blended conversion claims.

  4. 04 · Business implication

    Referral relationships and bed availability stop depending on one person’s spreadsheet. BD, admissions, and leadership work from the same record, which is the precondition for adding a program without adding chaos.

Process
  1. 01Mapped how BD and admissions actually tracked partners and beds
  2. 02Designed a data model that could hold partners, inquiries, and capacity
  3. 03Built the product around daily BD use, not a demo script
  4. 04Shipped the marketing site and onboarding around the same system
Case 02 / 05
Alumni operations
Afterflow, product site preview
  1. 01 · Operational problem

    Alumni contact after discharge was typically a coordinator’s list, a mass email tool, and good intentions. Milestones were missed. Ownership disappeared when staff turned over.

  2. 02 · System intervention

    An alumni operating system: records, follow-up cadence, and activity that a program can run after discharge.

    Scope. Workflow design for alumni and aftercare operations, product implementation, and the operating cadence around contact and milestones.

  3. 03 · Verified result

    Afterflow is live. It gives alumni work a system of record. It does not replace clinical aftercare, and it does not produce outcomes by sitting unused.

  4. 04 · Business implication

    Post-discharge follow-up survives staff turnover, and step-down or re-engagement conversations start from a record instead of a memory.

Process
  1. 01Documented how alumni work actually happened after discharge
  2. 02Defined records, milestones, and owners
  3. 03Built the product around follow-up, not a community feed
  4. 04Launched as a live system for programs that will staff the work
Case 03 / 05
Recovery housing · Census
Roll Call, product site preview
  1. 01 · Operational problem

    Sober living and recovery housing ran occupancy, check-ins, chores, and incidents across group chats and whiteboards. Morning standup reconstructed yesterday.

  2. 02 · System intervention

    A house-management and occupancy tool: census, resident movement, and daily operations in one record, built with operators who run the day in the app.

    Scope. Operations design for multi-house recovery living, census views, resident logs, and role-based access.

  3. 03 · Verified result

    Roll Call runs with recovery-housing operators. It is not presented here as a broadly sold platform. Fit is determined in a conversation, then a guided onboarding.

  4. 04 · Business implication

    Occupancy becomes a live number rather than a morning reconstruction, which is what makes house-level census usable for bed availability upstream.

Process
  1. 01Sat with house managers on the actual morning routine
  2. 02Designed occupancy and logs around that routine
  3. 03Built mobile-first so the floor can use it
  4. 04Onboarded operators who run the day in the app
Case 04 / 05
Directory · Family navigation

Trusted Treatment Navigator

trustedtreatmentnav.com
Trusted Treatment Navigator, product site preview
  1. 01 · Operational problem

    Families searching for treatment had no reliable way to separate verified providers from directories where visibility is purchased.

  2. 02 · System intervention

    An independent directory built on a verification-oriented ranking model, with provider profiles and a family-facing intake path that does not behave like a lead mill.

    Scope. Directory strategy, verification framework, brand positioning, provider onboarding, and the public site.

  3. 03 · Verified result

    The directory is live. It is infrastructure for ethical discovery, not a paid-admissions engine, and not a claim about clinical quality we cannot independently audit for every listing.

  4. 04 · Business implication

    Family-facing acquisition can be built on verification rather than purchased rank, and the inquiry path can hand off into an admissions workflow instead of a lead mill.

Process
  1. 01Defined what “verified” had to mean in practice
  2. 02Designed ranking that is not pay-to-play
  3. 03Built provider onboarding and profiles
  4. 04Launched a public navigation experience for families
Case 05 / 05
Veteran peer support

Foxhole Forum

foxholevets.com
Foxhole Forum, product site preview
  1. 01 · Operational problem

    Veterans navigating PTSD, addiction recovery, and transition often fall into silence between appointments and while waiting on VA resources. Existing forums and social spaces were not anonymous enough, not moderated for recovery, and not designed around the specific trust dynamics of military service.

  2. 02 · System intervention

    A private, anonymous peer-support community built for veterans: secure onboarding, moderated spaces, crisis escalation, and a brand experience that communicates safety without clinical pretense.

    Scope. Platform strategy, community architecture, anonymity and safety design, brand and marketing site, and moderation workflow.

  3. 03 · Verified result

    Foxhole Forum is live as a free, anonymous community. It is peer support, not clinical care, and it does not replace treatment. It creates a place veterans can enter before they are ready for formal services.

  4. 04 · Business implication

    Peer support can be infrastructure, not an afterthought. For operators and funders serving veterans, it fills the gap between crisis and intake and gives the community a moderated alternative to open social platforms.

Process
  1. 01Mapped the moments when veterans stop talking: waitlists, nights between appointments, early transition
  2. 02Designed anonymity and moderation rules around recovery-sensitive peer support
  3. 03Built the public site and community entry flow to signal safety before signup
  4. 04Integrated crisis resources and escalation paths as part of the system, not an afterthought

Products in the library

Status is labelled. Live products have pages. In-production tools are not sold as available software.

In production

AdmitIQ

Conversion visibility for admissions teams, where inquiries stall between first contact and the bed. In production; not offered as a public product yet.

In production

AuthIQ

Authorization and UR workflow support so clinical documentation and payer decisions are not trapped in a side process. In production.

In production

ClearBill

A focused authorization tracker for due dates, denials, and next steps. In production.

In production

Cadence

Outreach cadence, accounts, and activity for behavioral health BD teams. In production.

In production

First Call

Scenario practice for the first family conversation. In production.

In production

Dayflow

A daily operations view for teams that need today, tomorrow, and this week in one place. Early access; not a public product page yet.

Next step

Want a system like this for your operation?