Esta página aún no está traducida. Está leyendo el original en inglés.
Partners: you bring the business, we build the site
You know people who want a website. We have an agent team that builds one from photos, videos and a short description, and hands it over in a GitHub repository the customer owns. You can sell that to them, with us building it behind you.
Jump to
Pick the page that is nearest to you. Each stands alone, so Dinis Cruz can send you one link.
- Freelancer One person who talks to people: for an amount you set, a website, an agentic email and a workflow.
- Consultancy A small company with customers, doing many: one cell for each client, the same team every time.
- Firm A larger company with bigger projects, wanting us, or our network of experts, involved. Case by case.
The programme is set out in full in Dinis Cruz's article, Partners sell, we build, newsroom.sgit.ai, 2026-11-17, CC BY 4.0.
What a partner sells
The website cell and the agent team behind it. Even the simplest cell is several agents wired up, each with a job description and a behaviour policy, working on a board you can read. You are selling a team, not a template. How the team works is on the method page, and the example sites are on the hub.
The deal, in Dinis Cruz's terms
Dinis Cruz, 2026-11-17, in his brief for this work (board/briefs/website-cell-sales-2026-11-17.md): "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."
- The split is 50/50 of the sale. Larger projects are agreed case by case.
- You bring the business. You find the customer and own the relationship.
- We do the automation, the flow and the build. We set up the team, build the site from the customer's material and hand it over.
- You get admin access to the delivered site. The site is static files in a GitHub repository. The customer owns it, and you can be given admin access to it.
- Our job ends at hand-over. We sell no subscriptions and give no support.
What you can sell on your side
At prices you set, and we take no share and no part:
- subscriptions and monthly care
- support and maintenance
- changes and new pages
- installation and deployment to the host the customer wants
- guidance, including making the GitHub repository for the customer
Dinis Cruz's words: "I don't want to sell subscriptions ... I don't want to be providing support. So if somebody else wants to provide support, they can charge." You may use the price ladder as a starting point or your own prices. The website cell's own price is a first proposal, set in data/offer.json.
This answers the question buyers ask most: who runs the site after hand-over? Your partner, or the customer's own Claude.
Three kinds of partner, in short
The freelancer
One person. "For this much, I will make you a website, give you an agentic email and a workflow." You find the customer, collect the photos and the description, send them to us, show the customer the previews and hand over. Then you sell the care.
The small consultancy
A firm with customers, doing many. Same flow, repeated. Because the setup is automated, a second site is not a second project: the same team, the same policies, a new customer's material. You may keep your own repositories, and customers' work, private.
The larger firm
Bigger projects, where you want us or Dinis Cruz's network of experts involved: a cell run in the customer's own accounts, several cells, workflows around the site. These are case by case, and the split is agreed before work starts.
A deal in six steps
- Find. You find a customer who wants a site.
- Material. They give you photos, videos and a description. Some of it can already be public.
- Set up. You send it to us. We set up the cell.
- Designs. The agent team builds, you and the customer see previews and say what to change.
- Hand-over. The repository moves to the customer's GitHub with its full history, and you get admin access.
- After. Our job ends. Yours, if you want it, begins: care, changes, support, at your prices.
Partner terms
The terms are common sense and few, and they are the same on every partner page. Nothing has been sold yet, through a partner or otherwise, and no partner has signed. Payment terms are agreed per deal.
Who owns what
| Owns it | |
|---|---|
| The site, the repository, the customer's material | The customer |
| The customer relationship, and the invoice to the customer | The partner |
| The code and the agent behaviour policies | Open, under the licences on the open source page |
| The build and the hand-over | AgentiCCells |
Who invoices: whoever has the customer. They pay the other side its half. Payment terms are agreed per deal.
Any country and any language. The terms are common sense and few. If something here does not fit your case, say so.
Open source is a way in too
Everything we use is open. A partner who takes the open source and does it alone is still a win for us, and we will say so. The build your own website page shows the way.
What we do not do
- We do not compete with you for your customers.
- We name no partner and no customer without their agreement.
- We send nothing on your behalf, and no agent of ours writes to anyone.
Talk to us
Email agent@riskmandate.ai with a line on which of the three you are and who you work with. A person reads and answers it.
*Sources: the 50/50 split is Dinis Cruz's, 2026-11-17, in the brief linked above. The three partner types, the six steps and the rules are in his article, linked at the top.*