# AI Agent Blueprint

## Docs

- [Agent Components: The Building Blocks of an SOP-Driven Agent](https://docs.m9tz.de/agent-structure/components.md): Learn the five building blocks of every agent we design — role definition, input sources, SOP logic, escalation rules, and outbound interfaces — and how each shapes what your agent does.
- [CRM integration](https://docs.m9tz.de/agent-structure/crm-integration.md): How the M9TZ Agent Blueprint treats CRM data as its own bounded domain — and how department agents access only the slice of customer data they are authorised for.
- [ERP and legacy system integration](https://docs.m9tz.de/agent-structure/erp-legacy-systems.md): How department agents connect to your ERP or other established back-office systems through a stable adapter interface — without coupling your agent to any one product.
- [Integrations](https://docs.m9tz.de/agent-structure/integrations.md): How department agents connect to the systems around them — the adapter pattern that keeps agents stable as the tools behind them change.
- [Agent Structure: How an Agent Is Put Together](https://docs.m9tz.de/agent-structure/overview.md): Understand the building blocks of an M9TZ agent — what it's made of, how its parts relate, and where to go deeper on each one.
- [Agent Workflows: How an Agent Executes an SOP](https://docs.m9tz.de/agent-structure/workflows.md): Understand what an agent workflow is, how we document and approve it before building, and what it takes to update one after your agent goes live.
- [Build Phase: How We Construct and Test Your AI Agent](https://docs.m9tz.de/blueprint/build.md): Understand what our team builds during the agent build phase, what we need from you, how staging works, and what can affect your timeline and scope.
- [Deploy Phase: Moving Your AI Agent Into Live Operations](https://docs.m9tz.de/blueprint/deploy.md): Learn how go-live works, what the pre-deploy checklist covers, how the first week of monitoring runs, and what your 14-day hypercare period includes.
- [Design Phase: From Discovery to an Approved Agent Blueprint](https://docs.m9tz.de/blueprint/design.md): Learn what the Agent Design Document contains, how the collaborative review process works, and which decisions only you can make before build begins.
- [Discovery Phase: Map Your Business Before Building an Agent](https://docs.m9tz.de/blueprint/discovery.md): Learn what happens during the Discovery workshop, what to prepare before it, and what you receive when it wraps up — before any design work begins.
- [Handoff Phase: Own and Operate Your Agent After Launch](https://docs.m9tz.de/blueprint/handoff.md): Learn what you receive at handoff, how team training is structured, what ongoing support options are available, and how to request changes after launch.
- [How a Consulting Engagement Proceeds](https://docs.m9tz.de/consulting/engagement-model.md): A conceptual overview of how an M9TZ Agent Blueprint consulting engagement is structured — from initial conversation through implementation and handoff.
- [Frequently Asked Questions](https://docs.m9tz.de/consulting/faq.md): Answers to common questions about the M9TZ Agent Blueprint — what is free, what is paid, how scope works, and how to get started with a consulting engagement.
- [Engagement & Pricing Model](https://docs.m9tz.de/consulting/pricing.md): How consulting engagements are scoped and priced — individually, based on effort, with no fixed packages or published rates.
- [Scope & Boundaries: What Is Documented vs. What Is Consulting](https://docs.m9tz.de/consulting/scope-and-boundaries.md): A transparent explanation of what this documentation covers freely, what requires a consulting engagement, and how the two relate.
- [How Engagement Scope Is Determined](https://docs.m9tz.de/consulting/scoping.md): What goes into determining the scope of an M9TZ Agent Blueprint consulting engagement — departments, complexity, existing systems, and integration needs.
- [Introduction to the M9TZ Agent Blueprint](https://docs.m9tz.de/introduction.md): An overview of the M9TZ Agent Blueprint: a reusable architecture for department-based, SOP-driven AI agents with staged rollout and structured inter-department messaging.
- [Customer-Facing Department Playbook](https://docs.m9tz.de/playbooks/customer-support.md): See how the agent blueprint applies to a customer-facing department — role definition, SOPs, input sources, escalation rules, and outbound interfaces.
- [Sales / Pipeline Department Playbook](https://docs.m9tz.de/playbooks/lead-generation.md): See how the agent blueprint applies to a sales or pipeline department — role definition, SOPs, qualification logic, outbound interfaces, and escalation rules.
- [Back-Office / Accounting Department Playbook](https://docs.m9tz.de/playbooks/operations.md): See how the agent blueprint applies to a back-office or accounting department — role definition, SOPs, input events, approval routing, and audit trail interfaces.
- [Operations / Logistics Department Playbook](https://docs.m9tz.de/playbooks/scheduling.md): See how the agent blueprint applies to an operations or logistics department — role definition, SOPs, threshold monitoring, inter-department messaging, and escalation rules.
- [Quickstart: Your first department agent](https://docs.m9tz.de/quickstart.md): Start with one department, one VM, and one set of SOPs. This page walks through the first practical step in building a department-based agent infrastructure.
- [What is an agent?](https://docs.m9tz.de/what-is-an-agent.md): How the M9TZ Agent Blueprint defines an agent: a process-bound, SOP-driven software service scoped to one department or business function.