Museum Management Software: Custom Build or Buy Altru, ACME and PastPerfect
Buy. A single site under about 100,000 annual visitors with a membership base under 5,000 should stay on ACME or Altru and spend the difference on staff. PastPerfect is fine if your collection is small.
On this page
Buy. A single site under about 100,000 annual visitors with a membership base under 5,000 should stay on ACME or Altru and spend the difference on staff. PastPerfect is fine if your collection is small. Build when two or more sites share a gallery capacity, when membership rules live in staff heads, and when your registrar's loan spreadsheet is load-bearing.
What Altru, ACME, Tessitura and PastPerfect actually do well
ACME Ticketing is a clean, modern admissions product and its timed entry works properly for a single venue. Altru bundles ticketing, membership and fundraising in one place for a mid-size institution, which is genuinely convenient. Tessitura is deep on subscription and patron management and has a serious user community behind it. On the collections side, The Museum System from Gallery Systems is the standard for larger institutions, PastPerfect is remarkably good value for a small one, CollectiveAccess is a credible open option, and Axiell serves the European market well. Blackbaud Raiser's Edge NXT holds donors properly and there is no good reason to rebuild it.
The honest opening, from a firm that sells builds. For most museums in America, buying is simply the right call. If you are a single site under roughly 100,000 annual visitors, with a membership base under 5,000, no venue rental business and a collection under a few thousand objects, ACME or Altru will hold you fine and PastPerfect is not hurting anyone. The money is better spent on a person than on software, and any developer telling you otherwise has not looked at your numbers.
Buy if most of these are true:
- One site, one gallery capacity number, one entry point.
- Membership tiers your front-of-house team can state consistently without looking anything up.
- Group and school bookings arrive at a volume one coordinator handles comfortably.
- Your registrar handles a handful of loans a year rather than a rolling programme.
- Nobody assembles your Saturday revenue number by hand on Monday.
Where they stop: entitlements in staff heads and capacity as an attribute
The moment that decides most builds is smaller than any spreadsheet. A travelling exhibition opens, timed entry sells out, and a member arrives with a valid membership, is told at the desk that her tier does not include the special exhibition, argues, and is let in by a sympathetic front-of-house lead. That override is recorded nowhere. Multiply it across three sites and a week, and the membership programme's real economics become unknowable while your development director builds a renewal campaign on numbers that are wrong by an amount nobody can measure.
Altru and ACME model tiers well enough. They stop the moment your rule reads like a real rule: Family covers two named adults plus any four children under 18 at the same address, Contributor and above get two guest passes per visit but only one during a ticketed special exhibition, and reciprocal programme holders get general admission but not the special. That is outside the configuration screens and into staff training, so the rule lives in the front-of-house lead's head, staff turn over, and rules drift by site until a member gets a different answer at your two buildings.
The second break is capacity. Timed entry became permanent and most platforms bolted it on as an attribute of an event. Your gallery is not an event, it is a resource consumed by several booking types at once: public timed entry, group sales that live in an inbox, school programmes, members-only previews and private events. A school group of 60 books through a process the ticketing system never learns about, the 10:30 slot sells to the public as if the gallery is empty, and on Saturday the exhibition your curators worked two years on is experienced as a shuffling queue.
The third break is structural to the market rather than to any vendor. Collections management vendors sell to registrars and treat revenue as somebody else's problem. Ticketing vendors sell to marketing and finance and treat objects as marketing copy. So nothing connects the object to the exhibition to the ticket, and when your board asks which loans justified their insurance and crating cost, the answer is a guess assembled from memory.
The arithmetic: per-ticket fees versus the cost to build
This category is unusual because the licence is not the main cost. The per-ticket charge is.
Take your platform subscription, add the per-ticket fee multiplied by paid admissions, add payment processing, and add collections software maintenance. At 150,000 paid admissions and a combined platform and ticket charge of 25 cents an admission, that is $37,500 before subscription. At 400,000 admissions it is $100,000. Use your own contracted rate, and check whether the fee applies to free and member admissions too, because that clause is where the number quietly doubles.
A build carries hosting and support rather than a fee per visitor. A focused first release runs $60,000 to $130,000, so at the midpoint amortised over five years plus year two support you carry roughly $28,000 to $48,000 a year regardless of attendance, plus payment processing you would pay anyway.
The lines cross around $40,000 a year in platform fees plus per-ticket charges, which for most institutions means roughly 150,000 paid admissions across two or more sites. Past that point a build amortises inside about 36 months on fees alone, before counting the two staff whose actual job, once you watch them for a week, is moving data between systems by hand.
Then add the number nobody quantifies: the front desk overrides, the school block that was never in the capacity pool, and the Friday evening venue enquiry answered on Tuesday after the planner booked elsewhere.
What a custom build actually costs
A focused first release covering unified ticketing and timed entry with shared space capacity, a membership entitlement engine evaluated at scan time, a read-only sync from your existing collections system, front-of-house scanning apps and reconciled daily revenue runs $60,000 to $130,000 over 12 to 16 weeks. A full platform retiring Altru, or a Tessitura and PastPerfect combination, including collections cataloguing, loans workflow, group and venue sales and shop integration, runs $150,000 to $400,000 phased across 6 to 12 months.
The two lines nobody quotes:
- Collections data migration: 10 to 25 percent of the build. A 40,000 object database with thirty years of inconsistent cataloguing, free-text provenance and images linked by filesystem path is not a weekend import. Your registrar will spend real hours on decisions only she can make, and mapping to Nomenclature 4.0 or Spectrum procedures is part of the work rather than a nicety.
- Year two: 15 to 20 percent of build cost annually. Tier changes each membership year, new exhibition types, a new entry point, and accessibility retesting. If you receive public funds you should be building to WCAG 2.1 Level AA properly, which adds roughly 10 to 15 percent to front-end work when designed in and about three times that when retrofitted.
What else pushes price up here: payment card scope, since card-present scanning at the door plus online plus the shop means you want tokenised flows and a point-to-point encrypted terminal path to keep your scope small; and the number of physical entry points, because every door is a device, a network assumption and an offline mode. Your scanners must work when the building wifi drops, which it will, on the busiest day.
Four situations where building wins for a museum
- Regulatory and standards fit. Accreditation and lending relationships run on documented practice: facility reports from borrowing institutions, condition reports at four points in a loan, insurance certificates with coverage amounts and effective dates, and deaccession policy. A loan modelled as a workflow object with states, owners and required documents per state is auditable. A folder and an Outlook reminder is not, and the day a rider lapses for eleven days you will find out from somebody external.
- Scale economics. Past roughly 150,000 paid admissions, per-ticket charges exceed the amortised build and keep growing with the success you are trying to have.
- A workflow that is your competitive advantage. Your membership programme is a pricing product. Once entitlements are structured and overrides are captured with who, why and value, you can finally answer whether Family memberships are profitable at their current price given actual visit frequency and guest pass usage. Two museum clients repriced tiers off exactly that data in the first year.
- Integration sprawl across three or more systems. Collections, ticketing, donor management, shop point of sale (POS) and a shared drive of spreadsheets that does everything the other four refuse to. If a busy Saturday takes a finance coordinator most of Monday to reconcile because gross, net and shop numbers never agree, you are paying for the seams every week.
How to decide in a week, then scope discovery
Five questions, five days, and no vendor in the room. Monday, ask three front-of-house leads independently what a Contributor member and one guest are entitled to during a ticketed special exhibition, and compare the answers. Tuesday, count the door overrides recorded anywhere in the last month. Wednesday, take last month's busiest Saturday and produce one honest attendance and revenue figure per site without a human assembling it. Thursday, ask your registrar to produce the current status of every outgoing loan, with the return date and the insurance expiry, from a system rather than a spreadsheet. Friday, look up how many enquiries arrived at your events inbox outside business hours and how long each waited.
If Monday produces three matching answers and Wednesday takes ten minutes, stay where you are. If the registrar's spreadsheet is load-bearing and Monday produces three different answers, you have your case, and it cost you a week.
Then buy a paid discovery phase before any build. At Digital Heroes that produces a signed product requirements document before code, covering the accession and object model, the entitlement rules engine, the shared capacity model, the loan workflow states, permissions and acceptance criteria. You own it whether we build or not, and you can take it to every firm on your shortlist.
We recommend a partial build far more often than a full replacement: unify ticketing, membership and capacity, and leave collections cataloguing where it is, because curators and registrars have workflows that took years to settle and replacing them in phase one is how these projects die. We are the wrong firm for you if you want a body shop billing hourly, or if you are a single site that should renew ACME. We are more than fifty specialists across India LLP, US LLC and UK LTD entities, so your intellectual property assigns under your own law, and you meet the named team before signing. Museums hold things for centuries, and your software should at minimum outlive your vendor relationship. Verify us on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S record.
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.
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Brandon Hall Group research on onboarding reports that done well, structured onboarding drives measurable gains in new-hire productivity, employee engagement, and retention; the page notes 41% of organizations experience greater than 5% turnover among new hires. Source: Brandon Hall Group (2024) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
Frequently asked questions
How much does it cost to build custom museum management software?
A focused first release covering unified ticketing and timed entry with shared capacity, a membership entitlement engine, a read-only collections sync, scanning apps and reconciled daily revenue runs $60,000 to $130,000 in 12 to 16 weeks. A full platform replacing your ticketing and collections stack runs $150,000 to $400,000 across 6 to 12 months. Collections migration typically adds 10 to 25 percent on top.
How long does migrating a 40,000 object PastPerfect database take?
Three to five months of elapsed time, most of it waiting on decisions rather than on engineering. Thirty years of inconsistent cataloguing, free-text provenance and images linked by filesystem path need judgement calls only your registrar can make, and she has an exhibition to install. Budget her time explicitly in the project plan and map to a naming standard as you go rather than afterwards.
Who owns the collections data and the code if we commission a build?
You should own the repository, the cloud account and the data from day one rather than on completion, in writing before the first invoice. Museums hold things for centuries and your software should at minimum outlive your vendor relationship, so require documented schemas and an export that reproduces accession records, provenance and image files intact. At Digital Heroes the client owns everything from the first commit.
What happens if our ticketing platform raises its per-ticket fee?
Model it before it happens. Ask what the fee is tied to, whether it applies to free and member admissions as well as paid ones, and what your annual cost looks like at double your current attendance. If the fee scales with the attendance you are trying to grow, that is worth knowing while you still have time to react rather than during a renewal negotiation.
Can we keep The Museum System and build only ticketing and membership?
Yes, and it is what we recommend most often. Keep your collections system as the system of record for cataloguing, sync objects into the new platform read only, and build the layer that unifies ticketing, timed entry, membership entitlements and capacity. Curators and registrars have workflows that took years to settle, and replacing those in the first phase is the most reliable way to lose the project.
What is the difference between event capacity and a shared space resource?
Event capacity is a number attached to a single scheduled event. A shared space resource is a gallery or building with a capacity calendar that several booking types draw from at once: public timed entry, group sales, school programmes, member previews and private hires. Museums with multiple booking channels need the second, and that is a data model difference rather than a settings change any vendor can toggle.
Should a single-site museum with 60,000 visitors build anything?
No. ACME or Altru will serve you well at that size, PastPerfect will hold a modest collection, and the money belongs in a member of staff. Revisit the question when you open a second site, when timed entry starts competing with school groups for the same gallery, or when your registrar begins maintaining a loan spreadsheet the institution could not operate without.
Can a custom system handle front desk overrides without becoming rigid?
It should, because museums are hospitality businesses and the answer at the desk is sometimes yes regardless of policy. The point is not to prevent overrides, it is to capture who authorised each one, why, and what it was worth. Once that is recorded, the membership programme's real economics appear in a report instead of vanishing, and your development director can price renewals on something defensible.
What happens if our scanners lose network connectivity on a busy day?
They must keep admitting visitors, validating entitlements from a locally cached membership state and queueing scans for later reconciliation. Ask any developer how the door behaves with no signal for two hours, and how duplicate admissions are resolved when the queue syncs. Every entry point is a device, a network assumption and an offline mode, and building wifi drops most reliably on your busiest weekend.
How do we evaluate developers who have never built for a museum?
Ask them to model an accession record and a loan on a whiteboard, unprompted. If they cannot distinguish an accession number from an object identifier, or do not immediately ask whether you catalogue at object or lot level, they have never done this. Then ask how they would model a household with two named adults and a floating guest pass allowance, and listen for a rules engine rather than a column.
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.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
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.
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.
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.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Oliver.
Senior Account Director · UK · London · 3 posts on the site
Published · Last updated .
