Every restaurant booking, confirmed and seated.

A reservation path on your own site that says what the table is before anyone books, a confirmation the guest answers in one tap, and a released table in front of the host by three in the afternoon. Questions at eleven at night answered from your own guidelines.

Cut my no-shows on a 30-min call

Seven problems a restaurant lives with, and what we build for each.

Each one is a problem we hear from this trade, in plain words, and what a SharpHaw subscription puts in its place.

  1. A woman at her kitchen table late on a Sunday night under one pendant lamp, phone to her ear waiting for an answer, her hand on a handwritten list of names for a birthday dinner, a mug beside her

    01 · The problem

    Questions arrive on a Sunday night, and nobody can answer.

    People ask about opening hours, allergens, parking or a table for twelve while you are closed. By Monday morning they have booked somewhere else.

    What we build

    Support (opens the workspace in a new tab)

    A support chat on your website that answers day and night using your own rules and your own menu, and books the table when it can.

  2. The host at the reservation book on the stand by the door, pen stopped mid-line, looking up as a family arrives: a pram, a bunch of balloons and a grandmother with a walking stick

    02 · The problem

    A booking tells you a name and a time, and nothing else.

    You find out what the table needs when the guests walk in: how many, which sitting, a birthday, a pram.

    What we build

    Forms (opens the workspace in a new tab)

    A booking form on your own website that asks how many people, which sitting and the date, and tells the guest what the table includes before they book.

  3. The chef at the pass during evening service reading a message on his phone, a row of plated starters waiting under the heat lamps, a long laid table standing empty in the dining room behind

    03 · The problem

    Reminders go out, and nobody can reply to them.

    The guest cannot answer the message, so a cancellation reaches you at 19:40 with the food already prepped.

    What we build

    Automations (opens the workspace in a new tab)

    A confirmation the guest answers with one tap. If they cancel, the host knows by three in the afternoon, with time to fill the table.

  4. The host mid-service with the phone wedged between shoulder and ear, a stack of menus in one hand and a finger on the paper waiting list, two couples in coats waiting inside the door

    04 · The problem

    The waiting list is on paper, and nobody has time to call it.

    When a table frees up during service, the host has a phone in one hand and six menus in the other.

    What we build

    Customers (opens the workspace in a new tab)

    Guests join the waiting list from your website with their party size and the times they can do. When a table frees up, the list is called in order.

  5. The chef alone at a corner table between services, looking at a laptop, a phone and a printed menu laid side by side, each in a different colour and style

    05 · The problem

    Your brand looks different on the website, the email and WhatsApp.

    Each message looks like it came from a different place, and none of them look like your room.

    What we build

    Brand Kit (opens the workspace in a new tab)

    One brand across your website, every email and every message, built from your business and kept the same everywhere.

  6. The dining room on a quiet Tuesday night seen from the door: two tables taken, the rest laid with candles and empty, a waiter folding napkins with nothing to do, the chef in the pass with his arms crossed

    06 · The problem

    Tuesday and Wednesday are half empty.

    Friday turns people away while the quiet nights stay quiet, and the ads run the same every day.

    What we build

    Ads

    Ads planned around your week, aimed at the sittings that need filling, and measured in bookings rather than clicks.

  7. The staff meal before service: the chef, the host, a waiter and two cooks around one table by the pass, passing a tray of food and laughing, the dining room laid and empty behind them

    07 · The problem

    New guests have no story to trust, only a menu and a map.

    Nothing on the site says who cooks, where the fish comes from, or why the place exists.

    What we build

    Content Engine

    A blog about the kitchen, the suppliers and the team, written from your business, so people know the place before they book a table.

The site and the workspace, open before you book.

SUMI is invented and the photographs are generated, so we can show the work in full. The design, the code, the forms and the workspace are exactly what you would get.

The site · SUMI

Website design for a fourteen-seat sushi counter: an ink-black homepage with the name Sumi in a mincho serif and a brushstroke drawn down the page

