AgentiCCells
Choose a designDesign
言語: 日本語(日本)

このページはまだ翻訳されていません。英語の原文をご覧ください。

For firms: bigger projects, with our orchestration and a network of experts

You run a larger company with bigger projects, and you want us, or Dinis Cruz's network of experts, involved. This page is for you, and you can read it without any other. Email us as a firm when you want to talk.

See the website cell

What you sell

The website cell is the smallest thing we sell. For bigger projects the team grows: a writer, a reviewer, a data agent, a team for each workflow, with a conductor handing out the work and a person deciding what goes out. Where your customer wants agents to behave under written rules, the behaviour policies come with the cell and can be extended through riskmandate.ai. Dinis Cruz writes of the same pattern run at an event by six people (the article).

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 larger firm 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.LARGER FIRM 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 larger firm partnerSix steps in order. 1 Find: 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: The next project, case by case, with the experts the work needs.LARGER FIRM PARTNER1YOUR 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.6YOUR TEAMAfterThe next project, case by case, with theexperts the work needs.
The flow of a deal, first conversation to after hand-over. A proposal: no deal has run through a partner yet.

You and a customer describe a larger project: several cells, a workflow around the site, or a cell run in the customer's own accounts. We talk before any price is set, then agree in writing what we build, who from our network of experts is involved and the split. The agent team does the work in the customer's environment where it needs to, and a person reviews and decides what goes out. The customer owns the repository and material and you hold the relationship. You run support and retainers; we return for new features and policies on the same 50/50 unless we agree otherwise. 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 larger firm partnerFour lanes. The partner: Your team leads the project and the customer relationship, and brings the bigger brief. 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.LARGER FIRM PARTNERYou and your teamPARTNERYour team leads the project and the customerrelationship, and brings the bigger brief.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 larger firm 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. Larger projects: the split is agreed case by case, before work starts.LARGER FIRM 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.Larger projects: the split is agreed case by case, before work starts.
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 project in mind, or a customer with one; a person on your side who owns it; a call with us to agree scope and split. Where the customer is regulated, say so early.

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