How I built Contento as a system, end to end
I built Contento as a system before I built it as a website. One person, no team, no investors: a site with more than 40 public pages, 33 checks that run against it every morning, 118 scripts that publish and verify, and every decision written down with its evidence. This is how it fits together, and why each part exists.
Can one person run a company's whole digital presence?
Yes, if the repetitive work stops being theirs. Two months ago Contento was one sentence: Found. Trusted. Chosen. Today it is a site, an Academy with 12 guides, a Blog, a presence on eight platforms and a shop on the way. I am the only person in the company.
That is not a boast about volume. It only works because every part was designed to run, be checked and be backed up without me remembering to do it. The site is the proof, not the product. If I tell a business it has to be found, believed and picked, my own site has to pass that test first.
The rule before the code
Before I wrote a line, I set one rule: every decision gets written down with the evidence behind it. What I saw, what I decided, where it stands. There are 929 rows in that log now, and the ones that went wrong stay in, with what was learned.
When you work alone, memory is the bottleneck. With the record I don't decide the same thing twice, and when something breaks I can trace exactly where it came from. The AI agents I work with read the same record, so they don't propose something I already rejected last week.
What does the system actually do?
It does five jobs, and each one exists because something went wrong once without it.
| Part | What it does | Why it exists |
|---|---|---|
| Morning checks | 33 gates run against the public site every day: links, structured data, page weight, typefaces, footer, the file AI assistants read | Alone, a broken page can sit for weeks. Nobody else is looking |
| The watcher | Compares every number against the previous run, not only against the rule, and knows whether I changed anything | The hardest case is a number that moves when nobody touched it |
| Scripts | 118 of them publish, measure and verify; 693 commits since September 1 | When a task repeats, it becomes a script or a check |
| Backups | Two copies every day, in two separate places, with no one pressing a button | A backup that depends on remembering is not a backup |
| Agents | AI agents split by function: research, evaluation, documentation, code, branding | So I can look at the whole thing instead of putting out fires |
The checks don't only look for breakage. Once, a page appeared to double in weight in a few days with nothing published. The content was identical byte for byte; the platform was injecting blank space depending on which cached copy you got. Now the weight check measures the page with that space collapsed. Most checks on the list were born the same way: a bug found once becomes a test that runs forever.
Why build an Academy if you sell services?
Because it gets you found before someone knows they need you. A person searches for why their site doesn't show up, finds a guide that explains it properly, and only then wonders who wrote it.
The guides are long and built on my own measurements, not recycled opinions; the method behind them is published so anyone can run it and disagree. The Blog is shorter and practical, for owners of small teams. AI assistants and search engines cite whoever answers best, so a script rebuilds the file that tells them what is on the site straight from the sitemap. When I publish, I don't depend on remembering to add the new piece.
What happens when the platform says no?
You look for where it says yes. Squarespace doesn't let you put a file at the root of your domain, and that is exactly where the key for IndexNow has to live, the protocol that tells Bing and other engines about a new page right away. I uploaded the key as a site file and added a redirect that serves it where the engines expect it. A script checks it is still in place before every notification goes out.
The same thing happened with the code editor: setting its value by script looks saved and isn't. So nothing is called saved until a cold reload, outside the editor, says so. That rule is written down too.
One piece, eight channels
Contento publishes on eight platforms on a schedule, whether or not I am at the computer. I don't write eight things from scratch. I write one piece and open it into the shape each channel asks for: a long article, a thread, a carousel people save for later. The source doesn't change: the same idea, measured and dated.
Questions I get about this
Do you need to code to work like this?
You need to think in systems more than you need to code. The order matters: write the decision, put every list in one file, then automate what repeats. Code comes last.
Why Squarespace and not a custom stack?
Because most of the businesses I work with are on a platform like it. If I can run mine like production on Squarespace, the method carries over to theirs without a rebuild.
What do the AI agents decide?
Nothing that matters. They research, draft, check and document. The judgment, the priorities and every decision in the log are mine.
Does this apply to a business that sells products?
Yes. The pieces change, the method doesn't: one direction that decides, clear functions, checks that run on their own, and every decision written down.
What I can and can't claim
Every number on this page was recounted from the repository and the live site on October 5, 2026. What I can't tell you yet is that the system has brought in revenue on its own: the site is new, and I haven't measured that. What I can show is that it runs, that it catches its own errors, and that I built it end to end.
That is what I build for others: the website, the measurement, the content and the automation behind it, with a strategy and a plan. See how I work, or bring me a digital problem.
