Vol. I · No. 01 · Spring 2026 Columbus, Ohio Printed for operators, not procurement Pilot cohort opens Summer 2026
For IDD & home-care providers

Software for the ones who carry the care.

Enmantle unifies scheduling, EVV, ISP goals, billing, incidents, and learning in one system — designed from inside the work, by the people who've lived its daily weight.

Thank you. We'll be in touch as pilot seats open.

Pilot cohort opens Summer 2026 · Ohio providers first · No spam, ever

Ohio DODD
Sandata submission
Native, not bolted-on
Voice-first
Offline-tolerant mobile
Built for the field
Summer ′26
Pilot cohort opens
Ohio providers first
25–250
Staff · 5–40 clients
3–25 locations
§ 01 — the problem

The patchwork we replace.

Most IDD and home-care providers are running their agency on seven to twelve systems that don't talk to each other — legacy platforms written two decades ago, spreadsheets, shared inboxes, and a compliance binder. Every handoff between them is a tax on the people doing the work.

  • 01 Brittco Legacy DODD-focused ISP and incident workflow software. Dated interface, slow forms, no meaningful mobile. Replaced
  • 02 AxisCare / HHAeXchange Home-care scheduling, EVV, and billing, built for a different era. Dated UIs, heavy implementations, brittle integrations. Replaced
  • 03 Paper MARs and med binders Medication administration records on clipboards. No audit trail, no real-time escalation, no peace of mind. Replaced
  • 04 Google Sheets for scheduling The universal shadow system. Shared, fragile, impossible to audit, and the on-call manager's worst friend at 4 AM. Replaced
  • 05 QuickBooks-plus-exports for billing Hand-mapping service codes to cost centers every cycle. One wrong column and the claim bounces. Replaced
  • 06 LMS bought in a hurry A learning portal nobody logs into except the week before survey. Certifications drift, compliance drifts with them. Replaced
  • 07 A shared inbox named "incidents@" UI / MUI / Internal incident routing by forwarding. Nothing about this is survey-ready. Replaced
§ 02 — what it does

Four mantles. One platform.

Every feature in Enmantle lives inside one of four disciplines the field has been carrying for decades: the mantle of time, of care, of the business, and of the team. We didn't invent these — we just built the software that fits them.

01
§ Schedule

The mantle of time

Staff scheduling, shift swaps, GPS-stamped clock-ins, and native EVV submission to state aggregators. A calendar a DSP can operate from their pocket, not a training certificate.

  • Shift swap
  • GPS EVV
  • DODD / Sandata
  • Drive-time aware
  • Certifications-aware
02
§ Serve

The mantle of care

ISP goals, progress notes, medication tracking, incident reporting, and HPC tracking. Voice-first documentation and offline-tolerant mobile, because care doesn't pause for signal.

  • ISP goals
  • Voice notes
  • MAR
  • UI / MUI / Internal
  • Offline-first
03
§ Sustain

The mantle of the business

Billing across ADS, Transport, and HPC cost centers. Payroll calendar, expense approvals, bonuses, and a complete audit trail. Your agency's heartbeat on one screen instead of seven tabs.

  • Cost-center billing
  • Payroll calendar
  • Expenses
  • Audit logs
  • Exceptions inbox
04
§ Strengthen

The mantle of the team

Onboarding, learning and certifications, announcements, and secure WebAuthn identity. The HR backbone most providers have been stitching together with Google Forms and a prayer.

  • Onboarding
  • LMS
  • Certifications
  • Announcements
  • WebAuthn
§ 03 — a day in the work

From a 4 AM call-off to a closed week.

A single day inside an IDD agency touches almost every corner of Enmantle — and the work is easier when those corners know each other.

04:12Pre-dawn

A call-off comes in.

A DSP can't make the morning shift. Your on-call scheduler opens the app from bed and reassigns in under two minutes — with staff availability, certifications, and drive-time all surfaced inline. No spreadsheet. No group text. No panic.

07:00Morning

GPS clock-in. EVV handled.

