What Backyou does: group sales for hotels, end to end
A company needs forty rooms and a meeting room in October. The request arrives through a form on the hotel's site, by email, or through an agency channel. Backyou carries it from there: qualification, the quote, the negotiation, the option, the booking, the payment schedule, and the function sheets that tell the kitchen and the front desk what is happening on the day. Every client, every past deal, every rate and every agreement a hotel has handled sits in Backyou.
The one call the platform didn't make yet
Backyou came to us with a clear brief. Group business is where a hotel makes its margin, and every request asks the same thing: take it, decline it, and at what price. Say yes to the wrong one and you have blocked nights a better deal needed. Say no to a good one and a competitor gets it.
Backyou already held every piece of that answer: the client's history, the company's conversion record, what else was bidding for those nights, what was booked, whether a framework agreement capped the price. What it didn't hold was the reasoning. That still happened in the head of the most experienced commercial on the desk — and Backyou wanted it in the product, for everyone.
Backyou
“ Sidenet didn't arrive asking us to explain hospitality. They already knew how a group desk works, what a hotel checks before saying yes, and where the margin hides. We spent our time on the product, not on educating a vendor.”
Three standards to meet before launching to production
Scoring a demand well is easy to describe and hard to run in production. Backyou set the bar: nothing leaves Europe, nothing in the platform gets rebuilt, and a group's permissions hold exactly as they do today. Here is how each was met.
Data that stays in Europe, and out of any prompt that doesn't need it
Backyou's hotels are European and Backyou's stance on data is strict: EU-hosted models only, and no personal data in a prompt that doesn't need it.
Compliant by construction
The agent runs on an EU-hosted model behind Sidenet's PII guardrails — personal data is stripped before a prompt ever leaves, keeping the chain compliant by construction.
A rich API — and a decision that needs all of it at once
Backyou's API exposes everything the decision depends on: demands, contacts, companies, calendar, spaces, agreements — paginated and complete. That richness is the whole point; the data was there. The catch is on the agent side. An agent left to walk a dozen endpoints one call at a time takes page one of the competing demands and stops — the score comes back confident and incomplete.
One clean payload, assembled through a workflow
A workflow does the walking: every endpoint, every page, stripped to the fields the decision uses, handed to the agent in one piece. Backyou's API stayed exactly as it was.
What the user can't see, the agent can't see either
A hotel group has one sales team working for all its hotels. Backyou already controls who sees what: a commercial sees only their own hotel — its clients, its rates, its open requests. The group's director sees every hotel. An AI agent that reads all the data at once could break that. We had to make sure the agent respects the same rules as the user asking the question.
Same login, same rules
The agent uses Backyou's own API, logged in as the user. It only sees what that user can see. Nothing is copied or stored on Sidenet's side. Backyou didn't have to write anything new.
Backyou
“ We didn't build anything for this. The agents run on the same API our product runs on, with the same permissions. Sidenet handled the parts that are hard about agents — the workflows, the guardrails, the EU models — and we were live in weeks.”
Backyou's record, with a verdict on top — and a specialist network behind everything else.
One workflow and one agent for the flagship, and a network of specialist agents for everything else on the desk — all running on Backyou's own API. The workflow assembles what Backyou already knows about the request; the agent returns the verdict, scored, reasoned, and ranked against everything else open.
The build: one workflow, one agent — and a network for the rest of the desk
One chat in Backyou. An orchestrator reads every question and hands it to the specialist that owns it; each specialist has its own tools, its own model, and hard rules about what it will not guess.
- SalesDecides on incoming demands — take, decline, at what price“Can I go down to €130 a night on this one?”
- PipelineTriages what's open, what's stalled, what to chase first“Which of my 23 pending demands should I take first?”
- ClientsGoes deep on one client, company or dossier“What's this company's history with us?”
- RevenueDirector-level numbers across properties and periods“How is next quarter tracking against last year?”
- ProductHow Backyou itself works, for new users“How do I set up a framework agreement?”
The outcome: what Backyou's hotels get now
Better margin on group business
The take, decline and price call is made against the hotel's own history and calendar, on every request.
Hours become seconds
Checking a request used to take a commercial hours. Now it's done in Backyou before they even open it.
Priority, not just volume
Twenty demands or two hundred, ranked. The commercial knows what to work on first.
The whole team can decide
The judgement that lived with one experienced commercial now runs inside Backyou, for everyone.
Backyou
“ It never felt like a vendor relationship. Every question got an answer the same day, usually with a proposal attached. They were consultative from the first call — challenging our assumptions, not just taking requirements.”