# 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, sgit.ai

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

*Source: <https://newsroom.sgit.ai/articles/partners-sell-we-build.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) / 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 [Dinis Cruz](https://sgit.ai/about/index.md) · 2026-11-17 · [article v1.0.0](versions/partners-sell-we-build.md) · [newsroom v0.14.147](https://newsroom.sgit.ai/admin/versions.html) · 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

- **Our go-to-market is partners,** not competing with them.
- **Three kinds:** the freelancer, the small consultancy, the larger firm.
- **What they sell:** the website cell, and the agent team behind it.
- **50/50 when I am involved;** whoever has the customer invoices.
- **The customer owns the site;** the partner owns hosting, support and retainers.
- **My part:** set-up, then new features, templates, workflows and policies.
- **Any country, any language.**
- **A partner who does it alone is still a win.**

## Why partners

Since our sites went up, everyone I show them to wants one ([the website cell](the-website-cell.md)). 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](governance-from-zero.md)).

## 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](any-data-with-any-data.md)).
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](the-teams-operating-system.md)).

## 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:

- **A conductor,** who takes the brief and hands out the work ([who hands out the work?](who-hands-out-the-work.md)).
- **A researcher,** who reads what the person gave us and what is public about them, with sources.
- **A designer,** who makes the five designs.
- **A developer,** who builds and releases the site, with its checks.
- **A security reviewer,** who checks the policy, the leak scan and what the site exposes.

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](six-setups-of-an-agentic-system.md)).

## 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.

- **The split:** if I am involved, orchestrating and running the factory, the revenue from the sale is split 50/50. For the larger projects, we agree it case by case.
- **Who invoices:** whoever has the customer. If the customer came through me, I invoice and pay the partner their half; if through the partner, they invoice and pay me mine.
- **When:** the invoicing side pays the other its half within 14 days of being paid by the customer. A proposal; we agree it in each partnership.
- **Prices:** the partner is free to use our ladder, £500, £1,500, £5,000 and £20,000, or set their own ([the intersection](the-intersection.md)). The split is on what the customer pays for the build.
- **Subscriptions are the partner's:** hosting, maintenance, support, changes, a retainer of £50, £100 or £500 a month. I take no part and no share.
- **My part:** the set-up, and then new features, configurations, capabilities, workflows, templates and behaviour policies, each priced on the same 50/50.
- **Who owns what:** the customer owns their site, their repository and their material. The partner owns the relationship. The code and policies we give are open source; the partner may keep their own repositories and customers' work private, and that is fine.
- **Names:** nobody is named publicly, customer or partner, without their agreement.

## 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](integrate-with-whatever-is-on-the-other-side.md)). 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](https://agenticcells.ai/website-cell/), and tell me which of the three you are. The first partners will shape the rules with me.

## What this does not claim

- **No partner has signed yet;** the terms are a first draft.
- **Nothing has been sold;** the examples are demos with consent.
- **The payment terms are a proposal,** agreed per partnership.

## 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](https://agenticcells.ai/website-cell/). Earlier on this site: [the website cell](the-website-cell.md), [governance from zero](governance-from-zero.md), [any data, with any data](any-data-with-any-data.md), [the team's operating system](the-teams-operating-system.md), [who hands out the work?](who-hands-out-the-work.md), [six setups of an agentic system](six-setups-of-an-agentic-system.md), [the intersection](the-intersection.md), [integrate with whatever is on the other side](integrate-with-whatever-is-on-the-other-side.md).

## Threads

