Skip to content
OdysseyCMS

Use cases

Who OdysseyCMS is for, and how they use it

OdysseyCMS is built for people whose website has to bring in inquiries: agencies running client sites, freelancers who build and hand over, small businesses that market themselves, and brands with more than one location. The scenarios below are typical jobs, described step by step.

Agencies

Agencies: run every client site from one login

The problem
An agency with a dozen client sites usually has a dozen slightly different stacks: different plugin versions, different form tools, different SEO set-ups. Every audit starts from scratch, and every client call starts with "which login was that?"
With OdysseyCMS
With OdysseyCMS, every client site has the same technical baseline and the same dashboard. You switch between sites with ⌘K, and each client sees only their own.

Launch a client site on a staging subdomain

Build on clientname.kitesdev.com while the client reviews pages through preview links. On launch day, add their domain, have them publish the TXT record, and HTTPS is issued automatically. No certificate tickets, no server.

Hand over editing without handing over the keys

Invite the client's marketing manager with an editor role on their site only. They can publish blog posts and update service pages; the editor still enforces one H1 and alt text, so their edits do not undo your SEO work.

Report on SEO without a separate crawl

Open the SEO health panel for each client site before a monthly check-in. Failing checks link straight to the field that fixes them, so the fix often takes less time than the screenshot for the report.

Keep each client's email separate

Form notifications and auto-responders go out through each client's own SMTP server or Microsoft 365 account, from their own domain. One client's mail settings never touch another's.

Features used

  • One login, many sites
  • Roles per site
  • Preview links
  • Custom domains with automatic HTTPS
  • SEO health panel
  • Per-site SMTP or Microsoft 365

Recommended plan

A mid-size server for a handful of client sites; a larger one as the portfolio grows.

Freelancers

Freelancers: deliver sites that stay healthy after handover

The problem
You build a good site, hand it over, and six months later the client has renamed half the pages, uploaded 5 MB photos and added a second H1 to the homepage. Then they ask why traffic dropped.
With OdysseyCMS
OdysseyCMS keeps the guard rails on after you leave. The checks that protect the site are part of the editor, not a plugin the client can switch off.

A client renames a page

They change /our-services-2 to /services. OdysseyCMS writes the 301 from the old URL automatically, so links and rankings carry over.

A client uploads a photo straight from their phone

The upload is converted to WebP and AVIF, with responsive sizes and explicit dimensions. The page stays fast and does not shift while it loads.

You bring over a form from the old site

Import the existing HTML form, then add spam scoring, reCAPTCHA v3, an auto-responder and a webhook to the client's CRM. Submissions can be exported as CSV whenever the client asks.

You reuse what works

Duplicate a proven landing page for a new campaign and change only the copy. Schedule it to publish the morning the campaign starts.

Features used

  • Automatic 301 on slug change
  • WebP/AVIF conversion
  • HTML form import
  • Page duplication
  • Scheduled publishing

Recommended plan

The smallest server runs a single small site comfortably.

Small businesses

Small businesses: a site that brings in inquiries, without a developer on call

The problem
You need a website that ranks for what you do and turns visits into calls, but you do not have time to learn what a canonical tag is, and you should not need to.
With OdysseyCMS
OdysseyCMS handles the technical SEO by default and tells you, in plain language, when something on a page needs attention.

Publish a new service page

Write the page in the visual editor. The title and description fields show when they are too long or duplicated. On publish, the page is added to your sitemap and gets structured data and a social preview card automatically.

Answer common questions on the page

Add an FAQ section to a service page and OdysseyCMS generates FAQPage structured data from it, so search engines understand the questions and answers.

Bring offline customers online

Generate a QR code for your booking page, saved straight to the media library, and print it on flyers, receipts or the shop window.

Get every inquiry, and reply straight away

Build a contact form, send notifications to your Microsoft 365 inbox, and let the auto-responder confirm receipt to the customer. Spam scoring and reCAPTCHA v3 keep junk out.

Features used

  • SEO health panel
  • Length meters and duplicate warnings
  • FAQPage structured data
  • QR codes
  • Forms with auto-responders
  • Microsoft 365 sending

Recommended plan

The smallest server covers most single-location businesses.

Multi-location brands

Multi-location brands: local sites, central control

The problem
A brand with several locations needs each one to rank locally, with its own pages, forms and contact details. Head office needs consistency; local managers need to update opening hours without a ticket.
With OdysseyCMS
Run each location as its own site with its own domain, or run one site with location pages. Either way, roles keep local editors to their own content and the SEO baseline is identical everywhere.

Launch a new location from an existing one

Duplicate the pages of an established location, change the address, team and service details, and publish. Clean slugs, canonicals and breadcrumbs come with it.

Let local managers edit only their location

Give each manager a role on their location's site. Head office keeps admin rights on every site from a single login.

Route inquiries to the right branch

Each location's forms notify that location's team and can push submissions to a central CRM by webhook.

Check every location at once

Use the SEO health panel on each site to catch missing descriptions, duplicate titles or images without alt text before they cost local rankings.

Features used

  • One login, many sites
  • Roles per site
  • Page duplication
  • Custom domains
  • Webhooks
  • SEO health panel

Recommended plan

A larger server for a brand site with many location pages and editors; pages, users and domains are never metered.

A good fit, and not a good fit

OdysseyCMS fits well if

  • Your site is a marketing site: service pages, landing pages, a blog and forms
  • You manage more than one site, or plan to
  • You want technical SEO handled by default, not configured by hand
  • You want hosting, HTTPS and backups taken care of

Look elsewhere if

  • You need an online shop with a cart and checkout
  • You are building a web application with user accounts for visitors
  • You must self-host the CMS on your own servers

Questions about fit

Is each client site billed separately?

No. You pay for the server, and it runs as many sites as it can hold. Put a busy site on its own server when it needs one. One login still manages all of them.

Can a client have admin access to their own site?

Yes. Roles are set per site, so a client can be an admin on their site and have no access to anything else you manage.

Can I white-label the dashboard?

There is no white-label option today. Each client site runs on its own domain with its own design, but the dashboard is the OdysseyCMS dashboard.

Should a multi-location brand use one site or several?

Use one site with location pages if the locations share a brand, domain and team. Use separate sites if each location has its own domain, editors or forms that should stay apart.

Try it on your next site

Pick a server and launch the first site, or book a demo and bring the site you are planning.