About
bookfer came out of a simple observation: a twenty-room hotel or a six-cabin complex needs exactly the same seven pieces a chain does, and none of the options on the market give them together at a price that makes sense at that scale.
The thesis
Today the usual way out is a PMS over here, an engine over there, a site built by someone who no longer replies, a rates spreadsheet and enquiries landing in a WhatsApp nobody organises. Each piece works; the whole does not. And the work of keeping the whole aligned ends up being done by hand, by the person at the front desk.
bookfer's bet is that this whole becomes one system with one database, that it can be set up without help, and that every desk sees only its own. Everything else — the RMS, the agent layer, the assistant — comes out of that: they are things you can only do well once the data is already one.
How we work
01
A room is loaded once. If it appears in the engine, on the site, in the RMS and in LinkHub it is because it is the same row, not because there is a sync in the middle. Most problems in a hospitality stack are two systems saying different things about the same room.
02
If something is not there, we say it on the site and not on the third call. A pilot that starts with an inflated expectation ends in a silent churn four weeks later, and that churn teaches us nothing. We would rather have fewer sign-ups and know why the ones who stay, stay.
03
Hiding a button is not a permission. Every operation is evaluated against the service policy, and the AI assistant operates impersonating the real identity of whoever is asking, with a short-lived permission renewed on every call. There is no service account with superpowers behind it.
04
Configuring a mail server, waiting for an onboarding call, paying a setup fee: each of those is people left outside. Setup is nine steps you do alone, and guest emails go out without you configuring anything.
Product status
This table is the same one we use internally to decide what gets built. We publish it because the alternative — you finding out in week three — helps nobody, least of all us.
Solid and in production
Partial: it exists, but not complete
Does not exist yet
Where we are
We are not trying to make money in this stage. We are trying to answer four questions with data, and all four depend on properties using the system for real, with real bookings inside.
01
Does setup complete on its own, or is there a specific step where people drop out?
02
Do guests book through the engine, or does the habit go back to chat even though the link exists?
03
What do people who use it seriously ask for, and how is that different from what someone who tried it and left asked for?
04
What is the assistant used for when nobody is watching?
Write to us and we will talk it through plainly. If bookfer is not useful for your case yet, we will tell you in that same conversation.
01You tell us how you operate today.
02We tell you what it solves and what it does not.
03If it makes sense, we start the setup together.