Eight weeks before the retreat
Your spring retreat has sixteen places across twin rooms, a few singles and one shared room. Places sold quickly in January, most with a deposit by bank transfer. Now you are eight weeks out, the balance is due, and your spreadsheet shows eleven people paid, three partly paid and two you are not sure about because the transfer reference said 'yoga'.
Two friends booked separately and want to share. Someone who asked for a single now wants a twin to save money. The venue wants final numbers, room allocations and dietary requirements by Friday. You are copying cells from the spreadsheet into an email and hoping the gluten-free note from the booking form made it across.
One person has not paid the balance and is not answering. The waitlist has three names on it, but you cannot release the place until you know.
Why retreats outgrow the studio's systems
Studio booking software sells classes and packs well. A retreat is a different product: a large sum paid over months, a room type, a room share, travel details and personal information the venue needs. Most studio systems handle it as a single event ticket, which leaves everything else in a spreadsheet.
The payment schedule is the heart of it. Deposit, one or two instalments, a final balance and a cancellation policy that changes over time. Chasing each of those by hand for every guest is where the owner's time goes.
Personal details also move around too much. Dietary needs and emergency contacts end up in emails, spreadsheets and messages, which is untidy and harder to look after properly.
What a spreadsheet retreat costs
| Weak spot | Consequence |
|---|---|
| Unmatched bank transfers | Uncertainty over who has actually paid |
| Instalments chased by hand | Late balances and awkward messages |
| Room shares arranged by message | Last-minute rooming changes |
| Details copied to the venue | Dietary notes lost or wrong |
| Waitlist held in your head | Places left empty when someone drops out |
There is also cash flow. Retreat venues often want their own deposits early, so unpaid balances on your side quickly become your money at risk.
A retreat booking system with payments built in
We build a retreat booking page and a small back office, connected to Stripe for payments.
- Guests choose a room type (single, twin, shared) and can name who they are sharing with, or ask to be paired.
- They pay a deposit by card and agree to a payment schedule. Instalments are collected automatically on the dates you set, with reminders before each one.
- Failed payments trigger a retry and a friendly message, and you see a list of anyone overdue.
- The booking form collects dietary needs, emergency contact and travel details once, stored in one place with access limited to you and the people who need it.
- A rooming list and dietary sheet for the venue are produced from the bookings, ready to send.
- When a place is released under your cancellation policy, the waitlist is offered the space in order.
Your cancellation and refund terms are yours to set, with advice from your own adviser. The system applies them as written.
Eight weeks out, with the system
The balance date passes and most balances collect on their own. Two failed, both retried, one succeeded. You message the last one. The rooming list is correct because guests chose their own rooms. The venue gets a clean sheet in minutes.
- Deposits and instalments collected automatically
- A live list of who has paid what
- Rooming and dietary sheets that match the bookings
- Released places offered to the waitlist
Is your retreat admin like this?
- Retreat bookings live in a spreadsheet.
- Deposits come by bank transfer with unclear references.
- You chase balances individually.
- Rooming is agreed over WhatsApp.
- You copy guest details into emails for the venue.