Community Health Worker Programme Software: When CommCare Is Enough, When Julota Is the Right Tool, and When Billing Forces a Build
Billing plus scale decides this, not enthusiasm for better software. A grant funded programme under about 15 workers with no reimbursement requirement should stay on CommCare and put the money into wages, and we say that plainly.
On this page
Billing plus scale decides this, not enthusiasm for better software. A grant funded programme under about 15 workers with no reimbursement requirement should stay on CommCare and put the money into wages, and we say that plainly. Past roughly 25 workers, or once denials on community health worker encounters are a live problem, documentation has to be structured at the point of capture in a stairwell with no signal, and a form tool cannot do that. Most programmes reading this are still on the buy side of the line.
When is off the shelf genuinely the right call here?
CommCare was built offline first for exactly this kind of field work and it does that part properly. It is inexpensive, it is reliable in basements and rural dead zones, and for a programme that reports to a grant rather than a payer it is a reasonable answer that leaves your budget where it belongs.
Stay on CommCare, and stop reading here, if this describes your programme:
- Grant funded, with no reimbursement requirement attached to encounters.
- Under about 15 community health workers, with caseload assignment a supervisor can still hold in her head.
- Clinical escalations that reach a supervising nurse quickly because the team is small enough for that to work.
- Reporting obligations satisfied by counts and narratives rather than by service lines.
- One language pair and one geography.
Julota is the right purchase for a different problem. If your defining challenge is sharing consented client data across a coalition of police, fire, hospital and community organisations, that is what it is designed around, consent management is the hard part of that problem, and rebuilding it is not a good use of money. It is not a field productivity tool for a worker with a phone and no signal, so be clear which of the two problems you actually have before you buy either.
There is a third case for buying at any size. If nobody in your organisation can state what a billable encounter contains as a data model, do not commission software yet. Sit down with whoever handles your denials and write it out first.
When does a custom build actually pay off?
A worker parks outside a third floor walkup. There is no signal in the stairwell and none in the apartment. She spends 50 minutes with a client who has uncontrolled diabetes, no working refrigerator for insulin and an eviction notice on the counter. That encounter has to become three things at once: a clinical escalation that reaches a supervising provider within hours, a referral with a closed loop back to the pantry, and a documented service a payer will reimburse. Form tools handle the capture and nothing downstream.
Build when two or more of these are true:
- You bill a state Medicaid programme or a managed care plan and denials are a live problem.
- Your workers routinely document where there is no connectivity and paper has crept back in.
- You run more than about 25 workers, which is where manual caseload assignment stops scaling.
- Clinical escalations go to a provider working in a different system and the handoff is a telephone call.
- You are accountable for outcomes under a health plan contract, which needs encounter level data joined to utilisation.
Medicare introduced community health integration services in the 2024 physician fee schedule, and a growing number of state Medicaid programmes now cover community health worker services with their own certification, supervision and documentation requirements. The details differ by state and they change, which is precisely why this is hard to buy off a shelf and why you should confirm your own specifics with your billing counsel rather than with any published summary.
How do they compare on the things that matter in this industry?
Offline as the operating condition. Most software calls offline support a feature and implements it as a cache that syncs when convenient. Here a worker may document six encounters before anything reaches a server. Ask any vendor or developer what happens when a phone dies after three visits underground. You want durable local storage that survives the app being killed, identifiers generated on the device so sync never creates a duplicate client, a queue for photographs and signatures, explicit conflict rules for when a supervisor edited a care plan mid visit, and a sync state the worker can see.
An encounter as a service definition. A payer typically wants an identified need tied to a diagnosis or a health related social need, a supervising provider relationship, an initiating visit, time spent, and a service matching a defined activity. A free text note saying the worker helped with housing satisfies none of that. Structure at the point of capture is what gets billed, and the app should tell the worker in the driveway whether the encounter is billable and what is missing.
Payer rules in configuration or in code. This is the reporting rigidity question that decides your maintenance bill. If a state revises its documentation or supervision requirements and that needs a developer and a release, you have built the wrong thing. Insist your billing lead can edit required elements and activity mappings in an administration screen.
Assignment that reflects the model. A worker who lives in the neighbourhood, speaks the language and has already knocked on that block is worth several from across town. Assignment worth having weights travel geography rather than postal boundaries, language and dialect, continuity, declared conflicts that matter in small communities, and acuity rather than raw client counts.
Consent granularity. If you exchange data with partner agencies, some records including substance use treatment information carry disclosure restrictions a general permissions model will not respect. Retrofitting that is expensive, so raise it in the first conversation.
What does total cost of ownership look like at your scale?
On the build side, from Digital Heroes delivery experience, a focused first release runs $55,000 to $120,000 over 10 to 16 weeks. That buys an offline first mobile application, encounter documentation structured as billable service definitions, caseload assignment reflecting geography, language and acuity, supervisor review with clinical escalation on a response clock, and certification records tied to the date of service. A full platform adding closed loop referrals with partner accounts, claim file generation per payer, safety check in and escalation, outcome reporting joined to utilisation and integration with a health system record runs $140,000 to $320,000 phased over 6 to 12 months.
A worked programme of roughly 40 workers billing one state Medicaid programme priced out like this: discovery and the billable encounter data model $9,000, offline first mobile application $26,000, structured encounter documentation with in driveway validation $18,000, caseload assignment $14,000, supervisor review and clinical escalation $12,000, certification and supervision records with a date of service eligibility check $8,000, and migration of client records, consents and caseloads $7,000. That totals $94,000. A grant funded programme of fifteen workers with simpler assignment lands nearer $55,000, and honestly should think hard before spending it at all.
Each additional payer adds two to four weeks once the first has established the pattern, roughly $8,000 to $18,000, covering their required documentation elements, supervision evidence, claim file shape and validation rules.
Annually, infrastructure sits at $250 to $800 a month for a programme of that size, scaling with visit volume rather than staff count because photographs and signatures are what grow. Support and enhancement runs 12 to 18 percent of build cost. Then two lines that belong inside the business case rather than beside it: devices and mobile data, because the software does not work without a working phone and handsets break in the field, and payer rule maintenance, which is continuous as state programmes mature.
On the buy side the licence is not the number that matters. Take the encounters submitted in the last two quarters, the share that came back, and the reason codes. Encounters denied for missing documentation elements are the ones structured capture removes, and your billing staff can produce that figure this week.
What does the hybrid look like, and when is it the honest answer?
There is a genuinely good middle option here and it is underused. If your field capture on CommCare works and your workers trust it, leave the phones alone. Build only the encounter to claim layer that consumes submissions from your existing form tool and turns them into validated billable service lines. That runs $30,000 to $55,000 over six to nine weeks.
It stops encounters dying between the stairwell and the payer, which is where most of the money is lost, without asking a field team to learn a new application during a rollout. For a programme that has just started billing and is not yet sure reimbursement will carry it, this is the proportionate spend.
The other hybrid worth naming is the health record integration. Reading clinical context out of a health system is comparatively straightforward and belongs in a later phase. Writing your encounter back into the clinical record is the hard half, it depends on the health system's interface calendar rather than yours, and it should carry its own timeline. Treating it as a line item inside your plan is how programmes end up explaining a slipped date they never controlled.
Start referrals with your five highest volume partners rather than a directory of two hundred. A loop that closes with five partners is worth more than a directory that closes with none.
Which should you choose, by operator size and stage?
Find your row and act on it.
- Grant funded, under 15 workers, no billing. Stay on CommCare and spend the difference on wages. This is the most common situation and the advice does not change.
- Coalition programme whose hard problem is consented data sharing across agencies. Buy Julota. Consent management is what it is built around and rebuilding it is poor value.
- Fifteen to 25 workers, one payer, capture already working. Build only the encounter to claim layer at $30,000 to $55,000 and leave the field tool alone.
- Twenty five to 50 workers billing one or two payers, paper creeping back. Build the first release at around $94,000, with offline capture carrying the largest share because it cannot be retrofitted.
- Accountable for outcomes under a health plan contract. Build the full platform, sequenced so claim generation and referrals land before any write back into a hospital record.
Two conditions apply to every build row. Pilot on one or two teams for two or three weeks before everyone, because field conditions surface problems no design session predicts, from glare on a screen to a building where the address in your data does not match the buzzer panel. And settle ownership before kickoff: the repository, the infrastructure accounts and the right to hire anyone else should be yours in writing.
If you want that decision made properly rather than quickly, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Criteo's Global Commerce Review found retail apps convert at 18% versus 4% on mobile web (roughly 4.5x), and travel apps convert at 20% versus 6% on mobile web (about 3.3x). Source: Criteo (2017) →
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- Poor software quality cost the US economy an estimated $2.41 trillion in 2022, including roughly $1.52 trillion in accumulated technical debt, driven partly by unsuccessful development projects and low-quality legacy systems. Source: Consortium for Information & Software Quality (CISQ) - Herb Krasner (2022) →
- The global point-of-sale terminal market is projected to reach approximately $181.47 billion by 2030, growing at an 8.1% CAGR from 2025 to 2030, driven by digital payment adoption and demand across retail, restaurant, and hospitality sectors. Source: Grand View Research (2025) →
Frequently asked questions
Is CommCare cheaper than building our own system?
Yes, and for a grant funded programme under about 15 workers with no billing requirement it is the right answer. It was built offline first for field work and it does capture properly.
Where it stops is downstream. A submission is a form, not a service line that validates against a payer rule or a task that escalates to a clinician on a clock. If denials or late escalations are costing you, that is the boundary you have crossed, and the encounter to claim layer alone runs $30,000 to $55,000 beside it.
What does it cost to move off our current field tool?
Migration of client records, consents and existing caseloads was $7,000 in a representative build, so the file movement is not the expensive part. The real switching cost is adoption.
Workers abandon apps they cannot trust, and paper returns within a fortnight of the first lost visit. Budget a pilot with one or two teams running alongside the current process for two or three weeks, and treat that as project cost rather than a week of goodwill. If your current tool works and your workers trust it, consider building only the claim layer above it instead.
What if our field tool vendor changes pricing or its offline behaviour?
Price at this tier is rarely the issue. The exposure is a change to how offline sync behaves, or to what a submission looks like, landing in the middle of your field season on somebody else's release schedule.
Model the subscription at your projected worker count anyway, and ask what notice you get before a breaking change. The structural protection is owning the encounter to claim layer, because once validated service lines are produced by software you control, the field tool becomes a replaceable input rather than the thing your reimbursement depends on.
How long does it take to build and roll out to a field team?
Ten to 16 weeks to a usable first release, then a phased rollout with one or two teams before everyone.
Discovery is two weeks and the deliverable that matters is a billable encounter described as a data model, reviewed by whoever handles your denials. You want to hear activity type, time in and time out, coded need, supervising provider and worker certification status on the date of service. If a developer describes notes and attachments, they are building a diary and your denials will not improve.
How much does each additional payer add?
Two to four weeks each once the first payer has established the pattern, roughly $8,000 to $18,000 per payer. That covers their required documentation elements, supervision evidence, claim file shape and validation rules. Payer count moves the budget more than worker count does, which surprises most programmes.
Budget for revision as well as addition. State programmes change documentation and supervision requirements as reimbursement matures, so insist your billing lead can edit required elements and activity mappings in an administration screen rather than raising a change request every time.
Why does offline capture take such a large share of the first release?
Because offline is the operating condition, not an edge case. In a representative build it was $26,000, around 28 percent of the first release, covering durable local storage that survives the app being killed, identifiers generated on the device so sync never creates a duplicate client, a queue for photographs and signatures, conflict rules and a visible sync state.
Teams that build online first and add caching later rebuild this work, and in the meantime workers stop trusting the app.
What does integrating with a hospital electronic health record cost?
Treat it as two projects. Reading clinical context is comparatively straightforward and fits inside the full platform phase. Writing your encounter back into the clinical record is the hard half and depends on the health system's willingness and their interface calendar.
Budget the write back as its own phase with its own timeline rather than a line item in yours, because the elapsed time is controlled by an interface team that does not report to you.
Can community health worker visits actually be billed?
Medicare introduced community health integration services in the 2024 physician fee schedule, and a growing number of state Medicaid programmes cover community health worker services with their own certification, supervision and documentation requirements that differ by state.
The software implication is that a free text note will not survive an audit. You need structured activity types, real time capture with a start and stop, coded needs, a documented supervising provider and proof the worker was certified on the date of service. Confirm the specifics for your state with your billing counsel.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
Who owns the source code when an agency builds my app?
You should own the source code outright, and the contract must say it plainly with an intellectual property assignment that transfers ownership on final payment. Watch for agreements that only license the code to you, keep it in the agency's repository, or register the Apple and Google developer accounts under the agency's name. Insist on code delivered into a repository you control from week one, not at final handover.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
How do I vet a mobile app development agency before signing?
Ask for three apps they built that are live in the stores right now, then download them and read the recent reviews yourself. Ask exactly who will work on your project, because some agencies sell with senior staff and deliver with juniors or subcontractors, and request one past client you can call. An agency that stalls on any of those three requests is answering your question.
What are the most common mistakes first-time app founders make?
Overbuilding version one is the budget killer: loading the first release with every feature can double the cost and delays the market feedback that would have redirected half of it. The other repeat offenders are ignoring the backend in the budget, treating maintenance as optional, and signing contracts without code ownership. Halving the launch feature list is the highest-return decision most first-time founders can make.
What security does my app need if it takes payments?
Never store card numbers yourself: run payments through Stripe, Braintree, or a similar processor's software development kit so the heaviest compliance burden stays with the processor. Beyond that, a properly built app encrypts all traffic, keeps session tokens in the platform's secure storage (iOS Keychain, Android Keystore), and enforces backend rules so one user can never read another's records. Ask a prospective agency how they handle those three things; vague answers are disqualifying.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
Who can build a custom mobile app system?
Digital Heroes builds custom mobile app systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other mobile app companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Rohan.
Director of Web Platform Engineering · Delhi · 2 posts on the site
Published · Last updated .
