Build vs Buy: Media Archive and Preservation Management Software
Buy the repository, build the operational layer, or buy everything if your holdings are modest. Preservica and Arkivum handle fixity, format management and defensible custody better than any bespoke system.
On this page
Buy the repository, build the operational layer, or buy everything if your holdings are modest. Preservica and Arkivum handle fixity, format management and defensible custody better than any bespoke system. What they do not run is your vault, your carrier condition data, your digitization vendors or per item rights, and that is where a custom build earns its money.
Buy: the archives that should not be building anything
If your holdings are mostly born digital and number in the low thousands of objects, buy a preservation repository and stop. Preservica and Arkivum are aligned to the OAIS model, do fixity checking and format identification properly, and produce the audit trail a records regulator or a funder expects. A bespoke version of that would cost more and be worse, and any developer who tells you otherwise is quoting a project rather than solving a problem.
Buy when you have no digitization programme and no funding for one. Operational software for a programme that does not exist is an expensive way to describe an intention. Get the funding first, then buy the tooling that the funded plan actually needs.
Buy when a single collection management system already serves your cataloguers and the only real gap is safe storage. Adding a repository underneath an existing catalogue is a weeks long project. Replacing the catalogue is a years long one, and the second rarely delivers what the first would have.
Buy when your carriers are homogeneous. An archive holding only Digital Betacam and one film gauge has a condition survey that fits a form. The custom case is driven by variety, not by volume alone.
One vendor behaviour to plan for. Repository products commonly price against stored volume or object count, and a digitization programme is precisely a machine for increasing both, quickly. The quote that suited your first thousand hours of transfers will not be the quote at fifty thousand. Ask for the pricing tiers up front and model them against your programme's own transfer forecast rather than today's holdings.
Build: the operational layer nobody sells you
The build case in a moving image archive begins where the repository ends. Repositories start when the file exists. The expensive, time bound work happens before that.
Condition is the first driver. Prioritisation requires decay risk multiplied by content value multiplied by clearability, and decay risk is format specific in a way generic systems cannot hold. Acetate film needs an acidity reading, shrinkage and splice condition. Magnetic tape needs binder assessment, a record of whether baking was performed and at what temperature, and edge and pack condition. Give each carrier type its own schema, capture it on a tablet in the vault with barcode scanning, and you can produce a queue you are able to defend in a funding meeting even when it ranks a dull regional news series above a beloved drama.
Vendor chain of custody is the second. Items leave the building in batches, sit in a facility for weeks and return with a manifest in the vendor's format. If your record of that journey is an email trail, a mislabelled reel becomes an archaeology exercise. Generate the manifest yourself, scan items out and in, and require the vendor to post deck used, operator, interventions and quality control notes against each item permanently.
Rights is the third and the one that decides whether the programme survives its funding cycle. Clearance is a per item legal question with several independent answers, all of which must come back yes before anything can be licensed or streamed. Held as structured status with evidence attached, it can weight the digitization queue. Held in a researcher's head, it means the same series gets researched three times in ten years and files get made that nobody may show.
Roughly 50,000 or more physical items across mixed carriers, with funded multi year work and external vendors, is where this stops being optional.
Where the money goes on each route
Buying. Repository subscriptions scale with stored volume, and a preservation master at broadcast quality is large, so your software cost tracks your transfer rate rather than your headcount. Add implementation, metadata mapping from your existing catalogue, and the cost of whatever spreadsheet estate continues to run the physical side because the repository does not touch it. That spreadsheet labour is real and it is usually paid for out of curatorial time nobody costs.
Building. A first release covering the item and carrier register with barcodes and shelf locations, format specific condition capture, risk based prioritisation and the vendor batch workflow with chain of custody runs roughly $80,000 to $170,000 across 14 to 20 weeks. A full platform adding ingest with checksum verification and technical metadata extraction, fixity scheduling, storage and migration planning, per item rights clearance with document extraction and media asset management integration runs roughly $200,000 to $500,000 across 9 to 15 months.
Then the line that decides a ten year comparison, because archives think in decades. Custom software needs hosting, patching and somebody to change it when your practice changes, so budget 15 to 20 percent of build cost annually and name the person. Archives are unusually exposed here: a system built during a grant and unmaintained after it becomes a data extraction problem for whoever inherits the vault.
The reasoning behind the build band is variety and cleanup. Each distinct carrier family needs its own condition vocabulary, and retrospective catalogue reconciliation across decades of inconsistent series and episode identification is almost always underestimated.
Expenses that arrive in year two
The LTO migration horizon. If your preservation copies live on tape, every cartridge you write today carries a known expiry, because each drive generation reads back only a limited number of earlier generations and writes back fewer. That is not a risk, it is a scheduled bill. Any system worth building holds a storage plan per copy showing medium, write date, last verification and required migration date, and produces a five year migration cost view. Most archives cannot produce that page today without a week of work, and most funders have never been shown it.
Vocabulary negotiation. Conservators, cataloguers and the rights team frequently use different words for the same thing and the same word for different things. Agreeing the condition fields, carrier taxonomy and identification conventions takes longer than building the screens that display them. Archives with a documented condition survey method already in place move visibly faster.
Rights document volume. Extracting parties, term, territory and usage type from scanned cue sheets and contracts is genuinely useful work, but ten thousand documents is a different project from five hundred. Count them before anyone quotes.
Media asset management boundaries. If you run Dalet, Avid or Vidispine for access copies and editorial metadata, the hard part is not the connection. It is agreeing which system owns which field, and that argument belongs before design.
Nitrate and other separately stored material. Special handling, separate locations and restricted access rules break the assumption that all items behave alike, and they need modelling rather than a note.
Try sequencing one hundred items
Take a hundred items you have not yet digitized and try to put them in the order you would transfer them, with a written reason per item. Give a conservator, a curator and a rights researcher one week between them. Then examine what happened.
- How many items had condition data specific enough to rank, rather than a note saying fair or good?
- How many had a clearance status you would be willing to put in front of a commercial partner?
- How many required somebody to physically walk into the vault to answer a basic question about format or shelf location?
- Could you show a funder why item forty ranks above item nine, with evidence rather than judgement?
If the exercise finishes cleanly, your problem is storage and audit, so buy a repository and put the remaining budget into transfers. If it stalls because condition is prose, rights are unknown and the vault is the only reliable source of truth, then no repository will help, because none of those facts are things a repository is designed to hold.
Run the same exercise against any vendor demonstration. Ask them to show you how their system would rank those hundred items and what data it would need. The honest ones will tell you the ranking is not their job.
How to start without committing the whole programme
Begin with a condition survey pilot rather than a procurement. Survey two hundred items across your three most at risk carrier families using a defined method, and record how long each item took. That gives you a real survey cost per item, which is the number every subsequent funding application needs and which almost no archive can quote.
If your holdings are modest and born digital, request quotes from Preservica and Arkivum, ask for pricing tiers against stored volume, and model them at your five year transfer forecast rather than today's total.
If you hold a large mixed carrier collection with a funded programme, scope a first release around condition capture, prioritisation and vendor batch tracking only. Keep the repository underneath for storage, fixity and format management. A first release that only tells you what to do next, with evidence, has already changed how the money is spent, and it is the cheapest possible thing to prove.
On partner selection, ask any developer to whiteboard the data model before you sign. One who separates the work, the manifestation, the physical carrier and the digital instantiation understands that a single work can have six carriers of different quality and three digital copies of different provenance. One who draws assets and files has built a document store. Digital Heroes works PRD first, so the carrier taxonomy, condition schemas and prioritisation formula are written and approved by your conservators before code exists. The team is 50 plus people across 2,000 plus delivered projects, holds Fiverr Vetted Pro status, and publishes to 2.5 million subscribers on YouTube. India LLP, US LLC and UK LTD entities mean contracting and IP assignment happen under your own jurisdiction, which matters for institutions bound by public procurement rules.
Settle code and data ownership in writing before kickoff. Archives outlive vendors, and a system you cannot maintain is a future migration project.
If you want that decision made properly rather than quickly, 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. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- McKinsey Global Institute estimated that about half of all work activities globally have the technical potential to be automated by adapting currently demonstrated technologies, though few occupations can be fully automated. Source: McKinsey Global Institute (2017) →
- Sensor Tower's State of Mobile 2026 reports that global users spent 5.3 trillion hours in iOS and Google Play apps in 2025 (+3.8% YoY), roughly 3.6 hours per day per mobile user. (Note: the page does not itself contrast app time vs. mobile-browser time, so the 'overwhelming majority of time in apps vs browsers' framing is not directly supported by this source.). Source: Sensor Tower (2026) →
Frequently asked questions
What does custom archive preservation software cost against buying a repository?
Repository subscriptions scale with stored volume, so your bill tracks your transfer rate rather than your staff count. Building a first release with the carrier register, format specific condition capture, prioritisation and vendor batch workflow runs roughly $80,000 to $170,000 over 14 to 20 weeks. Full platforms with ingest, fixity scheduling, migration planning and rights clearance reach $200,000 to $500,000 across 9 to 15 months, plus annual maintenance.
How long does an archive management build take to deliver?
A usable first release ships in 14 to 20 weeks. The pacing risk is vocabulary rather than engineering, because condition fields, carrier taxonomies and identification conventions have to be agreed between conservators, cataloguers and the rights team, and those groups often use different words for the same concept. Archives with a documented condition survey method already in use move noticeably faster than those defining one mid project.
How difficult is migrating decades of catalogue data?
Difficult, and it is the most commonly underestimated line in this category. Legacy catalogues carry inconsistent series, episode and title identification accumulated over decades, plus duplicate records created when collections merged. Expect reconciliation to be a staffed workstream running alongside development rather than a load script at the end. Deciding which historical records are trustworthy enough to migrate is a curatorial judgement, not a technical one.
What should an archive system integrate with rather than replace?
Keep a preservation repository such as Preservica or Arkivum for storage, fixity and format management. Keep your media asset management platform, whether Dalet, Avid or Vidispine, for access copies and editorial metadata. Build the operational layer neither one covers: vault locations, carrier condition, prioritisation, vendor batches and rights. The hard part of those integrations is agreeing which system owns which field, and that belongs before design.
What does the LTO tape migration problem mean for planning?
Each LTO drive generation reads back only a limited number of earlier generations and writes back fewer, so every cartridge written today carries a known migration horizon whether or not it has been budgeted. A preservation system should hold a storage plan per copy recording medium, write date, last verification and required migration date, and produce a five year cost view. That page is what a board or funder needs and few archives can produce it quickly.
Who builds custom software for film and broadcast archives?
Repository vendors sell products, while operational systems are built by development firms willing to learn the domain vocabulary. Digital Heroes is one option: 50 plus people, 2,000 plus projects delivered, and a PRD first process where the carrier taxonomy, condition schemas and prioritisation formula are approved by your conservators before development begins. Entities in India, the US and the UK let public institutions contract and assign IP under their own procurement rules.
What makes Digital Heroes different from a generic development shop?
The willingness to keep your repository and your media asset management system and build only the layer neither covers. Most shops quote a replacement because a replacement is a larger project. The PRD stage also forces the work, manifestation, carrier and instantiation distinction to be modelled explicitly at the start, which is the difference between a system that survives a decade of accessions and a document store with archive vocabulary on the buttons.
How can we verify a development partner before committing funds?
Check the D-U-N-S registration and confirm the entity matches the one on your contract, which public institutions usually need for procurement anyway. Read the Clutch profile, where reviews come from verified client interviews rather than submitted testimonials, and look at the pattern in Trustpilot complaints rather than the score. Then require a written PRD before development, and put code, data and infrastructure ownership in the contract.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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.
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.
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 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.
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.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
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.
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 Liam.
Senior iOS Engineer · APAC · Sydney · 1 post on the site
Published · Last updated .
