Performing Arts Organization Software: Build or Buy

What the off-the-shelf products actually do well

A trustee asks the executive director for the fifty best prospects for the year end campaign. Nobody in the building can produce that list, because the person who has attended eleven performances across three seasons, always takes the good seats and has never given a dollar is sitting in the ticketing system where the development office cannot see them. That is the whole problem, and it is worth saying up front that four vendors have taken it seriously.

Tessitura holds ticketing and giving in one database and does it more completely than anything else in this market, which is exactly why the large houses run it. Spektrix has built a genuinely good mid-market platform with real customer relationship management (CRM) thinking behind it, and the hosting and card compliance come included. PatronManager gets the relationship model right by building on Salesforce, so you inherit a proper CRM rather than a fundraising module bolted to a cart. AudienceView covers a broad range of venue types. If you are smaller, Arts People and Blackbaud Raiser's Edge NXT together will carry you a long way.

Most companies should buy one of these and stop. If contributed income is under about a quarter of your budget, your season is four or five titles in one hall, and your development director can hold the donor file in their head, custom software is money that belongs on stage or in a development associate. We say that to arts clients regularly and it costs us work.

Where they stop

The break is the accounting split inside a single transaction, and it is specific to nonprofit arts rather than a general reporting complaint. A gala seat at $500 with a dinner worth $85 is not one number. Under the contribution guidance in ASC 958, $85 is an exchange transaction and $415 is a contribution, and your written acknowledgement has to state the value of the goods and services the patron received so they know their deductible amount. A subscription package with a bundled parking benefit raises the same question in miniature. A sponsorship with logo placement raises it in reverse.

Ticketing systems record the $500. Donor systems record the $415 if somebody typed it. Neither computes the split from the benefit structure, so a development coordinator maintains a spreadsheet of benefit values and applies it by hand before Form 990 Schedule G is prepared. Every arts finance director reading this already knows the spreadsheet.

The second break is the conversion ladder. Everyone in arts fundraising knows the pattern: first time attender, repeat attender, subscriber, small donor, mid-level donor. Each rung has a moment when the ask should happen, and the trigger is behavioural rather than calendar based. A third attendance in one season. A first upgrade into a premium price zone. Bringing more than four guests. Lapsing after two subscribed seasons. Products in this market report on transactions after the fact. They do not detect a patron crossing a rung and put them in front of a human that week, so the ask happens at year end to everyone at once, in an email, at the exact moment every other nonprofit is asking.

The third is the production result. Single ticket revenue net of discounts, subscription revenue allocated across the titles in the package, marketing spend attributable to that production, sponsorship raised against it, and expense from the general ledger by project code. The allocation rule is a judgement nobody has written down, so the number gets recomputed differently by whoever prepares the board packet, and a company makes programming decisions worth hundreds of thousands of dollars from a report it does not fully trust.

The arithmetic on cost to build versus per ticket fees

Price this per paid ticket, because that is how the money actually leaves. Add your annual platform licence, the per ticket fee your vendor takes, any per ticket charge you absorb rather than pass on, your donor database subscription, and the email platform. Divide by paid tickets sold last season.

Suppose you sell 70,000 paid tickets, pay a $34,000 platform licence, absorb $0.90 a ticket, and pay $14,000 for a separate donor database. That is $111,000 a year, or $1.59 a ticket. Against a build: a first release at the midpoint of our band is roughly $112,000, with year two support at 15 to 20 percent, so three years lands near $150,000 while three years of the current stack is $333,000 and rising with attendance.

The crossover for replacing the whole stack sits between 90,000 and 130,000 paid tickets a year. Below that, replacing ticketing is the wrong project regardless of how the spreadsheet looks, because you would be rebuilding seat inventory, checkout and card compliance that a vendor already maintains for you.

The number that actually decides it is different. Count the hours your development coordinator spends on benefit valuation, gift acknowledgement wording, prospect list building and board packet preparation. In companies between roughly $3 million and $20 million that is frequently half a role, and half a role is more than the annual cost of the layer that would remove it.

