Performing Arts Patron Management Software: Build or Buy

What the off-the-shelf products actually do well

It is the second Tuesday in March and renewal on-sale opens at ten. Your subscriptions manager has three windows open: the ticketing system, a spreadsheet named RENEWALS_FINAL_v4, and an email from development listing every patron whose giving level moved since last season. Seat A12 belongs to a couple who have sat there since 2009. The system knows A12 as a line on a past order. It does not know it as their seat.

Before deciding anything, give the products their due, because they are better than the March spreadsheet suggests. Spektrix handles straightforward renewals well and includes the hosting, the payment compliance and the support in the fee, which are real costs you would otherwise carry. PatronManager builds on Salesforce, so you inherit a genuine customer relationship management (CRM) system rather than a contact list attached to a cart. AudienceView covers a wide range of venue types and copes with presenters as well as producing houses. Tessitura holds ticketing and giving in one database more completely than anything else in this market. ThunderTix and Arts People serve smaller houses at prices a build cannot approach.

Most houses should buy. A single venue presenter under roughly $2 million in ticket revenue, with conventional packages and a modest donor file, is well served by Spektrix and should put the difference on stage. We say that in first calls and it costs us projects.

Where they stop

The break is that a subscriber does not buy seven tickets, they keep their seats, and almost nothing in this market models a durable seat holding. Off the shelf ticketing treats a seat as inventory attached to an event. Renewal is then a bulk order creation against next season, which works until the hall changes. Add a pit extension for the opera, remove row A, convert two boxes to accessible seating, and the mapping breaks in a way a human has to patch one patron at a time.

Underneath that sits seat succession, which no product we have seen expresses. When a centre orchestra pair opens, who gets it. A subscriber of fifteen years or one of three. Cumulative giving or tenure. A committee decision. Your rule is real, it is applied every season, and when a patron asks why somebody else got the seat you need an auditable answer rather than a recollection.

The regulatory edge is sharper here than most vendors admit. Under the accessible ticketing rule at 28 CFR 36.302(f), accessible seats have to be sold in the same manner, during the same hours and through the same methods as all other seats, and wheelchair spaces come with companion seating. A renewal rollover that quietly relocates a wheelchair space, or a presale that gates accessible inventory behind a phone line while everyone else buys online, is a compliance problem rather than a configuration preference. Your public purchase path is also a place where WCAG 2.1 AA conformance is expected, and retrofitting that onto a finished checkout costs several times building to it.

The third break is the exchange. Releasing two seats, finding comparable seats on another performance, deciding whether a price differential applies, deciding whether the exchange fee is waived because this patron gives at a level that includes free exchanges, and checking that dropping this performance does not end the package discount. Most platforms support exchanges. Few check package integrity at the moment of the exchange, so your agent promises something the system later contradicts.

The arithmetic on cost to build versus per ticket and per seat fees

Price this per paid ticket and per subscription household, because subscriptions are where the labour actually goes.

Suppose you sell 44,000 paid tickets across 2,600 subscription households. Add the platform licence, the per ticket fee you absorb rather than pass on, the separate donor database, and the staff licences for box office and front of house. Say that totals $96,000 a year. Now add the hidden line: 10 to 20 hours a week of a subscriptions manager rebuilding renewal data during the renewal window, plus two to four days per exchange backlog. At a loaded salary that is commonly another $18,000 to $25,000 of the year.

Against a build: our first release band is $70,000 to $150,000, with year two support at 15 to 20 percent. Three years at the midpoint is roughly $110,000 plus two years of support, so call it $150,000, against $340,000 or more for three years of the current arrangement.

The crossover sits between 2,500 and 4,000 subscription households when more than half your earned revenue arrives in packages, and it moves higher, toward 6,000 households, when your hall does not reconfigure and rollover works. Below 1,500 households the subscription wins every time, and it is not close.

What a custom build actually costs

What follows is what Digital Heroes has charged for work of this shape, not a market survey. A focused first release covering the patron record with households, subscription packages, renewal with seat continuity and provenance, the upgrade queue, and a working box office screen runs $70,000 to $150,000 and ships in 14 to 20 weeks. A full platform adding exchanges and flex passes, benefit gated presales, memberships, donation checkout, gift processing and reporting the development office trusts runs $180,000 to $450,000 phased over 8 to 14 months.

Data migration is 10 to 25 percent of the first release. The hard part is not orders, it is rebuilding seat provenance so the system knows a pair has been held continuously since 2009 and by whom, since that history is what your renewal logic depends on. Year two is 15 to 20 percent of build cost annually, covering hosting, seat map changes when the hall is reconfigured, and a developer reachable during on-sale week.

What pushes it up in this category: multiple venues or a reconfigurable hall; a general admission and reserved hybrid; more than about six package types in rollover; keeping an existing donor system such as Raiser's Edge NXT; access services including assistive listening inventory and audio described performance flags; and any obligation to keep selling through a presenting partner's own box office.

The four situations where building wins

A single item here means tighten your process. Two of them means the coordination has outgrown the product.

• Regulatory and access fit. Accessible seating under 28 CFR 36.302(f) has to survive rollover intact, companion seats have to stay paired, and your public checkout needs WCAG 2.1 AA conformance you can evidence. If your current platform forces accessible inventory into a manual path, that is an exposure rather than a preference.
• Scale economics. You are past the household crossover above, or the coordination between seats, packages, benefits and gifts has become the actual job of two or three people. At that point you are already paying for custom software in salaries and getting no asset for it.
• A subscription model that is your competitive advantage. Flex passes with your own redemption and blackout rules, seat succession by your own seniority rule, membership tiers that gate presales. If staff apply those from memory because no product expresses them, they are yours to encode.
• Integration sprawl across three or more systems. Ticketing, a separate donor database, scanning and access control at the doors, an email platform and the accounting system all needing the same patron. Three or more synchronised by export means the export is already a system nobody owns.

How to decide in a week

Run a rollover test rather than a demonstration, because rollover is where this decision is actually made.

Monday, take last season's final seat assignments and next season's calendar and hall configuration, and run a renewal rollover in your current system. Tuesday, count three things: seats that mapped cleanly, seats that could not map and needed a human decision, and accessible seats or companion pairs that moved without anyone approving the move. Wednesday, pull ten exchanges from last season and time how long each took end to end, noting how many required a supervisor to decide a fee. Thursday, ask your box office manager to look up one patron and state, from one screen, their seats, tenure, giving level, benefit entitlements and outstanding balance. Friday, do the per household arithmetic above.

If fewer than five percent of seats needed a human and the patron lookup took one screen, buy and configure better. That is the outcome for most houses. If a quarter of your seats needed decisions and the lookup took three systems, you are running the renewal by hand and paying a platform fee for the privilege.

If it is build, start with a specification and not a contract for code. Two to four weeks, fixed fee, ending in a written product requirements document covering the seat holding and provenance model, the succession rule as your board actually applies it, the exchange and package integrity rules, the accessible seating handling, the integration boundary with your donor system, and acceptance criteria. You keep the document either way, and it is what makes four quotes comparable.

Where Digital Heroes is wrong for you: single venue presenters under about $2 million, any house running Tessitura well, and organisations wanting a supplier to host and operate the box office rather than own it. We frequently recommend keeping single ticket sales on your current platform for a season while the new system proves itself on renewal, which is the smaller invoice. Code follows a signed specification, never precedes it. We hold India LLP, US LLC and UK LTD entities, so intellectual property assignment happens under your own jurisdiction rather than ours, and you can check us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S. Over fifty specialists and more than 2,000 projects, with the named engineers introduced first.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.