Clinical Trial Imaging Core Lab Software: Build or Contract the Read
The condition is whether you sell the read or buy it.
On this page
The condition is whether you sell the read or buy it. A sponsor with one imaging endpoint should contract Calyx, Clario, Median Technologies or ICON Medical Imaging and take the read as a deliverable, because those firms sell a service with the platform included and replicating a reader network for one study is not a rational use of capital. Build only if you operate a core lab, run reads through your own reader network, or carry imaging endpoints across a portfolio. A first release then runs $120,000 to $240,000 over 16 to 22 weeks.
When is off the shelf genuinely the right call here?
Contract the read if you are a sponsor with one imaging endpoint in one study. Calyx, Clario, Median Technologies and ICON Medical Imaging all handle blinded independent central review competently, and each arrives with regulatory familiarity and a reader network already assembled. You buy the endpoint, the platform comes with it, and that is exactly the right shape of purchase at that volume. The same holds when imaging is exploratory rather than a registrational endpoint, where the read does not carry submission weight and the cost of owning infrastructure cannot be justified.
You should also understand that you cannot licence their operating system, because it is not what they sell. Every incumbent in this category is a service organisation first. That is not a criticism, it is the market structure, and it is the reason the build conversation exists at all. If someone offers to sell you a core lab platform off the shelf, ask which core labs run their own reads on it and how many criteria sets it implements today.
Do not attempt this on general imaging infrastructure either. A picture archiving and communication system, or PACS, is designed to give clinicians the fullest possible view of a patient. A core lab system is designed to give one reader a deliberately constrained view of a de-identified subject in a defined order, then prove afterwards that the constraint held. Those are opposite design goals. You can sit imaging storage underneath a core lab, but the blinding, assignment, criteria and audit layers have to be purpose built.
When does a custom build actually pay off?
Two or more of these and the case is real. You are, or are becoming, a core lab and the read workflow is your operating capability rather than a tool you use. You run imaging endpoints across a portfolio and per study service fees have become a line your finance group asks about. You have your own reader network and want to control assignment, certification and turnaround. You work in a therapy area whose scoring system the service providers treat as bespoke, so you pay a premium every time. Or you need imaging results to reach randomisation or an interim analysis on a timeline no service handoff supports.
The tipping point is straightforward. When the read is something you sell, or something your science depends on being able to change quickly, you cannot keep renting it. Sponsors amend imaging charters mid study, and a read queue cannot wait for someone else's deployment window while subjects are being scanned.
There is one operational reality to weigh before committing. The constraint in a core lab is rarely infrastructure, it is reader supply: you may have eleven qualified readers, four of whom are practising radiologists with clinics, against sponsor turnaround commitments and studies that do not arrive evenly. A platform helps you schedule that constraint. It does not remove it, and a build that assumes otherwise will disappoint.
How do they compare on the things that matter in this industry?
Criteria coverage. Response criteria read like documents and behave like rules engines. Target and non-target lesion rules, measurement types, timepoint logic, progression definitions and the conditions that trigger adjudication all differ between RECIST 1.1, iRECIST, Lugano, RANO, PCWG3 and the non-oncology scoring systems in rheumatology, hepatology and ophthalmology. A service provider absorbs that for you. A build has to configure it, and each additional implementation is a real body of work needing medical review, not just coding.
Blinding. This is the security model of the whole application, not a display preference. Reader one must not see reader two's measurements, neither may see the site read or the treatment arm, and the adjudicator usually sees both reads without reader identities. Enforce it at the query layer so a session physically cannot fetch what it must not see, then examine the leak paths design reviews miss: exports, error messages, notification emails, worklist counts that reveal a colleague's progress, and support accounts with broad production access.
De-identification. Two mechanisms, not one. Header level tag handling that preserves the temporal and spatial relationships the read depends on, plus pixel level detection of burned-in text on ultrasound captures, scanned reports and secondary capture series where no tag rule will ever reach. Missing one is a privacy incident.
Reconstructability. Two years after a submission a reviewer asks how a liver lesion was measured at week 24. You need the image and series, annotation geometry, measured value, reader, timestamp, charter and criteria versions, the reader's certification status that day, and whether the timepoint was later re-read.
What does total cost of ownership look like at your scale?
A first release is $120,000 to $240,000 over 16 to 22 weeks: multi channel intake at $18,000 to $32,000, two mechanism de-identification at $22,000 to $40,000, charter driven technical quality control at $20,000 to $36,000, reader assignment and the blinding model at $24,000 to $42,000, a blinded read workspace with measurement tooling at $28,000 to $50,000, and adjudication at $14,000 to $26,000. That covers one criteria implementation and one read paradigm.
A core lab running oncology reads for four sponsors, one criteria set, cross sectional imaging only, 180 sites and 22 readers landed at $205,000 in about twenty weeks. Phase two added a second criteria implementation at $62,000, reader certification and discordance analytics at $48,000, sponsor turnaround dashboards at $38,000, storage tiering at $50,000 and an electronic data capture feed at $40,000, taking the programme to $443,000. Those are Digital Heroes delivery figures.
Running cost is 15 to 22 percent of build per year, plus $8,000 to $20,000 annually per sponsor integration, because every feed ties you to someone else's release schedule. Storage sits outside all of it and is the only line that grows every month, since retention obligations continue for years after a study closes. Archive tiers have retrieval delays measured in hours, and that is a commercial term to agree with sponsors up front rather than discover when a re-read is requested.
What does the hybrid look like, and when is it the honest answer?
The workable hybrid is narrow scope rather than split ownership. Build the platform for the criteria set and read paradigm that covers most of your current study book, and keep contracting reads in therapy areas you touch rarely. One criteria implementation and a two reader plus adjudicator paradigm covers a large share of blinded independent central review. Prove that machinery on a live study, then add the second criteria as a configured implementation rather than a parallel build. Sending your occasional neurology or ophthalmology work to a provider who already has certified readers for it is cheaper and faster than qualifying your own.
Three things are worth deliberately deferring. Sponsor turnaround dashboards at $25,000 to $50,000 win contracts but are a sales asset rather than a delivery requirement, and scheduled reporting satisfies most sponsors for a year. Re-read directive versioning across the entire read record is heavy engineering, so if directives are rare, handle them with a documented operational process first. And storage tiering can wait until volume makes the bill visible, provided you have designed the tiers on paper so the migration is not a rewrite.
Whatever the scope, budget four to six weeks of piloting with a small group of your actual readers before the first study goes live, and expect at least one substantial change to the read form out of it. The gate on go live is not software, it is reader acceptance. Radiologists who read for a living will abandon a workspace slower than the one they use in clinic, and a core lab whose own readers route around its platform has built nothing.
Which should you choose, by operator size and stage?
Sponsor with one imaging endpoint. Contract the read. Calyx, Clario, Median Technologies or ICON Medical Imaging. No software decision to make.
Sponsor with exploratory imaging across a few studies. Contract, and negotiate data return terms carefully instead. What you want is the annotated read record and the images in a form you can retain, because that is the asset, not the platform.
Sponsor with imaging endpoints across a portfolio, fees now a visible line. Price a first release at $120,000 to $240,000 against three years of per study fees. If the criteria you need are one or two sets, the arithmetic often works. If they are five, it usually does not.
New core lab with a reader network. Build, scoped to one criteria set and one paradigm. This is the case the first release band was designed for, and $205,000 is a realistic expectation rather than a floor.
Established core lab competing on turnaround. Build the full platform, and prioritise reader certification and discordance analytics before the sponsor dashboard. A rising adjudication rate usually signals charter clarity or reader training rather than the drug, and it is a number sponsors will ask about.
Whichever way you go, settle in writing before kickoff that you own the repository, the image storage accounts, the infrastructure and the validation package. A system producing endpoint data falls under 21 CFR Part 11, and image retention obligations outlast software suppliers, so portability is not a negotiating point.
If you would rather scope this before committing budget, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. 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.
- 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) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
- In an October 2025 survey of 530 small-business employers (conducted by TechnoMetrica, October 3-9, 2025), 88% reported using AI tools and 73% said those tools had been important to their competitiveness and growth over the past year, with 60% citing efficiency and productivity as the primary motivation for adoption (42% cited improving customer service). Source: Small Business & Entrepreneurship Council (SBE Council) (2025) →
Frequently asked questions
We are a sponsor with one imaging study. Should we build?
No. Contract Calyx, Clario, Median Technologies or ICON Medical Imaging and take the read as a deliverable. They arrive with regulatory familiarity and a certified reader network, and replicating that for a single study is not a rational use of capital. The build case belongs to organisations operating a core lab, reading through their own reader network, or carrying imaging endpoints repeatedly enough that per study fees have become a line finance asks about.
Why can we not just licence the platform Calyx or Clario use?
Because they are service organisations first and the platform is not the product. You contract the read, and the software comes with it. That arrangement suits a sponsor with one endpoint and suits nobody trying to operate a core lab, since the operating system you would need is not for sale. If a supplier offers you a packaged core lab platform, ask which core labs run their own reads on it and how many criteria sets it implements today.
Can we run a core lab on a hospital PACS or a vendor neutral archive?
No, for structural rather than technical reasons. A picture archiving and communication system is designed to give clinicians the fullest possible view of a patient. A core lab system is designed to give one reader a deliberately constrained view of a de-identified subject in a defined order and then prove the constraint held. Those goals are opposites. Imaging storage can sit underneath, but blinding, assignment, criteria and audit have to be built for the purpose.
How long before the first study can go live on a build?
Sixteen to twenty two weeks of development for the first release, then four to six weeks of piloting with a small group of your actual readers. Expect at least one substantial change to the read form out of that pilot. The gate is reader acceptance, not code. Radiologists abandon a workspace slower than the one they use in clinic, and a platform your own readers route around has produced nothing.
What does it cost to move a study off our current imaging provider?
Mid study, more than most people expect, and it is rarely worth it. You need the images, the completed read record with annotation geometry and provenance, the charter and criteria versions in force, and reader certification evidence, all in a form a regulator would accept years later. Negotiate that return at contract signature rather than at exit. Between studies the switch is straightforward, which is why the practical moment to change is a programme boundary.
What happens if our imaging provider raises its per study or per read fees?
Your exposure grows exactly as your imaging programme does, and your position is weak because the images, the read history and the reader certifications sit with them. The hedge is scope rather than scale: build for the one criteria set and paradigm covering most of your study book, keep contracting the therapy areas you touch rarely. That leaves you buying a service you can price against alternatives rather than one you cannot leave.
Why does each response criteria implementation cost so much?
Because a criteria set reads like a document and behaves like a rules engine. Timepoint definitions, target lesion selection, measurement constraints, progression logic and adjudication triggers each carry edge cases that only surface on real studies, and each implementation needs medical review rather than only coding. Expect $35,000 to $90,000 per criteria set depending on measurement complexity and modality span. It is the dominant cost term in this category.
Can models do the lesion measurement in a regulated endpoint?
Only as reader confirmed assistance, and only where the imaging charter pre-specifies it. Pre-populated segmentation a reader adjusts and approves saves real time, but the reader remains the decision maker and the record must show what was proposed, what changed and who signed. Where models earn their place uncontroversially is detecting protected health information burned into pixels, automated technical quality control against acquisition parameters, and workload forecasting for reader assignment.
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.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
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.
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.
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.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
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 Reyansh.
iOS Lead · Delhi · 1 post on the site
Published · Last updated .
