340B Compliance Software: Build Custom, Buy Verity or SUNRx, or Build the Qualification Layer Above Them
Footprint decides this, not drug spend. One registration, one purchasing account and one or two contract pharmacies means buy a packaged split billing product and spend the difference on clinicians.
On this page
Footprint decides this, not drug spend. One registration, one purchasing account and one or two contract pharmacies means buy a packaged split billing product and spend the difference on clinicians. Past roughly a dozen registered child sites, or with mixed disproportionate share and grant funded status under one parent, the eligibility question becomes specific to your organisation and no vendor can see the evidence that answers it. Even then the right move for most health systems is not a replacement. It is to keep the vendor for accumulation and ordering and build only the qualification and evidence layer above it.
When is off the shelf genuinely the right call here?
Verity Solutions, SUNRx, Sentry Data Systems and Macro Helix all do the arithmetic well. Accumulation, virtual inventory replenishment and ordering against a wholesaler account are solved problems, and rebuilding them adds cost without reducing risk. If your covered entity has one registration, one purchasing account and a simple outpatient footprint, one of these products plus a disciplined pharmacy team is the correct answer.
Buy, and stop reading here, if this describes you:
- A single site federally qualified health centre (FQHC) or critical access hospital.
- One or two contract pharmacy arrangements on a single third party administrator (TPA).
- Clinic registration that has been stable for years, with no acquisitions in progress.
- One state, so one set of Medicaid carve decisions to hold in your head.
- One electronic health record (EHR) with clean department and location coding.
At that shape the qualification question is genuinely small. A patient is a patient of the entity because they were seen at the one site you have, by a prescriber everyone in the building knows, and the vendor's approximation of eligibility is close enough that spreadsheet evidence still holds up when an audit letter arrives.
Two further cases where buying is right even at larger scale. If pharmacy, compliance and finance do not currently agree on who owns eligibility decisions, software will only make that disagreement visible in an audit report, so settle it first. And if your motivation is that programme savings feel too low, get an independent look at your registration and mixed use accumulation before funding anything, because in our experience the recoverable value is more often in registration accuracy than in tooling.
When does a custom build actually pay off?
The vendors own the arithmetic. What they do not own is the qualification evidence, because that evidence is a fact about your organisation rather than about the drug. Whether a person was a patient of the covered entity for a given prescription is built from an encounter at a registered location, a prescriber with an appropriate relationship on that date of service, and responsibility for care the entity actually holds. Three of those four facts live in your EHR, your credentialing system and a spreadsheet of clinic registrations somebody maintains by hand.
That gap widens as the organisation grows. Off the shelf tools express eligibility as configurable filters over the prescription feed: department codes, location lists, prescriber lists. Those hold until you acquire a practice, open an infusion suite in a leased building, add a telehealth clinic whose location code is a virtual department, or start a co-management arrangement with a specialty group. Each of those breaks a filter silently. Nothing errors. Accumulations simply keep running against a location that is no longer what the filter assumed.
Build the qualification layer when two or more of these are true:
- More than roughly a dozen registered child sites, with registrations that change between recertifications.
- Mixed disproportionate share hospital (DSH) and grant funded status under one parent, so different purchasing rules apply under one roof.
- Employed, contracted, locum and rotating prescribers mixed together, currently managed by a monthly exported list.
- Operations in more than one state, so Medicaid carve decisions and managed Medicaid identification differ by site.
- An audit finding you closed with a manual process that is still running today.
Programme savings that are material to your operating margin push the same way, because at that point a percentage point of qualification accuracy is a real number on a real budget.
How do they compare on the things that matter in this industry?
Effective dating. A child site registration becomes effective on a date, and a dispense before that date does not qualify. Ask a vendor how a mid quarter registration is handled, and whether prior accumulations are flagged for reversal when a registration date is later corrected. A filter list cannot answer that question. Dated rules can.
Prescriber currency. Most programmes run on a monthly exported roster, which is wrong within days. A physician who terminated on the fifteenth keeps qualifying dispenses until the next export, and every one of those is an overstated accumulation. Reading relationships from the credentialing system as a dated time series answers whether the relationship existed on the date of service, and copes with the retroactive corrections provider data routinely carries.
Payer classification. Preventing a duplicate discount requires knowing, per claim, whether the payer was Medicaid fee for service or a managed Medicaid plan, matched against how your entity is declared in the Medicaid Exclusion File for that state and billing number. Contract pharmacy files present managed Medicaid under commercial looking payer names, so a static lookup table fails quietly to a default. A review queue for unrecognised payer identifiers is the difference between a control and a report.
Release cadence. Manufacturer conditions on contract pharmacy arrangements have changed repeatedly since 2020, several of them requiring claims submission through a designated platform. Packaged vendors add connectors on their own schedule, which is a reasonable commercial decision and an awkward operational one for you.
Evidence retrieval. An audit picks specific accumulations and asks you to prove them. If that means one person joining a vendor export to an EHR report to a credentialing spreadsheet, you will spend a week per sample and find inconsistencies while an auditor is watching. Stored qualification decisions turn the same request into a query.
What does total cost of ownership look like at your scale?
On the build side, from Digital Heroes delivery experience, a focused first release covering the patient and prescriber eligibility engine plus split billing accumulation runs $70,000 to $150,000 over 12 to 18 weeks. A full platform adding wholesaler replenishment, Medicaid duplicate discount controls, contract pharmacy reconciliation, manufacturer restriction handling and audit evidence packs runs $180,000 to $450,000 phased over 6 to 12 months.
Priced component by component, so you can fund only what you need: eligibility engine $45,000 to $80,000, split billing accumulation $50,000 to $95,000, wholesaler ordering and replenishment $30,000 to $60,000, Medicaid duplicate discount controls $25,000 to $50,000, contract pharmacy reconciliation $40,000 to $75,000, manufacturer restriction handling $20,000 to $45,000, and audit evidence with self audit sampling $30,000 to $60,000. Going from three registered sites to ten commonly adds $25,000 to $50,000, because that is the point at which eligibility stops being a lookup and becomes a rules problem with effective dates.
Annually after go live, plan on support at 18 to 25 percent of build, manufacturer policy maintenance at $15,000 to $40,000, registration and recertification support at $8,000 to $20,000, hosting and security at $10,000 to $30,000, and audit support with staff training at $15,000 to $35,000. Add $8,000 to $25,000 for each major EHR upgrade, since encounter, location and provider data models move and eligibility logic breaks quietly rather than loudly, and $4,000 to $10,000 per contract pharmacy arrangement added or removed.
On the buy side, if your arrangement is priced as a share of programme savings or a rate per accumulated unit, as many in this category are, the fee rises exactly as the programme succeeds and there is nothing obvious to compare it against. Add the staff time spent assembling evidence the vendor does not hold. Then set both figures against the exposure nobody prices: repayment on accumulations that were never eligible.
What does the hybrid look like, and when is it the honest answer?
For most health systems this is the answer, and we give it whether or not it wins us work. Do not replace the vendor's ordering and inventory engine. Build the qualification and evidence layer above it and keep the vendor for the mechanics.
In practice that is three pieces:
- An eligibility engine, $45,000 to $80,000. Qualification expressed as versioned, dated rules over your own registration records, encounter data and provider roster, with every decision writing an explanation record naming the encounter, the location, the prescriber relationship and the rule version applied.
- A reconciliation layer, $40,000 to $75,000. Compare the TPA accumulation view against your own eligibility view and surface the dispenses where the two disagree, monthly, before an auditor finds them.
- Audit evidence and self audit sampling, $30,000 to $60,000. Immutable decision records with inputs and rule version, so sampling and reporting become a scheduled job rather than a quarterly project a director does personally.
Keeping the TPA is the largest single cost saving available in this category. Replacing a contract pharmacy administrator outright is a far bigger project with much less benefit, because the reconciliation view is where the findings actually hide.
The same logic applies to wholesaler integration. Ordering against the correct account and replenishment are worth building only once accumulation is trusted enough to drive purchasing.
Which should you choose, by operator size and stage?
Find your row and act on it.
- Single site FQHC or critical access hospital, one or two contract pharmacies. Buy a packaged split billing product. Keep a written eligibility policy and a quarterly self audit sample done by hand.
- Two to five registered sites, one state, one EHR. Still buy. Spend on registration accuracy and clean location coding in the EHR, which is cheaper than software and closes more findings.
- Six to twelve sites with several contract pharmacies. This is the decision point. Keep the platform and build the eligibility engine and reconciliation layer above it, roughly $85,000 to $155,000 depending on site count and how many TPA file formats you have to read.
- More than a dozen sites, mixed DSH and grant funded status, more than one state, or two EHRs after acquisitions. Build the qualification and evidence layer properly, phased, and keep the vendor for accumulation and ordering until you have run a full cycle in parallel.
- Savings material to operating margin, with specialty and infusion drugs in the mix. Build the full platform, but sequence it: mixed use split billing first, then Medicaid controls, then contract pharmacy reconciliation, then evidence and manufacturer restrictions last, because those rules will have changed since discovery.
Two conditions apply to every build row. Name one owner of eligibility policy across pharmacy, compliance and finance before kickoff, because the hard questions in this domain are policy questions wearing technical clothes. And run the new engine in parallel with the incumbent for a full accumulation cycle before switching, since the first thing a qualification rewrite tends to find is that your prior numbers were not quite what you thought they were.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- This World Bank report argues that digital technology adoption raises SME competitiveness, productivity and resilience, while documenting that smaller firms consistently lag larger ones in digital adoption - a gap that constrains their growth and market reach. Source: World Bank (2022) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- 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) →
- SHRM's 2025 benchmarking data puts the average cost-per-hire at $5,475 for nonexecutive roles and $35,879 for executive roles - executive hires are on average nearly 7x more expensive than nonexecutive hires. Source: SHRM (Society for Human Resource Management) (2025) →
Frequently asked questions
Should we replace Verity Solutions or Macro Helix entirely?
Usually not, and this is where most health systems get the decision wrong. Accumulation arithmetic, virtual inventory and wholesaler ordering are handled competently by the packaged products, and rebuilding them adds cost without reducing risk.
The part worth owning is the qualification and evidence layer, because eligibility depends on your own clinic registrations, prescriber relationships and encounter data, which no vendor can see properly. Building above the vendor rather than replacing it is the pattern that pays back, and it costs a fraction of a full platform.
What does it cost to switch 340B vendors or administrators?
The direct cost is modest. The real expense is that accumulation history and the evidence behind it do not travel cleanly, and you need both for years after the dispense. Before signing anything, ask how the complete accumulation record leaves the system, including the qualification basis and not just totals, and get the answer into the contract.
Switching a contract pharmacy administrator is a separate and much larger project. Each arrangement is a reconciliation feed in its own format, and in our delivery experience adding or removing one runs $4,000 to $10,000 in integration work alone.
What if our vendor's fee keeps rising as our programme grows?
Work out now what your fee looks like at double your current savings, because arrangements priced as a share of programme savings or per accumulated unit rise exactly as the programme succeeds. That is not a criticism of any vendor, it is arithmetic you should do before renewal rather than during it.
The structural response is to own the layer that determines whether savings survive an audit. Once qualification and evidence are yours, the vendor is providing mechanics you can price and compare, rather than a service nothing else is measured against.
How long before a custom qualification layer is making decisions?
Twelve to eighteen weeks for a first release covering eligibility and split billing accumulation in the mixed use area. Wholesaler replenishment and Medicaid controls follow over the next quarter, and contract pharmacy reconciliation and audit evidence generally land between months six and ten.
The variable that moves the schedule most is discovery on location coding: how clearly your EHR distinguishes registered child sites from other departments, and whether historical registration effective dates were ever recorded. Organisations with a clean dated registry of sites move noticeably faster.
What does each additional registered child site add to the cost?
Going from three sites to ten commonly adds $25,000 to $50,000 in our delivery experience. The cost is not strictly per site. It is the point at which eligibility stops being a lookup table and becomes a rules engine with effective dates, retroactive corrections and per site purchasing rules.
That architectural shift happens once. Sites added afterwards are cheap, which is why organisations expecting acquisitions are better off crossing it deliberately than discovering it during an audit.
Does the group purchasing organisation prohibition apply to us?
It applies to certain hospital covered entity types and not to others, so a parent running both a DSH and a grant funded clinic has to apply different rules under one roof. That is a common source of findings, because purchasing systems do not naturally distinguish the two.
A build should carry entity type at the site level and evaluate the purchasing account against it, rather than relying on staff to remember which account belongs to which programme. If you run mixed status today, this alone is often what tips the decision.
Does carving Medicaid in or out change the build or buy answer?
It changes the cost, and it should be decided on programme grounds rather than software grounds. Carving out removes a whole class of duplicate discount control and simplifies a build by roughly $25,000 to $50,000. Carving in is operationally harder, varies by state, and multiplies the control variants a multi state system maintains.
Quantify the savings difference first. Letting a software cost decide a programme design question is how covered entities give up more in savings than they save in build.
Will custom software actually reduce our risk in an external audit?
Only to the extent that it makes every qualification decision explainable with the evidence attached. The value is not the accumulation total, it is being able to show why a specific dispense qualified, under which registration, which prescriber relationship and which effective date.
Build the audit evidence pack as a first class feature rather than a report bolted on at the end. The practical gain is frequency: monthly self audits with automatic exception queues catch a broken location filter within weeks, whereas an annual manual review finds it after a year of accumulations that then have to be reversed.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
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.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
Who can build a custom software system?
Digital Heroes builds custom 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 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
More from Ezra.
Senior Brand Designer · APAC · Sydney · 1 post on the site
Published · Last updated .
