appy.agency
CRM for restaurants

A CRM built for restaurants

Reservations, regulars, private events and suppliers in one place — the book fills itself, no-shows get chased, and your best guests stop being strangers.

Free · no signup · a real plan and price in ~10 minutes, in your words.

to a working prototype
~1 week
to start
€500
chased automatically
No-shows

Off-the-shelf CRMs were built for a sales team. Not for restaurants.

Reservations live in three places — the booking widget, the phone pad and someone’s memory — and doubles happen on the nights you can least afford them.

No-shows cost real covers every week, and the deposit rules that would stop them are too fiddly to run by hand.

Your regulars are your margin, but nobody can say who they are, what they drink, or that they haven’t been in since March.

Private-event enquiries rot in the inbox for days — the couple books the venue that answered first.

See it from the inside

What your CRM would look like — screen by screen.

Not stock screenshots — this is the shape of the system we’d build for restaurants: your records, your stages, your words. Click through the screens.

The pre-service screen — tonight’s covers, who hasn’t confirmed, and the event enquiries that arrived while you were plating lunch.

A real starting point

Here’s the analysis we’d start from — for restaurants.

Not a template. This is the data model, pipeline and automations a business like yours actually runs on — mapped in your words. Your free analysis produces exactly this, shaped to you.

Your system, mapped

Your pipeline, exactly as your CRM would show it — your stages, your words. This is what we build from.

What it tracks

GuestsReservationsPrivate eventsMenusSuppliersDeposits

Where customers reach you

Booking widgetPhoneInstagramWalk-in

Connects to

Card terminalBooking widgetAccounting export

Busywork the system takes over

  • Booking confirmationsinstant confirm + day-before reminder, every channel
  • No-show depositscard hold on peak nights and parties of six plus
  • Regulars win-backa quiet nudge when a good guest goes missing
  • Event enquiry replymenus and dates out within five minutes, not five days

What this replaces — where it hurts today

  • Bookings split across three systems
  • No-shows eating peak nights
  • Regulars invisible to the floor

Your price, from your answers

Standard scope

Prototype · 1 weekstart here

€500

  • Guest + reservation records
  • One service’s booking sheet
  • The no-show deposit automation

Full build

€3,000€6,000

Estimate — it becomes one fixed price on the free call. Never hourly, no surprises.

€3,000every appy build lands in this band€9,000

What sets your scope

  • · Reservations + guest history in one book
  • · Deposit & no-show automation
  • · Private-events pipeline

Run · monthly

€160/mo

Hosting, monitoring, fixes and small improvements.

If you go all the way: ≈ €4,920 first year, all-in — and you own everything. Today's only decision is the €500 prototype.

Questions restaurants ask us

Does it replace our booking widget or work with it?
Works with it. Bookings flow in from the widget, the phone and walk-ins into one sheet — the widget keeps taking bookings, you finally get one book and one guest history.
Can the floor staff actually use it mid-service?
It’s built for the pass, not the back office — tonight’s sheet on a tablet, guest notes one tap away. If it needs a manual during service, we’ve built it wrong.
How long until we’re live?
A working prototype in about a week for €500. The full build usually lands in three to five weeks — quiet season is the perfect time to switch.
Who owns the system and the guest data?
You do — entirely. Your guest book is yours, hosted for you, exportable at any time. No per-seat lock-in, no platform holding your regulars hostage.

Have a mess like this one?

Book a free 30-min call. We’ll sketch what your version of this system would look like — and put a number on it.

Get a free plan & price