Home / AI for Nonprofits / Choosing case management and human-services software

Choosing case management and human-services software

Direct answer. Buying case software because a demo looked modern is how nonprofits pause the work they already owe funders. I run an independent shortlist process: requirements from real workflows, privacy review on every vendor, reference calls you control, and a decision memo leadership can defend. Vendors do not pay me for placement. I do not resell licenses. Field staff sit on demos because they know which three clicks break on Fridays. Finance sees seat math before the steering vote.

Written by Justin Ingram, healthcare AI consultant. Reviewed November 9, 2026.

Administrative and operational AI only. Not a clinical tool. A person reviews the work.

Requirements before demos

We write must have workflows: intake, referral, documentation, billing export, and reporting. Nice to have waits until must have is testable.

AI features are a line item, not the reason you buy. If the base record is unusable, smart summaries will not save you.

Privacy and agreements on the shortlist

Every finalist must answer how client data is used for model training, where it is stored, and whether they sign your agreement. I score answers, not slogans.

Counsel reviews before you sign. I document gaps for the board.

Reference calls that matter

You talk to peers with similar funding mix and site count. I send questions in advance. Vendors do not join those calls.

We ask what broke in the first ninety days, not only what they like.

Proof of concept with real tasks

The POC script follows one intake, one referral close, one note, and one export finance needs. Staff timebox the test.

Fail the vendor when required steps need a spreadsheet sidecar.

Implementation and migration risk

Data migration, form rebuild, and training cost more than licenses. I include them in the memo. Parallel run beats big bang when clients are mid service.

AI add ons wait until core workflows are stable unless counsel says otherwise.

Decision memo for leadership

The memo names the winner, the runner up, risks, and what you are not buying yet. Boards get plain language, not a feature matrix only IT reads.

I stay through contract language review if you want a second pair of eyes on operational clauses.

Cost models beyond license lines

I include interface fees, storage tiers, sandbox refresh, and per site charges vendors hide in footnotes. Finance signs the five year view, not only year one teaser pricing.

If the model depends on usage you cannot predict, the memo says so plainly.

Exit and data portability

Leaders must know export formats and notice periods before signature. I score vendors on exit friction, not only demo speed.

Your data belongs to your mission. Contracts should say how you get it back.

Selection workflow

  1. Workflow interviews across sites. I document without client identifiers in samples.
  2. Requirements and privacy questionnaire to vendors. Counsel marks deal breakers before demos consume your calendar.
  3. Demos scored against the script, not vendor flair. Staff scorecards due same day while memory is fresh.
  4. POC, references, and contract review. A steering committee human votes and a leader initials export and AI logging terms before signature.

Vendor selection checklist

  • Freeze requirements before first demo so vendors cannot redefine scope mid slide or skip billing exports.
  • Send privacy questions before pricing calls so legal cost surprises surface early.
  • Run the same POC script for each finalist on the same week with the same staff panel.
  • Talk to two references without the vendor present and ask what broke in month two.
  • Write who owns data export after exit and what file format you require in the contract before counsel signs.

Hypothetical: demo AI without billing export

A vendor showed summarization but could not export billing fields finance already uses. The shortlist dropped them despite flashy AI. The runner up won on exports and references from two peers with similar Medicaid mix. The steering committee logged dissent from a site that wanted faster go live, and that dissent shaped phased rollout. Parallel run lasted six weeks before cutover while billers compared exports nightly. Fictional scenario, not a client procurement.

What this is not

This is not a reseller agreement, not a certification of vendor security, and not a promise that any product fits every regulated program. I do not accept vendor referral fees or sit on selection committees as a vendor guest. Your steering committee keeps the final vote. I do not sign the contract on your behalf.

Questions people ask

When should we replace versus fix current software?

Replace when exports, permissions, billing interfaces, or multi site needs cannot be met after a serious cleanup and training push. Fix when staff bypass the system because training failed or forms are absurd. Assessment on the technology page clarifies which path fits before you spend selection money or sign a multi year contract.

How do you score AI features?

On data use for training, human override, audit logs, and whether assist is optional per role. Features without logging or rollback fail even if the demo looked slick. Core record quality and export fidelity still drive the majority of the score before any assist bonus.

Can we run selection without IT?

You need IT for integration, identity, and hosting questions. Programs own workflows and field truth. I facilitate both voices so requirements are complete and nobody signs a contract IT cannot support. Finance joins when pricing models hide per seat charges.

How long does selection take?

Depends on site count, funding mix, and how fast references return calls. Rushing references to hit a fiscal year end is how bad contracts happen. The memo includes a realistic implementation window and parallel run guidance. Expect weeks of staff time inside demos and POC.

Do you implement after selection?

I can advise on configuration priorities, migration order, and training sequence. Heavy build work is scoped separately with clear owners on your side. I do not tie selection to a single implementer or take license resale fees. Your vendor or internal team still owns go live.

Related pages

Book a free assessment

Let's Find the Growth Opportunities in Your Practice

Discover how AI can reduce admin, improve patient experiences, and help your practice grow with confidence.

Ready when you are. Free audit

Book audit