# The way in: why sovereign websites matter so much to RiskMandate, what Web Summit validated and what it showed was missing, something to buy now, how every technology I have been building meets in one product, and why nobody deploys agents they have not touched, seen and been able to stop, so the personal customer becomes the way to the corporate one, sgit.ai

> Web Summit gave us strong validation of the technology, the direction and the need: people understood the principle, saw it working and talked to people who had used it, and even the larger offerings drew real interest. What it also showed is that nobody came to us saying "I'll buy one of these now". Not because they did not see the value, but because they could not see where to start: no thing to buy today, for a known price, and be using tomorrow. RiskMandate is learnt by using it; the summit team had its momentum because Vicky Wang ran a full newsroom without writing a line of code, delegating to a team kept under behaviour policies. Sovereign websites are the answer to where to start. A site is something everyone needs, bought one-off, cheap to make and to run, with no lock-in, version control, provenance and Claude or ChatGPT as the editor, and every one is made and run by agentic cells under RiskMandate's policies. Using it is experiencing those policies: start, stop, delegate, visualise. My hypothesis is that nobody deploys technology they have not tried, trusted and been able to control. B to C to B: anyone who could be a corporate customer can first be a personal one.

*Source: <https://newsroom.sgit.ai/articles/the-way-in.html> · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../index.md) / [Articles](index.md) / The way in: why sovereign websites matter so much to RiskMandate, what Web Summit validated and what it showed was missing, something to buy now, how every technology I have been building meets in one product, and why nobody deploys agents they have not touched, seen and been able to stop, so the personal customer becomes the way to the corporate one

# The way in: why sovereign websites matter so much to RiskMandate, what Web Summit validated and what it showed was missing, something to buy now, how every technology I have been building meets in one product, and why nobody deploys agents they have not touched, seen and been able to stop, so the personal customer becomes the way to the corporate one

