CMS

A custom CMS without WordPress.

A custom CMS without WordPress: we write the admin, install it on your server, and maintain it. Public pages are fast HTML. Titles, redirects, preview, and Markdown export are fields—not plugins.

Custom CMS: public HTML site and admin fields for pages, media, and navigation. — The admin is only what the site needs.

What you can edit

Enough to run a marketing site. The list is the whole product, and it is the list we use ourselves.

PagesThe address, the search title, the description, draft or live, and whether it belongs in the sitemap.
SectionsBlocks you place on one page, or reuse when the same story belongs in more than one place.
NavigationHeader and footer. Internal pages and links out.
MediaImages and files, stored with the site, with room for alt text.
RedirectsWhen a URL changes, the old address still lands in the right place.
PreviewA private link so you can read a draft before it is public.
LanguagesAdd another language when the audience needs it.
MessagesThe form on the site arrives in the admin.
Markdown and LLM exportsEach public page can be downloaded as Markdown; llms.txt indexes the site for AI tools and plain-text readers.
E-commerceCatalog, cart, checkout, and order handling on fast HTML—product URLs built for the searches that sell.
CRMLeads, pipeline stages, and client records connected to your forms and site—not a one-size-fits-all SaaS login.

E-commerce catalog and CRM pipeline sharing one custom CMS install. — Store and CRM on the same stack.

E-commerce and CRM on the same install.

When the business sells online, the catalog lives in the same system as the marketing pages: each product can own a mid-tail query, checkout stays fast, and orders feed the same tracking stack as your ads. When the business runs on relationships, we build a CRM around your pipeline—lead source, stage, notes, and tasks—wired to contact forms, chat, and the assistant, not imported from a generic template.

Both are custom. We do not resell Shopify or Salesforce. We design the fields, permissions, and integrations you need, then maintain the software the way we maintain the CMS.

E-commerce: categories, variants, inventory fields you define, cart, checkout, and confirmation pages you can edit
CRM: contacts, companies, deals or jobs, activity history, and exports when you need a spreadsheet
Shared: one login, one preview path, redirects when URLs change, and search-friendly HTML on every public URL

SEO fields in the CMS tie titles and URLs to the queries from research. — Titles and redirects are fields—not plugins.

Why the admin matters for search.

A ranking lives on a URL, and speed lives in how little stands between that URL and the words. There is no plugin stack to update, and no theme that loads a dozen scripts before the sentence. We maintain the system on a regular cadence: the software, the redirects, and the pages that should be fast. A client install belongs to that client. This website is one of them.

The admin is also how the URL stays accurate after launch, which is the work described on the maintenance page.

The title and the description are fields on the page, written for the query from research.
A draft stays a draft. Preview is a private link, so an experiment is separate from the live page.
When a slug changes, a redirect keeps the old address attached to the new one.
The sitemap follows the pages you mark. A page you want kept out of the index can be set that way.
This website is one install. A client install belongs to that client.

The build standard is the same one on the implementation page: fast HTML, a page with a point, and an admin a person can open a year from now.

Your site. Your admin.

Each client gets their own install, inside a retained engagement. The roster stays small so the system and the searches both get attention. We quote a setup and a monthly after we know the site. Tell us what that is.