Osteria Marisalto · Build notes · Concept demo

Everything a restaurant can run from one system

Type the dish once. The website, the set menu, the printed card and the assistant all follow.

RestaurantItalian restaurant — what runs behind the websiteConcept demo

A concept demo for visual reference only — I don't use fixed templates. Your system is designed and built custom for your restaurant; use this to picture how yours could work and grab the ideas you like.

The problem

Where it hurts — and how it's fixed

Osteria Marisalto is a fictional Italian restaurant on the Gulf coast. This is what its owner sees: the same dishes and prices the website shows, in the one place they are typed. Change a price and the dinner menu, Thursday's set menu, the printed card and the assistant all follow; take the branzino off for three days and it disappears from all of them. Requests, reservations and private events arrive in one inbox; contracts and deposits sit next to them; the results page says what the site produced and how it knows.

The price changed in the kitchen, on the website last month, and on the printed card never — and the argument happens at the table.

One dish record. Food, drinks, set menus, specials and the printable card all read from it; a special price sits beside the real one and never overwrites it.

One price, everywhere, the second it is saved.

A birthday for eighteen, a catering enquiry and a gluten-free question arrive by phone, Instagram and email — and one of them is answered twice, one never.

Requests, reservations, private events and questions in one list with a state — new, open, done — and the contract and deposit for the ones that become a booking.

Every enquiry answered once; the ones worth money get a contract.

The website costs money every month and nobody can say what it brought in.

A results page that follows the visit to the menu, to the assistant, to the enquiry, to the booking — and says how it knows each number.

An owner who can see what the site produced, not guess.

The toolbox

Everything your restaurant can run here

Everything in this demo is interactive — here's what your restaurant can run from one system.

Live in this demo

Menu: food, drinks, set menus, specials and a printable card, all from one dish record; 86 a dish for a number of days.

Live in this demo

What's on: live music by night, events and promotions with a date on them.

Live in this demo

People: requests, guests, reservations, private events and follow-up in one list with a state.

Live in this demo

The assistant: what guests ask it, and what it could not answer — the questions the website should answer next.

Live in this demo

Reach, money and results: reviews and the Google profile, contracts and deposits, and what the site produced with how it knows.

Built to grow

What this system is built to grow

Recover time

The menu typed once; music, events and specials scheduled in one calendar instead of re-posted every week.

Grow revenue

Private events and catering answered the day they arrive, with a contract and a deposit behind them.

Protect profit

No stale price on a printed card, no dish sold that the kitchen took off, no deposit forgotten.

Under the hood

What I actually engineered

One record, many menus

A dish exists once; a set menu, a special and a printed card point at it. Hiding it for three days hides it everywhere, and it comes back on its own.

A printed menu that is a view

The printable card is laid out from the live records — paper sizes measured off real PDFs, tested — so the card in the stand is never a second copy.

Honest states on screen

What needs the owner's own accounts — live Google reviews, emailing guests — says so, instead of pretending to be connected.

Build notes

Honest about what's real

Built with

ReactNext.jsTypeScript

What it runs

Owner panel over one in-session store — nine areas, one dish recordConcept build — no sign-in, database, payments, email or Google account connected

Simulated in this demo

  • The restaurant, its guests, requests, reviews and numbers are invented. Menu edits last for the session; reload and the demo resets.
  • Nothing is connected: there is no website reading this panel, the assistant is not answering from it, and reviews, email, texts and deposits are shown as what they would need.

Wired up in production

  • Sign-in and staff roles, a database behind the menu, guests and requests, and the restaurant's website and assistant reading the menu live.
  • Reviews and the Google profile through the owner's own accounts, guest email with a privacy policy in place, and deposits through an approved payment provider.

Concept demo only. Osteria Marisalto is a fictional restaurant — its dishes, guests, requests and numbers are invented, and it is not a client project. It is a different restaurant from the Sole & Luna website demo on purpose: that one shows the site a guest sees; this one shows what runs behind it. The panel opens on its own page.

Custom-built for your restaurant

No fixed templates here — every build is designed from scratch around your restaurant. Use this demo as a visual reference: picture how yours could work and grab the ideas you like. Then I build yours around your brand, your menu, and the way you actually work — launched fast and priced fairly because the hard engineering is already solved.

NEXT STEP

Want this for your restaurant?

Choose the tools, send a scoped quote request, and get the right build priced after review.

Start your project