Most arts organisations don’t have a software problem, they have a connectivity problem. The tools exist, the question is whether they work together.
Walk into the back office of almost any arts organisation and you’ll find the same scene. A venue management system for bookings. A CRM for contacts. A finance system for invoicing. A shared drive full of Excel files and Word documents, each one trusted completely by the person who built it and viewed with quiet suspicion by everyone else, and a dozen more folders that aren’t shared at all, or shared only within a team, holding information that the rest of the organisation doesn’t know exists.
And somewhere in the middle of all of it, a person, usually experienced, usually overworked, who has built their own mental map of how everything connects.
That person isn’t just doing their job. They’re doing their job and quietly compensating for every gap the systems leave behind. They know that the confirmed booking hasn’t fed through to the finance run yet. They know which version of the contacts list to trust on a Friday afternoon. They know who to call when something falls between two systems, because they’ve been the one to catch it before.
They’re not just knowledgeable, they’re the glue. And that’s both a sizeable burden and an operational risk.
The real cost of disconnection
The arts sector has embraced digital tools enthusiastically, and rightly so. But enthusiasm, applied without strategy, tends to produce accumulation rather than integration. Each new tool solves a specific problem well. The booking platform handles the calendar. The ticketing system handles the front of house. The donor management platform handles fundraising relationships. Each one, in isolation, does its job. And it has never been easier to add another: a free subscription here, a shared spreadsheet that becomes load-bearing there, a department that quietly builds something of its own because the central system doesn’t quite serve their needs. Each decision is rational. The cumulative effect is not.
The problem is that none of these things happen in isolation. A programming team planning next season’s calendar and a commercial hire team responding to enquiries are working in the same spaces, but if they’re not in the same system, conflicts don’t surface until it’s too late. A marketing officer needs accurate event titles, timings, and artist names early enough to build a campaign; if that information lives in a programming spreadsheet that hasn’t fed through to anyone else, the brochure goes out based on a draft. A technical manager arriving for a load-in needs an event order that reflects what was actually agreed, not the version that was current three weeks ago before someone updated the booking and forgot to tell them.
When systems don’t talk to each other, the gaps have to be held together by people, manually, across different platforms. That takes time. It introduces errors. And it means that the decisions being made at senior level are often based on information that’s incomplete, delayed, or quietly wrong.
What connected actually means
Real operational connectivity is about having a single version of the truth that everyone in the organisation can trust. It means that when a Rentals Manager updates a booking, the Finance team can see the implications without waiting for a weekly sync. It means that when a Development Officer looks up a contact, they can see that this person’s last interaction with the organisation was a complaint about their conference booking experience, before they pick up the phone to talk about a major gift.
For the person managing a venue hire pipeline, it can be the difference between a proposal sent within the hour and one that takes a day to assemble, because the information lives in three different places.
This doesn’t mean every team needs access to every piece of information, or that one system needs to do everything. It means that when data is entered once, in the right place, by the right person, it can be surfaced in the right format for whoever needs it next. The alternative is the Master Schedule: the sprawling shared file that someone builds because the system couldn’t give the whole organisation the view it needed. It becomes a second system of record, with all the version control problems that brings. And the person who maintains it becomes indispensable in a way that serves nobody well.
Done well, a connected system becomes something more than a record of what happened. It becomes a source of insight: patterns in room utilisation, shifts in customer behaviour, relationships between revenue streams that only become visible when the data is whole. And from insight, action: the pricing conversation that happens because the system surfaced the opportunity, the renewal outreach that lands at the right moment, the resourcing decision made on current information rather than last quarter’s gut feel. That’s the difference between a system your team updates and a system your organisation actually runs on.
This is what world-class looks like in venues that are genuinely performing well operationally. Not more data. Better connections between the data they already have.
It starts with software. It doesn’t end there.
One of the most common conversations I have with arts organisations is about trust. Not trust in the philosophical sense, trust in a spreadsheet. Does everyone in this organisation know where to find the authoritative version of a piece of information?
More often than not, the honest answer is no. There are multiple versions of the contacts database. There’s the “official” room schedule and there’s the one the tech team actually works from. The board gets a report based on numbers that nobody is entirely sure align with what’s in the system.
But here’s the thing worth saying plainly: a single source of truth isn’t something you can just install. Software is a necessary part of the answer, but it’s not sufficient on its own. Getting there requires changes in process, in how information is captured, shared, and maintained. It requires a shift in attitude, a collective decision that the system is the record, not the shortcut beside it. And it requires discipline, which means it requires buy-in, and buy-in means people need to feel that the system works for them rather than against them.
Part of that work is establishing standard operating procedures: agreed ways of capturing, updating, and maintaining information that everyone follows consistently. SOPs aren’t bureaucracy for its own sake, they’re what turns a well-configured system into a reliable one. Without them, even the best platform will gradually accumulate the same inconsistencies and shadow processes it was brought in to replace. With them, the system becomes genuinely trustworthy, and the organisation stops relying on one person’s memory to hold it together.
That’s why the transition matters as much as the technology. Done well, moving toward a connected system is an opportunity to listen to what teams actually need, to remove friction that people have quietly been working around for years, and to build cross-team alignment around a shared way of working. An objective view from outside the organisation can help enormously here. Not to tell people what to do, but to reflect back what’s working, what isn’t, and where the real opportunities lie.
The shift worth making
The question worth asking isn’t “what else do we need?” It’s “how well does what we have actually work together?”
For many organisations, the answer to that question points not toward new tools, but toward rationalising and connecting what already exists. It means being willing to retire the spreadsheet that’s been running the room schedule since 2011, even though it feels safer than trusting the system. It means investing in configuration and implementation, not just licensing. It means thinking about software as infrastructure, the foundation everything else runs on, rather than as a series of individual solutions to individual problems.
Arts organisations are operationally complex in ways that generic business software rarely accounts for. Multiple revenue streams. Productions that span hours or months. Stakeholders who are simultaneously customers, funders, partners, and community members. The organisations that manage this complexity well are the ones that can see it clearly, in one place, in real time, without having to pull it together by hand.
But it doesn’t end at go-live. Organisations change: teams grow, priorities shift, new pressures emerge. A system that was well-configured two years ago may have quietly drifted out of step with how the organisation actually works today. Regular review, checking whether processes are being followed, whether the system is being used as intended, and whether the SOPs still reflect reality, is what keeps the investment working. The goal isn’t a perfect implementation at a point in time. It’s a platform that grows and adapts alongside the organisation it serves.
That’s what connected systems make possible. Not a technology transformation, a clarity transformation.
In our 40th year, Artifax remains built around the operational reality of arts and cultural venues, shaped by people who understand the complexity of what you manage day to day. Our approach combines a connected platform, where data is captured once, owned clearly, and presented in the way each team needs it, with the sector expertise and partnership to help you get the most from it. We know the difference between a system your team maintains and one your organisation actually runs on. We don’t just understand the software, we understand the work.