Certified Pizza Catering roll in the ovens and cook fresh pizza on-site — birthdays, weddings, job sites, anywhere in Sydney they can set up. They had a website when we met them, but it wasn't pulling its weight. Every booking still came in as a DM or a missed call, and someone had to stop what they were doing to answer it.
Hey! Are you free the 14th? Backyard 60th, about 60 people
And how much roughly?
Hi! Let me check the calendar and get back to you 👍
Unanswered · 2 days laterNo more back-and-forth. They book, pick a package and pay the $100 deposit in one go.
There was never a shortage of enquiries. The trouble was answering them. Every one needed a person, and the only people who could answer were usually flat out cooking.
Someone would ask about a Saturday. To find out, you'd have to go and ask the one person who kept the calendar in their head. Then they'd want a price, so you'd talk them through the packages again. Then the headcount, which never stayed the same for long. A few days later the date had either gone to someone else or the customer had gone quiet, and no one could tell you which.
None of this is unusual for a catering business, and none of it ever shows up as a lost booking you can point to. It shows up as evenings eaten up by the phone, and the enquiry that came in at 11pm and sat there until Monday, long after the customer had moved on.
The site went up first, covering the things people used to ring up and ask: what they cook, how it works, what it costs. The booking system is the bigger piece. It goes from the date to the deposit, and none of it needs someone at Certified Pizza to be free to answer.
The calendar won't offer a date sooner than seven days out. That's how long the kitchen needs to shop and prep, so nothing gets booked that can't be cooked properly.
There are two sessions a day, 12pm to 4pm and 6pm to 10pm, and each one can take two events. The page checks what's left before it offers you anything, so the same slot can't go out twice.
Three packages, from $25 to $32 a head, with all the details written out under each one.
Put in a number and the estimated food total moves with it. If it lands under the $1,400 minimum, the page says so before you go any further.
$100 through Square holds the date, and the balance is settled with a person before the event.
Not everyone wants to book on the spot. The enquiry form takes the date, location, headcount and package, so whoever replies within 24 hours isn't starting from scratch.
Charging the full amount up front would have been the same build, so this wasn't a technical decision. We didn't do it because a pizza catering job isn't a checkout. The headcount changes, people add things on, and someone still has to work out where the van can park. If a customer pays in full before speaking to anyone, they haven't really booked anything yet.
So the deposit is only there to hold the date. The session comes off the calendar, nobody's keeping a Saturday free for a maybe, and then someone from the business picks it up and confirms the balance before the event.
The automation was the straightforward part. The real decision was where to make it stop.
There's no dashboard metric to point at here. What changed is a list of things nobody has to do anymore, on both sides of the booking.
A booking system is more than a website. It has to keep track of a calendar and take money, and it has to get both right at nine on a Saturday night when there's nobody around to fix it.
So we don't hand the website to one company and the software to another, with someone else again on the domain, the email and the server it runs on. It all works together, so the same people look after all of it.
Tell us where the manual work is — the bookings, the forms, the thing someone retypes every week.