Pushbuild

Resy fills the tables. We make the guest data work for you.

Resy handles reservations, the waitlist and guest notes. Getting that information into the rest of the restaurant usually takes copying: the email list, the pre-shift notes, the covers report the owner wants. Resy connects with some POS systems, and guest data can be exported, with deeper access through Resy's partner programme. We check what your account allows and build from that. The scope is written down and agreed before we start.

Tell us what you needSee example projects

Sound familiar?

What restaurants and bars on Resy tell us before a project starts.

  • Guest emails sit in Resy and never reach our newsletter.
  • Someone builds the pre-shift notes by hand every afternoon.
  • We cannot see covers, no-shows and spend together in one place.
  • Large-party and private-dining inquiries come in by email and get lost.
  • Regulars are not recognised when they book at our other location.

What we build

Each one is a working piece you can open and check when it's done.

Guests into your email list

Guests who opted in added to your email tool with visit counts and the location they booked, so a regular gets a different note from a first-timer.

API integrations and data sync

Pre-shift sheet

Tonight's bookings, VIP notes, allergies and celebrations laid out on one page for the floor team, ready before service.

Google Sheets and Apps Script automation Python scripts and utilities

Covers and spend report

Reservations joined to POS sales, so you see spend per cover, no-show rate and busy slots by day.

Dashboards and reporting ETL and data pipelines

Private-dining inquiries

Event requests captured in one place with a reply, an owner and a follow-up until they book or pass.

CRM setup and lead pipelines

Post-visit follow-up

A thank-you and a review ask after the visit, sent once, never to the same guest twice in a month.

n8n, Make and Zapier automation

Group view across locations

Guest history pulled into one sheet, so the team at each location knows who is coming.

ETL and data pipelines

What we connect it to: Toast, Mailchimp, Klaviyo, Google Sheets, Slack, Zapier, Make.

Industries that use it: Restaurants, Breweries and wineries, Coffee shops.

Example projects

Illustrations of the shape of the work, not past clients. Yours gets its own written scope.

Example project

Pre-shift notes on the iPad

Example: a cocktail bar wants a 4pm sheet of tonight's guests with regulars, birthdays and allergy notes, so the bartenders know before doors open.

Resy export, Google Sheets, Apps Script

Example project

Covers against sales

Example: an Italian restaurant joins Resy covers to Toast sales each morning and sees spend per head by night.

Resy, Toast, Google Sheets

Example project

Event inquiry follow-up

Example: a restaurant with a private room tracks every buyout request from first email to signed deposit.

Gmail, HubSpot

Not sure where to start? Start with an Automation Audit.

Questions people ask first

Can you connect Resy to Toast?

Resy has its own integrations with some POS systems. Where those cover what you need we set them up; where they do not, we join the data on a schedule.

Can we get our guest data out?

Guest data can usually be exported from your account, and partners can get more through Resy's partner programme. We check which applies to you first.

Will guests get too many emails?

No. Only guests who opted in are added, and we set limits you approve.

How do we start?

Tell us what the team copies by hand before every service. We reply with questions or a written scope.

Tell us what you need built.

Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.

hello@pushbuild.com

(617) 299-8887