A management company might run a flagged select-service hotel, two soft-brand properties and five independents, and next quarter it will take on two more and lose one in a sale. The flagged hotel lives on its brand's website. Everything else needs a site someone at the group can launch, keep accurate and hand over cleanly. This page is about that second group of properties.
Before choosing any platform, sort your portfolio. Most groups find three kinds of property, and only two of them are a website problem for the group.
| Property type | Who usually runs the main website | What the group still needs |
|---|---|---|
| Franchised under a major flag | The franchise brand, inside its own platform and standards | Often nothing for the hotel page itself; sometimes a separate site for an on-site restaurant, bar or meeting space, if the franchise agreement allows it |
| Soft-brand or collection member | Shared: the collection lists the hotel, and the hotel keeps its own identity | A property site in the hotel's own name that matches collection rules |
| Independent | The owner or the management company | Everything: the site, domain, photos, rates link, policies, local SEO |
Check each franchise or collection agreement before planning a site. Agreements differ on whether a property may run its own website and what it may say on it, and that is a question for your brand contact, not your web platform.
The independents and soft-brand properties are where groups lose control. One was built by a local agency that has gone quiet. One belongs to a general manager's personal hosting account. One still shows a pool that closed two summers ago. None of them sits on a list at head office.

*The client register on a demo brand. For a hotel group, each row would be a property, tagged by region, owner or type.*
In We.Inc, your group runs a branded account and each property is a "client" under it. The property's sites, editors and domain belong to that account, which the group owns. When a general manager leaves, the site stays with the property and the group removes one login rather than chasing a password.
Tag properties in ways that match how you report: owner entity, region, independent or soft brand, and "under contract to sell". The register search covers names, notes and tags, so "which properties belong to this owner?" takes seconds before an owners' meeting.

*One property opened in the client manager. Each switch is set per property, on top of the group's defaults.*
Hotel teams change their websites for good reasons (a new package, a renovated room type, a winter closure of the terrace) and for risky ones (an unapproved rate claim, a photo with a guest's face, a "pet friendly" line the property can no longer honour). A sensible split:
| Change | Typical owner | Suggested control |
|---|---|---|
| Packages, events, seasonal menus | Property sales or F&B | Publish directly once the editor is trained |
| Room descriptions, amenities, accessibility details | Property operations with group review | Approval before publishing for the first months |
| Policies (cancellation, deposits, fees, pets, smoking) | Group revenue or legal | Group edits; property cannot publish without approval |
| Domain and SEO settings | Group digital lead | Switched off for the property |
| Code access | Group or its agency | Off for property teams |
The switches available per property in We.Inc are: publish sites, connect their own domain, see the code, blog, online store, forms and submissions, and SEO settings. On top of those, publishing can need your approval, set as a group-wide default and overridden per property. That is a single-step approval before a property's site goes live; it is not a multi-stage review chain.

*The approval queue. A property's change waits here until someone at the group approves and publishes it or asks for changes.*
Approval is most useful during handover periods: a newly acquired hotel, a new general manager, or a property with a fresh marketing coordinator. Switch it off once the team has shown it follows the group's rules, so seasonal updates do not queue behind a busy head office.
These are general information, not legal advice. Your counsel decides how they apply to each property.
Accessible-room information (ADA, 28 CFR 36.302(e)). The Department of Justice rule for places of lodging covers reservations made by any means, including websites. Among other things, the reservation service must let guests with disabilities reserve accessible rooms in the same way as other guests, and must identify and describe the accessible features of the hotel and its rooms in enough detail for a guest to judge whether a room meets their needs. Two practical consequences for the website:
Total price including mandatory fees (FTC fees rule). The FTC's Rule on Unfair or Deceptive Fees took effect on May 12, 2025 and covers short-term lodging. Where a business offers or displays a price, it must show the total price including mandatory fees clearly and prominently, and it must not misrepresent fees. For property websites, the risk is the marketing copy rather than the booking engine: a homepage banner saying "rooms from $139" while a mandatory resort or destination fee is added later. Put rate claims behind group approval and keep a list of every page that mentions a price.
A web platform cannot make a page compliant by itself. What it can do is make it easy to find every property page that mentions accessibility or price, and to control who may publish those pages. If your accessibility work is under way, AI-generated pages still need a human check with assistive technology; We.Inc helps you build pages, and your team must test them.
Hotel portfolios move. The website plan should treat a property joining or leaving as an ordinary event, with a checklist rather than a scramble.
When a property joins:
When a property is sold or the management contract ends:

*Every site's code can be downloaded. For a sold property, that turns "hand over the website" into a file transfer instead of a rebuild.*
The website vendor exit plan has contract wording for these situations that you can adapt for management agreements.
A property website for an independent or soft-brand hotel does four jobs: convince a guest the hotel is right, answer the questions that otherwise become phone calls, send people to the booking engine, and rank for the hotel's own name and neighbourhood.
What it should not do is take reservations itself. We.Inc does not include a hotel booking engine, channel manager or property management system. Keep those where they are and link to them. The site can carry forms for group sales, wedding and meeting enquiries (using the forms switch), a blog for local guides and events, and structured data for the hotel as a local business from the SEO panel.

*A sample client site from a template, in the live preview. Each property gets its own design and copy, not a copied page with the name swapped.*
Each property needs its own words. Ten hotel sites that share the same paragraphs with the city name changed will struggle in search and read badly to guests. Use the property's real history, rooms, neighbourhood and staff.

*The group brand: logo, colours and fonts used for the portal your property teams sign in to.*
There are two separate layers of branding. Your group brand is what property teams see when they sign in: your logo, colours, sign-in page and help pages on your own web address. Each property site has its own name, design and domain, because guests are booking the hotel, not the management company.
If you also want a common footer element on every property (for example "Managed by" and a group careers link), write it into your governance rules and check it at approval time; We.Inc does not push a shared content block into every site automatically.
Book a demo and bring two properties: one independent you are happy with and one that worries you. We will set both up during the call.
Last checked 2026-10-25.
This section is general information, not legal advice.
Book a demo. Pricing is tailored to your volume and setup, and you get your exact price on the call. 0% transaction fee.
It depends on the franchise agreement. Major flags usually host the hotel page on their own platform. Check each agreement before planning a separate site for the hotel, its restaurant or its event space.
No. We.Inc builds and runs the property websites. Reservations stay in your booking engine, and the site links to it. Enquiry forms for groups, meetings and weddings can run on the site.
The Department of Justice lodging rule at 28 CFR 36.302(e) covers reservations made by any means, including websites. Among other things, it requires the accessible features of the hotel and its rooms to be described in enough detail for a guest to judge whether a room meets their needs. This is general information, not legal advice.
The FTC Rule on Unfair or Deceptive Fees, in effect since May 12, 2025, covers short-term lodging. Where a price is shown, the total including mandatory fees must be shown clearly and prominently. Ask your counsel how it applies to each property.
The site code can be downloaded as a ZIP or exported to GitHub, and the domain can be transferred, so the new operator receives a working site. Remove your staff from the property account and pause it until the handover is confirmed.
We.Inc is an AI-powered website builder you can resell under your own brand. Launch a branded client dashboard, bill on Stripe Connect, and deliver AI-generated websites in minutes. White-label pricing is tailored to your volume and setup: book a 30-minute demo for a quote.