for agents/llms.txtv0.14.128

Home / Articles / The cell is the unit: positioning AgentiCCells around small, focused cells, each with an objective, a deliverable and a behaviour policy, each with a page that sells it, a free recipe and three ways to get help, a catalogue that grows one need at a time, in each industry's own words, and why we should run our own work in cells first

The cell is the unit: positioning AgentiCCells around small, focused cells, each with an objective, a deliverable and a behaviour policy, each with a page that sells it, a free recipe and three ways to get help, a catalogue that grows one need at a time, in each industry's own words, and why we should run our own work in cells first

By · 2026-11-16 · article v1.0.0 · newsroom v0.14.123 · agenticcellspositioningcellsproductgo-to-marketabparticle

Abstract: AgentiCCells needs a sharper idea at its centre, and I think it is the cell itself. A cell is the unit of what we sell: one focused job, with an objective, a deliverable and a behaviour policy, and as many parts as the job needs, a Claude session, a vault, a repository, a website, lanes and keys, a schedule, a connector, a person who owns it. A cell can be as simple as Claude replying to email, or as rich as a team keeping a website; every website is a cell. Now that the site factory creates repositories and changes AWS from a commit, we can put capabilities into cells that we never could before. So the selling has to be just as focused: every cell gets a page, with what it does, what you get, examples, use cases and its policy, and, on the side, four ways to start: the recipe for free, our agent helps you, we help you, or we set it up for you. The catalogue grows the simplest way: someone says "I need help with this", and we add a cell for it, often in the language of one industry, a clinic, a farm, a council. And we should live in cells ourselves: our team should think in cells, and I should move my own Claude work into cells, because that is the best test of whether they are easy to use, and the fastest way to find the next one.

A catalogue of cells: each one focused job with its own page, growing one need at a time, by industry too.

In short

Why the cell

AgentiCCells today explains itself by size: a ladder from one agent to a network of teams, the six setups of an agentic system, two modes of who runs the team (six setups of an agentic system). That is right, and it is how a buyer understands the price. But it is not how a buyer thinks about the problem. Nobody wakes up wanting "a few sessions with lanes and a vault". They want help replying to email, keeping a website, following up after an event.

So the cell itself should be at the centre: the unit of what we build, what we sell, and how we work. We need to think hard about what a cell looks like, how it is sold, what the customer is buying, how it is set up, and how it actually works day to day.

The anatomy of a cell

The anatomy of a cell: an objective, a deliverable and a behaviour policy always; other parts as the job needs.

Every cell has three things it cannot do without:

And then as many parts as its job needs: a Claude session to do the work; a vault for its memory, files and record (how a vault works); a repository and CI; a website on its own subdomain; lanes and keys to talk, sign and approve; a schedule of wakes; a connector to email, a calendar, Odoo or a CRM; and a person who owns it.

That range is the point. A cell can be as small as one Claude session replying to email under a policy, or as rich as a team keeping a website with a factory behind it (the site factory works). Every website is a cell. Now that the factory creates repositories and changes AWS from a commit, cells can carry capabilities that were too painful to set up before.

A page for every cell

A page for every cell: what it does, what you get, examples, use cases, its policy, and four ways to start.

Selling has to be as focused as the cell. Every cell gets its own page, built the same way:

And, on the side, four ways to start:

  1. Free: the recipe. The brief, the policy and the steps to run it yourself, with your own Claude. Most people should start here, and many will stay here, which is fine: it drives usage.
  2. Our agent helps you: a specialist agent reviews your setup and tells you what to fix (specialist agents for every team).
  3. We help you: two sessions with a person, on the ladder at £1,500.
  4. We set it up for you: in your accounts or ours, from £500 (atomic cells, end to end).

A catalogue that grows one need at a time

The catalogue grows the simplest possible way. Someone says: I need help with this. I need help sending these emails. I need help keeping this page current. And we add a cell for it. That is the workflow now: find the use case, write the cell, give it a page.

Some cells are general: reply to your inbox, follow up after an event, a weekly digest, a website you steer, translate your site, debrief your meetings, a CRM of your contacts, a policy for your agent, a vault for a project. Many will be specific to one industry, and that is good. A clinic's cell drafts patient letters in plain words for a clinician to approve; a farm's takes orders by email and keeps a page of what is in season; a council's answers the same questions every week, with the sources. The cell is the same underneath; its page, its examples and its words belong to that industry, and it connects to that industry's systems (integrate with whatever is on the other side).

Live in cells first

The best test of whether cells are easy to use is to use them ourselves, every day. Our team should start thinking in cells: what is this piece of work, what is its objective, its deliverable, its policy? And I should move my own Claude work into cells. Today much of it is sessions that come and go; as cells, each would come packaged with its brief, its policy, its vault and its record, and each would become an example on a page.

The same logic as the CRM applies: what we use ourselves gets better fastest, because the feedback loop is ours (a CRM for us and for our agents). Every cell we run becomes a page, a recipe and a proof.

What to build next

  1. A cell format: a folder with the objective, the deliverable, the behaviour policy, the recipe and the parts, the same for every cell.
  2. The page template for agenticcells.ai, with the four ways to start, generated from that folder.
  3. The first ten cells, from what we already do: reply to your inbox, follow up after an event, a website you steer, debrief your meetings, draft bills in Odoo, a policy for your agent, a vault for a project, a weekly digest, a page per place, CI behaviour policies.
  4. Our own work in cells: each of us moves one recurring piece of work into a cell this week.
  5. A request form: "I need help with...", into an agent's lane, which proposes the next cell.

What this does not claim

Where this comes from

My own thinking, 16 November 2026, and the current agenticcells.ai and its cells page. Earlier on this site: the intersection, six setups of an agentic system, atomic cells, end to end, the site factory works, specialist agents for every team, integrate with whatever is on the other side, a CRM for us and for our agents, where assist becomes execute, how a vault works.

Peer review Not reviewed yet. Review it

Threads

Startups & strategyAgents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 436 · start a reading list with it

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 →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.