By [Dinis Cruz](https://sgit.ai/about/index.md) · 2026-11-21 · [article v1.0.0](versions/the-way-in.md) · [newsroom v0.14.189](https://newsroom.sgit.ai/admin/versions.html) · riskmandatesovereign-websitestrategybehaviour-policiesagentic-cellsgo-to-marketarticle

***Abstract:** Web Summit gave us strong validation of the technology, the direction and the need: people understood the principle, saw it working and talked to people who had used it, and even the larger offerings drew real interest. What it also showed is that nobody came to us saying "I'll buy one of these now". Not because they did not see the value, but because they could not see where to start: no thing to buy today, for a known price, and be using tomorrow. RiskMandate is learnt by using it; the summit team had its momentum because Vicky Wang ran a full newsroom without writing a line of code, delegating to a team kept under behaviour policies. Sovereign websites are the answer to where to start. A site is something everyone needs, bought one-off, cheap to make and to run, with no lock-in, version control, provenance and Claude or ChatGPT as the editor, and every one is made and run by agentic cells under RiskMandate's policies. Using it is experiencing those policies: start, stop, delegate, visualise. My hypothesis is that nobody deploys technology they have not tried, trusted and been able to control. B to C to B: anyone who could be a corporate customer can first be a personal one.*

The way in: buy now, experience it, see and control it, trust it, then bring it to work.

## In short

- **Web Summit validated the technology, the direction and the need,** and the price points.
- **What was missing was a place to start:** something to buy now and use tomorrow.
- **RiskMandate is learnt by using it,** as Vicky Wang ran a newsroom without writing code.
- **Sovereign websites are where to start:** one-off, cheap, no lock-in, made by cells under policies.
- **Nobody deploys agents they cannot see and stop;** a site lets people touch them first.
- **B to C to B:** the personal customer is the way to the corporate one.

## What the summit validated

At Web Summit we had validation of the technology, the path and the direction. Validation that there is a need. Validation that people understand the concept and the principle: they saw it in action, in [the X-ray](the-riskmandate-x-ray.md) and [the Galaxy](a-galaxy-of-agents.md), and they talked to people who had experienced it. The energy was positive. Even the price points held: no one recoiled, and even the main offerings, up to the £20,000 tier, drew good interest ([partners sell, we build](partners-sell-we-build.md)).

## What it showed was missing

That is also an important signal. The people we met did not come to us and say: great, I will buy one of these now. Not because they did not see the value, or not mainly. They did not see where to start. There was no thing you could buy and use right now, no "I spend this many pounds, I get this, and I have it tomorrow". The larger offerings have a sales cycle, and that is fine, but we need a fast sale and a fast deployment as well.

## Why using it is the point

So much of RiskMandate is learnt by using it: you start, you execute, you get your head around it. The summit team had its momentum not only because of what we made, which was spectacular, but because of how it was made, how fast, and how deep. We built a full news publication ([PrompTugal.news](promptugal-news-the-newsroom-we-ran.md)): 73 articles in ten days, every one signed. And that gave Vicky the experience of running a newsroom without ever writing a line of code, as a project manager. She did not need to code. She delegated, to a development team that was controlled by behaviour policies.

That is the part that matters. It was possible because every agent was kept under control. I do a great deal of work this way now, and because the agents are limited in what they can do, I can delegate far more important tasks to them. Claude is an extraordinarily capable tool: at the same time a bicycle, a car, a Formula One car, a tank, a boat and probably a plane. You have to use the right capability for the job. By zooming in on the role, the function and the behaviour, we have a strong way of controlling what agents do ([feature behaviour policies](feature-behaviour-policies.md)). The hard part is how to start.

## From cells to websites

That is why we started selling agentic teams: [AgentiCCells](starting-agenticcells.md), a cell of agents run under RiskMandate's policies. Then the question was what these cells can do. One of the things they can do is make our websites. And once I had wired in the automation, the GitHub repository, the address in AWS Route 53 and the rest of the settings, I realised we had a new product: websites made easily, with the identity that connects to them ([the website cell](the-website-cell.md)). There are still many details to sort out, as [the first round trip](the-first-round-trip.md) showed, but for the first time we have something people can try now and buy now.

## Every technology meets here

When I mapped its properties, I realised how strong this offering is. It ticks the boxes I always talk about for a startup: a one-off service, cheap to make and cheap to run ([sovereign websites, the investment case](sovereign-websites-the-investment-case.md)). And it is where everything I have been building meets:

- **No lock-in,** and the owner keeps ownership of the data and the systems ([sovereignty you can move](sovereignty-you-can-move.md)).
- **Version control,** which most websites do not have, and provenance on every change.
- **Claude or ChatGPT as the editor:** the content management system is now the AI that builds the site.
- **Agentic cells under behaviour policies** make it, run it and change it.
- **Others can build on top of it,** with the owner still in control.

It also puts me right in the conversation I have been having for years: sovereignty, determinism, provenance.

## Nobody deploys what they have not touched

To buy a product, people have to trust it, and to trust it they have to try it. Nobody deploys technology in their organisation that they do not understand, do not control and cannot see. That is one of the problems with agents: they are powerful, but if you cannot see what they do, you will not deploy them, even if they are fine. You need the stop button, and you need to see it. What we had at the summit that was special was exactly that: start, stop, control, delegate, visualise and map ([an agentic console](an-agentic-console.md)).

So the hypothesis is simple. Someone will not buy or use this until they have experienced it, tried it and gained trust in it, until they say: yes, this works, I like it, I am going to use it for other things. A sovereign website is where that happens. The owner talks to the agents, sees their work, and sees what they are and are not allowed to do.

## B to C to B

Every person needs their own website and their own brand. You do not wait until you are looking for a job to build your brand. Everyone needs their own newsroom, to share what they know, and this is the way to do it. Which means that anyone who could be a corporate customer of RiskMandate can first be a personal customer of a sovereign website. B to C to B: the consumer product that people try now and buy now, which is critical for every startup, and the path from it into the company. A profitable way for people to learn, try and experience RiskMandate's policies, on something they all need.

## What this does not claim

- **It is a hypothesis,** to be tested by how many site owners go on to use cells and policies at work.
- **The summit interest was conversations,** not orders, as this article says.
- **The handover still has friction,** as the first round trip recorded.

## Where this comes from

My debrief in writer-10's session, on 21 November 2026. Figures on PrompTugal.news are from its own article. Related: [the first round trip](the-first-round-trip.md), [the website cell](the-website-cell.md), [starting AgentiCCells](starting-agenticcells.md), [PrompTugal.news, the newsroom we ran](promptugal-news-the-newsroom-we-ran.md), [feature behaviour policies](feature-behaviour-policies.md), [an agentic console](an-agentic-console.md), [sovereign websites, the investment case](sovereign-websites-the-investment-case.md).

## Threads

Agents & policy[This article as a graph →](graphs.md#the-way-in)

### Builds on

- [The RiskMandate X-ray: type a company's name and see what its AI helpers can reach, what they were asked to do and where the two do not match, how four search agents and a collector built it for the stand at Web Summit, why only facts whose sources were read reach the page, what it cost, about 1.13 dollars for thirteen companies, and how the four models compared on accuracy](the-riskmandate-x-ray.md) The RiskMandate X-ray: type a company, see its AI helpers' reach, mandate and gap, built by four search agents for about a dime a company.
- [A galaxy of agents: the Universe we showed at Web Summit, a live 3D solar system of the RiskMandate team where people are suns, their agents orbit them and their messages travel between them as arcs of light, read from the repositories as it happens, with each agent's behaviour policy one click away, and Gravity, the library it became, which can draw any system the same way](a-galaxy-of-agents.md) The Galaxy from Web Summit: the RiskMandate team as a live 3D solar system of people, agents and messages, and the library it became.
- [Partners sell, we build: the AgentiCCells partner programme in full, three kinds of partner, a freelancer, a small consultancy and a larger firm, what each one sells, the agent team behind even the smallest website cell, the rules of engagement, who owns what, who invoices, who gets paid and when, what stays with the partner, and why a partner who takes the open code and does it alone is still a win](partners-sell-we-build.md) The AgentiCCells partner programme: three kinds of partner, the agent team they resell, and the rules of engagement, 50/50.
- [PrompTugal.news, the newsroom we ran at Web Summit: desks of agents that captured, mapped, wrote and reviewed 73 signed articles in ten days, an accountant that counted every run, and fifty outreach drafts that no agent was allowed to send](promptugal-news-the-newsroom-we-ran.md) PrompTugal.news: 73 signed articles in ten days from desks of agents, a reviewer for every draft, and fifty outreach drafts no agent could send.
- [Feature behaviour policies: taking the idea of agent behaviour policies down to every feature, bug fix and resource, so that a feature's policy is also its description, what changed is the difference between two policies, the gap between what a resource can do and what a feature needs is where the vulnerabilities live, and signed policies travelling with each request make a bug or an attack a path that was never supposed to exist](feature-behaviour-policies.md) Write a behaviour policy per feature: it describes the feature, sets what to enforce, and makes a bug or attack a path outside it.
- [Starting AgentiCCells: a company that sets up small agentic teams, cells, in the customer's own environment, with a control centre, everything open and no state on our side; how it was named, researched, reviewed and set up in a day](starting-agenticcells.md) AgentiCCells: a new company that sets up small agentic teams in the customer's environment, with a control centre, all open, no state on our side.
- [The website cell: what we now sell, a GitHub repository fully set up with a live site on its own address, a CLAUDE.md and a behaviour policy, five designs by a team of agents, and then the site is yours to change with your own Claude, what it should cost, how it compares with Wix, Squarespace, Framer, Lovable and a freelancer, who already sells something close to it, and where to find buyers and partners](the-website-cell.md) The website cell mapped: a repository fully set up, five designs by agents, owned with your own Claude; price, competitors, partners.
- [The first round trip: a sovereign website made for Kate Curtis-Evans during our call, five designs from a design agent of its own, then handed over so she edits it herself from her own Claude, the friction that took multiple rounds to get through, what it says about over-privilege, and the next step, a signed and sealed channel from her site straight to the agent](the-first-round-trip.md) The first round trip of Sovereign Website with someone from outside: a site made during a call, handed over, and edited by its owner's own Claude.
- [Sovereign websites, the investment case: PrompTugal's investor decks rewritten for a deliverable that is needed everywhere, in every language, in a market built on rent and lock-in, a one-off delivery that is already fully agentic, value given before payment through a demo in a vault, a long list of upsells, and why this is now a proper, scalable, investable architecture](sovereign-websites-the-investment-case.md) Sovereign websites as an investment: one deliverable needed everywhere, a one-off agentic delivery, value first through a vault demo, and upsells.
- [Sovereignty you can move: why where your data is hosted is not sovereignty, why being able to move the site, the data and the schema is, why that makes the website cell a direct competitor to Wix, Squarespace and Fliplet with a proper sovereign offer, European-aligned, multilingual and privacy-first, and the business that other companies can build on it](sovereignty-you-can-move.md) Sovereignty is being able to move your site, data and schema, not where it is hosted; the website cell as a sovereign competitor.
- [An agentic console: a simulated control room for a team of agentic teams, with time you can rewind, accounts drawn as trust zones, stops that reach every agent, signed messages on three channels, and the console itself as an agent](an-agentic-console.md) An agentic console, simulated: accounts as trust zones, time you can rewind, signed messages on three channels, honest stops, and the console as an agent.

### Continued by

- [The showroom: what the Sovereign Website hub shows after its first days, 33 live sites from one pipeline, people's portfolios with five designs each, independent brochures for our startups, a provider guide, tools that run on the owner's own key, made-up businesses, a family of news sites, and the theme that is emerging across all of them, a site that is yours, says how it was made and can be worked on by your own AI](the-showroom.md) The Sovereign Website hub after its first days: 33 live sites from one pipeline, and the shared bones that are becoming the product.

[All articles](index.md) · [All graphs](graphs.md)

Article No. 517 · [start a reading list with it](https://newsroom.sgit.ai/for/make.html#r=517)

**Posting this article on LinkedIn?** The cover is [the-way-in.jpg](banners/the-way-in.jpg) (1920×1080, title and key ideas on it). Upload it as the article cover, paste the title, then select and copy the body from this page.

**Want the next issue by email.** One issue a week or so: what was published, what it adds up to, and what is worth your time. [Subscribe to the SGit Newsroom →](../subscribe/index.md)

[← All articles](index.md)


---

*[Site index for agents](../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/the-way-in.html)*
