Restaurant CRM for Independents: What It Does and Costs

Seven percent of a restaurant's guests can drive up to half of its orders, according to Toast's Q1 2026 data. A restaurant CRM is simply the place you keep track of those people: who they are, how often they come, what they drink, what they can't eat. For most independents in Canada, that place already exists inside the reservation system. It costs between nothing and a couple of hundred dollars a month. The expensive part is the habit of using it.

That's worth saying up front, because page one of Google for "restaurant CRM" is almost all vendors selling suites with segmentation, automation and AI, priced for groups with a marketing manager. A 40-seat room with an owner on the line needs something much smaller.

One operator on Reddit put it better than any vendor: "knowing your regular customers and making them feel valued would work better than some complicated loyalty apps." Another, shorter: "Regulars keep the lights on. End of story."

What does a restaurant CRM actually do?

It holds a record for each guest and puts it in front of your team at the moment it matters: when the booking comes in, and when the guest walks through the door.

A useful guest record is not long. Six things cover almost everything a small room uses:

Field	Example	Why it matters on the floor
Contact	Name, mobile, email	Confirm the booking, reach them if the kitchen floods
Visit history	11 visits since March, last one three weeks ago	Tells the host who's a regular before they say a word
No-shows and cancellations	2 no-shows, both on Saturdays	Decide whether to ask for a card next time
Allergies and dietary notes	Shellfish allergy, partner is vegetarian	The kitchen knows before the order, not during it
Tags	Regular, industry, birthday in May, press	Lets you sort and spot people at a glance
Notes	Likes the corner banquette, always orders the orange wine	The detail that makes a visit feel personal

That's it. Spend-per-visit is nice to have if your POS feeds it in, but you can run a warm room without it.

Notice what's missing: points, tiers, drip campaigns, predictive scores. Those belong to marketing and loyalty software, which is a separate decision. The Regulars Report found that nearly half of surveyed diners feel most valued when staff remember them, while only 30% say they consistently get that. The data is American, but the gap will be familiar to anyone who has watched a regular get seated like a stranger on a new host's first night.

Where does the guest data come from?

Mostly from bookings. Every online reservation hands you a name, a phone number, usually an email, a party size and a date. Do that for a year and the history builds itself. This is why a separate CRM so often duplicates what you already have: the reservation system was collecting guest records the whole time.

The gaps are predictable, so plan for them:

• Phone bookings. If whoever answers the phone writes the booking on a pad instead of entering it in the system, that guest never gets a history.
• Walk-ins. A walk-in leaves no record unless someone adds one. For a regular who always walks in, a 20-second entry after they sit down is enough.
• The POS. Most POS systems know the card, not the person. A guest who pays cash or splits the bill looks like three strangers.
• Delivery apps. Orders through the big apps usually come with limited guest contact details, so those customers are hard to reach directly.

The practical rule: pick one system as the home for guest records (for most restaurants, the reservation book) and make sure every booking, however it arrives, ends up there.

What does a restaurant CRM cost in Canada?

There are three ways to run a guest database, and the price gap between them is huge.

Option	Typical cost	What you get	Best for
Guest records inside your reservation system	$0 to about $200 a month, often included in the plan	Profiles, visit history, tags, notes, no-show counts, built from bookings automatically	Most single-location independents
General CRM (e.g. HubSpot)	Free for 2 users and 1,000 contacts; paid seats from $7 to $20 USD a month	A contact database built for sales teams, not a dining room. No link to your tables	Rarely a fit for restaurants
Restaurant CRM suite (e.g. Eat App Pro, SevenRooms)	Eat App Pro lists $389 a month ($299 billed yearly); SevenRooms quotes on request, around $685+ CAD a month in our comparison	Segmentation, automated email and SMS, loyalty, multi-location guest records	Groups with someone running campaigns every week
Email tool on top (e.g. Mailchimp)	Free up to 250 contacts; paid plans from $18 USD a month at the smallest list size	Newsletters to people who opted in	Any size, once you have consent

US-dollar prices move with the exchange rate. At about $1.37, a $20 USD seat is roughly $27 CAD, and a $389 USD plan is over $530 CAD a month.

SevenRooms' own cost guide flags where the real bill hides: paid setup and data migration, per-integration fees to connect the POS, and email or SMS charges that grow with your list. Ask about all three before you sign.

