Build vs Buy Laboratory Animal Facility Management Software: Census, Per Diem and the Counting Policy
Under about 1,500 cages, single species, no breeding colonies, buy SoftMouse or a modest Climb deployment and keep a disciplined spreadsheet.
On this page
Under about 1,500 cages, single species, no breeding colonies, buy SoftMouse or a modest Climb deployment and keep a disciplined spreadsheet. Build above roughly 8,000 cages with active colonies, per diem billed to federal awards and accreditation to maintain, because at that size your counting policy, your rate structure and your cage card format are institution specific and no product ships them.
When buying is obviously right
SoftMouse serves individual laboratories well and costs almost nothing against a build. RockStep Climb is genuinely good on colony and research data. For a facility under roughly 1,500 cages, running one species, with no breeding and per diem charged to a handful of accounts, either product plus an organised technician will carry you comfortably. Spend the difference on cage wash capacity, which is the constraint most small vivaria actually have.
a-tune tick@lab and Topaz Elements are the enterprise options and they do real work. If your facility runs conventional rodent housing with stable billing and neither of those things is generating disputes, replacing a working enterprise system is expensive and rarely justified. The honest question is not whether the product is good. It is whether the parts that hurt you are parts a product can ship.
There is a third case for buying that people talk themselves out of. If your institution's animal counting policy has never been written down, do not commission software. Whether breeders count against the same protocol allocation, whether you count animals produced or animals used, and how a transfer between protocols is attributed are decisions with more than one defensible answer, and they belong to your committee rather than to a developer. Settle them, in writing, and you may find your existing system was capable of applying them all along.
The point where your own rules become the product
A vivarium census is not an inventory number. It is a regulatory statement. Approved animal numbers on a protocol are a limit, reporting to the federal authority is done by pain category with counts, and housing density turns a cage count into a welfare question. That is why the ordinary tolerance for an approximate number does not apply here.
The build case starts when reconciliation is human. A veterinary technician notices a rack that looks wrong, counts cages, multiplies by average occupancy and lands well above the number the protocol approved. That is a deviation, it goes to the committee, it appears in the semiannual programme review, and if a site visit is near it becomes a finding about institutional oversight rather than about one laboratory's arithmetic. Software that warns at eighty percent of an allocation turns that into a protocol amendment filed in good time.
The second trigger is breeding. A transgenic colony is a pedigree, not a population, and a laboratory maintaining several lines produces hundreds of animals a month, most of which never enter an experiment. Colony tools model pedigrees and facility systems model rooms and cages, so most institutions end up with both and the facility never sees demand coming. Holding the pedigree and the census in one model means a litter recorded at birth becomes projected census with a weaning date attached, and cage wash sees three weeks ahead.
The third trigger is disputes. When a principal investigator challenges a per diem charge and nobody can settle it from records, you are not arguing about money, you are demonstrating that your census data does not support the invoices you issue.
A fourth trigger is species mix. Packaged products tend to serve rodent housing well and aquatic systems poorly, or the reverse. Once you run zebrafish tanks alongside mouse racks and both need census, per diem and health records, the institution ends up operating two products with two logins and reconciling them in a spreadsheet, which reintroduces every problem the software was bought to remove.
What each path costs, and who ends up paying
Packaged facility systems are commonly priced by cage count or by module, which means the licence grows as the facility grows and a large colony expansion arrives with a software invoice attached. Model that over five years rather than accepting a first year figure.
These are Digital Heroes bands across more than 2,000 delivered projects. A first release covering event based cage and animal census, barcode scanning at the rack, protocol allocation tracking with threshold warnings and per diem charge generation with account validation runs $70,000 to $150,000 and ships in 12 to 18 weeks. A full platform adding breeding colony and pedigree records, genotyping workflow, health surveillance and quarantine, veterinary treatment and procedure logs, cage card printing and federal annual reporting runs $180,000 to $420,000 phased over 7 to 12 months.
The largest multiplier is species class. An aquatic facility running zebrafish is a genuinely different model from rodent housing, and a system that does both properly is two systems sharing a login. Integration with the protocol system matters too, because approved numbers must arrive from there rather than being retyped, and integration with finance matters because per diem has to post.
On the buy side, add the annual licence, the implementation, and the staff time currently spent reconciling census by hand each month. Most facilities have never measured that last figure and are surprised by it.
The line items that appear after go live
Cage cards. This sounds trivial and it is the detail that most often extends a schedule. Layouts vary by protocol, label stock has to survive cage wash humidity and handling, and printers must sit where technicians actually work rather than where the network drop was convenient. Specify your existing printers and label stock during discovery, not afterwards.
Cost transfers. Per diem charges land on sponsored awards. A charge that posts to an expired award becomes a cost transfer, and cost transfers on federal awards attract audit attention out of proportion to their size. Validating the account period and balance before posting is a small feature that prevents a recurring administrative burden nobody attributes to the software.
Reporting deadlines. The annual report to the federal authority falls on a fixed date each year and the semiannual programme review recurs on its own clock. If your accreditation site visit sits inside the next eighteen months, that date, not the vendor roadmap, is the real project deadline, and it argues for shipping census and procedure capture first rather than colony features.
Governance time. If your counting policy is not written, agreeing it is a committee exercise measured in weeks of calendar time rather than hours of work. Start it before the project, in parallel with procurement, or it becomes the critical path.
Historic data. Years of census in spreadsheets with renumbered cages and closed protocols will need a human deciding what maps to what. Budget engineering days plus facility director hours, and expect the second to be the slower half.
A census reconciliation test
Run this over one week with your own staff and the answer will be obvious.
- Pick three active protocols and ask, without preparation, how many animals currently count against each approved number and by which rule. If three people give three answers, your policy is unwritten and that is the first fix regardless of software.
- Physically count one room and compare it against the system. Record the variance and how long the count took.
- Take last month's per diem charges for one busy laboratory and try to defend three of them from records alone, without asking anybody what happened.
- Ask what a sentinel positive would require: name the rooms, racks and animals that moved in and out over the last ninety days, with dates.
If the room count matches, the charges defend themselves and the movement query is answerable, your existing system is fine and you should stop here. If the movement question sends someone to a filing cabinet of transfer forms, event based history is the build, and it fixes the billing disputes and the allocation warnings at the same time because all three are one data problem.
Price the failures honestly before you present the case. A month of disputed per diem written off to preserve a relationship, the technician hours spent on physical counts that only exist because nobody trusts the record, and the days three people would lose reconstructing exposure history from paper. Those numbers are the business case, and they are usually larger than the facility expects because none of them has ever been recorded against a budget line.
Sequencing, and the governance to settle first
Write the counting policy before you write the requirements. Then sequence: census with scanning at the rack and protocol allocation first, per diem generation with account validation second, health surveillance and movement history third, colony and genotyping fourth, reporting last so it is built against real captured data rather than assumptions.
Insist on a written product requirements document before any code. In a vivarium that document is where the institution finally records how animals are counted, what a cage record actually is over time, and which reports must generate rather than be assembled. Digital Heroes runs this way as standard, with 50 plus people and more than 2,000 projects delivered, and contracts through an India LLP, a US LLC or a UK LTD so a university purchasing office gets a domestic entity and a clean intellectual property assignment. The team publishes openly on YouTube, where the channel carries 2.5 million subscribers, which is a fair way to judge how a partner communicates before you procure.
Put ownership in the contract before kickoff. The repository, the infrastructure accounts and the unrestricted right to hire another firm are yours from the first commit. Animal welfare records support inspection and accreditation across many years, and that history must never sit inside a system you cannot reach on your own authority.
When you are ready to turn this into a specification, 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. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- Deloitte's research found that digitally advanced small businesses experienced revenue growth nearly 4x as high as the prior year, were about 3x as likely to have exported, were nearly 3x as likely to have created new jobs, and were more than 3x as likely to have seen more sales inquiries in the last year. Source: Deloitte (research summarized by Google) (2017) →
- Retailers connecting point-of-sale and loyalty data in an omnichannel strategy reported up to 15% lower cost per purchase and nearly 20% higher incremental store revenue. Source: Deloitte (2024) →
- APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
Frequently asked questions
How much does custom vivarium management software cost?
A first release covering event based census, barcode scanning at the rack, protocol allocation tracking and per diem billing with account validation runs $70,000 to $150,000 over 12 to 18 weeks. A full platform adding colonies, genotyping, health surveillance, treatment records, cage cards and federal reporting runs $180,000 to $420,000 across 7 to 12 months. Multiple species classes are the largest cost multiplier.
How long until technicians are scanning cages?
The software side of scanning is typically ready inside the first release at twelve to eighteen weeks, and practical rollout adds a few more weeks because of hardware. Cage card layouts vary by protocol, label stock has to survive cage wash, and printers must sit where technicians work. Specify your existing printers and stock during discovery or that detail will extend the schedule after go live.
Can we migrate historic census and colony records?
Structured records import reasonably well. The slow part is human judgement: deciding which historic cage or protocol identifier corresponds to which current one after renumbering, closures and transfers. Nobody can automate that, and getting it wrong poisons every trend you build afterwards. Budget engineering days plus several days of your facility director's attention, and import colony pedigrees before census history.
What does this need to integrate with?
The protocol system, so approved animal numbers arrive rather than being retyped, and the finance system, so per diem charges post against valid accounts with a period and balance check. Building that check matters more than it sounds, because a charge landing on an expired award becomes a cost transfer, and cost transfers on federal awards draw attention far out of proportion to their value.
Who has to be involved from the institution?
The facility director, the attending veterinarian, someone from the committee office who can speak to counting policy, and a finance contact for per diem. Expect roughly a day a week between them. The unwritten counting policy is usually the critical path, so start that governance conversation in parallel with procurement rather than waiting for a developer to raise it.
Who actually builds vivarium and animal facility software?
Life sciences specialists and general custom development firms. Digital Heroes suits research institutions because work begins with a written product requirements document rather than a demonstration, so the counting policy, the cage record model and the reporting obligations get settled before code exists. Contracting through an India LLP, a US LLC or a UK LTD means a university purchasing office signs with a domestic entity.
What makes Digital Heroes different from a generic dev shop here?
The requirements document forces event based movement history into the design rather than a current location field, which is the single decision that makes containment queries, per diem disputes and allocation warnings all answerable from the same data. The firm also runs its own products, including ShopScore, HeroCheckout and Section Vault, so the team has maintained systems across years rather than only launching them.
How do we verify a development partner before signing?
Confirm a D-U-N-S registration, which institutional procurement usually requires anyway. Read the Clutch profile for reviews tied to named engagements and Trustpilot for the wider pattern. Establish which legal entity signs your contract and where. Then require the repository, the cloud accounts and the right to hire another firm in your institution's name from the first commit, written in.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
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.
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.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
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.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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.
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.
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 Theo.
UX Researcher · UK · London · 2 posts on the site
Published · Last updated .
