SOUPY FOR COMPETITIVE SOCIALISING
The whole night.One booking.
A game. A bite. Another round. Let guests make a night of it, with the resources, timings and team behind every part of the visit.
Your kind of venue. Your kind of Soupy.
In the product today
THE PEOPLE BEHIND A GREAT NIGHT
They came for a game. Give the whole occasion a plan.
Pool into dinner. Darts after drinks. A birthday with a few more moving parts. Connect configured activities, menus and extras in a sequential visit the guest can understand and the team can run.
Meet the products behind it
A LITTLE LESS EXPLAINING. A LITTLE MORE EXPLORING.
Give it a go.
Step through a fictional night. The controls change this example; they never create bookings, send messages or take payment.
4 friends. One visit. · Interactive example
Play. Eat. Play something else.
Build an example evening. Change the group size or add a second activity to see how resource availability affects the whole visit.
Start with pool.
4 players · 18:00 · Pool table 2
Illustrative published options and prices. Allow 15 minutes between parts; those gaps are not charged.
- 01Pool · Table 218:00–19:00 · 4 players£20
- 02Food · Table 619:15–20:00 · 4 guests£64
One sequential visit, with the actual resources behind each part. A real quote rechecks availability and payment requirements before confirmation.
Explore multi-part Bookings2 stages for 4 players. Example total £84. This is a draft, not a reservation.
Fictional records. Try the controls freely: nothing is booked, sent or charged.
THE RIGHT PRODUCTS FOR YOUR OPERATION
Start with what
earns its place.
A connected system. A practical starting point for competitive socialising. Enable the products you need, then build from there.
Bookings
Resources, timings and sequential activities in one configured guest visit.
Explore BookingsInbox
Keep group and corporate enquiries together, with reviewed booking proposals.
Explore InboxCRM
Remember the customer and the occasion, with permission-aware follow-up.
Explore CRMAnd the work
around it.
Products are enabled separately. Availability follows your workspace, permissions and provider setup.
A little less guesswork
Put your numbers
to work.
Change the assumptions. Watch the result. See what a different week could look like, on your terms.
Make every slot earn its place.
Play with your session length, changeover and utilisation. See the difference between a full calendar and a useful one.
Keep different capacities, session lengths and pricing separate. Count each physical resource in one type only.
How this is calculated
For each resource type: available sessions = resources × operating days × floor(open minutes per day ÷ (play minutes + changeover minutes)). Expected sold sessions = available sessions × utilisation. Sales = sold sessions × price, multiplied by guests per session only for per-person pricing. Add the independently calculated types for the venue total.
Resources and daily opening windows are identical within each type. Add different types separately and do not count a shared resource twice. Each session includes a full changeover, including the last one. Fractional sold sessions are an expected weekly average. The model excludes closures, shared staff constraints, tax and costs; it is not live availability.
Give the hours back to the room.
Model the time your team spends on recurring work. Use totals for all your sites combined, and keep each task distinct.
Use the hourly employment cost you want to value, including any employer costs. No employment or wage rates are assumed.
What does your current software cost?
Optional. List each tool once, using its monthly cost across all your sites. For an annual bill, enter the monthly equivalent.
Current spending only. This does not assume Soupy replaces any tool or predict a saving. Kept separate from staff time and venue economics.
How this is calculated
Weekly time = task frequency × people involved × minutes per task ÷ 60, summed across the listed tasks. Time released = baseline hours − scenario hours. Annual time value = hours released × hourly cost × operating weeks.
Time value is not cash saved, a staffing reduction or a promise of what Soupy will deliver. A longer scenario takes more time and produces a negative result. Do not count the same work in two tasks. This result stays separate from venue sales and contribution.
ONE VENUE. OR THE NEXT CHAPTER.
Keep your character.
Connect your operation.
For owners
Start with the work that matters most. See the relevant products and work through your own commercial assumptions.
For the team
Clear running orders, shared context and access that follows each person’s responsibility.
For growing groups
Keep businesses, sites and teams organised, with deliberate permissions and the right operating context.
Can guests book more than one activity?
Configured Bookings journeys support up to six sequential parts at one venue, within one seller/currency context and one lead customer. Parallel subgroup itineraries are outside this composer.
Can we price by person or by resource?
Resources support configured pricing bases, durations, increments and time bands. The calculator lets you compare per-resource and per-person scenarios; it is not a quote from your live inventory.
What happens when equipment needs a repair?
Assets and Maintenance keep condition, reports and repair work traceable. A maintenance report does not automatically close bookable resources; availability is managed in Bookings.
Does Soupy handle scoring or leaderboards?
This offering connects booking, hospitality and venue operations. It does not claim game scoring, leaderboards or an automatic itinerary optimiser.
Explore first. Talk when you’re ready.
Let’s talk about your venue.
Tell us what a better working day would look like. We’ll use your priorities to make the conversation useful.
No calculator figures are sent unless you choose to include your brief.
About the photography
Licensed venue photography sets the scene. Pictured people and venues are not presented as Soupy customers or endorsers. Product examples use fictional records.
Unsplash licence