Hotel CRM automation that builds a guest database you can use
Your PMS holds years of stays, but OTA bookings arrive with masked emails, profiles duplicate and nobody can say who your repeat guests are. We build a hotel CRM workflow that reads stays from the PMS, merges duplicate profiles, tags repeat guests, occasions and stay types, keeps marketing consent with each record and sends opted-in guests well-timed emails. It works with Revinate, HubSpot or the CRM you already pay for. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.
The problem
Why hotels lose touch with past guests
A hotel guest database is often the most valuable asset a property owns and the least used. The PMS creates a new profile for every OTA booking, spellings vary, and the same couple who stay every anniversary appear as five different records.
Without a clean database, direct marketing is a guess. Past guests who would book direct never hear from you, newsletters go to everyone or no one, and the OTAs keep the relationship and the commission.
What we build
What our hotel CRM software setup includes
Stays from the PMS
Reservations, stay dates, room types, rates and source read nightly from Mews, Cloudbeds, OPERA Cloud or your PMS through its API.
Duplicate merging
Profiles matched on email, phone and name with clear rules, and unclear matches sent to the front desk to confirm.
Guest tags
Repeat guests, first stays, occasion dates, business or leisure, direct or OTA, and length of stay, refreshed every night.
Consent with the record
Where and when each guest opted in to marketing, so campaigns only reach people who agreed.
Return-stay emails
A thank-you after checkout, an anniversary note before the date and a seasonal invitation for repeat guests, each stopping once the guest books.
Monthly guest report
Repeat guest share, direct versus OTA bookings by returning guests and bookings from each email.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Stay recorded
A checkout or new booking in the PMS creates or updates a guest profile.
-
02
Automated
Profile cleaned
Duplicates are merged and tags refreshed overnight.
-
03
Automated
Email queued
Opted-in guests in a segment get the approved message for that moment.
-
04
Front desk review
Front desk confirms matches
Staff confirm unclear merges and add preferences guests shared at the desk.
-
05
Manager or owner decides
Offers and rates
Any rate, package or discount offered to past guests is set by the manager or owner.
How it behaves
How the hotel guest database behaves
What the guest sees
- A thank-you after checkout, if they opted in
- An anniversary or seasonal note they asked for
- No more emails once they have booked again
- An unsubscribe link that works first time
What staff see
- One profile per guest with stays and preferences
- A short list of unclear merges to confirm
- A monthly report on repeat and direct guests
What the automation does
- Reads stays from the PMS every night
- Merges duplicates and refreshes tags
- Sends approved emails only to guests with consent
Edge cases and fallbacks
- Two guests share an email
- Kept as separate profiles and flagged to the front desk.
- OTA alias email only
- Profile is kept for service only; no marketing is sent.
- Guest asks to be forgotten
- Staff action it in the PMS and CRM, and the workflow excludes the profile from then on.
- PMS API limit or outage
- The nightly run retries later and never sends from stale data.
Architecture
A hotel guest database and CRM at a glance.
- Input
- Logic and services
- Data
- Output
- People
How it flows
- 1 Stays from the PMS, direct bookings and enquiries feed the workflow.
- 2 n8n merges duplicates and builds one profile per guest with consent attached.
- 3 Opted-in guests receive well-timed emails, and the manager sets any offer.
- 4 A monthly report shows repeat guests and direct bookings from returning guests.
Project planner
How the project runs, phase by phase.
Hotel CRM & guest database automation project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
PMS access, booking sources, current lists, consent records and CRM choice.
-
02
Design
2 to 3 days
Merge rules, tags, email moments, stop rules and report contents.
-
03
Build
1 to 2 weeks
PMS connection, merging, tags, emails and the monthly report.
-
04
Shadow run
About 1 week
Profiles build nightly while emails go to a test inbox the manager checks.
-
05
Launch
1 to 2 days
Switch on one email at a time and walk the team through merges.
-
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
Cost estimate
What it costs, line by line.
-
Discovery and design
PMS access, merge rules, tags and reporting.
$200 – $400
-
Build
Merging, tags, emails and stop rules.
$500 – $1,300
-
Integrations
PMS, CRM and email provider.
$150 – $400
-
Testing and shadow run
Nightly runs checked against a test inbox.
$100 – $250
-
Launch and training
Switch-on and front desk walkthrough.
$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. PMS, CRM and email subscriptions are billed to you directly. Importing many years of history 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 (Revinate, HubSpot, Mailchimp or your current tool).
- PMS API access: Included in some PMS plans and an add-on in others; confirmed with your vendor.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
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
Privacy and consent
Rules we design for, with the sources.
EU and UK: lawful basis and consent
Guest data is personal data under GDPR and UK GDPR; marketing emails need consent or, in the UK, the soft opt-in conditions under PECR, with an easy way to refuse.
Source: www.legislation.gov.ukUS: marketing texts need written consent
Promotional texts need prior express written consent under the TCPA rules, so the CRM keeps text consent separate from booking messages.
Source: www.law.cornell.eduGuest data stays with the property
Requests to disclose guest information go to the manager under your privacy policy and local law; the CRM never shares records automatically.
Free tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 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 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 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 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
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
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Hotel CRM and guest database questions questions, answered.
A hotel CRM keeps one profile per guest across stays: dates, room types, spend, preferences, occasions and marketing consent. Guest data platforms such as Revinate are built for hotels; general CRMs such as HubSpot can do the same job for smaller properties.
We read stays through the PMS API, such as the Mews Connector API, the Cloudbeds API or OPERA Cloud's CRM API, merge duplicate profiles and tag guests. The PMS stays the system of record; the database is a clean copy for marketing and service.
OTA bookings often carry an alias address that only works for that stay. We keep those profiles for service, and invite guests to share a direct email at check-in or on the pre-arrival form, with clear consent.
If you want deep hotel features and many PMS connections, a hotel platform such as Revinate fits. A small property may do better with HubSpot or a simple email tool. We recommend based on your PMS and budget, not commission.
That is a legal question for your manager and adviser under local privacy law. Our setup keeps access limited and never shares records automatically; any disclosure request goes to a person.
Repeat guest share, direct bookings from returning guests, list growth with consent and bookings from each email. We set them up in the monthly report.
Free 20-minute call
Want this for your hotels & b&b?
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.
More for hotels & b&bs
All servicesAI guest messaging & hotel chatbot
One assistant for website chat, WhatsApp, SMS and OTA messages that answers parking, check-in, breakfast and pet questions from your approved answers and hands everything else to the front desk.
From $2,500 · About 5 to 8 weeks Details
Pre-arrival emails, online check-in & upsells
Send a pre-arrival email that collects arrival time, registration details and special requests, offers relevant extras from your list and gets everything into the PMS before the guest arrives.
From $1,000 · About 4 weeks Details
Guest requests & housekeeping tasks
Turn guest requests from messages, the phone and the desk into tracked tasks for housekeeping and maintenance, with priorities, room status from the PMS and a follow-up to the guest when done.
From $1,000 · About 4 weeks Details