Nonprofit case management software compared — Bonterra Apricot, Salesforce NPSP, Casebook, and the AI-native stack. No 24-month config, no per-seat licensing.
The case management software in front of you was designed when the bottleneck was collection — get the intake form into the worker’s hands, land the right fields in the right rows, export the table on the last Friday of the quarter. That bottleneck moved.
Collection is solved. The new bottleneck is the workflow that reads every case note, every assessment, and every follow-up survey on arrival — and surfaces the risk before it becomes a crisis. The year-end outcome report is no longer the answer. The client is the unit of work, and the client record has to be intelligent.
That is the difference between nonprofit case management — the collection-era stack of intake form, case-note spreadsheet, services log, and year-end outcome survey, re-stitched at quarter-end — and nonprofit case intelligence: one persistent client record, read on every arrival, reported as a query, not a merge.
AI without a workflow is a clever intern with no desk. The nonprofits winning with AI are the ones whose client data has a place to land — one record, one ID, one story.
Nonprofit case management software is a platform that holds one persistent record per client across every interaction — intake, assessment, services delivered, case notes, referrals, outcome surveys, and follow-up — and reads that record so program staff get answers without a CSV merge. It replaces the typical stack of intake form, case-note spreadsheet, services log, and year-end outcome survey with one connected record.
Used by:
Client tracking software, services tracking database, social services case management, human services CRM, social work case management software — different terms point to the same software category. What varies is which stage of the lifecycle the buyer is thinking about when they search.
A nonprofit CRM (Salesforce NPSP, Blackbaud Raiser’s Edge, HubSpot) tracks donor relationships. Case management software tracks clients through service delivery. The donor CRM keeps the relationship history; case management keeps the service record and the outcome evidence.
The case management software in front of you was designed when the bottleneck was collection: get the intake form into the worker’s hands, land the right fields in the right rows, export the table at year-end, hand it to the analyst, wait three weeks, file the funder report.
That bottleneck moved. Collection is solved. The new bottleneck is the workflow that reads every case note, every assessment, every follow-up survey on arrival — and surfaces the risk before it becomes a crisis. The year-end outcome report is no longer the answer. The client is the unit of work, and the client record has to be intelligent.
AI without a workflow is a clever intern with no desk. The nonprofits winning with AI are the ones whose client data has a place to land — one record, one ID, one story.
For years, Open Play’s program and facility data sat in paper logs and spreadsheets — including a water log Marco Botha had kept by hand for nearly three years. The foundation needed comparable, real-time evidence to put in front of investors and partners, not a quarter-end export — and nothing in the old setup could flag an operational problem while it was still fixable.
After a stretch of heavy rain, Open Play’s water purification system reported it had run out of rainwater — which Marco knew was impossible. Because the reserve, groundwater-extraction, and harvesting figures were now live on the client and facility record, he cross-checked them in minutes. The numbers immediately surfaced the real cause: a probable reservoir leak or a failed float switch — caught while still fixable. Same logic for a nonprofit caseworker: when intake numbers, services delivered, and follow-up surveys are all on one record, the impossible reading shows up on Tuesday, not at year-end.
“Those statistics that we’re now running on Sopact immediately showed me there’s something significantly wrong … things like that, we would never have been able to do in the past.”
Every effective nonprofit case workflow moves through the same five stages — whether the program is workforce training, food assistance, shelter, housing navigation, family services, or multi-program human services. Memorize them; the rest of this page is detail under each.
Assessments, screenings, demographics, eligibility documents.
Theory of Change, Logic Model, outcome rubric — the program’s theory.
Field definitions, demographic codes, indicators, ownership.
Case notes scored, risks flagged, services joined to outcomes.
Form 990 Schedule I, CSBG ROMA, HMIS, CDBG, community impact.
Pick the lifecycle the client record carries (sections below), assign a persistent client ID at first contact, then let every later stage write back to the same row.
The program type changes, the dominant work changes, the funder report at year-end changes. The record underneath — one client carried across every stage — does not.
In legacy nonprofit case management, the record resets at the year-end export. In case intelligence, the record continues — first contact through year-three outcome survey — on the same persistent client ID.
One persistent client ID carries every intake, case note, service delivered, follow-up survey, and outcome from first contact through year three. Re-engagement in cycle two arrives with the full history attached.
Most nonprofit teams evaluating case management software are choosing between five recognizable names. Each was built for a different era; each made different trade-offs.
All five vendors will run a basic intake → service → outcome workflow. The differences show up at the third question your funder asks: how do you know the outcome happened, where is the evidence, and what does the agency-level report look like for the same client across three programs?
No per-seat tax. No per-record meter. The line items are the things that actually drive work — how many programs share the client record, how custom the data dictionary needs to be, which built-in skills get activated, and how branded the funder-facing reports have to look.
Your fields, your eligibility codes, your demographic categories — drafted from your existing intake form in one working session and signed once. Every later metric traces back to it.
Theory of Change skill, Logic Model skill, Outcome Rubric skill, Case-Note Reader skill, Cohort Roll-up skill — turned on by default, ready to read on arrival. Add the Logframe skill when a funder asks for it.
Logo, color palette, intake banner styled to your brand. White-label form, banner, and report design rolling out — funder-facing pages match your identity, not Sopact’s.
Closed-ended ratings and open-text answers scored together. Indicators populate automatically, with citation trails and attribution rules — what service drove which outcome, scored across the cohort, not by hand.
Form 990 Schedule I, CSBG ROMA, HMIS / CoC, CDBG progress, United Way community impact — each generated from one place with full citation trails. The data dictionary keeps every metric reproducible.
One intake-to-outcome program is the simplest case. Three programs (food + workforce + housing) sharing one persistent client ID adds dictionary reconciliation and cross-program reporting.
One physical site is straightforward. Multiple sites under one agency add HMIS-aligned fields, federation-level roll-up, and BI integration to Tableau, Power BI, Looker, or Snowflake.
90-day check-in is light. Year-1, year-3, and year-5 cohort attribution back to baseline intake adds depth to the dictionary and the reporting reach.
Built-in skills cover the common patterns. Your team’s domain rubrics — encoded in plain English, versioned, composed with the built-ins — let the skill library grow with the agency.
One brand on one form is simplest. Multi-brand white-label — separate funder portals, separate participant-facing portals — useful for fiscal sponsors, United Way agencies, and coalitions running multiple branded initiatives.
Reading reports in Sopact is included. Piping data via API into your existing BI stack (Tableau, Power BI, Looker, Snowflake) adds integration setup.
A 12-person family services agency running one program pays less than a 50-person multi-site community action agency running six. Both pay for the complexity they actually use — the data dictionary, the skills, the white-label depth, and the reporting reach. Talk to us with your program list; we will quote against it directly.
Nonprofit casework often touches confidential information — services received, household circumstances, family context, eligibility status. Here is what Sopact actually provides, named without overclaim.
AES-256 at rest, TLS 1.3 in transit, encrypted backups, scheduled key rotation. The reading model returns structured output and does not retain the underlying text.
Role-based access at the field level, single sign-on, multi-factor authentication, and a complete audit trail on every read and every write.
All AI calls run under enterprise-grade service-level agreements with no training-data retention. The model reads, returns structured output, and forgets.
Sopact is not currently HIPAA-certified or covered by a Business Associate Agreement (BAA). The controls above support a security-conscious deployment, but if your program is subject to HIPAA, FERPA, 42 CFR Part 2, or state confidentiality rules, you should evaluate the specific controls against your compliance program and consult your counsel before storing protected information. We are happy to walk through the technical detail with your security team.
Reports are not formats — they are questions. Case intelligence produces four distinct shapes from the same accumulating client record. Naming the shape tells you which one a funder, board, or director is actually asking for.
The 90-day follow-up survey nobody returned, the case-note overdue this week, the eligibility re-cert missed. Run continuously — surface gaps before the grant report is due.
A length-of-stay that doubled, a screening-score swing, a demographic distribution drifting from target. Anomaly against history or against the group.
Everything known about one client — first contact to today. Every intake, every case note, every service rendered, every outcome survey. Board chair’s “what happened to that family?” answered in two clicks.
Form 990 Schedule I, CSBG ROMA annual, HMIS / CoC, CDBG progress, United Way community impact — all as queries against the client records. The annual report drawn from one place.
Strip away the marketing and four properties separate nonprofit case intelligence from everything before it. If a system you’re evaluating lacks any of them, it belongs to the era that ended.
Generic generative-AI tools are easy to adopt and hard to trust: ask the same question twice and you can get two answers. For nonprofit casework that funders, auditors, or boards will scrutinize, that variance is disqualifying. Sopact runs the model to read, then locks the answer, so the result is reproducible and auditable every time.
A validated screen (NPS, PSS, VI-SPDAT, food security, custom indicator) tells you what changed. The case-note narrative tells you why. Sopact joins both on the same persistent client ID — so the score and the narrative reason live on the same row in the funder report.
Encryption at rest and in transit, role-based access at the field level, no training-data retention on AI calls, and a complete audit trail. Useful for any program; required for any agency whose funder asks how the data is handled.
New intake question, new rubric dimension, new outcome cohort, new white-label brand — described in language, live immediately. The system bends to the agency’s work instead of the agency’s work bending to the system.
The architecture is the same; the configuration scales with the work. Here is what each size of organization typically runs through Sopact.
A single case manager and an executive director. Intake form, case-note template, and one outcome survey. Live in a week. No integrator, no IT staff required. Outcome reporting is a query, not a year-end project.
Multiple program directors, mixed funder portfolio. One client appears across food, workforce, and housing — joined on a persistent ID. Funder-level reports (Form 990 Schedule I, CSBG ROMA) draw from one place.
Multiple physical sites, HMIS reporting, CDBG and CSBG grants, federal compliance. Sopact reads HMIS-aligned fields, runs the agency roll-up across sites, and exposes data to BI tools like Tableau, Power BI, Looker.
Ten questions that come up in nearly every nonprofit case management evaluation — answered here so the comparison work happens before the sales call, not during it.
Nonprofit case management is one shape of the stakeholder record. The same approach holds applicants, students, trainees, clients, and grantees across every program a foundation, agency, or university runs.
One intake form. One rubric. One year’s worth of case notes you already have. We’ll walk through how it would live as one record per client, what the AI would pull out of the long-form case notes, and what the year-end outcome report would look like coming out of one place instead of a CSV merge across four systems.