Covering DSP arrives at the home and clocks in via GPS-stamped EVV. Sandata and DODD submission happen in the background, with service-code mapping done for you. The only person who has to think about EVV is the regulator reading your clean audit trail.

10:30Mid-morning

An ISP goal, logged by voice.

The DSP captures a progress note against an active ISP goal using voice-first capture. The form fills itself. If the device is offline, the note queues locally and syncs when it reconnects — the work comes first; the sync comes after.

14:45Afternoon

A minor incident, routed correctly.

A minor incident is filed from the mobile app. Routing rules escalate the correct form — UI, MUI, or Internal — to the correct reviewer without an email thread, with deadlines tracked and notifications sent.

Fri 16:00Week's end

Billing closes without a weekend.

The billing director runs the weekly close across ADS, Transport, and HPC cost centers. Exceptions surface with a reason, not a spreadsheet. Payroll flows to the calendar you already trust. The weekend is yours again.

§ 04 — versus

Why providers leave the incumbents.

Brittco, AxisCare, and HHAeXchange solved real problems for a previous era of this industry. But the field has moved — and the people doing the work need software that moves with them.

Capability Enmantle — designed in 2026 — Brittco AxisCare HHAeXchange
Voice-first mobile documentation ● Native — None — None — None
Offline-tolerant field app ● Yes, by default — Limited ◐ Partial ◐ Partial
Native DODD / Sandata EVV ● Built-in ◐ Integrated ● Yes ● Yes
Billing across ADS / Transport / HPC ● Unified ◐ Partial ◐ Home-care focus ◐ Home-care focus
Learning & certifications in-platform ● Included — Separate LMS — Separate LMS — Separate LMS
Data export, no fees, no lock-in ● Guaranteed ◐ On request ◐ On request ◐ On request
Built by operators & DSPs ● Yes — Software vendor — Software vendor — Software vendor

Comparison is based on publicly documented capabilities as of Spring 2026. We have deep respect for what these platforms built. Enmantle exists because the category is ready for a tool designed from inside the daily work — not retrofitted onto a decade-old stack.

Origin · An Essay 2 Kings · 2:13

The origin of the name.

In 2 Kings 2, the prophet Elijah is taken up in a whirlwind, and his mantle — the cloak that marked his calling — falls to the ground. Elisha picks it up. The mantle passes. The work continues.

To enmantle is the verb for what happens next: to be wrapped with the cloak, clothed with the authority, and equipped for the calling. It is what every person in this field already knows how to do — just without a name for it.

"And he took up the mantle of Elijah that fell from him, and went back, and stood by the bank of the Jordan." — 2 Kings 2:13

Every provider in this field has been enmantled for the work. The owner-operator who started with two DSPs and a used minivan. The executive director who stopped counting the Saturdays. The DSP who remembers a client's birthday when no one else does. They took up the cloak. They went back.

We build the software that makes the mantle fit.

§ 05 — made from the field up

Not drawn up by a software vendor who visited a few agencies.

Enmantle was designed from inside the work — alongside operators, directors, and DSPs who know what a 4 AM call-off feels like, what an MUI incident demands, and what it takes to close a billing cycle without losing a weekend.

The software reflects how the work actually happens, not how it looks from the outside. Every screen was sketched against a real week. Every workflow was argued about with someone who would have to use it on their phone while managing a household and a caseload.

That's why our mobile app is voice-first. That's why it's offline-tolerant. That's why the calendar doesn't require a training certificate to operate. That's why incidents route themselves and the billing close doesn't cost you a weekend.

Every one of those choices is what a software vendor doesn't think of when they've never run an agency. We have. That's the whole difference.

§ 06 — the pilot

Summer 2026. Ohio first.

The pilot cohort opens for mid-market Ohio IDD and home-care providers ready to move on from legacy systems. Every pilot agency gets hands-on migration and design-partner pricing.

Who the pilot is for.

