THE ABA CLINIC PLATFORM

One platform for the clinic work that actually matters.

See what happened in care delivery, turn it into documentation, catch scheduling and authorization pressure, and give owners one operating view before problems become revenue loss.

Trusted operating signals

HIPAA architectureProtected data model
Audit trailsAction history intact
Role-based accessClinical and ops roles
Connected contextSessions, docs, scheduling

The ABA Clinic Platform

One system for the work that keeps clinics moving.

Owners need to see what happened in care delivery, what still needs documentation, where authorizations or staffing are getting tight, and which billing issues are starting to form. LenzABA brings those signals into one clinical operating view.

One place to see the session reality, documentation queue, scheduling pressure, and revenue risk before the next handoff is missed.

01SessionsSee what happened in care delivery while the details are still fresh enough to act on.
02DocsTurn session context into notes, BIPs, IPOCs, and treatment-plan work with review status intact.
03Scheduling + BillingCatch staffing gaps, authorization pressure, and billing risk before delivery becomes denied revenue.

THREE MODULES. ONE WORKFLOW.

Three operating surfaces. One owner view.

Sessions shows the care delivery reality. Docs turns that reality into reviewed clinical work. Scheduling carries the staffing, authorization, and billing pressure around it. Owners see the motion across all three without chasing status.

LenzABA Sessions
Capture session activity, review trends, and create the raw care-delivery context the rest of the platform builds from.
RBTsBCBAsLeaders
See Sessions
LenzABA Docs
Turn session trends, provider notes, and scheduling context into reviewed notes, BIPs, IPOCs, and treatment-plan work without manual reconstruction.
BCBAsClinical Leads
See Docs
LenzABA Scheduling
Manage staffing, coverage, authorizations, claims, and remits before operational drift turns into lost revenue.
AdminsOwnersBilling
See Scheduling

BUILT AROUND REAL ABA OPERATIONS

Care delivery moves fast. The operating view has to keep up.

Sessions happen. Documentation follows. Providers call out. Authorizations move. Owners need the pattern, the queue, the risk, and the next action without reconstructing the clinic from five tabs.

1

See what happened in care delivery.

RBTs capture the session reality as it happens. Supervisors see the signals before review day, not after a week of chasing updates.

2

Turn it into documentation.

Docs carries notes, BIPs, IPOCs, and treatment-plan work through one review queue with status and context intact.

3

Catch scheduling, authorization, and billing pressure.

Coverage gaps, expiring units, provider availability, claims, and remits surface before care delivery turns into denied revenue.

4

Give owners one operating view.

Clinical leaders and operators can compare care trends, documentation status, staffing risk, and revenue exposure from the same source of truth.

EXPLORE THE PLATFORM

Explore the platform by function.

Each module goes deep in its own area. Sessions captures care delivery, Docs owns formal documentation, and Scheduling handles staffing plus billing coordination. The platform works because those lanes no longer live in isolation.

LenzABA Sessions

Better visibility into session delivery, trends, and what is actually happening across care.

Move beyond raw collection and give supervisors and leadership a clearer view of clinical activity, patterns, and the session reality that later feeds Docs and Scheduling.

  • Session data capture
  • Graphing and review
  • Clinical visibility
  • Clearer insight across the care team
See Sessions
Sessions
Active session + capture controls
Live session running
Started
3:02 PM
Live counts
14
Session actions
Complete
OverviewTrialsFreqTimeABC
Response Correct
Prompt Gestural
Record Trial
LenzABA Docs

The intelligence layer that turns connected operations into clinical documentation.

Docs matters because it already has the session and scheduling context behind the document. This is where reviewed notes, BIPs, IPOCs, and treatment-plan workflows actually live.

  • BIPs and IPOCs from connected context
  • AI-assisted clinical drafting
  • Treatment-plan workflows
  • Faster BCBA review and approval
See Docs
Docs
Review queue + document status
2 pending reviews
Total
14
Pending
2
Approved
9
Revision
3
Status
Pending
Type
BIP + IPOC
Treatment plan updateMiloPending
Protocol reviewAveryApproved
IPOC revisionLucaRevision
LenzABA Scheduling

Staffing and scheduling should not run on spreadsheets and group texts.

See provider availability, coverage gaps, authorization limits, and billing-side follow-through in one place. No more piecing it together from three different systems.

  • Provider availability
  • Coverage shifts
  • Callout response
  • Authorization, billing, and supervision operations
See Scheduling
Scheduling
Revenue ops filters + KPI pressure
18 claims ready
Search provider or client
Milo Grant
From
Apr 1
To
Apr 22
Ready
18
Needs review
6
Blocked
3
Open Workbench
Open Export
Payer Rules

