Mesa Miúda — you don't book a table, you book the neighbours

Table booking is a crowded, solved-looking market. Every tool answers the same two questions, when and how many, and competes on speed. So we didn't build another booking form. We looked for what everyone misses.

The client.  Mesa Miúda is a 38-seat bistro in Príncipe Real, Lisbon. Marta owns it and cooks every night from 18:00 to 23:00. It has one long, narrow room with windows on one side and a bar and a 10-seat table at the far end. A host works only Thursday to Saturday. About 70% of bookings arrived as DMs, 4–6 messages each, mostly while Marta was cooking. Around 15% of Friday tables didn't show, and every week there was a review like "great food, but we sat next to a loud birthday."

Three insights from mapping the guest's and the owner's journeys:

- Noise belongs to the booking, not the person. The same guest celebrates on Friday and wants quiet on Tuesday. So we don't ask "are you an introvert?", we ask "what kind of evening is it?"

- No-shows start with friction. Cancelling means an awkward call, so people just don't come. One-tap cancel frees the table for someone else.

- Demand peaks when the owner can't reply, so the system has to answer, not the person.

The model.  Every booking gets a noise score from party size, celebrating and kids. Every table gets a forecast from its neighbours. A quiet dinner protects the tables around it, and celebrations go to the lively end by the bar. If nothing fits, the guest never hits a dead end: they get another time, another table or the waitlist. The rules also cover 2 high chairs, deposits for groups of 6+, and nights when Marta is alone.

For the guest: from "can I book?" to "you're booked" in about 27 seconds.

- Pick the evening: quiet, celebrating or no preference.

- See real availability and a live floor plan with the suggested table.

- Get confirmed instantly.

- Confirm, move or cancel in one tap from a WhatsApp reminder.

- After the visit, one question: was the noise right?

For Marta: she never has to open a dashboard. At 16:00 she gets a digest ("34 covers tonight, nothing for you to do"). Nothing interrupts service. At 23:15 she gets a summary, and real decisions arrive as one-tap buttons. Everything else runs by itself:

- instant replies to DMs with a booking link, and one follow-up with three options;

- a seating plan that builds itself;

- reminders the day before;

- unconfirmed tables released to the waitlist;

- guests who pick new times themselves when the kitchen has a problem.

The result: about 8.7 hours a week back for Marta, reply time down from ~3 hours to seconds, Friday no-shows aimed from 15% below 5%, and roughly €12,000 a year recovered. The limits: groups of 6+ still need Marta's tap, and walk-ins stay outside the system.

Built in Lovable. Full CJM here DEMO PROJECT here A note

I'm an introvert, and for me a good dinner out starts long before I sit down. Every time I book, I spend time on it: messaging to ask which tables are free, trying to get a quiet corner, calling before I leave to check they haven't seated a big party next to me. And sometimes it still goes wrong.

That's where Mesa Miúda came from. I wanted a booking that already knows what kind of evening I want, without making me explain it three times. It also doesn't label anyone: it never asks "are you an introvert?", only "what kind of evening is it?". It turned out the same idea saves the restaurant owner hours every week, so a quiet evening for me and a calm Friday for Marta come from the same system.