Have the box-office figures ready before the meeting.
Sales reports arrive in different formats. Before the marketing meeting, someone has to combine them and work out whether a change comes from attendance, ticket price or incomplete information.
Agree the reports, productions, update schedule and who can see them. Show when each report was last received and flag missing information instead of treating it as zero. Updates depend on the sources agreed for your build.
Compare the right weeks
Use daily and Monday–Sunday views, weekly targets and equivalent weeks of previous productions. Define the comparison with your team: reporting dates, performance dates, attendance, ticket quantities and the basis of average ticket price.
Separate advance sales from performances already given
Tickets sold for a future performance answer a different question from income relating to a performance that has taken place. Keep those views distinct and agree gross/net definitions with finance. This is reporting software, not a ticket-selling system.
Where we would begin.
Bring a sample venue report and the questions your team asks in the weekly meeting. We agree one useful view, its definitions and how to check the totals.
Not necessarily. We start with the process you want to improve, then agree whether it needs a connection, an export or a separate tool. Compatibility and any migration are checked during scoping.
Who decides the financial rules and contract terms?
Your team and advisers approve those rules and templates. We implement the agreed process and test it against examples you have checked.
How much does a project cost, and how long does it take?
That depends on the process, the source data, connections and review requirements. We agree the first deliverable, price and schedule before development; there is no universal package or promised turnaround.
Who owns the software, and who supports it?
Ownership, source-code access, licences, hosting, maintenance and support responsibilities are set out in the project agreement. We can discuss managed hosting or deployment to your own environment.
What should we bring to a discovery call?
No preparation is required. If useful, have one spreadsheet, form or repeated task in mind. In 30 minutes we can talk through the process and identify what it would take to automate it.
Free 30-minute discovery call · Google Meet
Talk through one process.
Identify what it would take to automate it. No preparation required; if useful, have one example in mind.
