Closed Loop Social Care Referral Platform: Build or Buy findhelp
Buy. A single clinic or hospital that wants to refer and know what exists should use findhelp, whose national directory coverage you could never maintain yourself, and join an existing Unite Us network if your region already has one.
On this page
Buy. A single clinic or hospital that wants to refer and know what exists should use findhelp, whose national directory coverage you could never maintain yourself, and join an existing Unite Us network if your region already has one. Building is justified when you convene the network, carry outcome obligations on your own contract, and your partners are organisations that will never log into a second system.
What the off-the-shelf referral products actually do well
Most organisations should buy here, and the reason is unusual: in this category the value is network density, and splitting the same community partners between two systems helps nobody. Say that before anything else.
findhelp maintains the broadest resource directory coverage in the country and gives a clinician a usable referral path at the point of care. Maintaining a directory yourself is a permanent obligation you will come to resent, because organisations move, close, change eligibility and lose funding constantly. Unite Us built a genuine network business and made real progress on the incentive problem by contracting with community organisations and moving money through the network, which is the honest answer nobody else has funded. Julota works from the cross agency, consent first direction and suits regional coalitions well. WellSky Community Services carries case management depth for organisations that need a record rather than a referral.
Each of those is a serious product and none of them is the reason closure rates stall. Buy one, join a network that already has partners onboarded, and put the money you saved into a coordinator.
There is a floor as well. A clinic making forty referrals a month to eight partners it knows by name does not need a platform. It needs a shared list, a named person and a follow up call. Software will not create a relationship that does not exist.
It is also worth naming what these vendors carry that a coalition would otherwise carry alone. Directory maintenance across thousands of organisations, accessibility testing, translation, a security posture health systems will accept, and the ongoing work of keeping a national resource set current. Those are real operating costs that disappear into a subscription line, and a coalition that builds inherits every one of them on the day it goes live.
Where they stop: the last mile belongs to a two person organisation
Here is the workflow every generic product models badly. A nurse care manager screens a patient at discharge, records food insecurity, transport difficulty and unstable housing, makes three referrals, and never hears about any of them again.
On the other side, a food pantry with one and a half paid staff receives the referral in an inbox checked on Tuesdays. They already know this family. They have served them for two years. The referral asks them to log into a system, confirm receipt, record the service and close the loop, which is eleven minutes they do not have for a health system that sends them no money. They help the family, because that is what they do, and they never touch the software. The report shows the referral open. Eighteen months later somebody concludes that closed loop referral does not work.
The software was not the problem. The model asks the least resourced party in the chain to do the most administrative work for the least benefit, and no product priced per user solves that. The second workflow it models badly is capacity. Directories tell you an organisation exists and what it does. They rarely tell you whether it can take anyone this week, so referrals flow toward the best known organisations, which are already full, while capacity sits unused two neighbourhoods over. A family gets one phone number, is told the waiting list is closed, and does not call the second.
The arithmetic: per user licensing against a coordinator and a build
Cost this against outcomes rather than seats, because in this category the seat price is not the decision.
Worked example to replace with yours. A network making 24,000 referrals a year on a platform at $120,000 annually, closing 22 percent, is paying about $5 per referral and $23 per closed loop. Add a coordinator at a loaded $70,000 and closure typically moves far enough that cost per closed loop falls even though total spend rises. That is the first thing to try, and it is not a build.
If closure is still short of what your contract requires, compare five year totals. Platform and coordinator at $190,000 a year is $950,000. A first release at $95,000 with year two at 18 percent, plus the same coordinator, runs about $513,000. The crossover is not referral volume, it is who owns the outcome: a convener with value based payment or waiver funding tied to delivery crosses at roughly 15,000 annual referrals, while a participating clinic never crosses at any volume.
The number nobody models is partner goodwill. Every system you ask a small organisation to enter data into without giving anything back spends a relationship you will need later.
What a custom build actually costs
In Digital Heroes delivery experience, a first release covering screening intake, a resource directory with eligibility and capacity, referral creation and routing, the low friction partner confirmation path and the coordinator worklist runs $60,000 to $130,000 in 12 to 16 weeks. A full network platform adding health record integration for screening and referral write back, consent management with segmentation, partner system interfaces, closure and outcome reporting and a client facing self referral path runs $150,000 to $400,000 across 6 to 12 months.
Migration is 10 to 25 percent of the build, and most of it is directory reconciliation rather than record movement. Partner records arrive from three sources with different names for the same organisation, and eligibility rules exist as prose in a document. Somebody has to sit with each partner and turn that prose into fields, which is also how you onboard them.
Year two is 15 to 20 percent annually, covering hosting, support, accessibility and language maintenance, and outside change: a new payer reporting format, a partner adopting a case management system, a screening instrument revision.
What pushes you up the band: health record integration, which is a real project against Epic or Cerner rather than a connector you switch on; the number of partner system interfaces, each its own negotiation; multi language and accessibility work, which is not optional given who the users are; identity matching across organisations; and payer specific reporting formats, one per contract.
The four situations where building wins
Regulatory fit comes first and it is what stops these projects in legal review. Consent has to be structured, scoped and revocable, naming both categories of information and recipient organisations, because substance use disorder records carry stricter federal protection under 42 CFR Part 2 than general health information. Screening results map to standard coding, including the social determinant Z codes in the ICD-10-CM range Z55 to Z65, and hospitals are already collecting screening data for quality reporting, so a referral platform should reuse it rather than screening the same person twice.
Scale economics is second, at the convener threshold above.
Third is a workflow that is your competitive advantage, which here means the last mile itself. A network that lets a two person pantry confirm a service in under thirty seconds, from a phone, with no login, reports closure rates a licensed platform will not match. That is the product.
Fourth is integration sprawl. Count them: the health record, the screening tool, the directory, partner case management systems, the consent record and payer reporting. When four or more must agree before a closure figure can be defended to an analyst, the figure is assembled by hand.
How to decide in a week
Call ten partner organisations who received referrals from you last month. Not a survey. A phone call, with two questions: did you serve this family, and did you record it in our system. Give a coordinator two days.
Then compare the two answers against your closure report. If services were delivered but not recorded for more than a third of them, your closure rate is measuring administrative compliance rather than help delivered, and buying a different platform will produce the same number. Ask the same partners one follow up question: what would make confirming take under thirty seconds. Their answers are your specification.
Run the second test on capacity. Pick three service types and try to find out, today, which organisations in your county can actually accept a referral this week. Time it. If it takes more than an hour, your directory is a phone book and referrals are being routed on reputation rather than availability.
A third check takes a morning and it is the one funders respond to. Take last quarter closures and split them into six states: service delivered, client declined, ineligible, capacity unavailable, unable to contact, and duplicate of a service already in place. If your system can only produce open and closed, you cannot tell a payer analyst anything about why the network performs the way it does, and you cannot tell your own board where to add capacity.
Then pay for discovery. Digital Heroes writes a signed product requirements document before any code exists, covering the consent model, the tiered partner confirmation paths, eligibility and capacity structures, integrations and acceptance criteria, and the coalition owns it whichever firm is appointed. We build and run our own products, including ShopScore, HeroCheckout and Section Vault, so the people choosing your architecture live with those decisions on their own revenue. We are wrong for you if you are a single clinic wanting a directory, or if your region already has a working network you would be competing with.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- 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) →
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
Frequently asked questions
How long does it take to launch, and how long until partners are active?
A first release ships in 12 to 16 weeks, but partner onboarding is the real timeline and it is measured in months. Start with the twenty organisations receiving most of your referrals, get them confirming through the low friction path, then expand. Networks that try to onboard two hundred partners at launch usually end up with two hundred inactive accounts and a closure rate that proves nothing.
Who owns the platform if the coalition changes lead agency?
The coalition should own the repository, the cloud accounts and the data, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit. This category runs on the trust of community partners, many of whom have entered data into somebody else system before and got nothing back, so being able to say the platform belongs to the network is an adoption argument rather than a legal preference.
What happens if a client revokes consent after a referral has gone out?
Revocation has to take effect immediately and be logged, and the partner should be notified that no further information will flow. Design consent as a scoped record naming categories of information and recipient organisations rather than a signature on a form, so revoking is a state change rather than an email. Substance use disorder information carries stricter federal protection and needs its own explicit consent.
Can community partners confirm a service without logging in?
They should be able to, and it is the single design decision that decides your closure rate. A text message link opening a page where confirming takes two taps, with no account and no password, works for organisations that will never adopt a portal. Reserve system to system interfaces for partners whose referral volume justifies the integration work, and use a paid coordinator for everyone else.
Should we join an existing network instead of standing one up?
If your region already has a network with partners onboarded, yes, almost always. Value in this category comes from density, and two competing networks split the same small organisations and halve everyone closure rate. Build only when you are the convener with outcomes on your own contract and no existing network covers your geography or your partner mix.
What is the difference between a resource directory and a referral platform?
A directory tells a clinician what exists and how to contact it, which findhelp does at national scale. A referral platform creates a tracked request with a recipient, a consent scope, an outcome state and a closure event. Many organisations buy the second when the first is what they needed, then measure closure on referrals nobody agreed to receive.
How much does health record integration add to the project?
It is usually the largest single cost driver and it is two pieces of work, not one. Pushing screening results and referrals out is the easier half. Writing referral status back into the clinician workflow is the half that gets cut when timelines slip, and cutting it is what makes the loop invisible to the care manager, which recreates the problem you funded the project to solve.
What outcome measures will a payer analyst actually accept?
Closure rate alone is weak and easily gamed, since closing a referral as unable to contact still closes it. Distinguish service delivered, client declined, ineligible, capacity unavailable, unable to contact and duplicate as separate states. Where the contract requires linkage to health outcomes, agree the measure definitions with the funder analyst before the build encodes them, because retrofitting definitions is expensive.
Can we keep our directory fresh without an annual audit?
Replace the audit with cheap continuous updates. A weekly text asking whether an organisation is accepting referrals, answered with one tap, keeps status fresher than any quarterly review. Model eligibility properly as well, since catchment area, income threshold, household composition, documentation required and languages spoken are what actually decide whether a match is real.
Is it worth building if we are a health plan rather than a provider?
Often yes, because a plan owns the outcome, holds the claims data needed for linkage, and usually contracts across a geography wider than any single network covers. The build case strengthens further where waiver or value based funding ties payment to delivery. What does not change is the last mile: a plan sized budget does not make a two person pantry adopt a portal.
How long does it take to build a custom CRM from scratch?
A focused first version takes 10 to 14 weeks in Digital Heroes delivery experience: about 2 weeks of discovery and data modeling, 6 to 9 weeks of build, and 2 weeks of migration and testing. Fully replacing a heavily customized Salesforce setup takes 5 to 8 months. Timelines slip most often on data migration, so insist that legacy data mapping starts in week one, not at the end.
Can AI features like lead scoring and email drafting be built into a custom CRM?
Yes, AI features are now a standard request: connecting a model API for lead scoring, call summarization, or drafted follow-up emails typically adds $5,000 to $15,000 to a build in recent Digital Heroes projects. The custom advantage is that the AI runs on your full data and your rules instead of a vendor's generic feature, and you are never pushed into an add-on tier the way Salesforce prices Einstein. Start with one AI feature tied to a measurable task, prove it works, then extend.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
How do I vet a CRM development agency before signing a contract?
Ask to see two live CRMs they built for businesses your size and talk to those clients about what happened after launch, not during the sales process. Then pin down three specifics: who owns the code (you should, fully, on final payment), what a change request costs after go-live, and how they plan data migration. An agency that cannot walk you through a migration plan on the first call will improvise yours.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
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.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Should we pay a consultant to customize Salesforce or just build our own CRM?
If your gaps are configuration-sized, hire the consultant; the Salesforce customization quotes our clients bring to Digital Heroes usually run $150 to $250 per hour, and small changes land fast. Switch to building your own once the customization estimate crosses roughly half the cost of a custom system, because you would be spending custom-development money while still renewing per-seat licenses every year. We regularly see teams put $60,000 into Salesforce customization on top of $40,000 a year in licenses, more than a comparable system they would own outright.
Who can build a custom CRM software system?
Digital Heroes builds custom CRM software 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 CRM software 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
Published · Last updated .