ADD THE AI ASSISTANT LAYER

Breathr connects to LenzABA and helps the clinic keep up.

Breathr is a separate add-on assistant layer for clinics that want help with parent communication, intake, admin coordination, alerts, and daily operational visibility. LenzABA gives the clinic the connected system. Breathr adds the communication and assistant layer on top.

Parent Communication

Web, voice, email, and messaging

Admin Assistant

Owner briefings and operator reminders

Intake Automation

Lead capture and qualification

Operational Briefings

Daily alerts and reminders

Parent
Hi, I wanted to check on my son's session schedule for next week?
Breathr
Marcus has three sessions next week: Tuesday 3pm, Wednesday 10am, and Friday 2pm. His Tuesday session moved from Monday due to a provider schedule change. Want me to send a calendar update?
See How Breathr Fits In

WHY THIS MODEL IS BETTER

Your clinic should not have to operate by translating between tools all day.

Disconnected systems create invisible tax: duplicate work, missed context, chasing people for updates, and constant uncertainty about what is actually happening across the clinic.

Operating tax
Chasing statusRe-entering contextLate revenue risk
One operating record

Disconnected stack

  • Work gets re-entered or repeated
  • Teams lose context between systems
  • Clinical and operational work drift apart
  • Issues get noticed late
  • Leaders spend too much time chasing status

LenzABA

  • Session data becomes draft context for Docs without re-entry
  • Supervisors see caseload status without asking for it
  • Scheduling and billing-side changes update clinical context in the same step
  • Nothing falls through the gap between "collected" and "acted on"
  • Leaders open one dashboard, not five tabs

SHOW THE WORK

Built around the friction ABA clinics deal with every week.

The proof is in the operating surfaces: session state, document review, authorization pressure, billing readiness, and target trends presented in the same language clinic leaders use to decide what needs attention.

Care deliverySession reality
Clinical recordReview queue
OperationsAuth pressure
RevenueBilling readiness
Session Pulse

Capture care delivery in the moment, then give supervisors the signals they need before review day.

Active session
Milo Grant
Functional Requests
Live session running
OverviewTrialsFreqTimeABC
Started 3:02 PM
Live counts 14
Record Trial
Session actions
Complete
Discard Session
Open ABC
ABC recording

Antecedent: transition demand. Behavior: refusal. Consequence: prompted return + token reset.

Document Reviews

Move BIPs, IPOCs, notes, and treatment-plan work through one queue with status and review context intact.

Total
14
Pending
2
Approved
9
Revision
3
Filters
Status
Pending
Type
BIP + IPOC
Treatment plan updateMilo GrantPending
Protocol reviewAvery HillApproved
IPOC revisionLuca ShawRevision
Revenue Ops Workbench

Catch authorization, staffing, and billing pressure before care delivery turns into denied revenue.

Provider or client
Milo Grant
Status
All Statuses
Workflow
All Workflows
From
Apr 1
To
Apr 22
Ready
18
Needs review
6
Blocked
3
Open Workbench
Open Export
Payer Rules
Target Progress

See phase changes, trend direction, and variability in the same view leaders use to decide what needs attention.

Target progress
Range 90dAim % OnZoom 1x
Phase change
Fade prompt
Level (current phase)
82%
Trend
Improving
Variability
Stable

SECURITY AND TRUST

Built for healthcare operations from day one.

The platform is designed around the kind of evidence owners, supervisors, and administrators need when care delivery, documentation, scheduling, and revenue decisions share context.

Review Security
01
HIPAA-compliant infrastructure

Built with healthcare compliance requirements from the architecture level.

Protected data model
02
Audit logging

Every significant action is recorded with full context for review.

Action history intact
03
Role-based access

Fine-grained permissions tied to clinical and operational roles.

Clinical and ops roles
04
Protected data

Clinical and operational data secured with encryption at rest and in transit.

Session, docs, scheduling context

FLEXIBLE PACKAGING

Choose the layer your clinic needs next.

Pro connects Sessions with Scheduling, including billing-side coordination. Platform adds Docs, the intelligence layer that turns operational context into clinical documentation.

Pro

$40/provider/mo

Run Sessions and Scheduling together so delivery, staffing, authorizations, and billing follow-through stop drifting apart.

Enterprise

Custom

Add API access, multi-clinic controls, and SLA-backed rollout support.

See Pricing

See how LenzABA would work in your clinic.

We will walk through your current workflow, show where the friction is, and map the right starting point for your team.

01Map your current workflow
02Find the pressure points
03Choose the right starting layer