Ciao is a fictional restaurant that I created as a passion project. I created it all: the brand identity, the menu, and the site. You can see it here: blueprintmrktg.com/portfolio/ciao
When I built it about a year ago, I was thinking about how it would look. I wasn't thinking about what happens after someone sees it, and that's the half I've spend most of my time on now.
What the site does
It tells you who Elisabetta and Luca are and why they cook the way they do. It shows you the hours, the location details, and enough of the menu to envision the meal. It looks like a place you'd want to eat at on a Saturday night, which is what a restaurant site is supposed to do.
What it doesn't do
There's a phone number, an Instagram handle, and a newsletter signup. That's the only way to reach them, and two of those channels only work if the restaurant is actively monitoring them.
Service runs 5:00 to 10:30. So does the phone. If somebody calls at 7:20 on a Saturday wanting a table for two tonight while the host is juggling walk-ins and table turnover, the call goes unanswered and they book next door instead. If someone sends a DM at 9pm about a private booking for twenty, by the time anyone checks Instagram the next morning, they've booked elsewhere.
But these losses are invisible. There's no log of unanswered calls or unread messages. The night was busy enough to feel good, but nobody's counting the revenue that walked out the door.
What I'd build behind it
1. The call nobody could take. A missed call gets a text back within seconds, with the reservation link and the hours. The person who called is still holding their phone, still deciding where to eat, and now they have a way to book that doesn't require anyone to be free.
2. The table that just opened. A 7pm Saturday cancellation is a revenue hole, and it usually stays empty. Filling it would mean pulling someone off the floor to work the phones during dinner rush. Instead, anyone who asked about that night gets an instant text the moment the slot opens, and the table books before staff even notice it was cancelled.
3. The guest who came once. Someone books a birthday dinner and has a great night, but then never hears back from the restaurant. Instead, an automatic message goes out, asking how it went, and giving them a reason to come back while the meal is still fresh in their head.
Why this matters for your business, not just restaurants
Service businesses—restaurants, salons, studios, clinics—look nothing alike, but they lose work in exactly the same three places: the enquiry nobody could answer, the slot that opened and stayed empty, and the customer who came once and quietly stopped coming.
What changes is the frequency. A restaurant might see you twice a year. A recurring service might book you every few weeks. And the faster the booking cycle, the quicker the drift. By the time you notice the gap, they're already booked with someone else.
A good site brings people to the door. Something still has to catch them once they get there.
If you want to know where that's happening in your own business, I do a free 30 minute audit and tell you what I find. See the Ciao site here.