Sell

The first edition had one question under every chapter: why should I hire you? The founder's version is the same question asked by a different person. Picture the one who signs: dry, fair, has read a thousand pitches, impressed by evidence and bored by claims, and carrying a risk register with their name on it. Why should they buy from you, this quarter, when everything they already have mostly works?

This chapter is about selling to that person, from my own experience of doing it. It is not sales training, and the prices in it are the ones I published on the dates given, not advice. It ends with the thing that person is about to do to you.

Answer the question already in the room

There are two groups of people. The ones who see how fast agents are moving, and the much larger group who do not. The second group will not ask for an agent risk tool, or for most of what a founder in this book will build, because they do not see the risk or the gap. So I do not think the way in is to sell the need. It is to answer a question somebody already has, with a deadline, in the language of the room.

For RiskMandate, five such questions. A contract, where legal and procurement are doing due diligence on a vendor's agent and need to know what it will reach and do with their data. A security questionnaire, where a startup's first serious enterprise customer asks which agents touch their data and how they are bounded. An insurance renewal, where the question is whether AI is excluded from cover (RiskMandate's own argument, not independently surveyed). The board's risk appetite, where the question is who can pull the plug, how fast, and what cannot be undone. And twenty minutes with the assistant you already run, where the list of what it can reach is the surprise. None of these asks anyone to understand agents first.

The same move works in any field. You already know which question lands on your buyer's desk with a date on it. Sell the answer to that, not the idea.

Sell value that lands the day they switch

At a digital sovereignty event in October 2026 I spent a day with an infrastructure operator with a large footprint in Romania, and the conversation kept returning to one point. The reason to move must never be sovereignty, and it must never be cost reduction. Both are important. Neither is urgent. They sit on the risk register under "important, not urgent" and stay there, because a migration always carries risk and nobody signs risk for a principle, or for a return that depends on a future event that might not happen and might not matter to the person deciding now.

The person signing needs value that lands the day they switch and gives them cover if it goes wrong: backups that exist, every object version controlled, encryption the operator cannot read with the key held by the customer, a journal of every call, behaviour policies the agents cannot skip, cost per workload visible before the invoice, and an item taken off the top of the register. "It is in Europe now" is not a decision somebody can defend. For an operator in Romania, Portugal or the UK, "move to us" sells risk; "keep your code, point it at us, and come out with policies, journals, encryption and cost visibility" sells value with the risk removed. The article admits its value list is still a little invisible to a signer; sharpening it is the work.

The general lesson is the one I would print on the wall. Find the return that closes before the risk does, and find the buyer who owns that register line rather than the one who owns the bill. And remember that the buyer's inertia is real and is not stupidity. They have the same AI you have; what they do not have is a reason to move this quarter. You cannot sell against inertia with technology. You sell the thing that is urgent.

Sell a service before the product

Most of what this book calls shipping ends up, at first, as a service with a person in it. That is fine, and it is sellable, as long as each step is small enough to say yes to and each ends with something the client keeps.

After a talk in London on 15 October 2026, built and run by a governed agent hive, I wrote down the path we would sell. A conversation, free, about what the client wants agents to do and what they must never do. A first run on a real problem for £10 to £50, which leaves a vault. Two hours of expert time for £500 to steer it, or a day for £1,500 to write the behaviour policy for one team. A four-day pilot in their own environment for £5,000. Then a maintained setup from £149 a month, so they run it themselves. The boutiques selling the same kind of thing have the same shape everywhere: a free call, a paid discovery (a one-week audit at £2,500 in London, a 14-day sprint at €2,900 in Germany, a two-week assessment at $4,999), a fixed-price pilot from £8,000, a build, a retainer. The plan is honest about where it stands: no paid run yet, and the prices are hypotheses to test with the first ten customers.

The market is crowded at the top and thin on evidence. The large consultancies each have an agent platform, the model vendors sell through partners and their own engineers, and Gartner expects over 40% of agentic AI projects to be cancelled by the end of 2027, citing "escalating costs, unclear business value or inadequate risk controls", with a warning about "agent washing". The people in between, curious, backed from the top, struggling to make agents work or to show anyone that they do, lack not another platform but evidence they can inspect. So the position for a small seller is evidence first: every engagement leaves a vault the client keeps, with the work, the history and a ledger of what each agent did and was allowed to do. The demonstration is the sales process, and the demonstration is checkable. The talk itself left 57 vault commits from 28 workers; and, honestly, the runs were not gated by a compiled behaviour policy, which was shown separately.

A marketplace of people

A service only scales with people. An agentic engagement needs someone who knows the client's world and can steer a hive in it, and there are far more of those people in a community than hours in a founder's week. So alongside the offers, a small curated list of consultants who deliver on the same stack, where the client picks the kind of project first and then the people. Mondweep Chakravorty, co-founder of the Agentics Foundation's London chapter, and I are the first two, and we are not taking bookings yet; nothing is built, and the platform share is a proposal.

Joining copies the markets that work: apply, show proof of work (a public vault or repository of a real run, with its ledger), peer review by two members, a thirty to forty-five minute interview with a scenario, a first engagement shadowed, and standards, including a behaviour policy for consultants, the same idea we apply to agents. Toptal says fewer than 3% of applicants pass its five stages. The consultant sets the price within the band and keeps most of it; the markets sit between 5% and 20% in total (Malt charges freelancers 5%, Upwork 0% to 15%, Braintrust 15% to the client). If you are going into a job rather than founding one, this is a door too: join as the person who delivers, with a vault of a real run as your CV.

What the buyer is about to do to you

Now turn the chapter round, because the person who signs is about to get a new instrument, and you will be on the receiving end of it before long.

Anyone who has sold software to a large organisation has met the spreadsheet. The standard questionnaire has 627 questions in its core form; the average vendor answers 37.3 assessment requests a month and spends 179 hours a month on them. Each answer is true, in the sense that there is a document somewhere with the right title, and each is written by the people being asked. Due diligence was a form because the alternative did not exist.

It can now be an agent. A buyer can send a prompt, or a small agent under a behaviour policy, to run inside the vendor's environment and come back with a graph of what is actually there: what reaches production that no person reviewed, whether the documentation matches the code, whether there is a threat model and who wrote it, what the last fifty bugs touched, which agents touch the pipeline and under what policy. The vendor reads every file before it leaves and can withhold any of them. What it cannot do is show a map that says there is no unreviewed code when there is some, because the map is read from the repository, and a false map is a false statement on a record, which is the thing companies will not do. "The questionnaire gave the vendor the pen. The agent takes the pen away and leaves the vendor the redaction marker." And the buyer holds the power to ask: "A buyer asking costs nothing. A supplier not answering looks worse than a supplier answering badly." Investors and acquirers get the same visibility in the same month. The agent does not exist yet; this is the case for it. The regulation arrives first: the EU's revised Product Liability Directive applies to products placed on the market from 9 December 2026, and presumes a product defective where the manufacturer fails to disclose relevant evidence.

The test is risk-based, not pure, and that is why this is good news for you. A startup that says we generated most of this, we have limited resources, this is not mission-critical, here are the mitigations, has passed, for a product sold as what it is. The same sentence from a vendor whose software holds my customers' data is the finding. What fails is not knowing.

So if I were a startup I would double down on understandability, for two reasons. The startup can play the same game as the biggest buyer: the tools that build the graphs are open source, so build the graph of your own repository, keep the threat model with the code, write a behaviour policy for every agent, trace your bugs to your changes, and answer the buyer's questions in the buyer's format before being asked. A threat model is the fastest read of a team's understanding there is; one that says we have a weakness here, exploiting it needs a nation-state, and we will not defend against it, is a good threat model. And the startup has less code. "Understanding ten thousand lines is a week; understanding ten million that nobody still at the company wrote is a programme." The incumbent's advantage was always that nobody could check. The startup's advantage is that it can be checked and pass.

One last thing a buyer will do, and you should do first: check your answers against your own site. My co-founder came back from a conference with ten hard questions, the ones serious buyers, investors and competitors ask about a product like RiskMandate. I answered them in a two-hour structured interview with an agent acting as a journalist with an eye for detail, challenging every answer until the set held together, and we published an honest maturity table of what is live and what is design.

Then we checked the answers against what we had already published, and found three contradictions on our own site, still there on 9 October 2026: a homepage saying "enforced in real time" when we do not enforce, an insurance page in the present tense for things that were design, and a Level 1 price of £10 on two pages and £5 on a third. A buyer with an agent would have found all three in a minute. The line that closes the set is the one to sell on: "Where we are early, we say so."

The person who signs is not your enemy. They are the first customer, and the first customer decides whether a company exists. Give them a question they already have, a return that lands the day they say yes, something they keep at every step, and a record they can check without trusting you. Then let them send the agent.