Building software with AI is quick. The real work starts when it has to run.

Many operators now build their own tools for guest messages, workflows and reports with AI, and for many jobs that is a good idea. This page shows where building pays off, what running it demands, and what HAYP takes off multi-property teams.

Why so many operators are building their own tools

AI coding assistants, no-code builders, AI agents and browser automation make a first version possible in days: a dashboard from a PMS export, an agent for guest questions, a script between two systems. Whether hotels should build their own software is now debated openly.

An example from a PMS user group shows how quickly that becomes operations. Since September 28, 2026 Booking.com no longer passes guest phone numbers to connected software (changelog), and Airbnb no longer shares real numbers with it either (help article). So an operator had an AI assistant read the numbers on the platforms in a browser and copy them across, with the password and two-factor codes.

The problem is real, and the workflow runs. But it shows where the cost of building sits: not in the first draft, but in access, rules and upkeep.

What speaks for building it yourself

The advantages are real, and for some jobs they win.

01

Exactly your process

The tool follows your workflow, not a vendor's average customer.

02

A first version in days

Try an idea without a selection process or a contract.

03

No license per unit

You pay for model usage and hosting, not for every unit.

04

Know-how in your team

Building teaches you the data and processes, which helps when you assess vendors.

05

Gaps no vendor fills

Edge cases get solved even when they are too small for a vendor.

Where building it yourself pays off

Good candidates are internal, need no guest data or portal logins, and may fail now and then.

  • One-off scripts, for example to prepare data for a system change.
  • Internal reports from exports that only your team uses.
  • Prototypes that clarify requirements before you buy or commission.
  • Training material for new staff.
  • Office helpers that need no logins for Booking.com, Airbnb or your PMS.

Build vs buy AI: DIY and HAYP side by side

The difference rarely shows in the first version. It shows in the months after.

TopicBuilt with AIWith HAYP
Platform changesNew rules from Booking.com, Airbnb or Meta surface when something breaks.The HAYP team maintains connections and product and adapts both when platforms change their rules.
KnowledgeOften only its builder knows how it all fits together.Agents, rules, approved answers and messages live in the app, and every AI action is logged.
AccessPasswords and two-factor codes sit in scripts, browsers or AI tools.Airbnb, Booking.com and Expedia through Channex or the HAYP Channel Manager, WhatsApp directly. Roles control who sees what.
Guest dataData lands in chat tools, and often nobody owns retention or access requests.Hosted in Frankfurt, with retention policies, anonymization, privacy export and consent tracking in the Guest CRM.
Replies to guestsWhat the model writes often goes out unchecked and unlogged.Three modes per agent, guardrails, a grounding check and handover to your team, all logged.
CostStaff time, model usage, hosting, monitoring and on-call cover across several budgets.A price per unit and month, no minimum term, and setup with our guide is free.

Platform rules and law: what to settle before you build

  • Interfaces: Booking.com currently accepts no direct connections from individual properties and has paused onboarding new connectivity providers (connect.booking.com). Airbnb connects hosts through software partners such as channel managers (Airbnb).
  • Login details: Airbnb's terms forbid sharing login details with third parties (terms of service). A browser agent with an extranet login holds all the account's rights and reads guest messages that may hide instructions (OWASP on prompt injection).
  • Contact details: for Airbnb bookings from November 20, 2026, hosts may ask for contact details only in narrow exceptions (policy).
  • Data protection: guest data in an outside AI tool usually needs a data processing agreement under Article 28 GDPR and internal rules against shadow AI (guidance of the German data protection authorities).
  • Disclosure: guests are to be told when an AI replies to them directly, unless it is obvious (Article 50 of the EU AI Act).

This overview is not legal advice.

What HAYP takes off your team

HAYP sits on top of your PMS, with Apaleo integrated directly. It takes over the parts of a home-built setup that need lasting care:

  • Connections: messages from Airbnb, Booking.com and Expedia arrive through Channex or the HAYP Channel Manager instead of an extranet login. WhatsApp is connected directly, with the 24-hour window, templates, opt-in and opt-out.
  • AI within limits: the AI Autopilot works in one of three modes per agent. Guardrails, once switched on, also check guest messages for manipulation attempts, a grounding check holds back weakly backed replies, and your team takes over when in doubt.
  • Data and permissions: roles and data access per team, hosting in Frankfurt and GDPR tools in the Guest CRM.
  • Upkeep: the HAYP team keeps developing the product and adapts it when platforms change their rules, so nobody on your side has to maintain code.

Your own systems stay connected, through webhooks from automated messages or a custom integration.

FAQ

Questions about building with AI

Is it worth building hotel software yourself with AI?

For internal tools, often yes: reports, one-off scripts, prototypes. Once a tool answers guests, logs into portals or stores guest data, running it becomes the main job: rules change, access must be secure, and someone must maintain it after its builder has left. HAYP takes over exactly those parts.

Should we build our own AI agent for guest messages?

An agent that writes replies is quick to build. The effort is the framework around it: collecting messages from every channel through the intended routes, answering only from checked knowledge, handing over when unsure and logging every action. The AI Autopilot brings this, with three modes per agent.

How do we reach Booking.com and Airbnb guests without a phone number?

Through the platform's message thread, which HAYP brings into the inbox via the channel connection, with no phone number or extranet login needed. Where the platform's rules allow it, digital check-in asks guests directly for a number and consent. See the guide on guest phone numbers.

Can we connect HAYP to our own tools?

Yes. Automated messages can also go to your own system as a signed HTTPS call, retried after 1, 5 and 15 minutes. Guest contact details are only included if you switch that on. Custom integrations for other systems are available on request.

How does HAYP's cost compare with building it yourself?

The modules cost €2 to €6 per unit per month, net, with no minimum term; WhatsApp adds €49 a month plus Meta's fees. Setup with our guide is free, or HAYP does it for a one-time fee. Building yourself means staff time, model usage, hosting and on-call cover, which rarely sit in one budget. Details are on the pricing page.

Show us what you have built

In a demo we go through your workflows: what HAYP covers, what keeps running via webhook or integration, and what is better kept in-house.