A fourteen-seat counter with two sittings, and a reservation that asks covers, sitting and date up front and refuses a party the room cannot seat.

Open the site (opens in a new tab)

SharpOS · Customers

SharpOS Customers: a real capture of a seeded demo workspace: the CRM table listing customer records with emails and dates

The waiting list and the guest list as one record you hold: name, party size, the window they can make, and the nights they came.

Open the workspace (opens in a new tab)
Pricing

The price, before you ask.

Starter is €2.500/month, plus VAT, no annual contract, no setup fee. Everything on this page runs on it. Move up, down, or out any month.

Starter

€2.500/month

For a business that wants one partner across the website, the content, the ads and the automations, instead of four suppliers.

  • Conversion-focused premium website
  • SharpOS workspace access
  • 1 new landing page per month
  • 4 blog posts a month: your expertise, built to be found
  • Ads management on Meta and Google
  • AI automations for the recurring work
  • Up to three channels managed
  • On-page SEO and GEO optimisation
  • Monthly performance report
  • Performance work, audits and uptime monitoring

All prices are plus VAT, which varies by your country of taxation. No annual contract, no setup fee, no minimum term.

Straight answers, before the call

Do we keep our reservation platform?
Yes, and it stays the book. What gets built is the path in front of it: your site saying what the table is, the request on your own domain, a confirmation and reminder the guest can answer, a waiting list the host can work, and a report that counts seated covers. Where a platform can be connected we confirm it first; nothing on this page promises it.
Can the assistant answer allergen questions?
Not from memory, and not on its own. Allergen information is a duty the kitchen carries, so the assistant points to the allergen list your kitchen keeps current or hands the question to a person. It does answer the practical questions: sittings, party sizes, the step at the door, corkage, whether the terrace is covered, from wording you approved.
Who works the waiting list?
Your host, from a list that is already sorted. Guests join it from the site with party size and the window they can make, and a released table reaches the host with the matching names at the top. The ring is a person's job on purpose: a table released at 19:40 is resold by someone who can say "we can seat you at eight" in a real voice.
We run three rooms. Does one path cover all of them?
One workspace, one guest list, three rooms. Each room's request, confirmation and waiting list carry its own name and wording, and the report shows seated covers by room and by night, so the general manager sees the group and each host sees their own door.
What does it cost?
One fixed monthly fee with no discovery fee, no setup invoice and no minimum term, and the SharpOS workspace included rather than billed separately. Everything on this page is in Starter, the plan published above and on the Plans page, plus VAT, with no annual contract. Move up, down, or out any month.
Read the full FAQSee plans
How it works

One partner, one fee, one weekly loop.

What we stand for, how the fee works and how a week with us goes. The answers above cover the specifics; every line here can be checked on the Values page.

  • One partner, not four suppliers

    Website, content, ads and automations, run as one weekly loop from Starter.

  • One published fee, before the call

    Starter is on the Plans page, plus VAT, no setup fee, no annual contract.

  • The founder does the work

    The person on your first call is the person who ships it, every week.

  • Nothing finishes

    Plan, build, iterate: each month starts where the last one ended.

  • Yours stays yours, in writing

    Domain, brand, content and data are yours and leave with you.

  • And if you ever leave

    Any month, no exit fee, two months of continuity; the engine stays ours.

Who you would be working with

SharpHaw is one senior software engineer, Gabriel Espinheira, running the website, the content, the ads and the automations as one weekly loop for businesses across Europe, with SharpOS as the workspace it all runs in. How that works, who does the work, and everything the subscription covers are written up on the site.

About SharpHawOur services

Bring one Friday's book. Leave knowing where each no-show began.

Thirty minutes on one Friday's book: where each booking came from, when it was last confirmed, and which tables stayed empty with the prep done for them. Yours whether or not you engage. No proposal afterwards.

Cut my no-shows on a 30-min call