Mid-market IDD and home-care providers: 25–250 staff, 5–40 clients, 3–25 locations. Waiver-funded work. Owner-operators, EDs, and compliance directors ready for a system that matches the ambition of their agency.

If you're running Brittco, AxisCare, HHAeXchange, or a stack of spreadsheets — you're exactly who we want to talk to.

  • Now Waitlist open Request early access; a real person gets back to you
  • Spring ′26 Design-partner interviews We map your actual workflow before we map software
  • Summer ′26 Pilot cohort begins — Ohio 2–4 week onboarding · parallel run · migration included
  • Late ′26 Expansion — PA, IN, KY, MI, TN, NC, GA, TX Prioritized by waiver volume and aggregator fit
§ 07 — frequently asked

Questions providers actually ask.

What is Enmantle?
Enmantle is an all-in-one software platform for agencies that serve people with intellectual and developmental disabilities (IDD) and home-care clients. It unifies scheduling, electronic visit verification, ISP goal tracking, incident reporting, billing, payroll, and staff learning in a single system.
Who is Enmantle built for?
Mid-market IDD and home-care providers with 25 to 250 staff, 5 to 40 clients, and 3 to 25 locations. Typical buyers are owner-operators, executive directors, and compliance directors at agencies serving waiver-funded clients.
How is Enmantle different from Brittco, AxisCare, or HHAeXchange?
Legacy platforms were built 10 to 20 years ago by software vendors, on aging technology stacks with form-heavy, slow interfaces. Enmantle is made from the field up — designed from inside the work by operators, directors, and DSPs who have lived it — so the software matches how caregivers actually work: voice-first documentation, offline-tolerant mobile, and a unified system instead of a dozen bolted-on tools.
Does Enmantle support Ohio DODD EVV and Sandata?
Yes. Enmantle is built to submit directly to Ohio Department of Developmental Disabilities (DODD) EVV aggregators including Sandata, with GPS-stamped clock-ins, service-code mapping, and automated error handling. Expansion to additional waiver states is on the roadmap.
Which waiver states will Enmantle support next?
After Ohio, Enmantle is prioritizing expansion into Pennsylvania, Indiana, Kentucky, Michigan, Tennessee, North Carolina, Georgia, and Texas. States are prioritized by waiver volume, EVV aggregator compatibility, and pilot-cohort interest.
How does Enmantle's pricing work?
Enmantle uses tier-based pricing that scales with your agency's size — number of clients, staff, and locations. Specific tiers and pilot-cohort pricing are shared during the design-partner conversation, not posted on a landing page. Pilot agencies receive design-partner pricing and migration support at no additional cost.
Does Enmantle work offline in the field?
Yes. The mobile app is offline-tolerant by default. DSPs can clock in, capture voice-first ISP notes, log medications, and file incident reports without signal. Data syncs automatically when the device reconnects, with conflict resolution handled on the server side.
Can we migrate our data from Brittco, AxisCare, or HHAeXchange?
Yes. Enmantle includes guided migration from the legacy systems most common in this category — staff rosters, client profiles, active ISP goals, certifications, and open billing cycles. Pilot agencies receive migration support directly from the Enmantle team at no additional cost.
Is Enmantle HIPAA compliant?
Yes. Enmantle is built on a HIPAA-aligned architecture with encryption in transit and at rest, role-based access control, WebAuthn identity, and full audit logs. Business Associate Agreements are available for pilot agencies.
How long does onboarding take?
Pilot onboarding is designed to take two to four weeks end-to-end, covering data migration, staff onboarding, EVV configuration, and a parallel-run period before you fully cut over from your prior system.
Who owns our data in Enmantle?
You do. Agency data remains the agency's property. Full CSV and audit-log exports are available on demand, with no export fees and no lock-in on termination.
When can I start using Enmantle?
The pilot cohort opens in Summer 2026, starting with Ohio IDD and home-care providers. Join the waitlist on enmantle.com to be notified when pilot seats open in your state.

— Final word —

The cloak is heavy. The platform isn't.

Join the waitlist. We'll be in touch as pilot seats open in your state.

Request early access