Here's the math that matters. A suite at $530 CAD a month is $6,360 a year. For a room with a $60 average cheque, that's 106 extra covers a year just to match the bill in sales. Once food, labour and rent come out of each cheque, the real number is several times that, and it all has to come from campaigns someone actually writes. If nobody on your team will run those campaigns, the suite is a very expensive address book.

Do you need a separate CRM?

For most independents, no. If your reservation system already keeps visit history, tags and notes, you have a CRM. What you probably don't have is the routine.

A separate tool starts to earn its place when at least one of these is true:

• Someone on staff will send email or SMS campaigns at least twice a month, and you've measured that they bring people back.
• You run a points or tiers program that needs its own logic.
• You have two or more locations and want one guest record across them.
• Your POS spend data is central to how you treat guests (wine-heavy rooms, tasting-menu rooms).

If none of those apply, spend the money elsewhere and spend ten minutes on the book instead.

What does using a guest database look like in a 40-seat room?

Say you seat 40 and do about 1,100 covers a month. At an average party of 2.5, that's around 440 bookings a month. After a year, your reservation book holds something like 3,000 distinct names. If the 7% figure holds anywhere close for you, about 200 of those people are your regulars.

Two hundred people is not a marketing segment. It's a list your host can learn.

The whole routine fits on an index card:

1. Before service (10 minutes). Open tonight's book. Scan for tags: regulars, birthdays, allergies, last visit's notes. Tell the floor and the kitchen.
2. During service (as it happens). When a server learns something worth keeping ("they're celebrating," "she hates cilantro"), it goes into the guest's notes before the end of the night.
3. Once a week (15 minutes). Tag anyone who has booked three times or more as a regular. Look at who hasn't been back in two months.

That's under two hours a week. It costs nothing if the guest records come with your reservation system, and it's the "special treatment, favourite seats, remembered orders" that one owner described as the reward regulars already get, without a points card.

What can you do with guest data under Canadian law?

Two different rules apply, and mixing them up is the most common mistake.

Running the booking. Collecting a name and phone number to confirm and manage a reservation is part of the service. You don't need a marketing checkbox to text someone their reminder.

Marketing to the list. A newsletter or a "we've missed you" email is a commercial message under Canada's anti-spam law. A guest who dined with you gives you implied consent for up to two years after their last visit, and each new visit resets the clock. Express consent (an unticked box they choose to tick) has no expiry until they withdraw it. Every message needs your business name, contact details and an unsubscribe, and the CRTC expects you to honour an unsubscribe within 10 business days.

The cleanest setup is an optional, unticked "send me news from the restaurant" box on the booking form, with the date recorded when someone ticks it. That one box gives you a list you never have to worry about.

In Quebec, Law 25 also requires a designated person in charge of personal information, which by default is the owner, and allergy and health notes deserve extra care. Our guide to customer data and privacy law covers retention, deletion and breach rules province by province.

Who owns your guest list?

You should. Not every setup makes that easy.

Before you commit to any system that holds guest records, ask four questions:

• Can I export everything? A spreadsheet with names, contact details, visit history, tags and notes. Ask to see the export button, not hear about it.
• Who else can contact my guests? Marketplace platforms may recommend other restaurants to diners who booked with you. That's a trade for discovery, and you should make it knowingly.
• What happens if I leave? Guest data tied to a POS or loyalty contract often leaves when the contract ends.
• Is consent recorded? If marketing opt-ins aren't stamped with a date and method, you'll be rebuilding the list from scratch the day you switch.

A guest database is the one asset in your software stack that gets more valuable every month you use it. It should move with you.

The short version

Most independents don't need to buy a CRM. They need to use the guest records their reservation system already keeps, and build a ten-minute habit around them. Pay for a suite when someone will run campaigns, not before. Collect marketing consent separately, and make sure you can take the list with you.

If you're adding up the rest of your software bill, our breakdown of what restaurant software actually costs and what loyalty software costs in Canada will help.

When you're ready to take reservations, Trudy's Table is built for Canadian independents, with guest history included. Canadian owned, and free for Canadian restaurants.

---

Sources: Resy and Toast, The Regulars Report 2026, SevenRooms, restaurant CRM cost, Eat App pricing, HubSpot CRM pricing, Mailchimp pricing, ISED, Getting consent to send email, CRTC, CASL guidance on implied consent, CFIB, Quebec Law 25.

---