for agents/llms.txtv0.14.177

Home / Articles / 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: 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

By · 2026-11-17 · article v1.0.0 · newsroom v0.14.147 · agenticcellspartnersgo-to-marketwebsitesagent-teamsbehaviour-policiesproductarticle

Abstract: Our go-to-market for the website cell is not to compete with the people who already sell websites, workflows and IT to small businesses. It is to give them what we have. This is the partner programme, written so I can send it to the people I already have in mind this week. There are three kinds of partner: a freelancer who talks to people and wants to sell more; a small consultancy with customers who want this; and a larger firm with bigger projects, which wants us, or my network of experts, involved. What they sell is the unit we now make: a website cell, a GitHub repository fully set up with a live site, a CLAUDE.md and a behaviour policy, five designs by a team of agents, and the site handed over to its owner's Claude. Even the smallest one is a team of agents, a conductor, a designer, a developer, a researcher and a security reviewer, each with a job description, and that team is what partners resell. The rules are simple. If I am involved, doing the orchestration and running the factory, the sale is split 50/50. Whoever brings the customer invoices them. The customer owns the site. Hosting, support and monthly retainers belong to the partner, entirely: I do not do subscriptions. My part is the set-up, and then new features, templates, workflows and behaviour policies. It works in any country and any language. And a partner who reads this, takes the open source and does it alone, is still a win: one more team running our technology, and one more place agent behaviour policies are used for real.

Three kinds of partner: a freelancer, a small consultancy and a larger firm, and what each one sells.

In short

Why partners

Since our sites went up, everyone I show them to wants one (the website cell). I could try to sell them one by one. Or I can give the ability to sell them to the people who already talk to small businesses, artists, consultants and companies every day, and who would like to sell more. They have the relationships; we have the factory, the agents and the policies. That is the whole idea, and it is why I want this to be ridiculously partner-friendly.

And there is no losing case. A partner who reads this and decides to take the open source and do it themselves is still using our technology, is a potential customer for the harder things later, and is one more team running agent behaviour policies for real (governance from zero).

Three kinds of partner

  1. The freelancer. One person, who talks to people and can say: for this amount, I will give you a website, an agentic email, a workflow. They focus on one kind of customer and one flow, and want to do more of it. I have several of them in mind already.
  2. The small consultancy. A firm with existing customers, who want this, and who might do many: a website cell for each client, then the workflows behind it (any data, with any data).
  3. The larger firm. Bigger projects, a bigger ladder, and a reason to want us involved: our orchestration, and my network of people who already know how to run agentic teams, the way six of us ran around 250 agents at Web Summit (the team's operating system).

What they sell: a team, not a template

The smallest website cell is a team: conductor, researcher, designer, developer and security reviewer.

The thing to make explicit is that even our simplest workflow is a team of agents wired together, not one prompt. A website cell has, at least:

Each has a written job description and a behaviour policy, and each signs its work. That team, with or without vaults for the customer's material, is what a partner resells. On a bigger job, the team grows: a writer, a reviewer, a data agent, a team per workflow (six setups of an agentic system).

How a deal works

A deal in six steps: the partner finds the customer, we build, the owner keeps it, the partner runs it after.
  1. The partner finds the customer and agrees what they want: a site, a flow, a price.
  2. The customer's material comes in: photos, videos, words, links; into a vault if it is private.
  3. The factory sets up the cell: repository, address, site, CLAUDE.md, policy.
  4. The agent team makes five designs; the customer chooses, with the partner.
  5. Hand-over: the site is the customer's, in their repository, with their Claude; the partner gets admin access if the customer agrees.
  6. After: the partner hosts, supports, changes and charges for it as they choose; we come back for new features, templates, workflows and policies.

The rules of engagement

The rules of engagement: who owns what, who invoices, who gets paid, and what stays with whom.

Common sense, written down. Where something is not covered here, we talk.

Any country, any language

Nothing here is tied to the UK or to English. The agents write in the customer's language, the site is static and serves anywhere, and the partner invoices in their own currency under their own law. A partner in Portugal sells in Portuguese; a partner in Brazil sells in Brazil. Our part is the same everywhere.

Next: packages for products

The same model works for products. A startup that wants its customers to use its product well could have a package: a cell set up to run it, with the connectors, workflows and policies for that one product, the way we built ours around Odoo (integrate with whatever is on the other side). A package for Odoo, one for WordPress, one per product, sold by its makers and their partners. That comes after the website cell, which is first.

What I am asking

If you sell to people who need a website, or a workflow, or a little help with AI: do you want to go into business on this? Read this, look at the examples on agenticcells.ai, and tell me which of the three you are. The first partners will shape the rules with me.

What this does not claim

Where this comes from

My own briefs of 17 November 2026, here and to the AgentiCCells team (its strategy, board/strategy/website-cell-go-to-market.md, in the AgentiCCells website repository); agenticcells.ai. Earlier on this site: the website cell, governance from zero, any data, with any data, the team's operating system, who hands out the work?, six setups of an agentic system, the intersection, integrate with whatever is on the other side.

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. 465 · 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.