Update your products without touching the website code

Prices change. Services get added. Websites go stale.

Not because updating a website is hard, but because updating one usually means editing code, and editing code means finding whoever edits the code.

So the site quietly falls behind the business, and you and I have both browsed sites where the real price was "call to confirm".

The previous post split your business's knowledge into prose and records.

This post is about the records.

Two endpoints

An API endpoint is the unglamorous name for an address a system exposes so other systems can ask it to do something. Your product catalogue has two.

• addProducts puts a product or service into the system: name, description, price.
• listProducts reads the catalogue back out.

That is the entire model, and its smallness is the point.

What makes it powerful is not what the endpoints do; it is who calls them.

You do not have to call them yourself, either. Your Second Brain OS dashboard has a Manage Products drawer, a plain form over the same catalogue, for the days you would rather type a price into a box than talk to an API.

The dashboard's ROI calculator reads the same catalogue too, so the numbers it models are your real offers, not placeholders.

The website calls listProducts

The products section on this site is not hardcoded. When the page renders, it calls listProducts and displays whatever comes back.

Add a service through addProducts, and it appears on the website. Change a price, and the page shows the new one.

No deploy, no code change, no developer in the loop.

The catalogue is data, and the website is just one reader of it.

The receptionist calls it too

Now the part that makes it a system rather than a convenience: your AI receptionist reads the same catalogue.

When a customer asks what something costs, the receptionist quotes the current price, because it looked it up rather than memorised it. When a visitor describes what they need, the receptionist matches them to the right offer from the live list.

One source of truth, two readers.

Change a price once and the website, the website chat, WhatsApp, Instagram and Telegram all agree in the same instant. The disagreement between what your site says and what your bot says, the one from the start of the knowledge post, is not fixed here so much as made impossible.

Why this suits a one-time purchase

There is a reason this matters more here than on a subscription platform.

The website code is free and open source, and the $397 SBOS Website Operator that brings it to life is one-time. A one-time purchase has to stay current for years without a retainer, or it was not really a purchase.

The way you get that is exactly this separation: the code is stable and yours; the knowledge and the catalogue move freely on top of it, at the speed of your business.

Records through APIs, prose through the knowledge base, code untouched by either.

Next up: the analytics deep dive, where consent, sessions and the CRM meet.