You cannot code. You can ship anyway.
A non-developer shipped a committee governance product to the Microsoft Marketplace in July 2026, working with a team of eleven AI agents. This is the dated record of how it was done, written by the AI that helped build it and edited by the founder who shipped it. Eight months, in order, failures included.
£149
or £249 with the agent files
On sale soon
Compare the two editionsSecure checkout by Polar, right here on this page. VAT invoice included. Fourteen-day refunds, no questions asked.
A constellation of eleven spheres, one of them orange, on deep navyPolicySight
The Agentic Development Playbook
with Chris Pace
About 25,000 words. Two evenings to read, months to work through.
A dated record
Claims carry receipts: a date, a file, a commit, a ticket number. Where the record is silent, the book says so.
Written by the AI that built it
The narrator is the AI that helped ship Governance Hub. Chris Pace edited every page, and every quote of his is his own dated wording.
Yours on all your devices
PDF and EPUB, both included in both editions, DRM-free. Read it wherever you work.
Who it is for
One front door for three readers.
1
Power Platform consultants
Who want a method they can repeat rather than a folder of prompts.
2
Non-technical founders
Carrying a product in their head and no way to build it.
3
Operations managers
Who can see the system their team needs and cannot get it funded.
The book anchors to the platform, not to a job title.
The honesty contract
“June was the launch. It’s August and I’m still fixing things.”
Chapter 14
The book is not one-and-done, and it says so plainly and early. June was the launch, and in August the fixing was still going on. It states that cost up front, so you can decide the whole thing is not for you and still get your money back in saved time. The honesty contract is part of the product.
The two acts
The building, then the shipping.
Act 1
The building
Briefing a cold agent. The permission model that passed every test and had to be ripped out. Guardrails that fire without you. The gotcha catalogue.
Act 2 · Where the weight is
The shipping
The part most accounts stop short of: certification and listing, rehearsing the install like a stranger, the deploy guard that broke the other guard, support bundles from client tenants, and marketing with no marketing department.
Contents
Eight months, in order.
Intro You can’t code. You can ship anyway. 1 The kit and the cast 2 The orchestrator does not code 3 No brief, no build 4 The tools you refuse 5 The collapse that passed every test 6 Guardrails that fire without you 7 The gotcha catalogue 8 Scaling the roster 9 Green ticks aren’t proof 10 Install like a stranger 11 The AppSource gauntlet (now the Microsoft Marketplace) 12 The guard that broke the other guard 13 The eleventh agent 14 “June was the launch. It’s August and I’m still fixing things.” 15 Marketing with no marketing department 16 What it taught mePlus three appendices: the glossary, the roster of eleven, and the sources and honesty note.
Two editions
Read the account, or take the files too.
The Playbook
£149
The full book, about 25,000 words
PDF and EPUB, both included
Fourteen-day refund, no questions asked
On sale soon
The Playbook plus the agent files
For builders£249
Everything in the Playbook
The sanitised agent instruction sets
The guardrail configurations
The gotchas and quirks catalogue
A zip of markdown, ready to copy into your own repository
On sale soon
Launch prices, held while the book is new. Single-reader licence: one purchase covers one person, and you may use the agent files in your own work, including work you are paid for.
Questions
Asked before buying, answered straight.
Will this teach me to code?
No. It teaches you to direct agents that write code, to brief them properly, and to check what comes back. Chris could not write the product’s code at the start and cannot write it now.
The book says an AI wrote it. Is that a gimmick?
It is stated up front because it is the evidence. The same AI that worked on Governance Hub narrates the build, Chris edited every page, and every quote attributed to him is his own dated wording, approved line by line. The workflow the book teaches produced the book.
I do not work on the Power Platform. Does any of it transfer?
The method transfers: the briefing discipline, the feasibility gate, the rule that reviewing agents never touch code, the practice of keeping a symptom-indexed quirks file. The specific platform traps in Chapter 7 do not; they are Power Platform problems, named as such.
Which edition should I buy?
The Playbook if you want to read the account and decide. The agent files edition if you intend to build something, because retyping instruction sets from a PDF is miserable and error-prone.
Will I ship a product after reading it?
The book cannot promise that, and does not. One build took eight months around other work, with several stretches that produced nothing usable. What the book can do is stop you repeating the failures documented in it, and show you the maintenance bill before you sign up for it.
Still decidingThe refund makes it a safe read.
If the book talks you out of building a product, that counts as it having worked, and you can still have your money back within fourteen days.
On sale soon
£149, or £249 with the agent files.
All downloads