The SBOS Website Operator: the agent that makes this website live

The website you are reading this on is open source. The design, the components, the whole codebase: free, cloneable, yours to deploy today.

So what does the SBOS Website Operator step buy?

Not the building. The receptionist inside it.

The building is free. The plumbing is not.

Clone the repo and you have a beautiful site: the design system, every section you have scrolled past today, the chat panel, the forms, the blog.

What you do not have is anything for those pieces to talk to.

• The forms render, but a submission goes nowhere.
• The chat panel opens, but no agent answers.
• The products section shows placeholder offers, hardcoded.
• The analytics script has nothing to report to.

Walk through the building and you experience each of these gaps yourself. That is by design.

The SBOS Website Operator, one time ($397 inside the upgrade path, $550 bought on its own), is what closes them:

• Forms that work: lead capture and purchase forms wired end to end, so a submission becomes a contact.
• Event sync to your CRM: Click, Lead, Purchase, appointment created and appointment cancelled, each landing on the right contact as it happens.
• Privacy-friendly analytics, enabled for your website as part of this step. You do not need to have bought anything before: a brand-new SBOS account gets its domain registered here, and the dashboard and funnels start filling from the first visitor.
• Structured data via addProducts and listProducts: your live catalogue, read by the website and the receptionist alike, updated without touching code.
• Knowledge management as a skill of its own: not just storing content, but deciding what belongs in the knowledge base and what does not, so the receptionist answers from the right material.
• Blog writing and content creation: the operator drafts, revises and publishes posts with you, in your voice, straight into the site.
• Email guidance: skills for the emails your funnel needs, from the one-off "thanks for booking" to the weekly newsletter, following the event-driven flow the emails post explains.

The agent also knows how to operate the repo

Here is the part that matters most if you are not a developer.

Yes, you can clone the repo yourself. You can point Claude at it and ask for changes. Nothing stops you.

But the code follows a strict pattern, and knowing the pattern is the difference between a safe edit and a broken page. Every section is a generic component with a thin wrapper around it. The wrapper holds the copy, the images and the defaults; the page composes wrappers and passes props.

Want a section to behave differently? You change a prop, not the component.

The SBOS Website Operator ships already trained on this pattern: the design guidelines, the wrapper rules, where copy lives, what never to touch. So the edits a business owner actually wants are conversations, not code sessions:

• "Change the headline"
• "Add a testimonial"
• "Publish this post"

Safe, small, describable edits, made by an agent that knows the house rules of this exact codebase.

A raw clone plus a general-purpose AI can get there too. It will just get there with more friction, more broken builds, and more "why did it rewrite that component" afternoons. The agent removes the friction because the repo's conventions are part of what it knows.

Even the accent colour is a control, not a decision frozen into the design: pick a different one from the navbar and the whole site follows.

Content: markdown in, published page out

The website has a blog built in, and it works on the simplest possible flow.

Drop a markdown file into the content folder and it becomes a styled page on your site. Markdown is plain text with the lightest possible formatting marks, and it happens to be the format AI models are most comfortable writing.

Which means publishing is a conversation too:

• "Write a post answering the question customers keep asking."
• "Update the pricing mentioned in last month's post."
• "Publish this."

The agent drafts in markdown, you revise in conversation, and the finished file is the published page. No CMS, no copy-paste, no formatting session.

Knowledge: the website teaches the receptionist

The same content does a second job.

Your pages and posts sync into a knowledge base: a store of your prose that your receptionist can search by meaning, not by keyword. Ask the receptionist a question, and it answers from what your site actually says, not from a model's general guesses.

The SBOS Website Operator manages that whole lifecycle:

• Content goes in as you publish, but selectively: the operator knows the difference between prose worth searching and records that belong in the product catalogue, and between public knowledge and things that should never reach a customer-facing answer.
• The receptionist searches it in every conversation.
• Outdated content comes out, so last year's prices never resurface.

Deciding what to include is the real skill here. A knowledge base that swallows everything answers from noise; one that is curated answers like someone who knows the business.

The loop this creates is quietly powerful. A question keeps coming up in chats. You have the agent write a post answering it properly. The post publishes on the website and the receptionist learns the answer the same day.

One piece of writing, teaching two surfaces.

The component library

What the open repo gives you, section by section:

Every one of them is already doing its job on the page you are reading, which is a more honest showroom than any screenshot gallery.

And every one of them is free. The operator is what makes them do something.

Three ways to buy it

The SBOS Website Operator is the step where the website itself joins the system: capturing, measuring, syncing, selling, and teaching the receptionist as it goes.

If you followed this series in order, you have already met the knowledge machinery in the knowledge post. If you arrived here from somewhere else, you did not miss a prerequisite: the content and knowledge flow above comes with this step.

There are three ways to get here, and the maths between them is the pitch:

• Day 0, everything at once: $550. The full system, website included: receptionist, booking, the appointment lifecycle, and the operator.
• Step by step through the upgrade path: $36 receptionist, then $98 booking, then $198 lifecycle, then $397 for the operator. Each step earns the next.
• Individually, later: the receptionist is always $36, there is no substitute for that. But bought on their own, booking is $148, the lifecycle is $298, and the operator is $550.

Read that last line again. The operator alone, bought later, costs exactly what the entire system costs on day 0.

That is not a trick; it is the honest cost of arriving one piece at a time. The bundle exists so that nobody has to.

Either way: no monthly fee, pay-as-you-go credits that never expire, your own AI key if you want it.

The design was a gift. The agent is the business end.

Next up: hosting it for $0, and how far the free tier actually goes.