A weekend trade, managed on weekdays on a corner of the table
The owner of a private event venue juggles enquiries arriving by phone and messages, the calendar of booked weekends, the deposits that confirm (or don't), damage deposits to collect then return, extras added along the way — tableware, cleaning, sound system — and a check-in and check-out condition report for every rental. Most often, all of it lives between a paper diary and a spreadsheet.
The serious tools in this market target town halls and public facilities, not private owners; the private-venue specialists are English-speaking platforms built for other habits. The documented reality: people literally search for free Excel venue booking templates — and the weekend promised twice eventually happens.
Your bookings, extras and deposits — structured
Describe how you work: “I rent out a converted barn for weddings and birthdays. A booking has a date, a package (day, weekend), a status: enquiry, hold, deposit received, paid in full, completed. Each booking has its extras (cleaning, tableware, sound system), a 30% deposit, a damage deposit returned after the check-out report. I want the year's calendar, pending deposits and damage deposits to return.”
The generated application structures that mechanism: the calendar of dates, bookings attached to clients with their statuses, priced extras, payments — and the two lists that protect the business: what must be collected, what must be returned.
- Bookings: date, package, status, amounts
- Clients and open enquiries
- Extras per booking: tableware, cleaning, sound system
- Payments: deposit, balance, damage deposit held / returned
- Check-in and check-out condition reports with notes
The typical weekend, secured from enquiry to returned deposit
An enquiry comes in: you check the date in two seconds, place a hold with its expiry date. Deposit received, the booking confirms and the weekend locks. On Friday, the check-in report fills in from a phone; on Sunday, the check-out one — and the damage deposit is returned (or withheld) on a written basis, not a memory.
The application arrives with realistic demo data (wedding season, varied packages, extras) to project yourself immediately, and three generation levels (Sketch, Craft, Masterpiece).
A tool that belongs to the venue
A venue gets passed on, sold, developed: its rental history and client base must stay with you. Code ZIP export, GitHub push, free hosting or the included dedicated URL.
Free Discovery plan for the first application; Pro (€25/month) and Max (€149/month) to iterate, with the cost shown before each generation.
Typical generated entities
- Booking
- Client
- Extra
- Payment
- Condition report
Generated screens
- Year's booking calendar
- Booking detail: status, extras, payments
- Pending deposits
- Damage deposits to return
- Season dashboard
Dashboard indicators
- Weekends booked this season
- Pending deposits
- Damage deposits to return
- Revenue per month
Frequently asked questions — venue rental
Can my clients book online themselves?
The generated application is your internal tool: you enter enquiries received (phone, messages, visits). Since the code is exportable and standard, a public enquiry form can be added by a developer if volume justifies it.
Can we manage several spaces (hall, garden, adjoining cottage)?
Yes: describe your actual spaces and each booking attaches to one or more of them — the calendar shows availability per space.
Are booking statuses imposed?
No: you describe YOUR statuses (enquiry, hold, deposit received, paid in full, cancelled…) and they structure the application. A hold with an expiry date gets chased before it is lost.
Can condition reports be done on a phone?
Yes: the generated application is a web application usable from a phone — check-in and check-out reports fill in on site, with dated notes.
What does it cost for a single venue?
The first application generates for free (Discovery plan). Paid plans (Pro €25/month, Max €149/month) only matter if you iterate more — with the cost shown before each generation.