Pharmacy Benefit Claims Processing Software: Custom Build or Licence Darwin, JUDI and ProCare Rx
Buy, or carve out entirely. If you are a health plan wanting a competent commercial pharmacy benefit, licence a platform or hand it to a pharmacy benefit manager, because the economics of rebuilding what the market already does well are poor.
On this page
Buy, or carve out entirely. If you are a health plan wanting a competent commercial pharmacy benefit, licence a platform or hand it to a pharmacy benefit manager, because the economics of rebuilding what the market already does well are poor. Build the adjudication engine only when your pricing model is the product you sell and configuration turnaround is your growth constraint.
What the off-the-shelf platforms actually do well
The modern platforms in this category are serious pieces of engineering and it would be dishonest to pretend otherwise.
Abarca's Darwin and Capital Rx's JUDI both exist because their founders concluded that older adjudication engines could not express modern pricing, which is a fair conclusion and they acted on it. Both handle real time claims under the National Council for Prescription Drug Programs Telecommunication Standard, route on the card's bank identification number and processor control number, resolve eligibility, apply formulary and utilisation management edits, price against network contracts and answer inside the window a pharmacist can tolerate. ProCare Rx serves smaller pharmacy benefit administrators and does that job. SS and C Health and the long established Argus platform carry deep operational history.
They also carry the parts that quietly cost the most to build: benefit stage accounting, accumulator handling, reversal processing, and in several cases the Medicare Part D obligations including true out of pocket tracking and prescription drug event reporting.
The question to ask them is not whether the software works. It is whether a licensing path exists for what you are, because these platforms are frequently sold inside a broader relationship rather than as a bare engine you configure yourself. Ask directly and ask early, since the commercial shape decides whether you have a buy option at all.
Where they stop: your pricing model is their configuration
The gap that pushes an organisation to build is nearly always the same one, and it is not a missing feature.
Pricing a fill is not a lookup. It is a comparison across candidate calculations: an ingredient cost derived from a benchmark, a maximum allowable cost entry for a multi source drug, the pharmacy's submitted usual and customary charge, plus a dispensing fee varying by network and channel, minus member cost share determined by formulary tier and benefit stage, adjusted for accumulator position, and different again for mail, ninety day retail and specialty. Platforms model that as configuration. If your differentiator is that you will administer a pricing arrangement nobody else will, configuration is the wrong shape, because you cannot wait a quarter for somebody else's configuration team to express your product.
Underneath sits the part that costs real money. Every client contract carries guarantees, and effective rate guarantees are measured across a contract year on a defined claim population. Discover in month eleven that a generic discount guarantee is short and you write a cheque, and nothing in the adjudication path told you it was happening. That is a data architecture failure wearing a pricing costume, and it happens because the winning price is stored and the candidates that lost are not.
The third gap is the reject message. Standard reject codes tell a pharmacist what happened and almost nothing about what to do next, so the pharmacist calls, and your help desk staffing becomes a function of your reject messaging quality rather than your claim volume. The free text space exists. Almost nobody uses it deliberately.
The arithmetic: per claim fees against a build
Adjudication is priced per claim, sometimes per paid claim and sometimes per transaction including reversals, and that distinction matters more than the headline rate. Get it in writing before you compare anything.
Multiply your annual adjudicated claims by the effective per claim fee including the transactions you did not think you were paying for. Then add the two costs that sit outside the invoice. First, configuration change orders: ask what the last non standard contract term cost to configure and how many weeks it took from signature to production. Second, the guarantee true ups you paid last year, because those are the direct financial consequence of not being able to see your position mid year.
The crossover is high in this category and it should be. Below roughly five million claims a year, per claim fees do not come close to a build plus the drug file licence plus the operations staff who watch it. Between five and twenty million, the decision turns on how many distinct client contract models you administer rather than the volume itself, because it is contract variety and not claim count that consumes configuration capacity. Above twenty million claims with several genuinely different pricing arrangements, the per claim fee plus change orders plus guarantee leakage will exceed a first release inside two years. Medicare Part D moves the line the other way, since it roughly doubles scope on its own and should be costed separately rather than folded in.
What a custom build actually costs
From Digital Heroes delivery experience, a first release covering real time claim handling, member and benefit resolution, formulary and utilisation management edits, network pricing with full candidate retention, reject messaging and reversals runs $180,000 to $400,000 across 6 to 9 months. A full platform adding rebate administration and manufacturer invoicing, client billing and guarantee tracking, prior authorisation workflow, pharmacy network contracting, specialty handling and client and member portals runs $700,000 to $2,000,000 over 18 to 30 months.
Migration runs 10 to 25 percent of first release cost and it is dominated by benefit and network configuration rather than claim history. Every plan design, formulary version, network contract and accumulator position has to be reconstructed and then proven against production claims, and the only acceptable proof is running both engines in parallel against live traffic and comparing every priced claim. Budget year two at 15 to 20 percent of build cost annually, plus the drug file licence, which is a running cost that belongs in the business case from day one rather than appearing as a surprise line.
Other drivers: the number of distinct client contract models; specialty and limited distribution handling; state Medicaid work, which adds requirements that differ by state; and whether you take on Part D, which brings benefit stages, true out of pocket accounting, low income subsidy handling and prescription drug event reporting as a programme of its own.
The four situations where building wins
Regulatory fit. Part D obligations, state Medicaid programme rules and the reporting they carry are the clearest case, and they are also the clearest case for phasing rather than building everything at once. If you administer Part D, treat it as a separate budget and a separate timeline. Folding it into a commercial build is the most common way these projects overrun.
Scale economics. Past roughly twenty million claims a year with multiple contract models, per claim fees and change orders exceed the build and keep compounding.
A workflow that is your competitive advantage. Genuine pass through or cost plus arrangements that legacy engines model awkwardly. Keep every candidate price and the reason the winner won, permanently, on the claim. Then guarantee measurement runs continuously against those stored components instead of being reconstructed from a warehouse in month twelve, and a client's position is visible weekly, which is early enough to change network steering or dispensing mix. In most builds that reporting capability is what closes the business case, not the adjudication engine.
Integration sprawl. Count what must agree in a few hundred milliseconds: the drug file, eligibility, accumulators, the formulary version, the network contract, the pharmacy's switch and your own history for duplicate detection. Once three or more of those are owned by different parties, the orchestration is the product and nothing in the critical path can afford a synchronous call to a system you do not control.
How to decide in a week
Run the contract expression test. It takes two people and no engineering.
Take your five most recently signed client contracts. List every pricing and guarantee term in each: the benchmark, the dispensing fee structure, any carve outs, the channel differences, the guarantee definitions and the claim population each guarantee is measured over. For each term, mark whether your current platform expresses it natively, expresses it with a workaround, or requires an offline adjustment at billing.
Count the offline adjustments. If there are none, buy, renew and put the money into clinical programmes. If two or three contracts each carry an offline adjustment, you are already running a shadow pricing system in a spreadsheet and it will produce a guarantee surprise eventually. That is the finding.
Second test, one afternoon: ask for your position against every client guarantee as of last Friday. If the answer takes more than a day to produce, you cannot correct anything mid year, which is the actual cost you have been absorbing.
Then commission a paid discovery of two to three weeks ending in a signed product requirements document covering the transaction model, the pricing candidate structure, the latency budget per stage, reversal and duplicate handling and acceptance criteria. Digital Heroes writes that before code and you keep it regardless, which is how quotes from several firms become comparable rather than three different projects wearing the same name.
Who we are wrong for: an organisation whose real complaint is reporting and transparency rather than adjudication. Build the analytics layer over your claim extracts and leave the engine alone, because that is a far smaller project and it solves what your clients are actually saying. Digital Heroes has more than fifty specialists and over 2,000 projects, holds India LLP, US LLC and UK LTD entities so ownership assigns under your own law, and puts a named team in front of you before signing. Verify us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- 76% of developers are using or planning to use AI tools in their development process in 2024 (up from 70% in 2023), with current active use rising to 62% from 44%; 81% agree increasing productivity is the biggest benefit of AI tools. Source: Stack Overflow (2024) →
- This analysis cites IDC research that companies lose 20-30% of revenue annually to inefficiencies caused by data silos, Gartner's estimate that poor data quality costs organizations at least $12.9 million per year on average, and a Salesforce benchmark that 80% of IT leaders say data silos hinder digital transformation - illustrating the business case for integrating systems. Source: Cherry Bekaert (citing IDC, Gartner, Salesforce, DATAVERSITY) (2024) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
Frequently asked questions
How much does it cost to build a pharmacy claims adjudication platform?
A first release with real time claim handling, formulary and utilisation management edits, network pricing with full candidate retention, reject messaging and reversals runs $180,000 to $400,000 across 6 to 9 months in Digital Heroes delivery experience. A full platform adding rebates, client billing, guarantee tracking, prior authorisation and portals runs $700,000 to $2,000,000 over 18 to 30 months. Medicare Part D should be costed as a separate programme.
Why is pharmacy adjudication harder than medical claim adjudication?
Because it is genuinely real time. A pharmacist stands at the counter with the patient, so the practical processing budget is a few hundred milliseconds and every rule you add spends part of it. Medical claims can pend to a human queue. A pharmacy claim cannot. That constraint forces precomputed benefit snapshots, pricing data held in memory, and a hard rule against synchronous calls to systems owned by somebody else.
How long before a custom engine can take live pharmacy traffic?
A first release is typically ready for controlled live traffic in six to nine months, and it should run in parallel against production claim volume before any pharmacy depends on it. Load testing at peak volume with realistic member and drug distributions belongs in the first month rather than the last. Organisations with one line of business and no Part D exposure move considerably faster than those carrying both.
Who should own the code for a custom pharmacy benefit platform?
You should hold the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm to continue, agreed in writing before kickoff. Digital Heroes assigns ownership from the first commit. In a business where a client contract can turn on whether you will administer a particular pricing arrangement, needing somebody else's permission to change your own engine is a commercial handicap rather than a technical detail.
What happens if the engine is slow or a dependency fails mid claim?
You decide the behaviour deliberately rather than discovering it. Anything outside the critical path that must be asked, such as a real time authorisation check, needs a defined timeout and a defined result when it expires. A pharmacist would far rather receive a documented deterministic answer than a hung connection, and a pharmacy switch that times out repeatedly will generate help desk calls faster than any pricing error.
Can we license a modern platform instead of building?
Possibly, and you should ask early. Capability is real in Darwin, JUDI and ProCare Rx, so the question is commercial rather than technical: is there a licensing path that fits a regional plan bringing pharmacy in house, a pass through administrator or an employer coalition. These platforms are often sold inside a broader service relationship rather than as a bare engine, and that shape decides whether a buy option exists.
What is the difference between adjudication and rebate administration?
Adjudication decides in real time whether a fill is covered and what everyone pays. Rebate administration happens afterwards and decides which claims generated manufacturer rebate eligibility, then invoices for it. They are different systems with different clocks, but they share one requirement: eligibility must be evaluated and stored at adjudication time with the formulary and contract version that applied, because reconstructing it later against a formulary that has changed loses revenue.
How do we reduce pharmacy help desk call volume?
Most of it comes from rejects that state what happened but not what to do. Use the free text message space deliberately: give the date a refill becomes eligible, name the covered alternative and its tier, or state that an electronic authorisation request has already been initiated and where. Then rank reject reasons by resulting call volume and fix the top few. Call volume falls without changing the benefit.
Should we build reporting instead of the engine?
For many organisations, yes, and we say so before quoting anything larger. If clients are complaining about transparency and claim level auditability rather than about what the engine can price, build the analytics layer over your claim extracts and leave adjudication alone. That is a far smaller project, carries none of the real time risk, and addresses the complaint that is actually costing you renewals.
What ongoing costs follow a custom adjudication build?
Fifteen to twenty percent of build cost annually for support and change, plus the drug file licence, which is a permanent running cost and belongs in the business case from the beginning. Add contract configuration work as new clients sign, quarterly content updates, and testing capacity, because every pricing change needs regression against historical claims before it reaches a pharmacy counter.
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.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
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.
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.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
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.
If we build for 20 users now, will the software cope with 500 later?
It should, without a rewrite, if it was built on a standard cloud stack; going from 20 to 500 users is mostly a hosting configuration change costing hundreds a month, not a second project. What actually breaks under growth is sloppier work: database queries never indexed for volume and features designed assuming one office's worth of data. Before signing, ask the vendor what happens to the system at ten times today's data, and listen for a specific answer.
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
Published · Last updated .
