What Residential Treatment Software Actually Costs

You asked three vendors what their software costs. You got three versions of the same answer: it depends on your program, let's set up a call. Then you sat through the call and got a number that turned out to be the monthly licence fee and nothing else.

Part of that is sales technique. Part of it is honest, because the price really does depend on how big your agency is and what you turn on. But the deeper problem is that the licence fee is the smallest predictable piece of what you will actually spend. The rest lives in setup, migration, transaction fees, staff hours, and what happens at renewal. Nobody puts those on a pricing page, including us.

So instead of a number, here is the framework. Fill it in with your own invoices and the answers you get in writing, and you will have a total you can defend to a board.

Start with what you already pay, not what the new thing costs

Before you evaluate anything, pull twelve months of invoices and sort them into categories. Most residential programs are paying separately for some version of this list:

• Charting and clinical records
• Billing, and often a clearinghouse on top of it
• HR and payroll
• Scheduling and time tracking
• Required training and certification tracking
• Electronic signatures
• Internal chat, help desk, document storage

Add them up. That total, not the licence line on any one of them, is the number you are actually comparing against. It is also the number most directors have never assembled, because the invoices arrive in different months from different departments and nobody owns the whole picture.

Consolidation is the entire argument for software built for residential treatment rather than eight products stitched together. If a vendor replaces four of your seven categories, subtract those four before you compare. If it replaces none of them, you are adding a line item, not trading one.

Per-claim and per-transaction fees

This is where quotes drift furthest from reality. Ask directly, and ask for it in writing, whether the vendor charges per claim submitted, per claim rejected and resubmitted, per statement mailed, per text or email reminder, per e-signature envelope, per user seat, or per bed.

Each of those has the same structural problem. The fee scales with the activity you are trying to increase. A month where you filled beds and billed hard is a month where your software bill goes up. A month where you had to rebill a payer three times costs you three times. You cannot forecast it, and you cannot cut it without cutting the work.

The other thing to check is the floor. Some contracts carry a transaction minimum, which means a slow census does not lower the bill but a busy one raises it.

Implementation and configuration

Every serious system has a one-time setup cost. That is not a red flag. Being vague about what it covers is.

Get specific about what setup includes: your forms, your wording, your workflows, your user roles and permissions, your program structure. A residential program does not document like a clinic. If the vendor's setup means switching on a generic template and handing you a login, you will pay for the difference later in workarounds, or in change orders every time you need a form altered.

Ask what happens six months in when the state changes a form or you open a new unit. Is configuring the system to how your program actually runs part of the relationship, or is it billable professional services at an hourly rate you have not been quoted?

Data migration, and the cost of the system you are leaving

Migration is the line item most often quoted at zero and delivered as a headache. Pin down four things.

What actually comes across: full charts, or demographics and open episodes only. What format the rest arrives in, because a folder of PDFs is not the same as searchable records. What you have to keep the old system running for, and what that read-only access costs per month once you are no longer using it. And whether your data comes back out cleanly if you leave, in a format someone else can load.

That last one is a real cost even if you never use it. A vendor who will not commit to a clean export in writing has priced your exit into your renewal, whether or not either of you says so out loud. The same conversation should cover where the data lives and who can see it, which is a HIPAA and audit-log question as much as a pricing one.

Training time is real money, it just does not arrive as an invoice

Count it as staff hours, because that is what it is. Direct care staff, supervisors, nurses, billing, HR. Every person who touches the system, times the hours of training, times what you pay them. Overnight shift has to be trained too, and usually on overtime or a coverage shuffle.

Then count it again for next year. Residential programs turn over direct care staff. Training is not a go-live event, it is a permanent monthly cost of every system you run. Ask whether new-hire training is included forever or only during onboarding, and whether it is live sessions you have to schedule or something a supervisor can assign the week someone starts.

The number of separate systems matters here more than anything. Training a new house parent on one platform is a different cost than training them on five.

Duplicate entry is a bill you pay every day and never see

If two systems do not talk, someone types the same thing twice. That is a recurring cost with no invoice attached, and over a year it is usually larger than the licence fee that caused it.

Look for it in the obvious places. A clinical note written in one system and re-keyed into billing. A schedule built in one place and hours entered somewhere else for payroll. Incident data compiled by hand for a monthly report because it lives in three systems. Ask staff where they retype things. They will tell you immediately, because they hate it.

Then ask what real integration costs. Interface fees are often quoted per connection, per year, plus a build charge, and they are the one line item vendors are most willing to discuss only after you have signed. Billing that generates itself from the note, or one calendar across every unit, removes that cost rather than pricing it. That is the practical difference between a platform and a record system with things bolted onto it.

What renewal looks like

The first-year price is a sales price. The renewal is the price. Before you sign, get answers to these:

• How long is the initial term, and what is the notice period to not renew
• Is there an annual increase built into the contract, and is it capped
• What does it cost to add a facility, a program, or a unit mid-term
• Are support and updates included, or do they become a separate line later
• What is repriced at renewal, and on what basis

A contract that raises your rate every year on a base that grows with your census compounds twice. Model three years, not one.

Flat agency pricing versus per-claim pricing

These are two different models, and the difference is not really about which is cheaper this month. It is about what the bill tracks.

Per-claim and per-transaction pricing tracks your activity. Your cost rises with volume, with rebills, with statements sent, with messages. You cannot forecast it in a budget, and the vendor's revenue grows when your billing work grows.

Flat per-agency pricing tracks the size of your agency, not your activity. You pay one bill for the whole agency, set by your total active census across every home and program. It does not change when you hire staff, bill harder, or have a heavy documentation month. That is how Kordera prices: one flat bill for the whole agency, no per-claim, per-statement, or per-message fees, plus a one-time setup to configure the platform to your agency and get your records in.

To compare the two fairly, do not compare monthly rates. Build a three-year total for each. Year one is licence plus setup plus migration plus training hours plus any interface build. Years two and three are licence plus estimated transaction fees at your real claim volume, plus duplicate-entry hours, plus the contractual increase. If a per-claim quote wins on a slow year and loses on a good one, you have learned something about which risk you are buying.

None of this gets you a price. It gets you a list of questions that any vendor should be willing to answer in writing before you sign, and a total you built yourself instead of one that was presented to you.

If it is useful, bring your current invoices to a one-hour demo and we will go through the categories against what you are already paying. If the math does not work for your program, that is a fine outcome and you will still leave with the framework.