Questions agencies ask us first.

SESAME reads everything already published about a property: its current website, its Booking.com listing, its WebHotelier record and its place on the map. It then writes every page, picks the photographs, wires up the booking engine and builds a finished website on Hotelwize Builder.

You review what it wrote, block by block, and publish when it sounds like the property rather than like software.

Agencies that build and run websites for hotels. One person can take a property from a link to a published site in a sitting, which is why a studio of three can carry the workload of a much larger one.

Properties are welcome too, but the invitation list is agencies first.

Yes. You sign in with a Hotelwize account, and the sites SESAME builds are created and hosted on Hotelwize Builder. If your agency does not have an account yet, say so in your access request and we will sort out both together.

Places to stay: hotels, villas, apartments, guesthouses and small groups. SESAME checks that the link you give it really is a place to stay before it starts, and will refuse a build it cannot confirm.

The draft arrives in about ten minutes. Your review is the part that takes real time: expect an afternoon for the first site you are happy to publish, and considerably less once you know where you usually want to intervene.

A link. The property's current website is best, but a booking page or an OTA listing is enough.

After that, a handful of choices: the theme, the voice, the languages, the booking engine and the property's code in it. Everything else SESAME works out.

From what the property has already published: its own website, its Booking.com listing, its WebHotelier record with the room types and rates, and Google Maps for the address, the coordinates and the beaches, villages and museums nearby.

Every fact SESAME keeps carries a note of which source it came from, so an address, a room count or a licence number can be traced back rather than taken on trust.

That is the usual case for the sites most worth rebuilding. The Booking.com listing carries the description, the room list, the facilities and often the best photographs, and the WebHotelier record carries the rooms. A property with nothing but a social page is the one case where you will need to bring material yourself.

SESAME ranks every image it finds for resolution, composition and subject, classifies what each one shows, and tells you when a page has nothing good to put on it. It will not invent a photograph. You can add your own, and they go through the same curation as the rest.

You choose the theme when you start, from the Hotelwize Builder themes SESAME supports. The palette and the typefaces are taken from the property's existing branding, its logo, its colours and its fonts, so the new site looks like a continuation rather than a replacement. You can override any of it.

The page structure is planned for each property and restricted to what the chosen theme can actually build: a homepage, a page for each room type, facilities, dining, location, offers and contact, plus whatever this property has that deserves its own page, a spa, a restaurant, a wedding venue.

You see the plan before a word is written, and you can change it.

A title and a meta description for every page in every language, a heading structure, alt text on every image, schema.org structured data for the hotel, its rooms, its offers and its restaurant, a sitemap and a robots file.

Finished sites are measured with Lighthouse, and the report names each failing audit rather than handing you a score to interpret.

Every URL the old site served is mapped onto the new one and a redirect created for it, so links, bookmarks and search rankings survive the move. A page with genuinely no successor is recorded as gone rather than pointed somewhere misleading.

As many as the property needs. Each language is written from the same brief rather than translated from the English, so the Greek reads as Greek, written for a Greek guest, instead of as English in Greek words.

Adding a language later is another writing pass, and it goes through the same review.

Yes, and that is deliberate. Every block carries a colour bar until somebody approves it, and a site cannot go to Production until every block has been approved in every language.

You are responsible for what you approve: prices, room descriptions, capacities, facilities, the tourism licence number and the contact details. Our terms say the same thing in legal words.

Approve a block as it stands, edit it in place, or regenerate it with a note saying what was wrong with it. A regenerated block comes back unapproved, so nothing slips past you because it was approved in an earlier shape.

A draft lives on staging and carries a demo notice, so it can be shared with a client without being mistaken for the real thing. Publishing moves it under the property's own company, on its own domain, with the notice gone.

A project belongs to whoever created it and to your agency. Make it visible to your team, or invite people individually by email as viewers, reviewers or editors. A client can be given a reviewer's seat and approve their own copy without being able to break anything.

It is free until you publish. Building a site, reviewing it, regenerating half of it and starting again cost nothing.

Hosting the published site on Hotelwize Builder, and the SESAME fee for your agency, are agreed with you when you are invited.

A build is a large amount of AI work, and it runs on your key rather than ours for two reasons: you pay Anthropic's own rates with nothing added on top, and no quota of ours decides how many sites you can build in a week.

You add the key on your profile. We check it with Anthropic, keep it encrypted in Azure Key Vault, and never show you more than its last few characters again. Remove it whenever you like and it is deleted.

Anthropic bills you directly, at its own published rates. What a build uses depends on the size of the site, how many languages it writes and how much you regenerate, so a single figure would be a fiction. The app records what each build consumed and what it was spent on, so you can price the next one from your own numbers rather than from a promise.

We do limit which Claude models a build may use, so a build cannot quietly reach for the most expensive one available.

A failed build is never retried automatically, precisely so that you are not charged for a second attempt you did not choose. Start it again yourself when you want to.

Tell us. The SESAME team can run the build for you, and the app will say when that is what happened.

On Hotelwize Builder, under your agency's company or the property's own, depending on how you set it up. SESAME itself runs on Microsoft Azure in the EU.

Yes. Nothing about a build requires a new domain. You point the existing one at the new site when you are ready to publish, with the redirects already in place behind it.

WebHotelier, wired to the property's own hotel code, and Hotelwize Liquid when you ask for it by name. Either way, every call to action on the finished site ends at a booking form rather than at a phone number.

It writes from what it read, and records where each fact came from. But AI output can be wrong, and it can faithfully repeat a mistake that was already on the old website, which is the more common failure of the two.

That is what the review step is for. Check the numbers in particular: prices, capacities, distances, the tourism licence and the contact details.

Google's guidance judges the page, not how it was produced: whether it is useful, accurate and written for a person. A generated page nobody read is exactly the kind that does badly, which is why nothing here publishes unreviewed.

Every page is written for its own property from its own material. Two hotels on the same theme do not get the same sentences.

Your material stays yours, and the copy SESAME writes is yours to use for that property once it is published or delivered to you. The theme it sits in stays ours, and is licensed to you through Hotelwize Builder. The terms set this out in full.

SESAME is invitation only. Ask for an invitation with your agency's details and we will reply by email. Asking does not oblige us to send one: we are taking on few agencies at a time while the service is young, and we would rather answer the phone than grow a queue.

No. What you give SESAME is used to build the site you asked for, and for nothing else. We do not sell personal data either. Our privacy policy is the long version.

SESAME runs on Microsoft Azure in the EU, in West Europe. Your Anthropic key is encrypted in Azure Key Vault and deleted the moment you remove it from your profile. Your Hotelwize access token is held only while a build is running, and deleted when it finishes.

Write to aggelos@hotelwize.com for a copy of your data, a correction or a deletion, at any time.