Build vs Buy: School Based Medicaid Claiming Software

Buy: the districts that should not consider building

Check one thing before anything else. Several state education agencies provide a claiming system to districts at no cost, and if yours does, that is the answer. Paying to build alongside a free state system is a governance conversation you will lose in front of a board.

Buy if you are under roughly 5,000 students or recovering less than about $300,000 a year. Frontline Medicaid Services and PCG EasyTrac both file claims competently, both carry state specific configurations, and both cost a fraction of any build. At that scale the money belongs in therapists rather than software, and a special education director who says so in a board meeting is right.

Buy if your billable services are concentrated. A district claiming mostly speech therapy delivered by employed speech language pathologists has one credential model, one service type and one prescription pattern. The complexity that drives a build comes from breadth: occupational therapy, physical therapy, nursing, counselling, personal care and specialised transportation each behave differently.

Buy if your compliance coordinator is confident in the current documentation. If a program integrity request would be uncomfortable but survivable, you have a process problem rather than a software problem, and process is cheaper to fix.

One vendor behaviour worth understanding. Claiming platforms are frequently priced as a percentage of recovered revenue rather than as a flat fee, which means your software cost scales with your success and a good year of claiming produces a bill nobody forecast. It also means the vendor's incentive is to maximise claims filed, which is not identical to your incentive, since you carry the recoupment risk. Ask for flat pricing as an alternative quote and compare both at your projected recovery.

When a district genuinely should build

The build case is about the join between systems, and it is a compliance case before it is a revenue case.

The first trigger is the prescription gap. An IEP says thirty minutes of direct speech therapy twice weekly, in a group of no more than three, in the special education setting. Your log says thirty minutes on Tuesday. Whether those agree is the entire compliance question, and nothing checks it at the moment the therapist taps save because the prescription lives in PowerSchool Special Programs, Frontline IEP, SEIS or Embrace while the log lives in the claiming vendor's portal. Custom software imports the prescription as a first class object and validates against it at the point of entry, which is the only moment fixing an error is cheap.

The second is consent and eligibility as dates. Under IDEA Part B at 34 CFR 300.154, one time written parental consent is required before a district first accesses a child's public benefits, with annual written notification thereafter. Eligibility moves monthly. A district storing either as a checkbox rather than as a dated span will bill services outside the covered period and repay them later with interest in the form of an extrapolated finding.

The third is contracted providers. Staffing agency therapists bring their own credential validity, supervision relationships and invoice reconciliation, which is a second data model most platforms handle poorly.

The fourth is unclaimed revenue. Sessions logged without a matching prescription line, providers with incomplete credential records, nursing services nobody realised were billable. A dashboard of billable but unclaimed services by campus and provider is usually where a CFO finds the money that funds the build.

Above roughly $1M of annual recovery with two or more of those, the arithmetic supports a build.

Costing a claiming platform against a build

Buying. Percentage of recovery pricing is common, so model it at your best year rather than your average. Add the labour you are already spending: the compliance coordinator's quarterly reconciliation between prescribed and delivered service, the chase for time study responses, and the consultant who rebuilds the cost report from raw exports every September. That consultant line is usually the largest hidden number in a district's claiming operation.

Building. A focused first release covering prescription linked logging with offline support, credential and consent enforcement, eligibility spans and claim file generation runs roughly $70,000 to $150,000 across 12 to 18 weeks. Adding time study administration, cost settlement support, denial management, audit packet generation and analytics takes the total to roughly $180,000 to $450,000 phased across 6 to 12 months.

Then the part districts systematically forget. You are now running a system holding student records with Medicaid retention obligations that run years past the date of service, which means hosting, patching, access logging and a named owner for as long as those records must exist. Budget 15 to 20 percent of build cost annually and confirm your technology department will accept the responsibility in writing, because a system orphaned by a superintendent transition becomes an audit problem rather than a maintenance problem.

The band moves with source system count. A district that consolidated two IEP platforms after a merger pays for two integrations, and states with unusual methodology add real scope.

Costs that never appear in a district proposal

Offline capability. Therapists work in hallways, portables and buses where connectivity is fiction. A build that assumes a signal will be abandoned by clinicians within a month, and abandonment is precisely what produces Friday afternoon reconstruction from memory, which is the single most common root cause of indefensible documentation. An offline queue with local validation is not an enhancement here, it is the requirement that makes everything else work.

Clinician adoption. Your therapists did not ask for new software and are already documenting for three audiences. Budget training, a genuine pilot with a small cohort, and a feedback loop that changes the app. Districts that impose a tool by memo get compliance theatre.

The 837P and 835 competence. Generating a professional claim file in your state's coding, modifiers and rate structure, then posting remittances and working denials, is a specific skill rather than general integration ability, and state portals are frequently unpleasant. Ask any developer which clearinghouse or state portal they have actually submitted to.

Time study response rates. A quarter with weak participation does not produce a smaller administrative claim, it can produce an invalid sample and no claim at all. Escalation to supervisors has to be designed in, not added after a bad quarter.

Records retention. FERPA obligations plus state Medicaid retention mean the system and its data must remain accessible for years, which constrains hosting decisions and vendor arrangements from day one.

Pull ten old claims and time the packet

Choose ten claims filed at least eighteen months ago, ideally across three service types and including one contracted provider. Then assemble what a program integrity reviewer would request, and time it.

• The IEP page prescribing the service, at the revision in force on the date of service.
• The session log with duration, group size and setting, plus evidence of when it was entered and whether it was later edited.
• Proof the provider held the required credential on that date, including supervision for any assistant.
• The written parental consent covering that date, the eligibility record for that month, and attendance showing the student was present.

Score it honestly. Ten complete packets inside a day means your process works and better tooling is optional. If any consent cannot be found, any log was entered days after the session without a visible edit trail, or any contracted provider's credential dates are unknown, you have measured your exposure. Remember that findings are extrapolated across the population rather than limited to the sample, so a small failure rate in ten claims is not a small number.

Take the same ten to any vendor demonstration and ask them to show the packet assembled from their system. Watch how many artifacts they cannot produce because they live elsewhere.

A district: the next four steps

First, confirm whether your state provides a claiming system at no cost, and confirm the current methodology in writing rather than from memory. State methodology changes more often than districts expect and a vendor configuration a year behind your reality is a real risk.

Second, run the ten claim audit above. It costs a compliance coordinator two days and produces the only evidence that will persuade a board either way.

Third, if you buy, ask for a flat fee quote alongside the percentage of recovery quote and compare both at your projected best year. Ask specifically how the platform reconciles prescribed against delivered service when the IEP lives in a different vendor's system.

Fourth, if you build, phase it: three highest volume service types and one campus cohort, running parallel with your existing vendor for a full quarter before switching anything. Keep your cost report consultant for methodology and stop paying consultant rates for data assembly.

On partner selection, ask them to whiteboard the difference between a prescription, a session log and a claim. Three objects with different lifecycles means they have done this. One table called services means they will learn it during your audit. Digital Heroes works PRD first, so consent modelling, credential rules and offline behaviour are written and approved by your special education and compliance leads before code exists. The team is 50 plus people across 2,000 plus delivered projects, holds Fiverr Vetted Pro status, and publishes to 2.5 million subscribers on YouTube. Contracting through an India LLP, US LLC or UK LTD keeps procurement and IP assignment under your own law.

Put the repository, the cloud accounts and the right to hire another firm into the contract before kickoff. Retention obligations outlast vendor relationships.

If you would rather someone argued with your brief than agreed with it, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You keep the specification either way.