Club overview
What to do this week
Worked out across tickets, {{sts}}, hospitality and partners. Each one links to the people behind it.
One customer, across everything
What you can only see once tickets, {{sts}} and hospitality share one record.
Every {{game}} this season
Crowd, hospitality and revenue for each date, played and coming up. Click one for the detail.
Where the money comes from
Revenue this season by area, against the same point last season.
Every name, fixture and figure is example data generated for this prototype. With your systems connected, the same views come from your own data.
Ask your data
Once tickets, {{sts}} and hospitality sit together, nobody has to build a report. Ask a question in plain English and get the answer, with the people behind it ready to export or email.
In this prototype the questions above have their answers built in. The live system answers questions about your own data in the same way.
Ticket sales
Sales for every {{game}} by {{stand}}, against capacity and against the same fixture last season. Whether tickets sell through your current platform or through ours, this is what the numbers mean and who to talk to.
Sales pace
By {{stand}}
{{Sts}} and tickets sold so far, against capacity.
Where {{fans}} come from
Distance from home, for ticket buyers and for hospitality customers. Use it to decide where marketing money goes.
How they buy
Tickets this season by channel.
This season so far
The crowd at every {{game}} played, how many {{stSeats}} went unused, and ticket revenue.
{{Sts}}
Every {{holder}}, how often they actually come, and how likely they are to renew. Spot the ones drifting away months before renewals open, while there is still time to do something about it.
Renewal forecast for next season
Ready to act on
Lists built from attendance and spend, ready to call or email.
Hospitality dashboard
Coming up
Every room for the next four {{games}}, against capacity, with booking pace compared to the same fixture last season.
Needs your attention
Worked out from the bookings, so nothing slips. Each one links to the people or the list behind it.
Booking pace
Places booked in the weeks before {{ko}}. Shows whether a fixture is on track while there is still time to act.
Show as a table
{{oppsSell}}
Average share of {{md}} places sold, last three seasons. Use it to set prices and to decide where to put your selling effort.
How full each room is, by season
{{Md}} places sold as a share of capacity. {{curSeason}} covers the {{games}} played so far.
Where the money comes from
Hospitality revenue by room, this season so far against the same point last season.
Eight example spaces. Prices, fixtures and guests are generated for this prototype. With your real bookings these figures come from your own data.
Hospitality diary
Every room, a week at a time, with what is on in each one. Days with several events show each event in its own room, so a meeting in a box, networking in the bar and a private party in the lounge all sit side by side. {{Md}}s and bigger events show the places booked against capacity. Guests with access needs are flagged in every cell, and a red flag means a room can't meet a need. Click a day for the bookings, and a booking for the guest's details and history.
Rooms, capacities, fixtures, events and guests are examples. Each venue sets up its own rooms, set-ups and access facilities.
{{Md}} sheet
Everything the team on the door, the stewards and the kitchen need for one fixture or event: who is coming, access needs checked against each room, dietary needs and balances still to collect. Download it or open it on a tablet on the day.
Access check
Each room's facilities against the needs of the guests booked into it.
Rebooking reports
Everyone who booked for {{anOpp}} or an annual event in past seasons, with their contact details and whether they've booked again yet. Ready to export or invite back.
Customers
Everyone who has booked hospitality, with what they've spent, how often they come, what they need and whether they hold {{aSt}}. Regulars, lapsed regulars and new customers are worked out from their bookings.
Campaigns
Turn a report into an email in two clicks. Pick who it goes to, check the message and send. Replies and bookings are tracked back to the campaign, and anyone who hasn't agreed to marketing is left out automatically.
1. Who it goes to
Built live from the bookings.
2. The message
Words in curly brackets fill in for each person.
Recent campaigns
What each one brought back. Example results.
Partners and sponsors
Every business in one record: the boxes they book, the {{games}} they sponsor, their business club membership and their staff party. Whoever picks up the phone knows the whole relationship.
Sponsorship still to sell
The next six {{games}}. Hover a cell to see who bought. Sell the gaps first, starting with last season's sponsors.
Booking widget for your website
Hospitality and venue hire booked straight from your website. It sits on your existing pages in your colours, shows what is available, and asks for access and dietary needs up front. Every request lands in the diary for your team to confirm and invoice. Try it: make a booking and then look for it in the diary.
Hospitality and private events
See what is available and send a booking request in a couple of minutes.
Example prices. {{Md}} tickets are still issued through your ticketing as now; the widget takes the booking, the guest details and the needs.
How it works
Two ways to work with us. Connect what you already have, or run everything that touches a {{fan}} or a business on one system we build and run for you: tickets, {{sts}}, hospitality, partners and your app. You choose, and you can start with one and move to the other.
Connect what you have
Keep your ticketing platform. We connect to it and everything else, and give every team one view.
- Ticket and {{st}} data pulled in by report, export or API
- Hospitality diary, {{md}} sheet and invoices run on our system
- One record per {{fan}} and per business
- Dashboards, renewal warnings, campaigns and answers in plain English
One system for everything
Everything in Option 1, plus ticketing itself, built and run by us. No data waiting in someone else's platform, and every sale and every scan in one place.
- Tickets sold on your own website, with seat selection
- {{Sts}} sold and renewed online, with Direct Debit instalments
- Tickets in your own app and in Apple and Google Wallet, with a code that refreshes to stop touting
- Entry through the turnstiles you already have
- A ticket exchange, so unused seats resell instead of sitting empty
Side by side
| Option 1: connect | Option 2: one system | |
|---|---|---|
| Ticketing | Your current platform | Ours, on your website and app |
| {{Fan}} data | Updated by report or API | Live: every sale, renewal and scan |
| {{Sts}} | Sold on your platform, analysed here | Sold and renewed here, with Direct Debit |
| Tickets in your app | Through your platform's app partner | Built in, with wallet passes |
| Booking fees | Stay with your platform | Yours |
| Getting started | Weeks | Phased, switching ticketing over at a season break |
What each team gets
How we would build it
Option 1 is steps 1 and 2. Option 2 carries on through steps 3 and 4, at the pace that suits you.
Why us
Pixel and Shovel, Brighton · hello@pixelandshovel.co.uk