Fixed quote after a free call

Restaurant CRM automation that turns first visits into regulars

Guest details are scattered across the reservation platform, the POS, the events inbox and a marketing list nobody has cleaned in years. We connect them into one restaurant CRM, whether that is the guest book in SevenRooms or OpenTable, Klaviyo, Mailchimp or HubSpot, tag regulars, lapsed guests, birthdays and private diners automatically, and send consent-based messages that stop as soon as a guest books. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why restaurants lose track of their regulars

Most restaurants already hold more guest data than they use. The reservation platform knows who booked and how often, the POS knows what they spent, and the events coordinator has a folder of past private diners. None of it lines up, so the venue cannot tell who its regulars are or who has not been back since spring.

Marketing then falls back on a monthly blast to everyone on the list. Regulars get the same email as one-time visitors, guests who never opted in get messages they did not ask for, and nobody knows which campaign filled a quiet Tuesday.

What we build

What our restaurant CRM automation includes

One guest profile

Reservations, POS checks where the POS allows, Wi-Fi or website sign-ups and event enquiries matched by email or phone into one guest record.

Automatic segments

Regulars, first-time guests, lapsed guests, birthdays and anniversaries, private diners and big spenders, refreshed every night.

Consent kept with the profile

Where and when each guest opted in to email or text, so campaigns only reach people who agreed.

Lifecycle messages

A thank-you after a first visit, a nudge to lapsed guests, a birthday note, each with stop rules once the guest books.

Private dining follow-up

Past event hosts flagged before the same season next year, as a task for the events coordinator rather than a blast.

Weekly guest report

New guests, returning guests, lapsed guests won back and bookings that came from each campaign.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Guest data arrives

    A reservation, check, sign-up or event enquiry creates or updates a guest profile.

  2. 02 Automated

    Profile tagged

    Visit count, last visit, occasion dates and consent update the guest's segments overnight.

  3. 03 Automated

    Message queued

    Opted-in guests in a segment get the approved message for that moment.

  4. 04 Team review

    Team reviews campaigns

    The manager checks each new campaign, its audience and wording before it goes live.

  5. 05 Manager or chef decides

    Offers and pricing

    Discounts, set menus and any offer to guests are decided by the owner or general manager.

How it behaves

How the restaurant CRM system behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the guest sees

  • A thank-you after their first visit, if they opted in
  • A birthday or anniversary note they asked for
  • No more messages once they have booked again
  • An unsubscribe link that works first time

What the team sees

  • One profile per guest with visits, occasions and notes
  • Segments for regulars, lapsed guests and private diners
  • A weekly report of guests and bookings by campaign

What the automation does

  • Matches and merges guests from every source
  • Refreshes segments every night
  • Sends approved messages only to guests with consent

Edge cases and fallbacks

Same guest books under two emails
Matched on phone number and merged; unclear matches go to the manager.
Guest has no marketing consent
Profile is kept for service use only; no campaign is sent.
POS shares no customer data
The CRM runs on reservations and sign-ups, and spend is left out.
Reservation platform API limit or outage
Updates queue and retry, and the manager gets an alert.

Architecture

A restaurant guest CRM at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Reservations OpenTable, Resy POS checks Toast or Square Sign-ups Web, Wi-Fi, events n8n Match and merge Guest CRM Profiles, consent Campaigns Email and text Manager Approves offers Weekly report Guests and bookings
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Reservations, POS checks and sign-ups from the website, Wi-Fi or event enquiries feed the workflow.
  2. 2 n8n matches each record by email or phone and merges it into one guest profile with consent attached.
  3. 3 Segments trigger approved messages to opted-in guests, and the manager signs off any offer.
  4. 4 A weekly report shows new, returning and lapsed guests and bookings by campaign.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Restaurant CRM & guest marketing automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Where guest data lives today, which systems allow access, current lists and consent records.

  2. 02

    Design

    2 to 3 days

    Matching rules, segments, message moments, stop rules and report contents.

  3. 03

    Build

    1 to 2 weeks

    Connections, merge logic, segments, lifecycle messages and the weekly report.

  4. 04

    Shadow run

    About 1 week

    Profiles and segments build daily while messages go to a test inbox for the manager to check.

  5. 05

    Launch

    1 to 2 days

    Switch on one message at a time and walk the manager through segments and approvals.

  6. 06

    Support

    Ongoing

    New segments, seasonal campaigns and report tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n SevenRooms or OpenTable guest profiles (route confirmed per project) Square Customers API or Toast orders API Klaviyo, Mailchimp or HubSpot Twilio SMS Google Sheets or Looker Studio for the report

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Data sources, matching rules, segments and reporting.

    $200 – $400

  • Build

    Merge logic, segments, lifecycle messages and stop rules.

    $500 – $1,300

  • Integrations

    Reservation platform, POS, email tool and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a test-inbox run the manager checks.

    $100 – $250

  • Launch and training

    Switch-on and a walkthrough for the manager.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Reservation, CRM, email and messaging subscriptions are billed to you directly. A POS link with a restricted API may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM or email tool: The vendor's own plan (SevenRooms, OpenTable, Klaviyo, Mailchimp or HubSpot).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Twilio SMS (US): About $0.0083 per message segment plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: marketing texts need written consent

Promotional texts to mobile numbers need prior express written consent under the TCPA rules; reservation confirmations are a separate, transactional flow.

Source: www.law.cornell.edu

UK: marketing by text and email

PECR requires consent, or the soft opt-in conditions, for electronic marketing, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

US: opt-outs honoured quickly

Opt-outs by reasonable means, such as replying STOP, must be honoured within a reasonable time and no more than ten business days. Our workflows record them at once.

Source: www.kelleydrye.com

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Restaurant CRM software questions questions, answered.

A restaurant CRM keeps one profile per guest: visits, spend where the POS shares it, occasions, preferences and marketing consent. Reservation platforms such as SevenRooms and OpenTable include guest profiles; email tools such as Klaviyo or a general CRM such as HubSpot can play the same role for marketing.

If your reservation platform already has a strong guest book, we usually build on it and connect your email tool. If guests come from many places, or you run several brands, a separate CRM can make sense. We recommend based on your systems and budget, not on a commission.

Often. Square offers a public Customers API, and Toast offers orders and menus APIs under partner, custom or standard access. Some POS data reaches the CRM through the reservation platform instead, as with OpenTable's Klaviyo app, so we confirm the route for yours before quoting.

Partly. Lifecycle messages are marketing automation, but the bigger win is clean guest records and knowing who your regulars are. Promotions only go to guests who opted in, and every message has an easy opt-out.

No. Each segment has a cap on messages, sequences stop as soon as a guest books, and one shared opt-out list covers every flow.

Returning guest share, lapsed guests who come back after a message, bookings by campaign and list growth with consent. We set these up in the weekly report from day one.

Free 20-minute call

Want this for your restaurants & café?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call