Anti-Doping Compliance Software: Build the Operations Layer, or Stay Inside ADAMS
The threshold is roughly 500 samples a year, combined with one question: do you plan and justify your own test distribution, or do you execute someone else's.
On this page
The threshold is roughly 500 samples a year, combined with one question: do you plan and justify your own test distribution, or do you execute someone else's. Below that line, stay inside ADAMS with disciplined procedures and spend the budget on more tests, because more tests is a better anti-doping programme than better software. Above it, and particularly if you manage collection personnel directly or take cases to hearing, the operations layer around ADAMS is worth building, at $80,000 to $500,000 depending on how far you go.
When is off the shelf genuinely the right call here?
This category has an unusual shape, so start with the honest structural fact. ADAMS is the system of record required for whereabouts filings, results and results management data exchange. You will use it whether you build anything or not. There is no licence to displace and no vendor to escape, which means the usual comparison of subscription against build does not apply. The real question is whether the manual surround you have wrapped around ADAMS is costing you more than replacing it would.
For a large share of sports bodies, it is not. Stay where you are if this describes you. You test a few dozen athletes a year. You work almost entirely in competition. You use an external service provider for collections, so mission logistics, officer accreditation and chain of custody sit with them under contract rather than with you. Your results management is handled by a national body or a hearing service rather than in house. And you have not had a case turn on documentation.
In that situation ADAMS plus a well kept set of procedures is the right answer, and we say so to organisations who arrive expecting a quote. A programme that spends $150,000 on software instead of on collections has made itself worse at anti-doping while feeling more organised.
There is a second thing to check before commissioning anything. Ask whether a regional body or a group of partner federations already operates shared operational tooling you could join. Shared operations across several programmes is materially cheaper than parallel builds, and the genuinely local part is usually only the risk model. Programmes skip this question because building feels more like independence, but joining a shared platform is not a loss of independence when the system of record is mandated anyway.
When does a custom build actually pay off?
When at least two of these hold.
- You plan and justify your own test distribution. If the model deciding who gets tested is yours, it currently lives in one analyst's spreadsheet, and nobody can reconstruct six months later why one athlete was tested three times and another not at all. That is a governance exposure, not an inconvenience.
- You manage collection personnel directly. Accreditation with expiry, gender and language constraints, conflict of interest declarations, geographic base, kit stock by lot number, availability and contractor payment. That is workforce management with compliance attached, and it is usually run on email and a phone.
- You handle results management through to hearing. Especially if you have had a case where documentation rather than science decided the outcome, or where an evidence bundle took three weeks to assemble by hand from four sources.
- You receive and act on intelligence. Whistleblower material, customs referrals and passport patterns need compartmentalised storage with source protection, not a shared inbox and good intentions.
- You operate across sports and jurisdictions. Where sanction rules, privacy obligations and language requirements differ genuinely, a single process cannot express both and the workaround is a person holding the difference in their head.
The tipping point is evidentiary rather than operational. A programme whose credibility rests on paper forms and one person's institutional memory carries a risk that grows with every case it brings. That is a board argument, not an information technology one.
How do they compare on the things that matter in this industry?
Four comparisons decide this, and none of them concern reporting dashboards.
Explainability of the plan. A spreadsheet cannot be queried or audited, so when a programme is reviewed, or an athlete's counsel asks whether testing was targeted improperly, you have a memory rather than a record. A built plan carries named weighted risk factors, computed athlete scores with visible inputs, coverage tracked against plan by discipline and analysis type, and every deviation recorded with a reason and an approver. It also exposes what spreadsheets hide, which is the discipline nobody has tested out of competition in fourteen months.
Tamper evidence. The distinction that decides arbitrations is between a log you can edit and a record you cannot. Append only custody events, corrections written as superseding entries rather than overwrites, hashed sequences, and scanned rather than typed kit and sample codes. An audit table an administrator can update is not evidence, and opposing counsel will say so correctly.
The rolling twelve month window. Three whereabouts failures within a rolling twelve month period constitute a rule violation under the Code. That means an attempt record the collector cannot backdate, a notice with delivery evidence, a response window, review by someone other than the collector, and a live position showing what expires when. Filing failures detected at the deadline rather than during a quarterly sweep.
Offline field capture. A no advance notice mission at a residential address at six in the morning is exactly where connectivity fails. Signature capture, photographs and durable local storage that survives the application closing, with identifiers generated on the device so sync cannot duplicate a mission. A spinning icon on a doorstep becomes a paper form, and a paper form becomes an argument.
What does total cost of ownership look like at your scale?
Two bands and a running cost.
A focused first release covering the test distribution plan with risk scoring, mission and officer assignment, offline field capture of the doping control form, and append only chain of custody through to laboratory dispatch runs $80,000 to $170,000 and ships in 14 to 20 weeks in Digital Heroes delivery experience. That version retires the planning spreadsheet and makes the custody record defensible, which are the two things a hearing tests.
A full platform adding an athlete whereabouts application, officer scheduling and payment, therapeutic use exemption workflow with panel review, compartmentalised intelligence handling, results management through to hearing and global data exchange runs $200,000 to $500,000 across 8 to 14 months. A national programme collecting roughly 2,400 samples a year with sixty contracted officers and three accredited laboratories lands near $498,000 across both phases, split $162,000 and $336,000.
The line most programmes misjudge is the athlete whereabouts application at around $72,000, with its failure workflow a further $54,000. It sounds like a form and it is the most legally consequential form your athletes will ever complete on a phone.
Running costs are permanent and specific. Evidence storage is not database rows: photographs, signed forms and custody attachments accumulate per sample and must stay retrievable and verifiable for years. Mobile device management for contracted officers, including remote wipe for a device lost before sync, is a standing obligation. Continuing engineering runs roughly a sixth of build cost annually as standards are revised and laboratory formats change. Add annual field application training, because turnover among contracted collection personnel is normal and an officer improvising around a form is a custody risk.
Amortised over five years plus engineering, a $498,000 platform is roughly $180,000 a year. Set that against your surround cost and the value of a case you lose on documentation.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is not one option among several. It is the only shape that exists, because ADAMS is not going anywhere. Every build here is already buy the platform and build the thin layer, and the real question is how thin.
The thinnest useful version is the plan and the evidence bundle. Build the test distribution plan as a governed object and the assembly of a hearing file from whatever sources you already have, and change nothing else. That is a fraction of a first release and it addresses the two failures that reach a board: testing you cannot justify, and a case file assembled by one irreplaceable person over three weeks.
The next version adds field capture and custody, which is the $80,000 to $170,000 release. Keep collections outsourced if they already are, and specify in the contract that your service provider's custody data flows to you in a structured form. A provider unwilling to agree that is a provider whose evidence you cannot independently produce.
The fullest hybrid keeps ADAMS for filings and exchange, keeps an external provider for collections in regions where you have no officers, and builds only planning, intelligence separation and results management in house. Many mid sized programmes should stop exactly there.
The hybrid becomes dishonest when it is used to defer compartmentalisation. Intelligence handling half built, with user roles standing in for real separation, is worse than not building it, because it creates an impression of protection that a source is relying on.
Which should you choose, by operator size and stage?
Plainly.
- Federation, a few dozen athletes, in competition testing, outsourced collections. Stay in ADAMS. Write better procedures. Spend the money on tests. Nothing on this page changes that answer.
- Growing programme, 500 to 1,000 samples, planning your own distribution. Build the plan first, as a standalone piece. It is the smallest project here and it converts an unexplainable spreadsheet into something you can defend in a review.
- National programme, over 1,000 samples, officers you manage directly. Build the first release: planning, missions, offline capture and custody. Field it with a subset of officers for a full quarter before the whole roster.
- Programme taking cases to hearing, or receiving intelligence. Go to the full platform, phased across two funding years. Lead phase two with whereabouts, because that is where the legal exposure concentrates, then therapeutic use exemptions and intelligence, with results management last since by then the evidence it assembles is already being captured properly.
- Multi sport or multi jurisdiction body. Build, and treat the jurisdiction difference as a data model question rather than a configuration one. Programmes that discover in month six that sanction rules differ structurally rebuild rather than adjust.
One discipline regardless of stage. Before anyone quotes, get the risk model written down and approved. It usually exists only in one analyst's head, writing it down forces decisions that were previously implicit, and that exercise is worth doing even if you never commission a line of code.
When the shortlist is down to two and you need a tiebreaker, 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. 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.
- The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- The average number of formal learning hours used per employee fell to 13.7 in 2024, down from 17.4 in 2023, a decline the report attributes partly to a shift toward informal and on-the-job learning not captured in the formal-hours metric. Source: Association for Talent Development (ATD) (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
What does it cost to move off spreadsheets and an external provider?
The engineering is 14 to 20 weeks and $80,000 to $170,000 for the operations core. The switching cost people underestimate is contractual and human rather than technical: recovering custody data held by an external collection provider in a usable structured form, and building an officer roster you previously rented.
Before you commit, check your service provider agreement for what data you can extract and in what format. If it does not say, ask now rather than at the point you want to leave, because that clause is the whole switching cost in one sentence.
What happens if our collection provider or shared platform changes its terms?
Judge this on grounds you can verify rather than speculation. The two that matter are data portability and per mission economics at your growth rate. Confirm in writing that mission records, doping control forms, custody events and attachments are exportable in a documented structured form on demand.
If a shared regional platform changes its governance or scope, the exposure is different: your risk model and your athlete data sit inside somebody else's decision. That is acceptable when your programme is small and it becomes a governance question once your programme is large enough to be reviewed on its own record.
How long does an anti-doping build take before it is usable in the field?
Three weeks of discovery, then 14 to 20 weeks to first release. The schedule risk sits in discovery rather than engineering, because the weighting logic that decides who gets tested exists only in one analyst's spreadsheet and head, and writing it down for approval forces decisions that were previously implicit.
Field the release with a subset of officers before the whole roster. Offline capture has to survive a doorstep at six in the morning, a stairwell with no signal, and a device that runs out of battery before sync, and none of that is provable in a test environment.
Does building anything replace ADAMS?
No, and any proposal implying otherwise should be treated as a warning about the vendor rather than the plan. ADAMS is the system of record required for whereabouts filings, results and results management data exchange, and it stays in every scenario.
What a build adds is the layer it was never meant to be: your own test distribution planning, officer management and payment, intelligence with structural separation, and the evidence bundle a hearing panel actually receives. The two coexist rather than compete, which is why there is no licence saving to offset the build.
Can we keep outsourcing collections and still build?
Yes, and for many mid sized programmes that is the right shape. Build planning, intelligence separation and results management in house, keep an external provider for collections in regions where you have no officers, and keep ADAMS for filings and exchange.
The one thing to insist on is that the provider's custody data reaches you in a structured form rather than as scanned forms. Your evidence bundle is only as good as what you can produce independently, and a provider who will not agree to that is worth reconsidering on that ground alone.
Why is the athlete whereabouts application the largest single line?
Because it carries a career level consequence in a phone form. In the worked example it came to $72,000, with the failure workflow behind it a further $54,000. Three whereabouts failures in a rolling twelve month period constitute a rule violation under the Code.
Every ambiguity in that interface becomes an argument later. The filing experience, the delivery evidence, the sixty minute slot handling and the rolling window calculation all have to be right, and getting them nearly right produces cases you cannot pursue.
Is a standalone test distribution planning tool worth building on its own?
For a programme in the 500 to 1,000 sample range, frequently yes. It is the smallest project in the category and it addresses the exposure that reaches a board fastest, which is testing you cannot justify when reviewed.
Built properly it carries named weighted risk factors, athlete scores with visible inputs, coverage tracked against plan by discipline and analysis type, and deviations recorded with a reason and an approver. It also surfaces systematic under coverage, which is the failure a spreadsheet is structurally unable to show you.
Who owns the code, the evidence and the hosting if we build?
You should hold the repository, the hosting accounts and the right to bring in another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit.
For an organisation whose independence is the product, being unable to leave a vendor is a governance problem rather than a commercial one. Evidence storage makes it sharper still: custody attachments and signed forms must remain retrievable and verifiable for years, and their availability cannot depend on a supplier relationship staying healthy.
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.
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.
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.
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.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
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.
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.
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.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
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 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 Rohan.
Director of Web Platform Engineering · Delhi · 2 posts on the site
Published · Last updated .
