The Blueprint

By Gareth Price · Last updated

A Field Guide to Building Organisations of People and Agents

Your newest hire never sleeps, never takes a holiday, and will do exactly what you tell it to.

That’s the problem.

Agents have made it cheap to add workers and no easier to build an organisation. Most teams bringing agents in are repeating the oldest mistake in small business: organising around whoever, or whatever, happens to be good at something. One agent quietly does six jobs. One person is the only one who knows how it all fits together. When either goes away, the business stops. Being able to build an agent isn’t the same as being able to build an organisation of them.

The Blueprint is a practical method for designing a company where people and agents share the work: where every role, human or not, has a written outcome, clear standards and one person accountable for it, and where the whole organisation is documented well enough that you could stand it up again tomorrow. It draws on half a century of thinking about systems and organisations, from Deming and Drucker to Grove and Gerber, and rebuilds it for teams where half the org chart runs on a model.

It is written for the leader who already lives in Claude, ChatGPT or Grok, who has seen what an agent can do in an afternoon, and who suspects — correctly — that the window in which small, fast organisations can outrun large, slow ones is open now and will not stay open long.

Table of Contents

Front Matter

Part I: The Shift

Part II: The Destination

Part III: The Org Chart

Part IV: Writing It Down

Part V: Running the Machine

Part VI: Getting Better

Part VII: The Human Side

Appendices

Key Concepts

Frequently Asked Questions

  1. What is The Blueprint about?

    The Blueprint is a field guide for business leaders whose teams now include AI agents. It argues that agent sprawl is an organisation design problem rather than a tooling problem, and shows how to solve it: design an org chart of roles before deciding who or what fills them, write a one-page charter for every role, keep procedures in plain English, track commitments against evidence, give every agent a human sponsor, and turn every recurring failure into a system fix.

  2. Who is The Blueprint written for?

    The primary reader is a founder, executive or operator who has started using AI agents in tools such as Claude, ChatGPT or Grok, sees the leverage they offer, and wants to know how to organise them as their numbers grow. The book assumes no technical background. Technical detail is kept in sidebars and a dedicated appendix for the reader’s engineering team.

  3. Do I need to be technical to use this book?

    No. The method works in the desktop AI apps and team chat tools most leaders already use every day. Each chapter ends its main argument with a short exercise you can do in Claude, ChatGPT or Grok, and implementation detail such as scheduled jobs, enforcement rules and agent protocols is collected in Appendix D for whoever builds your systems.

  4. How is The Blueprint different from other books about AI agents?

    Most writing about agents is about building them. The Blueprint is about organising them alongside people. It draws on decades of thinking about systems and organisations — Gerber, Deming, Drucker, Grove — and tests it against real cases from a working company that runs a mixed team of humans and agents, including the failures, plus current research on how multi-agent systems succeed and fail.

  5. What is Agentic Resources?

    Agentic Resources, a term coined by the book’s author, Gareth Price, is HR for agents: a function on the org chart, run by a person, an agent or both, that owns the agent workforce. It writes job descriptions and role charters, onboards new agents in public, reviews their performance, promotes them to more autonomy, settles turf wars between duplicate bots, hands roles to new models, and retires agents without losing what they knew.