# Agentic Organisation Foundry — complete guide Revenue Puzzles · The Agentic Organisation Bookshelf · working framework v0.1 Read the organisation as a library of intent, rules, decisions, knowledge and capabilities. Give people and agents the right books, clear ownership and explicit authority to act. Each book is a starting specification. Supply your organisation's approved content, actual owner and permitted actions. Source: https://revenuepuzzles.com/playbooks/agentic-organisation/ ## 01 — Founding Why do we exist, and what value should this organization create? How agents use this shelf: Use founding intent to interpret goals. Founding changes stay with accountable leadership. ### Purpose The enduring reason the organization deserves to exist. Suggested first artifact: `A one-page purpose statement.` Owner: ______ | Approved version: ______ | Review date: ______ ### Mission & vision What we do today, for whom, and the future we are trying to create. Suggested first artifact: `A mission statement and a concrete future-state narrative.` Owner: ______ | Approved version: ______ | Review date: ______ ### Customer promise The outcome customers should reliably receive and the experience we commit to. Suggested first artifact: `A customer promise with explicit boundaries.` Owner: ______ | Approved version: ______ | Review date: ______ ### Business model How value is created, delivered, and captured; who pays and why. Suggested first artifact: `A business model map with revenue and cost drivers.` Owner: ______ | Approved version: ______ | Review date: ______ ### Values & identity The principles that guide trade-offs and define the organization's character. Suggested first artifact: `Values illustrated with real decision examples.` Owner: ______ | Approved version: ______ | Review date: ______ ### Stakeholders Whose interests matter, who is accountable, and which commitments shape the organization. Suggested first artifact: `A stakeholder and commitment map.` Owner: ______ | Approved version: ______ | Review date: ______ ## 02 — Governance Who may decide what, within which boundaries? How agents use this shelf: Translate rules into permissions, approval gates, and enforceable limits. Instructions alone do not enforce authority. ### Decision rights Which decisions belong to owners, leaders, teams, or agents, and who is accountable. Suggested first artifact: `A decision-rights matrix.` Owner: ______ | Approved version: ______ | Review date: ______ ### Codes of conduct Expected behavior toward customers, colleagues, partners, and other stakeholders. Suggested first artifact: `A code of conduct with concrete examples.` Owner: ______ | Approved version: ______ | Review date: ______ ### Autonomy boundaries Where an agent may observe, recommend, draft, act with approval, or act independently. Suggested first artifact: `An authority matrix by action, scope, and risk.` Owner: ______ | Approved version: ______ | Review date: ______ ### Approvals & escalation When work must pause, who resolves exceptions, and how humans can intervene. Suggested first artifact: `An approval and escalation map with stop conditions.` Owner: ______ | Approved version: ______ | Review date: ______ ### Risk & assurance How risks, privacy obligations, policy conflicts, and incidents are reviewed. Suggested first artifact: `A control register with owners and evidence requirements.` Owner: ______ | Approved version: ______ | Review date: ______ ### Procurement rules Vendor selection criteria, purchasing authority, spending limits, and exceptions. Suggested first artifact: `A procurement and spending policy.` Owner: ______ | Approved version: ______ | Review date: ______ ## 03 — Strategy Where will we compete, and how will we allocate scarce resources? How agents use this shelf: Plan and recommend within approved strategic choices and budgets; route changes to the relevant decision owner. ### Markets & positioning The customers, problems, markets, and alternatives we choose to compete around. Suggested first artifact: `An ideal customer and positioning brief.` Owner: ______ | Approved version: ______ | Review date: ______ ### Strategic bets The few choices and assumptions expected to produce an advantage. Suggested first artifact: `A strategy memo with bets, exclusions, and assumptions.` Owner: ______ | Approved version: ______ | Review date: ______ ### Goals & outcomes The results to achieve, their definitions, targets, and time horizons. Suggested first artifact: `An outcome tree and metric contracts.` Owner: ______ | Approved version: ______ | Review date: ______ ### Financial strategy Revenue logic, unit economics, capital allocation, runway assumptions, and financial constraints. Suggested first artifact: `A financial model with explicit assumptions and limits.` Owner: ______ | Approved version: ______ | Review date: ______ ### Portfolio & roadmaps How initiatives are sequenced, funded, compared, stopped, or expanded. Suggested first artifact: `A prioritized portfolio and outcome-based roadmap.` Owner: ______ | Approved version: ______ | Review date: ______ ### Sourcing & partners Which capabilities to build, buy, partner for, or keep under direct control. Suggested first artifact: `A build-buy-partner decision map.` Owner: ______ | Approved version: ______ | Review date: ______ ## 04 — Management Who owns outcomes, and how is the organization coordinated? How agents use this shelf: Assign explicit human accountability and bounded agent mandates. Review outcomes, capacity, cost, and exceptions. ### Org & capability map Departments, teams, capabilities, and the relationships between human and agent contributors. Suggested first artifact: `An organization map connected to a capability map.` Owner: ______ | Approved version: ______ | Review date: ______ ### Roles & mandates The purpose, responsibilities, authority, and limits of each human or agent role. Suggested first artifact: `Role charters covering inputs, outputs, and authority.` Owner: ______ | Approved version: ______ | Review date: ______ ### Outcome ownership One accountable owner for an outcome, process, metric, system, or agent. Suggested first artifact: `An ownership register with escalation contacts.` Owner: ______ | Approved version: ______ | Review date: ______ ### Cadences & planning The recurring cycles for planning, allocation, review, coordination, and improvement. Suggested first artifact: `An operating calendar with required inputs and decisions.` Owner: ______ | Approved version: ______ | Review date: ______ ### Reporting & monitoring Which business results, operational signals, agent behaviors, and exceptions are reviewed by whom. Suggested first artifact: `A management scorecard with alert and action thresholds.` Owner: ______ | Approved version: ______ | Review date: ______ ### Capacity & dependencies Available people, agent capacity, operating budgets, bottlenecks, and inter-team dependencies. Suggested first artifact: `A capacity and dependency board.` Owner: ______ | Approved version: ______ | Review date: ______ ## 05 — Execution How does work move from a request to an accepted result? How agents use this shelf: Work through explicit triggers, inputs, permitted actions, acceptance criteria, and escalation paths. ### Value streams The complete journeys that deliver value: acquire-to-renew, hire-to-onboard, or procure-to-pay. Suggested first artifact: `A value-stream map with customer and business outcomes.` Owner: ______ | Approved version: ______ | Review date: ______ ### Processes & SOPs Repeatable steps for sales, service, finance, procurement, people operations, and other functions. Suggested first artifact: `A process card with trigger, owner, steps, and outputs.` Owner: ______ | Approved version: ______ | Review date: ______ ### Playbooks & workflows Guidance for variable situations and executable flows for repeatable work. Suggested first artifact: `A playbook linked to its corresponding workflow.` Owner: ______ | Approved version: ______ | Review date: ______ ### Handoffs & promises What another team or agent receives, in what format, by when, and with which acceptance rules. Suggested first artifact: `A handoff contract covering inputs, outputs, and service levels.` Owner: ______ | Approved version: ______ | Review date: ______ ### Quality & acceptance How a deliverable is checked and who or what can accept it as complete. Suggested first artifact: `A definition of done and a quality checklist.` Owner: ______ | Approved version: ______ | Review date: ______ ### Exceptions & recovery What happens when data is missing, a tool fails, policy blocks action, or a result must be reversed. Suggested first artifact: `An exception runbook with retry, rollback, and escalation rules.` Owner: ______ | Approved version: ______ | Review date: ______ ## 06 — Knowledge & memory What do we know, what is trusted, and what must be remembered? How agents use this shelf: Retrieve the relevant approved context with provenance and access controls. Separate evidence, assumptions, and instructions. ### Shared definitions The common meaning of customers, stages, revenue, success, risk, and other business terms. Suggested first artifact: `A glossary and versioned metric dictionary.` Owner: ______ | Approved version: ______ | Review date: ______ ### Trusted facts Which records and sources are authoritative, how current they are, and who maintains them. Suggested first artifact: `A source-of-truth register and freshness rules.` Owner: ______ | Approved version: ______ | Review date: ______ ### Domain context The product, market, customer, and operating context needed to interpret a task. Suggested first artifact: `Curated domain briefs linked to approved policies.` Owner: ______ | Approved version: ______ | Review date: ______ ### Decision memory What was decided, by whom, based on which evidence, and what could trigger reconsideration. Suggested first artifact: `A decision log with rationale and review conditions.` Owner: ______ | Approved version: ______ | Review date: ______ ### Evidence & provenance The traceable link from a claim or output to the records and sources supporting it. Suggested first artifact: `An evidence catalogue with source and timestamp fields.` Owner: ______ | Approved version: ______ | Review date: ______ ### Knowledge lifecycle How context is approved, versioned, scoped, refreshed, archived, and removed. Suggested first artifact: `A knowledge lifecycle policy and content ownership map.` Owner: ______ | Approved version: ______ | Review date: ______ ## 07 — Agent capabilities How do agents reason, act, get evaluated, and improve? How agents use this shelf: Bind capabilities to role authority and approved tools. Evaluate proposed changes before expanding autonomy or releasing updates. ### Skills & instructions Reusable procedures, task instructions, and tool-use patterns for particular kinds of work. Suggested first artifact: `A versioned skill catalogue with prerequisites and limits.` Owner: ______ | Approved version: ______ | Review date: ______ ### Planning & coordination How tasks are decomposed, assigned, checkpointed, and coordinated within a mandate. Suggested first artifact: `A planning and coordination specification.` Owner: ______ | Approved version: ______ | Review date: ______ ### Model selection Which model or reasoning approach is suitable for a task's quality, cost, and latency needs. Suggested first artifact: `A model selection policy with fallback rules.` Owner: ______ | Approved version: ______ | Review date: ______ ### Evaluations How quality, policy adherence, tool behavior, and business usefulness are checked. Suggested first artifact: `Representative evaluation cases and release thresholds.` Owner: ______ | Approved version: ______ | Review date: ______ ### Feedback & learning How results, corrections, and failures become proposed improvements with evidence. Suggested first artifact: `A feedback log and controlled improvement loop.` Owner: ______ | Approved version: ______ | Review date: ______ ### Agent lifecycle How an agent is registered, configured, released, monitored, paused, rolled back, and retired. Suggested first artifact: `An agent registry linked to owners and release records.` Owner: ______ | Approved version: ______ | Review date: ______ ## 08 — Integration & systems How do business applications, agents, and data connect? How agents use this shelf: Expose typed, authorized interfaces. Reconcile system changes and design repeated actions to avoid duplicate effects. ### Business applications CRM, finance, support, HR, and other systems that hold records or perform business operations. Suggested first artifact: `A system catalogue with owners and authoritative records.` Owner: ______ | Approved version: ______ | Review date: ______ ### Tools & connectors The approved capabilities agents can call, their effects, and their required permissions. Suggested first artifact: `A tool catalogue with input, output, and permission contracts.` Owner: ______ | Approved version: ______ | Review date: ______ ### APIs & endpoints The interfaces through which systems read, write, or trigger actions. Suggested first artifact: `An interface register with ownership and versioning.` Owner: ______ | Approved version: ______ | Review date: ______ ### Events & data contracts The meaning and structure of events and data passed between systems. Suggested first artifact: `Versioned event schemas and data contracts.` Owner: ______ | Approved version: ______ | Review date: ______ ### Identity & record mapping How the same customer, company, user, or object is recognized across systems. Suggested first artifact: `A canonical identifier and field mapping specification.` Owner: ______ | Approved version: ______ | Review date: ______ ### Sync & reconciliation How changes propagate, conflicts are resolved, and systems converge after failure. Suggested first artifact: `A sync policy with reconciliation and duplicate-prevention rules.` Owner: ______ | Approved version: ______ | Review date: ______ ## 09 — Infrastructure Where does everything run, persist, and receive technical protection? How agents use this shelf: Enforce scoped access, budgets, isolation, recovery, and operational visibility in the runtime itself. ### Compute & runtimes The environments that execute software and agents, including scheduled and long-running work. Suggested first artifact: `A runtime map with capacity and environment boundaries.` Owner: ______ | Approved version: ______ | Review date: ______ ### Storage & indexes Where records, documents, files, logs, and retrieval indexes physically persist. Suggested first artifact: `A storage map with retention and access classifications.` Owner: ______ | Approved version: ______ | Review date: ______ ### Identity & access The service identities, authentication, authorization, and least-privilege access behind actions. Suggested first artifact: `An access model linking roles to actual permissions.` Owner: ______ | Approved version: ______ | Review date: ______ ### Secrets & network How credentials, connectivity, isolation, and endpoint access are managed. Suggested first artifact: `A secrets and network boundary map.` Owner: ______ | Approved version: ______ | Review date: ______ ### Telemetry & costs The technical logs, traces, runtime metrics, usage limits, and cost signals operators need. Suggested first artifact: `An observability and cost-control configuration.` Owner: ______ | Approved version: ______ | Review date: ______ ### Backups & recovery How data and service are restored, incidents contained, and recovery validated. Suggested first artifact: `A tested backup and recovery runbook.` Owner: ______ | Approved version: ______ | Review date: ______