You Have a System: Where You Change It, Where You Run It

What you have

You did not buy a website. You have a business operating system, and the website is one of the things it runs.

Here is what that means concretely. Your system runs:

• Your site — the public pages, your standing content, and how you appear to someone who has never met you
• Quotes and pricing — your service list, what each one covers, and the settings that drive every estimate you send
• Locations — the cities and ZIP codes you serve, and which services are offered where
• Content and media — blog posts, FAQs, testimonials, the gallery, and the image library everything draws from
• Search visibility — your SEO settings and a content-health view that tells you what is thin or missing
• Jobs and paperwork — job records, contracts, warranties, the people attached to each, and accounting reports
• Contact and booking — your contact form, which fields it asks for, and your calendar and booking settings

That is not a settings page with three toggles. It is the business, configured.

Where you change it

The CMS ops panel, and that is most changes.

You sign in and do it yourself. No code, no developer, no waiting, no ticket. Everything in the list above is a form you can open right now, and what you change is reviewed before customers see it — you look at it, then it goes live.

This is the normal way to run your system and it should be the first place you look. Most owners are surprised how much is already theirs. As tested on the headmaster's exterior cleaning business already — this is not a demo, it is the system that runs a real company.

How you run the business

The other half of your week is not changing the system at all. It is bids, estimates, proposals, outreach emails, review replies, social posts and follow-ups — the knowledge work that fills your calendar. That runs on Claude.ai.

The difference that matters is not which tool you open. It is what happens when you get it wrong:

Read the last row twice. It is the reason these are kept apart. A bad change to your site is a screen you go back into.

A bad email is already in someone's inbox.

When you want more than the system does

Sometimes you will want something the panel has no screen for. That is not you doing it wrong and it is not a limitation you have to work around — it is an enhancement I have not provided yet.

It goes to your implementor. That is the whole answer.

It goes to your implementor, who works in Claude Code.

A tenant can have Claude Code and a small starter kit on their own system too — some will want to make basic changes in the IDE themselves. But the CMS ops panel is where most changes happen, and nothing in this track requires it. If you never open an IDE for as long as you run this business, nothing has gone wrong.

A tenant who connects lets their implementor push new features as they ship. That connection is opt-in, scoped, and revocable — you turn it on, it reaches only what you allow, and you can turn it off.

Two things fall outside the panel right now:

• Site-wide banners and seasonal styling — a promotional banner across the top of your site, or a colour and theme change. No panel screen owns this yet.
• Navigation and menus — adding, removing or reordering the items in your site's menu.

Both are tracked as panel work, not left as a permanent split in how your system is run. Until they land, ask your implementor.

The risk difference holds wherever the change is made: a change to the system is reviewed before customers see it, and a message to a customer is not.

Where the effort actually pays

New owners tend to spend their first month on the *website*, because it is visible and satisfying. That is almost always the wrong place to start.

Ask a blunt question about any task: if I got one hour back here, what would it be worth?

• Rewriting your "About" page — worth something, once, and it is already written.
• Getting a bid out the same day instead of three days later — worth the job.
• Replying to a two-star review within a day — worth every future customer who reads it.
• Turning one site visit into a follow-up sequence — worth the repeat work.

The pattern: effort pays where work is repeated, time-sensitive, or currently not happening at all.

Effort does not pay on things that are already done and rarely seen.

Your site matters. It matters *less* than the fact that a request for quote sat unanswered over a weekend.

A word about the words

You will see two phrases in the wild:

• "Vibe coding" — describing what you build by conversation with an AI rather than by typing code.
• "Agentic delivery" — describing work where AI tools carry out multi-step tasks with you supervising.

Both are useful shorthand for talking to other business owners. The precise term for the way your system is built and maintained is agent-orchestrated delivery: automated tools do the work, and a human holds the decisions that are expensive to undo. When this curriculum needs to be exact, it uses *agent-orchestrated*. When you are explaining it at a chamber-of-commerce breakfast, the shorthand is fine.

What to do this week

1. Sign in to your CMS ops panel and open every section once. Change nothing. You are learning what is already yours, and that list is longer than most owners expect.
2. Open Claude.ai and confirm you can sign in.
3. Write down the five tasks that eat the most of your week.
4. Mark each one system or business — and for the system ones, note which panel section owns it.
5. Start with the business-side task that is currently *not happening* — the follow-ups you never send, the reviews you never answer. That is where the first hour pays most.

You do not need Cursor or Claude Code this week, or any week. If a change turns out to have no panel screen, that is your implementor's job — not a tool you have to learn.

The rest of this track works through all three, one capability at a time: what the system runs, where you change it, and how you run the business on top of it.