iCareManager Gains Five Elms Growth Backing for IDD Care

Supervising care across several sites means depending on work a manager cannot watch in person. iCareManager builds the shared record around that responsibility, connecting the support someone receives with the plans, medication records and administrative work an agency needs to keep current.

The Columbia, Maryland company announced a strategic growth investment from Five Elms Capital on November 10, 2026. Financial terms were undisclosed. The investment is intended to support platform modernization, expanded AI capabilities, market reach and senior leadership growth in software for intellectual and developmental disability (IDD) and human services providers.

Co-founders Kamal Sheikh, CEO, and Babar Nawaz, COO, are expanding a business founded in 2011. Their opportunity reaches into a demanding part of healthcare software: helping a provider turn the daily work of supporting people into information that remains useful across an organization. Bringing AI into that record makes customer adoption, reliable documentation and continued human support part of the same development job.

What Five Elms is backing at iCareManager

The transaction supplies growth backing for an established care-management platform. The announcement describes modernization and expansion rather than a priced venture round, and provides no valuation, ownership percentage or named series. Those omissions leave the economics private while the operating agenda is relatively clear: improve the software, develop its AI capabilities and reach more providers.

Five Elms Capital specializes in software businesses serving particular industries, with operational resources spanning hiring, product and commercial growth. That focus is relevant to iCareManager because an agency's requirements stretch beyond an attractive demonstration. Software has to fit the people doing the work, the information supervisors need and the administrative rules surrounding service delivery.

For the founders, expansion also means supporting a wider set of organizations through change. More capability creates more decisions about configuration, training and how responsibilities move between staff. The investment's leadership and go-to-market priorities therefore belong beside the product roadmap. Selling another agency introduces another local operating history that the software team will have to understand.

The deal brings an investor into that continuing work without making its eventual results knowable today. iCareManager has disclosed where it intends to invest, giving customers a concrete agenda to discuss as the platform develops. Implementation experience and usefulness inside daily care will give those conversations more substance than the financing headline alone.

The care record has several jobs

An individual support plan describes what a person needs and hopes to achieve. iCareManager's person-centered planning software brings those goals, preferences and service plans into a shared system. Its value to an agency depends on the connection between the plan and what staff can actually record and review as support happens.

CareTracker is the company's documentation layer for that daily work, with service records and visibility across sites and shifts. A supervisor can use that information differently from a direct support professional, even though both are working from the same underlying service. The commercial attraction of a shared platform sits in preserving that connection rather than repeatedly reconstructing it.

Medication administration adds another relationship. iCareManager's electronic medication administration record connects pharmacy systems with the medication workflow, including updates and refill information. Barcode and logging capabilities are company-described features. Their presence explains the scope of the platform; claims about measured error reduction would require separate outcome evidence.

These responsibilities give the company's AI expansion a defined setting. Documentation assistance can be evaluated against the work surrounding a note: whether the relevant information is available, whether colleagues can follow it and whether the agency retains a useful account of service. That is a more demanding product conversation than asking whether a generated paragraph sounds professional.

Medicaid makes continuity commercially consequential

For eligible in-home personal care and home-health services funded by Medicaid, electronic visit verification is a federal requirement implemented through states. The scope matters: the requirement concerns specified services and visits, rather than every activity an IDD organization performs. Providers have to connect the appropriate documentation with the rules that apply to their programs.

CMS technical guidance describes variation in the codes and units used for personal care claims across and within states. That helps explain why an industry-specific record can become difficult to replace. An agency's information has to describe care in terms that remain useful when it reaches the reporting and payment process.

The investment case can be understood through that operating relationship. iCareManager already connects care-management functions with administration and billing, so its AI work can develop within an existing sequence of activities. This is an interpretation of the platform's position, rather than a claim that the investor disclosed a particular retention rate or that automation has already improved collections.

An agency evaluating new tools will have its own measures of usefulness. Re-entering information, searching for a missing record or training a colleague all consume working time, even when none appears as a separate line on the software invoice. Keeping that work visible gives a provider a practical way to discuss the modernization agenda with the vendor.

Adoption follows the staff onto the next shift

iCareManager's implementation guidance describes needs assessment, configuration, data migration, role-specific training, go-live assistance and ongoing support. That sequence makes the customer relationship part of delivery. The platform has to become usable by the agency's actual staff while its existing work continues.

Security also belongs in that buying conversation. The company's security page describes encryption, access controls, audit trails and its SOC 2 Type II and HIPAA posture. Those statements are the vendor's description of its controls; agencies can request the underlying documentation through its trust center when evaluating their requirements.

For Sheikh and Nawaz, the growth agenda now links software development with the people responsible for introducing it to customers. A documentation feature creates a training task, an integration creates a coordination task, and a larger provider footprint gives support staff more local circumstances to understand. Maintaining those connections is part of making the platform easier to use as its scope expands.

The next implementation will bring its own support plans, medication routines and shift changes into iCareManager. The founders' expanded organization will be working alongside that agency as it decides which parts of the day software can carry further, and where a member of staff still needs another person on the phone.