Startups & strategyAgents & policy[This article as a graph →](graphs.md#partners-sell-we-build)

### Builds on

- [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.
- [Governance from zero: Nina J. noticed that identity and behaviour policies come with our smallest £500 offer, not as a premium upgrade, because "we're only testing it" has never reassured a security review; my answer is that even the £0 offer has all of it, and here is why open source is what makes that possible, why security sold as an upgrade is a choice, and why a pilot with its governance built in is a pilot that can convert](governance-from-zero.md) A reply to Nina J.: identity and behaviour policies come with our smallest offer, even at £0, because everything is open source.
- [Any data, with any data: why I am now comfortable saying we can connect any data source with any other, the nine steps from access to a vault, a key and a map on the other side, how each owner keeps control, where the person stays in charge, and why connecting two, five, fifty or a hundred datasets should be something an agentic cell sells](any-data-with-any-data.md) Why we can now connect any data source with any other: nine steps, owners keep control, a person approves every key, sold as cells.
- [The team's operating system: web-summit.sgit.ai, the one site where six people and their agents ran Web Summit, with a brief and a command centre for each person, a key and an inbox for each agent, the board as files, and the outside world on a map](the-teams-operating-system.md) web-summit.sgit.ai: one site where six people and their agents ran Web Summit, in four layers built on git.
- [Who hands out the work? A reply to Markus Franz on Ippen's editorial team of agents, with our answer from six people and around 250 agents at Web Summit and from this newsroom, a person sets the work, one conductor agent hands it out, specialists and a reviewer do it, and a person decides what goes out, plus one thing we would add to one front door, a way to close it](who-hands-out-the-work.md) A reply to Markus Franz: who hands out the work to agents? A person sets it, one conductor hands it out, a person signs off, and the door can close.
- [Six setups of an agentic system: from a single task to one agent, sub-agents, several sessions, a conductor and its team, and conductors of conductors, with the altitudes of a run inside each and command and control growing at every step](six-setups-of-an-agentic-system.md) Six setups of an agentic system, from a task to conductors of conductors, with the altitudes of a run inside each: make the dangerous thing unreachable.
- [The intersection: SGit, SHarness, Agent Behaviour Policies, RiskMandate and AgentiCCells as one stack of separate companies, now with real customers, real usage and real examples, one ladder of offers on every site, and a plan to align them all](the-intersection.md) SGit, SHarness, ABP, RiskMandate and AgentiCCells as one stack of separate companies, with real usage and one ladder of offers on every site.
- [Integrate with whatever is on the other side: why we never start by asking a customer to move, how we build around the systems they already run, from Odoo 12 to Salesforce, and how, over time, either their system gets better and we retire our code, or ours becomes the better place](integrate-with-whatever-is-on-the-other-side.md) We never start by asking a customer to move. We integrate with what they run, build around it, and either retire our code or become the better place.

### Continued by

- [The sovereign website: a pivot brief for agenticcells.ai, what the site says today and what it should say next, sovereignty as the headline, a website you own, control, change and can run anywhere, the deliverables explained, the infographics to draw, five homepage designs to choose from, and the partner programme and examples that already prove it](the-sovereign-website.md) A pivot brief for agenticcells.ai: lead with sovereignty, show the deliverables, draw the infographics, and make five homepage designs.
- [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.
- [One commit, one site, one owner: the small change to the AgentiCCells site factory that unblocked the most, giving a GitHub account access to the repository it creates, so that one commit with a site's details and its owner's account makes the repository, the DNS record in AWS, the address, HTTPS and the owner's access in under a minute, and all that is left is to point Claude at it](one-commit-one-site-one-owner.md) The factory change that unblocked the most: one commit makes a repository, DNS, an address, HTTPS and the owner's access in 55 seconds.
- [You bring the business, we build the site: the AgentiCCells partner programme as it now stands on agenticcells.ai, one page per kind of partner, each with four figures, the fit, the flow, who does what and the money, a launch price of £250 with free evaluations every day, partner terms published, five designs on every page and ten languages from day one, all built in a night by the site's own agent team from two newsroom articles](you-bring-the-business.md) The AgentiCCells partner programme as built overnight: one page per partner, four figures each, £250 launch, free evaluations, ten languages.
- [Static against the platforms: why a static site in your own repository, edited by Claude and watched by a security agent, is a real alternative to WordPress, Wix and Squarespace, what the numbers say about their reach, their attack surface, their complexity and their lock-in, and a converter that could bring a WordPress or Squarespace site across](static-against-the-platforms.md) Why a static site in your own repository, edited by Claude, is an alternative to WordPress, Wix and Squarespace, and a converter to bring sites across.

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

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

**Posting this article on LinkedIn?** The cover is [partners-sell-we-build.jpg](banners/partners-sell-we-build.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/partners-sell-we-build.html)*
