Vivarium and Animal Colony Management Software: Custom Build or Off the Shelf
Buy. Under roughly two thousand cages, one species and one building, licence Climb or tick@lab and put the money into husbandry staff.
On this page
Buy. Under roughly two thousand cages, one species and one building, licence Climb or tick@lab and put the money into husbandry staff. The line moves when your per diem rate table carries exceptions no vendor billing module expresses, when several species or buildings sit under different governance, or when approved animal numbers need enforcing rather than reporting.
What RockStep Climb, tick@lab and Topaz already do well
Most facilities should licence a product, and we say that to people who arrive expecting to hear otherwise. If you run one building, one species and a handful of internal accounts, the annual fee is far cheaper than anything we would build, and the vendor absorbs upgrades you would otherwise own forever.
All three are credible and they are credible in different ways. RockStep Climb is the most modern of them and handles rodent colony structure properly: matings as records rather than notes, genotypes attached to individual animals, and a pedigree that behaves like a graph instead of a list. Its interface is the one husbandry staff adopt fastest, which matters more than any feature comparison. Tick@lab covers census, ordering, health surveillance and reporting across large multi-species facilities and is used at genuine scale, so if you are running a thousand-plus cage barrier operation it will not fall over. Topaz Technologies has been in animal facilities longer than either and knows the domain deeply, including the workflows around procurement and veterinary care that newer products skim.
None of them is a bad choice on capability. What they share is that each shipped a billing module built around a rate model the vendor chose, and a protocol relationship that assumes your approved numbers live in a document somewhere.
Buy if your facility is stable, your finance office is content to receive a spreadsheet, and your principal investigators do not dispute invoices often enough for anyone to have counted the hours. In that situation the integration work that justifies a build has no payoff, and a build is a way to spend $100,000 arriving where you already are.
Where they stop: the per diem exception and the protocol counter
It is 6:20 in a barrier room. A technician walks a rack marking cages that need changing, cages with a new litter, and one cage card reading five animals when there are seven in the box. That card printed three weeks ago. The facility census says something different again, because the last three weanings were emailed to the manager on a Friday and never entered. The following Friday the per diem invoice for that investigator's grant goes out on the spreadsheet number, and it is wrong in the direction that costs the facility money.
Per diem is where the leak sits, and it is specific in a way no product models. The daily charge depends on cage count rather than animal count, so a cage emptied on the fourteenth bills fourteen days and not thirty. Then come the exceptions every facility actually runs: a grace period on newly weaned litters, a reduced rate for quarantine, a flat charge for a procedure room, a core subsidy on a pilot study, and a chargeback split across two funds for a collaboration. Rates change at the start of your fiscal year through a rate approval process finance controls, and the resulting charge has to land in the general ledger as a journal entry against a fund and account string in a format your finance office dictates rather than the vendor's.
The second gap is the protocol boundary. Approved animal numbers, species, pain category and expiry live in a protocol management system, frequently a different product entirely, while the animals live in the colony system. Nothing joins them continuously, so the census passes the approved number on a Tuesday and nobody sees it until a semiannual review. Exceeding an approved number is reportable, and it almost never happens through a decision. It happens through breeding, weeks before anyone runs a report.
The arithmetic: licence per cage versus the cost to build
Do this with your own invoices rather than a vendor's list price.
Take your annual licence, support and hosting, plus any per-user charge, and divide by your average cage count. Facilities that have shown us their renewals usually land somewhere near $12 per cage per year at mid scale, with the figure falling as cage count rises. At that rate 4,000 cages is $48,000 a year and 8,000 cages is $96,000.
A first release covering census with dated events, cage cards on your printers, live protocol counters and the per diem engine with a general ledger export runs $70,000 to $150,000. Take the middle at $110,000, add migration, add year two support, and the two-year figure is roughly $151,000.
On licence fees alone the crossover therefore sits near 6,300 cages. That is the wrong number to plan against, because the licence is not what this costs you. Add the days a month somebody spends correcting invoices, and add the charges that never get raised at all. Facilities bill conservatively, because the safe error is to leave a charge off rather than to invoice a principal investigator wrongly and spend a week arguing. Across the animal facility builds we have delivered, recovered revenue in the first full year has repeatedly covered a meaningful share of the build, purely from charges previously dropped. Count that and the crossover moves to somewhere near 3,500 cages.
What a custom build actually costs
- First release: $70,000 to $150,000 in 14 to 20 weeks. Cage and animal records with dated event history, cage card design and printing on your hardware, protocol assignment with live counters and threshold alerts, and a per diem engine with effective-dated rates and a general ledger export in your finance system's format.
- Full platform: $180,000 to $420,000 phased across 8 to 14 months. Adds breeding and genetics with genotype import, health surveillance and sentinel results, ordering and quarantine, an investigator portal and protocol management integration.
Migration runs 10 to 25 percent of the build, and vivariums sit high in that band. Census cannot simply be imported as a running number, because the whole point is that it derives from dated events, so historical weanings, transfers and deaths have to be reconstructed well enough that a past month can be rebilled. Year two runs 15 to 20 percent of the build annually.
What pushes the number up: several species with genuinely different husbandry and reporting, because non-human primates, large animals and aquatics are not rodents with a different label. Several buildings or institutions on one system, since rate tables and governance then differ per site. Cage card printer and rack reader hardware, which is the piece technicians touch daily and therefore the piece that decides adoption. Individual animal identification by barcode or radio frequency tag. And integration with an existing protocol management platform, which is a real interface project rather than a feed.
What keeps it down: start with rodents in one building, your current rate table, and the reports you send today rather than the ones you wish you had.
The four situations where building wins
- Regulatory fit. Three obligations attach to the same cage at once: welfare under the Animal Welfare Act and the Public Health Service Policy, financial chargeback to a named fund, and scientific traceability for the study. Approved animal numbers, pain category and protocol expiry need to be live constraints that block a weaning, not fields in a document reviewed twice a year. Facilities carrying AAALAC International accreditation and filing the annual USDA report on covered species feel this hardest, because the census has to be reconstructable for any past date.
- Scale economics. Cage count past roughly 3,500 once invoice correction time and dropped charges are counted honestly.
- A workflow that is your competitive advantage. Your per diem rate structure is the clearest case. It is negotiated, exception-heavy and specific to your institution, and it is also how the facility funds itself. Encoding it properly, with effective dating and a restatement path for a corrected month, is a build.
- Integration sprawl across three or more systems. A protocol management platform, a general ledger, a genotyping vendor's result file and a cage card printer are four unrelated classes of problem. The most common trigger we see is an incumbent vendor declining to integrate with the protocol system your institution just bought.
How to decide in a week
Run two exercises with people who already work there.
First, pick a cage that emptied mid-month four months ago and ask your team to produce the exact charge that should have been raised for that month, showing the dated census events behind it and the rate in force on those dates. Then ask what happens if that month now needs restating. If the answer involves a spreadsheet and a person's memory, your billing is not auditable, and it is also probably undercharging.
Second, take your three largest breeding protocols and ask for the current count against approved numbers, split between animals used and animals currently alive. If nobody can produce both denominators today, the protocol ceiling is not being watched and you are relying on luck between reviews.
Then move to a paid discovery phase. Ours runs two to three weeks and produces a signed product requirements document covering the cage, animal, protocol assignment and event model, the per diem rules with their exceptions written down, the exact general ledger file format, the cage card layout and printer, and acceptance criteria. That specification is what makes a fixed price stay fixed, and it belongs to you whether or not we build it.
Digital Heroes is wrong for you if you want a hosted product with a monthly fee, or a supplier who will run your facility reporting as a service. We build systems the institution owns. Our India LLP, US LLC and UK LTD entities mean the intellectual property assigns under your own law. More than fifty specialists, in-house products including Section Vault and ShopScore, a named team you meet before signing, and a record checkable 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.
- 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) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
Frequently asked questions
How much does custom vivarium software cost for a mid-sized facility?
A first release covering census, cage cards, live protocol counters and per diem billing with a general ledger export runs $70,000 to $150,000 over 14 to 20 weeks. Adding breeding and genetics, health surveillance, ordering and an investigator portal takes the total to $180,000 to $420,000 across 8 to 14 months. Budget 10 to 25 percent again for reconstructing historical census events.
Can we keep our protocol management system and build only the colony side?
Yes, and that is usually the right shape. Institutions rarely want to replace a platform the compliance office already runs, so the build holds animals, cages and events and reads approved numbers, species, pain category and expiry across an interface. What matters is that the counter updates as weanings and transfers happen rather than nightly, because a ceiling breach discovered the next morning is still a breach.
Who owns the code and the animal records if we commission a build?
The institution does, from the first commit, and it should be written into the contract before kickoff. That covers the repository, the cloud accounts, the data and the right to hire another firm without permission. Digital Heroes assigns through its India, United States and United Kingdom entities so the transfer happens under the buyer's own law rather than a supplier's.
How long does it take before husbandry staff are actually using it?
Fourteen to twenty weeks to a first release they use on day one rather than a pilot. The adoption risk is not the software, it is cage cards. If cards print slowly, on the wrong stock, or with a barcode that will not scan through sanitiser on a glove, technicians revert to paper within a fortnight and everything downstream stops being trustworthy. Prove printing in week three.
What happens if a past month of per diem charges has to be restated?
A build should treat this as a first-class path rather than an exception. Charges derive from dated census events and the rate table in force on those dates, so a restatement recomputes the month, produces a delta, and posts a correcting journal with an approver and a reason recorded. If a product cannot show you that path in a demonstration, your finance office will reject its output within two billing cycles.
Is it worth building if our facility runs a single species in one building?
Almost certainly not. That is the profile the commercial products model best, the licence will cost a fraction of a build, and the vendor carries the upgrade burden. Revisit the question if you add a second building under different governance, take on aquatics or large animals, or find that invoice corrections have quietly become somebody's regular week.
What is the difference between colony management and laboratory information management software?
A laboratory information management system tracks samples and assay results through a workflow. Colony management tracks living animals whose identity changes while you hold them, through breeding, weaning, transfer between protocols and death, with a census that must be reconstructable for any past date. Sample tracking assumes stable objects. Animals are not stable objects, which is why general laboratory platforms fit this badly.
Can genotype results from a core facility be imported automatically?
They should be, because retyping them is where errors enter the pedigree. Results usually arrive as a spreadsheet from a core or a commercial vendor, so the build needs a mapping from the sample identifier on that file back to the individual animal, with the assay name and result date preserved. Ask any developer how they handle a file whose column headers change between runs.
Should we replace our finance system as part of this?
No, and any firm suggesting it is overreaching. The build computes the charge and produces a journal entry file in the exact format your finance system ingests, including the fund and account string convention your office dictates. That export is the single most requested feature by the person who signs invoices, and it is also the cheapest part of the project to get right if it is specified early.
What happens if the estimate turns out to be wrong once we start?
That is what the paid discovery phase is for. It produces a signed specification covering the data model, the per diem exceptions written down individually, the general ledger format, the protocol interface and acceptance criteria, and the fixed price is fixed against that document. Changes afterwards are priced in writing before work starts. Anyone quoting this category without discovery has not asked about your rate table.
Is a custom internal tool secure enough for HR records and financial data?
A properly built custom tool is generally safer for sensitive data than the shared spreadsheet it replaces, because you get role-based access, audit logs, encrypted storage, and the ability to cut one person's access instantly. Ask the agency specifically for encryption in transit and at rest, permissions down to the field level, and an audit trail showing who viewed or changed each record. If HIPAA, GDPR, or SOC 2 expectations from enterprise clients apply to you, raise it before the quote, because compliance features add real scope.
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.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
How long does it take to build an internal tool from scratch?
A working first version typically ships in 4 to 8 weeks, and larger multi-module tools run 10 to 16 weeks. Across Digital Heroes internal tool projects the schedule splits into roughly one week of process mapping, 3 to 6 weeks of build, and 1 to 2 weeks of testing with your actual staff. The most common delay is not development but waiting on the client for sample data and workflow decisions, so name one internal owner before kickoff.
How do I know when spreadsheets are no longer enough to run my operations?
Replace the spreadsheet once more than three people edit it, versions travel by email, or a single broken formula could cost real money. Other reliable signals: staff keep personal shadow copies, month-end reporting takes days of manual assembly, and nobody can say who changed a number or why. In Digital Heroes discovery calls the tipping point is almost always a specific expensive error, a mispriced quote, a missed order, or payroll built on a tab someone sorted wrong.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools 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 internal tools 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 .
