Hospitality websites for your property | Qwe

Skip to content

Qwe Hospitality Web

What makes the propertydifferent, on the way to a booking.

Information design shaped around the kind of property it is, then the photographs and copy, the link through to the booking page you already use, review on staging, and going live. Qwe Launch covers all of it.

  • Built for lodging, not adapted
  • Designed on the phone first
  • Keeps your booking system
A fictional boutique hotel interior with contemporary art and natural materials
01 / BoutiqueMUSEDesign preview — fictional property
An open-air bath at a fictional ryokan, in stone, timber and still water
02 / Ryokan — KAGURA

Generated concept imagery. The properties, rates and availability shown are fictional

Built for hotels, not adapted

A new logo and a new colour
do not explain the property.

A boutique hotel is chosen for its culture and its street. A ryokan is chosen for the bath, the meal and the season. A city hotel is chosen on availability, room comparison and how easy it is to reach. The proportion of photography, the order of the information and the route to a booking differ accordingly.

Design systems for Qwe Launch

Choose the ground the site is built on.

What we sell is Qwe Launch: Qwe builds the site and takes it live. MUSE and KAGURA are the design systems you choose between within it. METRO is a study, not a product.

Interior of the fictional boutique hotel used for the MUSE previewDESIGN PREVIEW / FICTIONAL PROPERTY

01 / Boutique

MUSE

Available in Qwe Launch

For independent design-led hotels. Not only the rooms: the food, the music, the art and the neighbourhood, edited into one stay.

The open-air bath at the fictional ryokan used for the KAGURA previewDESIGN PREVIEW / FICTIONAL PROPERTY

02 / Ryokan

KAGURA

Available in Qwe Launch

For Japanese inns. The bath, the meal, the rooms and the season, in the order that settles a guest’s mind before they book.

A guest room in the fictional city hotel used for the METRO previewDESIGN PREVIEW / FICTIONAL PROPERTY

Research preview / City

METRO

Not for sale — study

A study, not part of Qwe Launch. We are testing how quickly dates, party size, rooms, breakfast and transport can be compared.

Website, booking, and the guest

All the way
to the booking.

The work does not end at the website. Bookings go through the OTAs, and the messages before arrival go through the phone and the inbox. We build all three ourselves. Each is contracted separately, and you can start with only the one you need.

01 / Website

The website

Photo ratio and the order of the information change with the kind of property. A house with no room photography can still go live. We implement it and put it online.

Open for enquiries

02 / Booking

Direct booking

A booking engine we build ourselves: inventory and rates, multi-night and date-based discounts, cancellation terms, OTA calendar import, phone bookings, and the screens the property works in.

It does not take card payments yet — guests pay at the property. It is not yet running at a real house either. We are looking for the first one to launch it with.

Looking for the first property

03 / Guest

Talking to guests

ConcierBot answers questions before and after arrival, in the words the property chooses, in several languages including English and Japanese. It is already running, as a separate product under a separate contract.

Live · separate contract

All three together, or only one — the same enquiry reaches us either way. We take one property at a time, so there may be a wait.

Future research

Areas we are studying, not selling.

None of the three below is a product or an enquiry we accept. We will look at them after the Qwe Launch paid pilot is finished, and only once requirements, unit economics and delivery capacity have been approved separately.

AUREL / Research only

Luxury, full service

Rooms, restaurants, spa, membership and events across one property.

Not for sale — no enquiries
NEST / Research only

Whole-house and small stays

Information and arrival guidance for properties run by a few people.

Not for sale — no enquiries
ATLAS / Research only

Groups and multiple properties

Brand consistency and access control across several properties.

Not for sale — no enquiries

One paid pilot

From choosing the design
to signing off and going live.

What we are opening is one paid Qwe Launch pilot, for a single independent boutique hotel or ryokan. You choose MUSE or KAGURA as the design language, and we build the scope agreed before the contract.

  • Review of the current site, booking page and assets
  • Photographs and copy adapted to the property’s brand
  • Review on staging, then live after sign-off
  • The link through to your existing booking system

