Box office, development and finance each hold part of the picture, in three systems that rarely agree. Here is how arts organisations get one view the board and funders can trust.
Arts and cultural organisations bring ticketing, fundraising and finance into one view by landing data from each system in one place, matching people and performances across them, agreeing a small set of definitions such as attendance, earned income and contributed income, and reporting from a single model. The box office keeps its system, development keeps its CRM, finance keeps its ledger. What changes is that the numbers finally reconcile.
Three teams, three versions of the season
A typical venue or touring company runs a ticketing and CRM platform such as Spektrix or Tessitura, a fundraising database, a finance system, and a stack of spreadsheets for everything those systems do not hold: education work, touring dates, grant conditions, hire income. The box office reports tickets sold. Development reports gifts and pledges. Finance reports income by nominal code, after refunds, comps and the timing of when a show is recognised.
Each figure is right on its own terms, and none of them match. The board pack takes days to assemble, and the question that matters, how a production performed once every income line and cost is counted, is answered months later if at all.
What one view needs
One list of productions and performances. Every system has its own codes for a show. A maintained reference table that maps them is the backbone of everything else, because it is what lets ticket income, sponsorship, production costs and audience data sit against the same production.
One view of the person. A ticket buyer, a member, a donor and a Friend are often the same person held in different places. Matching them, carefully and within your privacy notice, is what makes audience development reporting possible: who came for the first time, who came back, who moved from buyer to member to donor.
Agreed definitions. Capacity, attendance, paid attendance, comps, yield per seat, earned income, contributed income. Write them down once, build them into the model, and every report uses the same meaning.
Finance as the anchor. Ticketing and fundraising totals should reconcile to the ledger each month. Where they do not, the report should show the difference and why, rather than leave two numbers to argue.
What it gives you
For the executive team, a season view: income against budget by production, pacing of sales against previous comparable shows, and contributed income against target. For marketing, audience behaviour by segment and channel. For development, donor retention and pipeline. For funders, the data behind annual returns, such as those Arts Council England asks of National Portfolio Organisations, produced from the same model rather than rebuilt each year.
How we build it
On Microsoft's stack this is a Power BI model over a small Microsoft Fabric platform: ticketing and CRM data extracted through the platform's API or scheduled exports, the finance system's trial balance and transactions, and the spreadsheets moved into maintained tables. A first version covering ticketing and finance for one season typically follows a four-week Establish phase and an 8 to 12 week build.
Start with the question the board asks most often and cannot answer quickly. Build that well, prove it reconciles, then add fundraising and audience development. Our free audit is a straightforward way to see what your current systems can already support.
Related reading
What a data strategy actually needs to contain
Self-service BI that people use
Fewer dashboards, more decisions
Shauna Duffy
Director of Professional Services
Part of the Hopton Analytics team, delivering governed analytics programmes for UK mid-market organisations.