What a custom build actually costs

Numbers below come from Digital Heroes delivery experience. They are not sector benchmarks and nobody should quote them as such. A focused first release covering the unified constituent record, the giving pipeline with portfolios and proposals, behavioural conversion triggers, benefit valuation and acknowledgement generation, and a production level revenue view runs $75,000 to $150,000 and ships in 14 to 18 weeks. A full platform adding campaign management, memberships and benefit delivery at the door, galas with table seating, board views and accounting integration runs $180,000 to $420,000 phased over 8 to 14 months.

Data migration is 10 to 25 percent of the first release and lands high in that range for any company with a long donor file. Thirty years of pledges, tribute and memorial gifts, soft credits to a family foundation and coding conventions invented by staff who left in 2004 is discovery work, not a mapping exercise, and anything affecting reported totals needs your auditor in the room. Year two is 15 to 20 percent of build cost annually, covering hosting, the benefit schedule your board changes each season, and someone reachable during subscription on-sale.

What drives the number up here specifically: whether you replace ticketing or integrate with it, which is the single largest fork; multiple venues or a resident company arrangement where another organisation sells some of your seats; a festival structure with overlapping programmes; and education programmes with their own registrations and grant reporting.

The four situations where building wins

Any one of these on its own is a reason to configure better. Two of them together is a reason to build.

• Regulatory and reporting fit. Your benefit structure is complex enough that the exchange and contribution split under ASC 958 is being done by hand, and Form 990 Schedule G is assembled from a spreadsheet each year. That is an audit exposure rather than an inconvenience.
• Scale economics. You are past the per ticket crossover above, or your development team costs more in reconciliation hours than the layer would cost to build.
• A conversion model that is your competitive advantage. Your membership tiers, your subscriber benefits or your patron ladder are genuinely yours, and every product forces them into a shape that loses the distinction you built deliberately.
• Integration sprawl across three or more systems. Ticketing, a separate donor database, an email platform, the accounting system and grant reporting all needing the same constituent. Once three or more of them are synchronised by export, the export is already a system nobody owns.

How to decide in a week

Run the trustee's question as an actual test rather than debating features.

Monday, ask your team for the fifty best prospects for the year end campaign who have never given, ranked, with attendance history attached. Time it honestly and note how many systems they open. Tuesday, take three gala or benefit gifts from last season and ask your finance director to reproduce the exchange and contribution split and the acknowledgement wording from source records rather than from the spreadsheet. Wednesday, ask for the net result of your best selling production last season and your worst, with the subscription allocation shown, and see whether two people produce the same figures. Thursday, do the per ticket arithmetic above with real numbers. Friday, decide.

If the prospect list took under two hours and the production numbers agreed, buy. Configure what you have properly and hire the development associate instead. If the list took two days, the acknowledgement split could not be reproduced, and the production numbers disagreed, you have a patron model problem, and no ticketing platform is going to solve it because it is not a ticketing problem.

Whichever way it lands, buy the specification before you buy the software. Two to four weeks, fixed fee, ending in a written product requirements document covering the constituent model, the benefit and acknowledgement rules agreed with your auditor, the subscription allocation rule agreed with your finance director, the integration boundary with your ticketing platform, and acceptance criteria. You keep the document either way, and it lets you compare quotes that are otherwise not comparable.

Where Digital Heroes is wrong for you: companies under about $3 million, anyone running Tessitura well already, and boards that want a vendor to operate the system rather than own it. We recommend integrating with your ticketing platform more often than replacing it, which is the smaller invoice. Nothing gets written until a product requirements document is signed. Our India LLP, US LLC and UK LTD entities mean the intellectual property assigns under the law your own counsel already reads, and the record is public on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S. Fifty plus specialists, more than 2,000 projects delivered, and the people who will do the work sit on the call before signing.

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