An event business runs on many small promises: a date, a venue, a vendor, a quote, an invoice. When these live in spreadsheets, chat threads and one person’s memory, something slips. One system can hold the whole chain, from the first enquiry to the final invoice, so the team works from the same facts.
Enquiry to quote
Every event starts as a message. Capture it in one place with the date, the type of event, the rough size and who asked. Then build the quote from the same record, so nobody retypes details.
What to look for:
- every enquiry has an owner and a next step
- quotes can be revised without losing earlier versions
- a lost enquiry is recorded with a reason, so you learn from it
Scheduling and the calendar
Once an event is confirmed, its date and venue should appear in one shared calendar. This sounds basic, but double booking a venue or a team is one of the costliest mistakes in the business. A single calendar that everyone checks beats several private ones.
Bookings and tickets
Some events need bookings and tickets: seminars, workshops, ticketed shows. The system should take a booking, issue a ticket for each attendee and show how many places are left. For private events such as weddings or corporate functions, the booking is simpler, but the same idea applies: one record per event that everything hangs from.
Each event as a project
This is where an event business gains the most. Treat each confirmed event as a project with tasks and owners: book the stage, confirm the caterer, arrange the sound, print the signage, brief the crew. Give each task a person and a date.
Then the project view shows what is done, what is late and who is waiting on whom. The manager no longer asks around. Reusing a task list for a similar event saves effort and prevents forgotten steps.
Vendors and suppliers
Most events depend on outside vendors: caterers, decorators, sound and light, transport. Keep their details, what you agreed and what you have paid in one place. If the same vendor is used again, you start from the earlier terms rather than from scratch. Tie each vendor to the event it belongs to, so you can see what each event really cost.
Billing
Invoicing should come from the same record as the quote. Part payments, advances and the final invoice are then easy to follow, and you can see which events are fully paid and which are not. Keep accounts in step with the event, so the figure you quote, the figure you invoice and the figure you book are the same figure. Ask your accountant how they want the entries to look.
Questions to ask before you choose
- Can I see one event from enquiry to payment on a single screen?
- Can a task list be copied from a past event?
- Can I see what an event earned after vendor costs?
- Who can see what? Not every crew member needs to see quotes and margins.
Start with one event type
If you run several kinds of event, start with the most common. Set up its flow, run a few real events through it, and adjust. Adding another type later is easier once the team trusts the system.
Review each event afterwards
When an event ends, spend a short while comparing the plan with what happened: tasks that ran late, vendors who let you down, costs that surprised you. Keep those notes on the event record and use them to improve the task list for the next one.
Where Teapot Techies fits
We set up Odoo for event teams, covering scheduling, bookings and tickets, projects and tasks, and billing, starting from standard Odoo and adjusting it to how you plan and run events. Read more on our event management page or about Odoo implementation.