# Domain Packs and the Vertical Playbook ## The intended flywheel: each vertical costs less than the last The company makes **domain packs** for each vertical. Domain packs have a sector knowledge-base and a set of validated agents. The company develops the domain packs with an institute. The institute supplies data, credibility and access to member companies. The logic is that each partnership makes the next vertical cheaper. Only the domain packs change. ```mermaid graph LR A[Shared platform layer] --> B[Domain pack: vertical 1] A --> C[Domain pack: vertical 2] A --> D[Domain pack: vertical N] E[Institute partner] --> B E --> C E --> D B --> F[Validated agents and knowledge base] F -->|playbook| C ``` > [!warning] The sources show only one vertical > A fine-tuned domain model exists for one sector. The other sectors are in the pipeline, in development, or at the agreement step. > > The engagements include approximately ten sub-verticals. Some engagements are generic chatbot work. The team has fewer than ten persons. > > This is **vertical sprawl** and not a playbook at this time. ## What compounds and what does not Customer data does not go into a shared model (see [[Borrowed Data Is Not a Moat]]). The playbook compounds. The playbook has schemas, agent templates, test sets and integration patterns. The playbook is a moat only if the contracts let the company use again what the company builds. > [!tip] Test for a playbook > The test measures the time to launch the *second* customer in a vertical. The test also measures the engineer-days. The test compares the two values with the values of the *first* customer. > The test also shows if the agents of the second customer were configuration or new code. ## Why it matters Verticalization is the right strategy in this market (see [[The Age of Vertical Models]]). But the strategy is right only if the company keeps its focus. The company must give approval for a new vertical only after it measures how much of the previous vertical it uses again. ## Related - [[Foreman MOC]] - [[Platform or Solutions - The Central Question]] - [[Institute Channel and Subsidy Dependence]] - [[Agent Skills as Codified Domain Expertise]] - [[Data Flywheel]]