AgentiCCells
Choose a designDesign
Idioma: Español (España)

Esta página aún no está traducida. Está leyendo el original en inglés.

For consultancies: one cell for each client, the same team every time

You run a small company with customers, and some of them would want this. This page is for you, and you can read it without any other. Email us as a consultancy when you want to talk.

See the website cell

What you sell

A website cell for each client, then the workflows behind it. Because the set-up is automated, a second site is not a second project: it is the same team and the same policies with a new customer's material. Even the smallest cell is a team of agents, a conductor, a researcher, a designer, a developer and a security reviewer, each with a job description and a behaviour policy (source). You are selling a team, not a template.

The model is Dinis Cruz's, in his words: "the rules of engagement here are 50-50 split ... if they bring the business, I do the automation, I do the flow, I set that up, and then they can do whatever they want" (his brief, 2026-11-17). The full programme is in his article, Partners sell, we build (CC BY 4.0).

How it fits together, for a consultancy partnerThe partner brings the business and sells to the customer. The partner sends the material to the AgentiCCells factory, where the conductor, researcher, designer, developer and security reviewer work under agent behaviour policies from riskmandate.ai. The factory hands the site over into the customer's own accounts: a GitHub repository with its history, and Claude to manage the site afterwards. The partner gets admin access to the repository.CONSULTANCY PARTNERYoubring the businessThe customerwants the sitematerialAGENTICCELLS FACTORYconductorresearcherdesignerdevelopersecurity reviewerBehaviour policies for every agentfrom riskmandate.aihand-overTHE CUSTOMER'S OWN ACCOUNTSGitHubThe repository,with its history.ClaudeManages the siteafter hand-over.
How the parts connect. The partner gets admin access to the delivered repository; the customer owns it.

A worked example, from first conversation to hand-over and after

How a deal runs, for a consultancy partnerSix steps in order. 1 Find: you and your team find a customer. 2 Material: photos, videos and a short description from the customer. 3 Set up by the factory: AgentiCCells sets up the agent team and its behaviour policies. 4 Five designs: the agent team builds five designs and the customer chooses. 5 Hand-over: the repository moves to the customer's GitHub with its history and the partner gets admin access. 6 After: Repeat with the next customer: the setup is automated. Keep your own repositories.CONSULTANCY PARTNER1YOU AND YOUR TEAMFindA customer who wants a website,a workflow or an agent email.2YOU AND THE CUSTOMERMaterialPhotos, videos and a short description.Some of it can already be public.3AGENTICCELLSSet up by the factoryWe set up the agent team and itsbehaviour policies, and load the material.4THE AGENT TEAMFive designsThe team builds five designs of the site.You and the customer pick and comment.5AGENTICCELLSHand-overThe repository moves to the customer'sGitHub, with its history. You get admin.6YOU AND YOUR TEAMAfterRepeat with the next customer: the setupis automated. Keep your own repositories.
The flow of a deal, first conversation to after hand-over. A proposal: no deal has run through a partner yet.

One of your clients asks for a site, or you offer one. You collect their photos, videos and words, and which parts may be public, and send them to us. The factory sets up the cell, the agent team makes five designs, and you and the client choose. The repository goes to the client's GitHub with its history and you get admin access. You run hosting, support and retainers at your prices, and the second client repeats the same steps with the same team. This is an example of how a deal would run, not a record of one: no deal has run.

Who does what

Who does what, for a consultancy partnerFour lanes. The partner: Your team finds customers and runs many deals, collects material, shows previews, sells care. AgentiCCells: builds the setup and the flow, runs the agent team and hands the site over; its job ends there. The agent team: a conductor, researcher, designer, developer and security reviewer, each under a behaviour policy, each signing its own work. The customer: gives photos and words, chooses and approves a design, and owns the repository.CONSULTANCY PARTNERYou and your teamPARTNERYour team finds customers and runs many deals,collects material, shows previews, sells care.AgentiCCellsTHE FACTORYBuilds the setup and the flow, runs theagent team, hands the site over. Ends there.The agent teamUNDER POLICIESconductorresearcherdesignerdevelopersecurity reviewerEach agent signs its own work and logs it.The customerOWNS THE SITEGives the photos and words, picks a design,approves it, and owns the repository.
Four parties and what each does. The agent team's roles are our own team's; the behaviour policies come from riskmandate.ai.

The same, as a table for screen readers and search:

YouAgentiCCellsThe customerThe agents
Find the customer, agree the priceYesAgrees
Send the materialCollects and passes it onReceives itProvides it and says what may be public
Set up the cellRuns the factoryConductor, researcher, designer, developer, security reviewer
Five designsShows themChoosesDesigner and developer make them
Hand-overReceives admin accessMoves the repositoryOwns the repository
Hosting, support, retainersYours, at your pricesNo part, no sharePays you
New features and templatesAsksBuilds, priced on the same splitAgent team

The money

The money, for a consultancy partnerThe customer pays for the site; whoever has the customer invoices. The sale is split 50 percent to the partner and 50 percent to AgentiCCells when we are involved. The partner keeps entirely, at their own prices: hosting, support, retainers, subscriptions, changes and installation. AgentiCCells takes no share of these. Payment terms are agreed for each deal.CONSULTANCY PARTNERThe customer pays for the siteWhoever has the customer invoices.50%50%YouAgentiCCellsThe split of the sale, when we are involved.What you keep entirely, at your priceshostingsupportretainerssubscriptionschangesinstallationWe take no share and no part of these.Payment terms are agreed for each deal.
The 50/50 split is Dinis Cruz's, 2026-11-17 (the brief). A proposal, not a contract.

The figures and rules come from Dinis Cruz's article; where the page and the article differ on the website cell's price, data/offer.json wins, because Dinis set it after the article.

What you need to start

A client list or a way to reach it; one person at your company who sends us material and talks to clients; the clients' GitHub accounts. You decide how you price and what you promise.

Partner terms

Nothing has been sold yet, through a partner or otherwise, and no partner has signed. The terms are common sense and few. The customer owns the site, the repository and the material. You own the relationship. Our code and policies are open, and you may keep your own repositories and your customers' work private. Nobody is named publicly, customer or partner, without agreement. It works in any country and any language, and you invoice in your own currency under your own law. The same terms are on the partners page.

Talk to us

Email us as a consultancy. Say who you are and what you have in mind. A person reads it and answers. No agent of ours writes to anyone on its own.

*Source for the figures and rules above: Partners sell, we build, Dinis Cruz, newsroom.sgit.ai, 2026-11-17, CC BY 4.0.*