Zoo and Aquarium Management Software: Custom Build Versus ZIMS, ZooEasy and Tracks
Buy, and keep ZIMS whatever else you decide. For a small collection, a rescue with a modest permanent population or a private breeder, ZIMS or ZooEasy plus a clipboard is the right answer and a build would consume the curator you cannot spare.
On this page
Buy, and keep ZIMS whatever else you decide. For a small collection, a rescue with a modest permanent population or a private breeder, ZIMS or ZooEasy plus a clipboard is the right answer and a build would consume the curator you cannot spare. The case changes above roughly 400 accessions, or at any aquarium where life support data drives daily animal decisions.
What the off-the-shelf products actually do well
A sea otter transfers on Friday and your registrar has spent two weeks assembling a packet that should have been an export. That is the situation, and the answer to it is rarely to replace the systems you already run.
ZIMS by Species360 is the backbone of this profession and it earns that position. It holds the taxonomic, transaction and medical record, and much of its value is that other member institutions can read what you hold, which is what makes transfers and cooperative breeding programmes work at all. You are not replacing it, and any developer who suggests otherwise has not understood the network.
ZooEasy is genuinely good for smaller collections and private breeders, particularly on pedigree. Tracks and Animal Care Software both serve daily husbandry record keeping at institutions that want something lighter than a build. ZooMonitor, from Lincoln Park Zoo, does behavioural observation properly and is used widely. On the operational side, Gateway Ticketing and Blackbaud Altru handle admissions and membership, and Brightly or Maximo handle facilities work orders.
If you run a modest collection with a single site and no life support plant, that combination is correct and cheaper than anything commissioned. We tell institutions this during scoping calls, and it costs us projects we would rather not have taken anyway.
Where they stop: the hours between 6am and 4pm
Two workflows defeat the products in this category, and neither is about the species record.
The first is capture. A keeper notes reduced appetite on a paper sheet at 9am and types it into a system at the end of shift, or does not. That is a two to five day lag between an observation and a veterinarian seeing it. In an animal care operation that is a clinical problem wearing an administrative disguise, and it happens because entry on the existing tools takes longer than paper does with wet hands, in glare, or behind a concrete holding wall with no signal.
The second is water. An aquarium is a water treatment plant with animals in it. Sand filters, protein skimmers, ozone contact, ultraviolet sterilisation, chillers and duty and standby pump pairs, with ranges for ammonia, nitrite, nitrate, pH, salinity, alkalinity, dissolved oxygen, oxidation reduction potential and temperature that differ by system. For marine mammal pools the federal animal welfare regulations set explicit water quality requirements, including coliform sampling and pH monitoring on a defined schedule, and those records are inspected.
Your building automation system alarms when something crosses a line right now. It does not tell you that oxidation reduction potential has trended down for nine days while an ozone generator degraded, which is the pattern that actually costs you a display. No animal records product joins the sensor stream, the hand tested chemistry and the keeper observations into one timeline, because no vendor is trying to serve both worlds.
The arithmetic: per-seat licensing against a build
Pricing here is unusual, because your institutional record already sits in a shared system funded on a membership basis, while everything around it is quoted per named user.
Take your own proposals. Suppose an operational husbandry product quotes at $75 per user per month and you need logins for sixty keepers, curators, aquarists, veterinary staff and the registrar. That is $54,000 a year, plus configuration in year one and a further charge each time you add a taxon group or a site. Add the facilities system and the behavioural observation tool and most mid-sized institutions land somewhere near $70,000 recurring.
Against that, a focused first release sits at $65,000 to $140,000 once. The crossover lands close to sixty keeper and curator logins, or roughly 400 accessions, whichever you reach first, and it arrives sooner for an aquarium than a zoo because of the life support layer.
Below those figures, buy, and put the money into an extra keeper shift instead. A product that improves on somebody else's development budget is a better deal than a system frozen at whatever you could specify in one procurement cycle. Above them, the deciding number is not the licence. It is the 45 to 90 minutes per keeper per day spent transcribing paper, which you can count this week with a stopwatch and a willing team, and which for sixty keepers is a headcount.
What a custom build actually costs
These are Digital Heroes delivery bands across more than 2,000 projects. A first release covering keeper daily records, diet and enrichment delivery, training logs, exhibit records and a tablet interface built for the actual conditions runs $65,000 to $140,000 and ships in 12 to 18 weeks. A full platform adding life support telemetry, water quality trending, commissary and browse management, permit and regulatory document tracking and veterinary workflow runs $160,000 to $380,000 phased over 7 to 14 months.
Two costs that never make it into a board paper:
- Migration is 10 to 25 percent of the build. Historic daily records, diets, training histories and the binders in the mammal building. Group accessions are the hard part, because a split or merge that was recorded as a note has to become an event with a date before any historical query returns the truth.
- Plan on 15 to 20 percent of build cost annually once year two starts. Building automation systems get upgraded and change how they expose data, permit requirements shift, tablets reach end of life on a cycle nobody budgeted for, and the veterinary team asks for something reasonable that was not in scope.
What drives the number up here specifically: life support integration, because every automation platform exposes data differently and some expose it badly. Veterinary scope, since a hospital module with anaesthesia records, controlled substance logging and imaging references is close to a project of its own. The number of distinct taxon groups, because mammals, birds, reptiles, fish and invertebrates need five different record shapes. And multiple sites with animal movements between them.
The four situations where building wins
Four conditions. Two or more and the case is defensible to a board.
- Regulatory fit. Acquisition and disposition records under the Animal Welfare Act with their retention clock, marine mammal inventory reporting on its own deadline, CITES documentation for internationally protected species, controlled substance records that satisfy a Drug Enforcement Administration inspection including the biennial inventory, and accreditation evidence on a five year cycle. Those attach to animals and groups, expire, and need escalation. No product holds all of them.
- Scale economics. Past sixty logins, per-seat pricing across keepers, aquarists and veterinary staff outruns a one-time build inside three years.
- A workflow that is your competitive advantage. Identity as a chain of events rather than a row: accession, identifier assignment, group split, group merge, transfer, death, with every daily record attached to the identity as it existed that day. That is what lets a pathologist ask what a fish ate six months ago and get the right answer.
- Integration sprawl across three or more systems. The shared species record, a husbandry tool, a building automation system, a facilities work order platform and a commissary spreadsheet is five places holding one animal's day.
Not on the list: collection size alone. A large zoo with consistent record shapes and no life support plant may still be better served by buying. What breaks products is variety in the record shape, not the number of animals carrying it.
How to decide in a week
Run the transfer test. Pick one animal, ideally one that arrived from another institution, and assemble the complete packet you would send if she moved on Friday: medical history, diet as actually eaten, training record, lineage, permits and twelve months of weights. Time it, and write down every binder, drive and person involved.
If it takes an afternoon and two systems, your setup works and you should not build. If it takes a fortnight, you have measured the problem and you can multiply it by the transfers you do a year.
Second test, same week. Stand in the mammal building at the end of a shift with a stopwatch and time three keepers transcribing paper. Multiply by your keeper count and by 250 working days. Then ask the veterinary team how often they have learned about an appetite change later than they would have liked, because that is the same number expressed as clinical risk.
After that, commission a paid discovery phase. At Digital Heroes that produces a signed product requirements document before any code is written, covering the identity model including groups, the life support integration boundary, the regulatory document layer and acceptance criteria. The institution keeps that document whichever firm it hires, which matters when a curator or a director changes. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under law your own counsel reads, and you meet the named engineers before signing.
We are the wrong firm if you need people walking your holding areas weekly during design, or a supplier who will also maintain your plant room hardware. We build the software, integrate it with what you already run, and hand over the repository and the accounts.
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.
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- 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) →
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
Frequently asked questions
Should any institution replace ZIMS?
No. Its value comes substantially from the fact that other member institutions can read what you hold, so a private replacement isolates you from transfers and cooperative breeding programmes. Build or buy the operational layer around it instead, covering keeper daily records, water quality, diets, enrichment, permits and veterinary workflow, then agree a clearly bounded flow between the two rather than an ambitious two way synchronisation.
How should a group accession that splits be modelled?
As a chain of events rather than a row with a quantity. Accession, identifier assignment, split, merge, transfer and death all carry dates, and every daily record attaches to the identity as it existed on that date. Ask a developer to draw this before you talk price. If they sketch one animal record with a count field, they cannot answer a question about a fish that changed exhibits in March.
Can software read our life support control system?
Usually yes, by reading the existing automation platform rather than replacing it, though every system exposes data differently and some expose it poorly. The value is holding sensor streams, hand tested chemistry and animal observations in one timeline. The feature worth paying for is trend alerting on rate of change rather than threshold breach, because a slow drift over nine days is what costs you a display.
Who owns the code and the animal records if we commission a build?
You should own the repository, the cloud hosting accounts and the unrestricted right to hire another firm, written into the contract before kickoff. At Digital Heroes the client owns the code from the first commit. Animal records carry lifetime and cross institutional significance, so a system your institution cannot reach without a vendor's cooperation is a governance risk rather than a commercial inconvenience.
Why do keepers keep using paper after we buy a system?
Because entry takes longer than paper does. Keepers work with wet or gloved hands, in glare or in a chill room, often with forty seconds between tasks and no signal behind concrete. Any system that ignores those constraints becomes a transcription burden at the end of shift. Offline first capture, large touch targets, defaults carried from yesterday and voice notes are what actually move an institution off paper.
What is the difference between ZIMS and ZooEasy?
ZIMS is the institutional and inter institutional standard, holding taxonomic, transaction and medical records other member institutions can read. ZooEasy targets smaller collections and private breeders with strong pedigree management, and carries no expectation of running life support plant, a veterinary hospital or a public facility's regulatory paperwork. Public institutions generally keep ZIMS and add operational software around it rather than choosing between them.
How long before a first release is usable on the floor?
Twelve to eighteen weeks, then a training period timed around your quieter season rather than a school holiday peak. Roll out one building at a time. Adoption is decided by the daily record screen and nothing else, so pilot it with the keepers most sceptical about tablets rather than the most enthusiastic, because the sceptics find the problems that matter.
Can it track permits and renewals reliably?
It can, and the common failure is not a missing permit but one sitting in a cabinet with nobody watching the renewal after a staff change. Attach each document to the animal or group it covers, give it an expiry that generates a task with an escalation path, and assemble transfer packets against a checklist that varies by species and destination, since requirements differ substantially between them.
Is it worth building for a rescue or a small collection?
No. At that scale a build consumes attention you need for animals and creates a maintenance obligation with no one to carry it. ZIMS plus a disciplined paper routine, or ZooEasy for a breeding operation, is genuinely the right answer. Revisit the question if you take on a life support plant or cross into the hundreds of accessions with multiple taxon groups.
Where does artificial intelligence genuinely help here?
Two places. Voice capture of keeper observations, turning a spoken note into structured text with the animal, behaviour and timestamp already attached, which removes the end of shift transcription hour. And image assisted individual identification for species with natural markings such as dorsal fins or spot patterns. Neither is worth building until daily record capture is solid, and diagnostic prediction is not where the budget should go.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
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.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
What is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
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 Layla.
Senior Account Manager · Wellness · Sydney · 1 post on the site
Published · Last updated .