Price, effort, revision rounds, schedule and acceptance terms are fixed before the contract. Ongoing maintenance is not included. Booking (Qwe Booking) and ConcierBot are separate contracts, and the same enquiry covers them.

01
FIT

Agree what is in scope

The property, the booking route, the assets, who is responsible, and when you want to be live.

02
BUILD

Build what was agreed

MUSE or KAGURA adapted to the property’s brand, connected to the booking page you already use.

03
ACCEPT

Live after sign-off

Display, booking route and measurement checked on staging, then published once you approve.

Scope candidate

A candidate scope, not a promise.

What follows is a starting point for discussion. It is not a guaranteed page count or deliverable list. It is fixed, together with cost, schedule and rights, in the quotation and specification issued before any contract.

Qwe Launch candidate

Areas of information

  • Home, rooms, the property, access, contact
  • Target devices and browsers fixed in the specification
  • A booking route into the page you already use
  • Basic SEO, headings and interface wording
  • Page count and delivery format fixed after approval

Delivery

Build through to launch

  • Photographs and copy placed and adapted to the brand
  • Basic measurement, SEO and accessibility
  • The link through to your existing booking page
  • Review and revision on staging
  • Publishing to production after sign-off

Not included by default

Handled separately

  • Photography, copywriting, translation, asset licensing
  • Fees for booking or PMS services, and API integration
  • Domain, hosting and paid plugin costs
  • ConcierBot — a separate product under a separate contract
  • Booking (Qwe Booking) — a separate contract
  • AI staff, ongoing maintenance, multiple properties, METRO, and the templates on their own (none currently for sale)

The page count, revision rounds, schedule, licence terms and supported environments are fixed in the quotation and specification issued before you order.

Before we quote

What we ask before quoting.

Pick five things and the enquiry arrives with the context already in it. Nothing here has to be decided — “not sure yet” is a valid answer to all of them.

Initial offer

One property, properly.

We are opening one paid Qwe Launch pilot and no more. Whether it becomes generally available is a decision we will make after the unit economics, the legal review and a real production environment have been checked.

Photography, copywriting, translation, third-party service fees and domain or hosting costs are not included. Payment terms, revision rounds, acceptance, cancellation and licence terms are fixed in writing before any contract. The templates on their own, maintenance, multiple properties and METRO are not for sale.

From story to stay

01

First conversation

The kind of property, the number of rooms, the booking route, and the questions guests keep asking you.

02

Choose the design language

MUSE or KAGURA as the starting point, then adjusted to the brand and how the property runs.

03

Build and set up

Photographs, text and booking links placed. Pages and features added where the scope calls for them.

04

Staging and sign-off

Display, booking route, enquiries and measurement checked, then published once you approve.

Questions

Common questions

Nothing needs to be settled before you get in touch. We work from where the property actually is.

Can we talk before the photographs and copy are ready?

Yes. We look at your current site and booking page first, and put together the list of assets and information that will be needed. If photography or copywriting is required, we describe that as separate work.

Can we keep the booking system we use now?

We connect the site to your existing booking page as a link. API integration and embedded availability search are outside the paid pilot.

Can the colours, type and structure of MUSE or KAGURA be changed?

Yes, within the scope agreed in the specification. Colour, typography, photography and text are adjusted to the property’s brand.

Does it include updates and maintenance after launch?

No. Qwe Care is not for sale until its service levels, response times, costs and price have been approved separately.

Are Qwe’s booking engine or AI features included?

No. The scope is the link through to your existing booking page. ConcierBot is a separate product under a separate contract, and Qwe Booking and AI staff are not currently for sale.

Your hotel, clearly chosen

Send us the property URL and the
booking page, and we will map the scope.

You do not need the photographs or the copy first. We look at the current site, the booking page, the number of rooms, the assets and who will be involved, and set out whether the paid pilot fits and what it would require.

Ask about the paid pilot