A blog for aging services leaders, homeless services providers, and the practitioners bridging both worlds.
Compassionate staff and proven programs have always been essential in social and human services. But the organizations achieving the greatest impact today are adding something more. Technology leadership has become a core strategic responsibility.
Our customers run aging services networks, homeless shelters, IDD care coordination programs, domestic violence services, and veterans support organizations. When technology fails here, the consequences are real. That reality shapes how we think about technology for CaseWorthy.
Operational Pressure Is Also a Technology Problem.
Workforce shortages, funding volatility, and rising demand are typically framed as operational challenges. They are technology challenges too, and the two compound each other in ways most executive teams don’t fully account for.
When staff levels fall and caseloads rise, pressure concentrates on your systems. Manual workarounds multiply. Institutional knowledge disappears into undocumented processes. Each departure becomes a data integrity risk. Social workers currently spend as little as 20% of their time in direct client contact. Better-integrated technology could push that closer to 45%, the equivalent of adding significant capacity without a single new hire.
Fragmentation has become normalized in human services technology. In an environment defined by funding pressure and rising demand, it’s no longer sustainable.
The cost of inaction compounds. Technical debt consumes an estimated 40% of IT balance sheets on average. Nonprofits allocate less than 3% of budgets to technology versus 6% in the private sector. That gap is not a sign of fiscal discipline; it’s a structural drag on mission capacity.
Heroic Effort Is Not a Strategy
Child welfare turnover runs roughly 30% annually, costing agencies $54,000 to double a salary per departure. Home care turnover exceeds 79%. Three out of four social workers report burnout. Sixty percent say their case management systems disrupt their work at least once a week.
The workforce crisis has a technology dimension that is underappreciated. When workers leave, they take with them the workarounds, informal processes, and institutional knowledge that were never captured in the system, because the system wasn’t built to capture them. What looks like organizational resilience is often heroic individual effort compensating for inadequate tools. That model is invisible until it breaks.
Well-implemented platforms standardize workflows and embed institutional knowledge into the system itself, reducing that dependency. Digitally mature nonprofits show 1.3 times lower burnout rates. Not because technology solves human problems, but because it removes the administrative friction that makes the work harder than it needs to be.
AI Is Already in Your Organization
Many executive teams treat AI adoption as a future decision. It isn’t.
AI is already entering organizations through vendor tools, embedded analytics, and staff using external AI applications to manage workloads they can’t otherwise keep up with. The question isn’t whether to adopt AI. It’s whether you’ll govern it intentionally.
Unmanaged AI use creates real exposure. The core risk isn’t that AI is dangerous, it’s that AI amplifies what’s already there. Fragmented, ungoverned data produces fragmented, ungoverned insights, only faster.
AI doesn’t fix a team. It amplifies what’s already there. Getting the data architecture right isn’t a precondition to eventually doing AI — it’s what makes AI meaningful.
Responsible deployment requires three things: unified and trustworthy data, clear human oversight, and governance that protects the dignity of the people being served. It’s key to ensure those guardrails exist before deployment, not after an incident.
The Funding Landscape Demands Defensible Data
Outcome-based funding is the direction of travel. Results for America have shifted more than $2.5 billion toward evidence-based programs since 2012. The Foundations for Evidence-Based Policymaking Act requires federal agencies to designate chief data officers and build structured evidence plans. Nearly all human services nonprofits track some program metrics, but only half are tracking actual constituent outcomes, and a quarter lack the data infrastructure to do so reliably.
Organizations without integrated systems are at a structural disadvantage in every grant cycle. A CTO who understands this doesn’t wait for the program team to ask for better reporting. They architect the data environment proactively, ensuring every service, assessment, and outcome flows into a unified record that can be queried, reported, and defended. That’s not back-office work, it’s critical infrastructure.
Vendor Selection Is a Risk Decision
One of the most underappreciated sources of long-term fragility in this sector is deploying platforms that weren’t designed for the work. Generalist enterprise systems don’t natively understand eligibility determination, person-centered care planning, HMIS compliance, or Medicaid billing. Organizations end up spending years customizing these platforms to approximate functionality that purpose-built systems have from day one. That customization debt accumulates, increases implementation risk, and creates configurations that become brittle when the team that built them moves on.
Vendor selection isn’t a procurement decision; it’s a risk decision. The right partner understands human services deeply enough to anticipate operational realities, not just respond to requirements documents. They should be a genuine thought partner on where the sector is heading. We’ve watched this repeatedly: the initial demo is promising, real-world complexity sets in, and budgets burn faster than expected. Organizations don’t set out to build software — they set out to serve people. And the cost of maintaining software, including infrastructure, security, compliance, and support, is often underestimated upfront. That ongoing burden doesn’t end at go-live, and for organizations on thin margins, it’s a material risk.
At CaseWorthy, we’ve made two architectural bets on this basis. The first is CORE, our data lakehouse: a unified foundation for every program, workflow, and client record across our platform. The second is Cara, our AI assistant, built on CORE and designed to augment frontline professional judgment rather than replace it. Both are paying off.
What This Requires
If technology is still a support function in your organization, that positioning is costing you in staff capacity, funder relationships, and the ability to prove impact. It’s also leaving you flat-footed on AI, which hasn’t arrived on the horizon. It arrived quietly, inside your organization, through your vendors and your staff.
The organizations that will lead this sector treat technology architecture as mission architecture. They invest in unified data because siloed data is incompatible with whole-person care. They deploy AI from a position of data integrity and clear governance. They choose technology partners who share accountability for getting it right.
The sector is ready for this level of ambition. The question is whether its technology leaders will rise to meet it.
About the Author
Dan Korzeniewski is an experienced technology leader with over 25 years of experience spanning software engineering, architecture, and leadership across enterprise SaaS organizations, with deep expertise in enterprise platform architecture, scalability, and cloud-native systems. As CTO at CaseWorthy, Dan leads the company’s technology strategy and engineering organization, responsible for the technology behind the CaseWorthy platform. He is passionate about building a high-performing engineering culture and is focused on making CaseWorthy’s platform faster, smarter, and more impactful through investments in unified data infrastructure, AI capabilities, and platform architecture designed to scale across the full complexity of human services.
