Esta página aún no está traducida. Está leyendo el original en inglés.
Cells
A cell is a small agentic team set up in your environment. It is useful on its own, and you can remove it without breaking anything else. There are four sizes, from one agent to a network. Every price is a first proposal, and nothing has been sold. Examples we have made are on the hub.
Jump to
The four sizes
| Price | Format | agenticcells.ai sells (proposal) | riskmandate.ai sells (proposal) |
|---|---|---|---|
| £500 (first proposal) | An agentic flow we run ourselves with agents. No meetings, low touch, almost fully automated. | A cell we run for you, such as a website cell. | A behaviour policy. |
| £1,500 (first proposal) | Preparation before, two meetings, work in between, a presentation, then final delivery. | A small cell set up with you and handed over to your accounts. | A policy written with you, tested on your agents and handed over. |
| £5,000 (first proposal) | About two days of engagement, one meeting or a couple, heavier lifting, maybe some travel and more time with you. | A team of cells with a conductor, a board and keys, working on your own work. | Policies for a team of agents, with the evidence of what they do. |
| £20,000 (first proposal) | A customer engagement. We come in, spend time with you, map the work and deliver a whole set of things. | A custom network of cells and conductors across a division. | Policies and observability across all the agents you run, from one to hundreds. |
The same ladder on both sites, with the prices and formats as Dinis Cruz gave them. All prices are a first proposal and not yet offers. What each site sells at each step is a proposal too. A policy alone is a RiskMandate sale, a team is an AgentiCCells sale, and a dual sale is possible: a team with its policies.
The formats condense Dinis Cruz's words of 2026-11-16 (board/briefs/two-sites-2026-11-16.md): the first step has "no meetings" and is "low touch"; the second has preparation, "2 kind of meetings", work, a presentation and a final delivery; the third is "2 days engagement" with "more heavy lifting" and "maybe some travel"; the fourth is "a customer engagement". The same ladder is on riskmandate.ai, where it sells agent behaviour policies. A policy alone is a RiskMandate sale and a team is ours, usually with policies, so a dual sale is possible. What each site sells at each step is a proposal.
The model is fixed-price cells. Every price is a first proposal, not an offer. Whether support comes as finite packs or in some other form is still to be decided.
Two modes: who runs the team
Any cell can be run in one of two ways. Both come from Dinis Cruz, Atomic cells, end to end, newsroom.sgit.ai, 2026-11-15. Prices are a first proposal, not an offer.
- No-touch: we run the team. £250 (launch price, usually £500), first proposal. The agentic team runs on our accounts and builds for you. You need only a browser. This is the website cell: you steer with a key, and at handover the repository moves to your GitHub.
- Their own: they run the team. From £1,500, first proposal. The team runs in your own GitHub and Claude accounts, which are set up in a couple of meetings. We then step away. It costs more and needs those accounts, and you hold the access.
What differs is whose accounts the work runs in. In the second mode we keep no state, because the work never ran on our side.
Neither mode has been sold yet. The end-to-end flow for the first is being built now.
The ladder in Dinis's words
Dinis Cruz gives the same ladder for every company on the sgit.ai sites (The intersection, newsroom.sgit.ai, 2026-11-16): "£500 for one workflow, done in a session; £1,500 for two sessions and a handover; £5,000 for a few days and a team; £20,000 for a bespoke engagement." For us, "one agent or a website" sits at £500. Every price here is a first proposal, as the article says of ours. The article notes that only AgentiCCells and RiskMandate show prices today, and that the rest of the ladder is a proposal.
The ladder as biology
The newsroom reads the ladder as biology (Atomic cells, end to end, Dinis Cruz, newsroom.sgit.ai, 2026-11-15). Its words are quoted below. Every price is a first proposal, not an offer.
- Single cell. "One site, one small team, a feedback lane and a handover." £500, first proposal. This is the no-touch mode above.
- Cell handed over. "Set up with the customer in a couple of meetings and handed over into their own accounts." From £1,500, first proposal. This is the second mode above.
- Colony. "Several cells integrated with the customer's work, with a conductor, a board and keys." £5,000, first proposal.
- Multi-cell organism. "A custom network of cells, conductors of conductors, policies and observability." £20,000, first proposal. The article's caption calls this stage "a network".
The article's rungs and the four sizes above are not a perfect match. Its £1,500 rung (first proposal) is a single cell handed over, while the £1,500 size above (first proposal) is a few sessions. Dinis's newer wording, "two sessions and a handover", fits both readings, so we have kept both and not reconciled them. Neither has been sold yet, and the biology is the newsroom's way of reading the ladder, not a measured result.
The six setups of an agentic system
The newsroom describes six setups, from the simplest up, in Six setups of an agentic system:
- A task.
- One agent.
- An agent with sub-agents, in one runtime.
- Several sessions, one per role.
- A conductor and its agents.
- Conductors of conductors.
The lower three are a prompt. The upper three are a setup, with keys, lanes, boards and policies.
The four sizes in detail
For each size: what we set up, what you provide, what you own afterwards, and how long it takes. Every price is a first proposal, not an offer. No size has been sold yet, so no time below is measured on a customer. Where we have no figure, the page says so. The "includes" lines come from data/cells.json (Dinis Cruz, board/BRIEF.md, 2026-11-15).
One agent (£500, first proposal)
- Matches the setup: an agent with sub-agents in one runtime (six setups).
- What we set up: one agent with sub-agents in one runtime, for one workflow, set up in a session.
- What you provide: the workflow you want helped, and a place for the agent to run. Which runtime is yours to choose (see open source).
- What you own afterwards: the setup, as files in your own repository. We keep no state.
- How long it takes: one session, as the "includes" line says. We have not timed it on a customer.
- The same price as the website cell, a different thing. The website cell is the no-touch mode, run on our accounts. This size runs in your environment.
A few sessions (£1,500, first proposal)
- Matches the setup: several sessions, one per role (six setups).
- What we set up: one session per role, each its own runtime, sharing lanes and a vault.
- What you provide: the roles you want, and the accounts those sessions run in.
- What you own afterwards: the sessions' setup, the lanes and the vault, all in your environment.
- How long it takes: not yet known. The newsroom says "a couple of meetings" for the handed-over cell (Atomic cells, end to end); we have not matched that to this size.
A team (£5,000, first proposal)
- Matches the setup: a conductor and its agents (six setups).
- What we set up: a conductor and its agents, a key per agent (only the public half published), a board as files, and the console.
- What you provide: a repository for the board, accounts for the agents.
- What you own afterwards: the repository, the board, the briefs and the public keys. Private keys stay in each agent's session and are gone when it ends.
- How long it takes: a week of setup, as the "includes" line says (board/BRIEF.md). This is a proposal, not a measured time.
A network (£20,000, first proposal)
- Matches the setup: conductors of conductors (six setups).
- What we set up: conductors of conductors across a division or network, with policies and observability.
- What you provide: the division's structure, the policies you want, and who may approve changes.
- What you own afterwards: the same as a team, for every conductor: boards, briefs, policies and the observability files.
- How long it takes: not yet known, and no figure has been proposed. We will not guess one here.
If you would rather do this yourself, everything we use is open. Start with open source and the method.
Can we sell it? Three questions for each size
Newsroom prompt: "Can you sell it?" (newsroom digest of 2026-11-15). For each size we answer three questions: have we sold it, can we deliver it at this size, and would the buyer understand our words. Prices are first proposals. These are our own judgements, not measurements.
| Size | Have we sold it? | Can we deliver it at this size? | Would a buyer understand the words? |
|---|---|---|---|
| One agent | No. | Not shown for a customer. The nearest evidence is the website cell, which is a different thing, and its demos (case study). | Probably. "One agent for one workflow" is plain, but "sub-agents in one runtime" is not. Untested on a buyer. |
| A few sessions | No. | Not shown for a customer. We run roles as separate sessions ourselves (our team as a cell), which is our own use, not a delivery. | Doubtful. "Sessions", "lanes" and "vault" need an explanation. Untested on a buyer. |
| A team | No. | Our own team is the nearest example (our team as a cell). We have not delivered one in a customer's environment. | Partly. "A team of agents with a board" is clear; "conductor" and "keys" are not. Untested on a buyer. |
| A network | No. | No. We have not built or delivered one, and propose no time for it. | Doubtful. "Conductors of conductors" is our jargon. Untested on a buyer. |
No size has been sold, and no page on this site should be read as saying otherwise (FAQ, trust). If you want to be the first, write to us. We will say so plainly if the first sale changes any row.
What every cell includes
- The console, so you can see the agents and what they do.
- A key per agent, with only the public half published.
- A board of files in your own repository.
- No state on our side. When the work is done, everything stays with you.
Five ways to make a cell yours
From Dinis Cruz, Fork it (newsroom.sgit.ai, 2026-11-16). The article calls this a plan. Each example's page on the hub says which of the five it offers today; the hub shows the current state of each, and we state no count here.
- Fork it on GitHub. Works today, as the standard GitHub fork link on each hub page, for a public repository. The cells are not yet built to be forked by a stranger: expect to change our team's settings and rules after you fork.
- Deploy it in one click. Planned. Not built: no cell has a deploy button yet.
- Run it in your assistant. Planned. Not built.
- Take it as a vault. Planned. Not built: no cell has a vault download yet.
- Ask us. Works today, by email to agent@riskmandate.ai, on the paid ladder. First proposal prices, nothing sold yet.
The first four are meant to be free. That is the article's plan, not something we offer yet.
Examples live on the hub
We do not list every cell we have made on this page. The hub does that, with one page per cell, so you can find one, open it and copy it. This site sells; the hub lists. Every cell we host publicly is a demo, made to show how the work goes, and it says so. None is a customer's site, and none has been sold.
The lead examples are two personal websites made by the site factory, with the people's agreement to be named: Yiheng Wang's site (hub page; the newsroom article A website that is her, 2026-11-16) and Silvio Switha's portfolio (hub page; A portfolio with a film first, 2026-11-16). Both are demos. The articles give the factory's measured times; read them there, we do not restate them as a promise.
Examples by kind: the site factory, the site template, an email cell and a specialist agent. A proposed example, not yet built, is the job-seeker cell. Each page on the hub has a fork link; the five ways to make a cell yours are below.
What this page does not claim
- No cell has been sold yet.
- The matching of cells to setups is our reading, not a measured result.
See also where we fit in the stack.