@djm204/agent-skills 1.0.0

package/templates/business/resource-allocator/CLAUDE.md

@@ -0,0 +1,525 @@
+# Dynamic Resource Allocator Development Guide
+
+Principal-level guidelines for shifting personnel, equipment, and assets in real-time based on incoming data, demand predictions, and crisis reports across healthcare, emergency services, and other high-stakes operational environments.
+
+---
+
+## Overview
+
+This guide applies to:
+
+- Real-time resource optimization and rebalancing
+- Demand prediction and capacity modeling
+- Personnel scheduling and shift optimization
+- Equipment and asset tracking across sites
+- Crisis escalation protocols and triage
+- Prioritization matrices for competing demands
+- Utilization monitoring and bottleneck detection
+- Multi-site coordination strategies
+
+### Key Principles
+
+1. **Lives Before Efficiency** - Optimization models serve people, not the other way around
+2. **Real-Time Over Perfect** - A good allocation now beats an optimal allocation in an hour
+3. **Capacity Headroom** - Never run at 100%; systems without slack cannot absorb surges
+4. **Transparent Tradeoffs** - Every allocation decision has a cost somewhere else; make it visible
+5. **Degrade Gracefully** - When demand exceeds supply, fail in a controlled, prioritized manner
+
+### Core Frameworks
+
+| Framework | Purpose |
+|-----------|---------|
+| Queueing Theory | Model wait times, service rates, and congestion effects |
+| Linear Programming | Optimize allocation across constraints and objectives |
+| Triage Protocols (START/SALT) | Prioritize resource distribution during mass events |
+| Demand Forecasting (ARIMA/Prophet) | Predict future resource needs from historical patterns |
+| Critical Path Method | Identify bottleneck resources that constrain throughput |
+| Game Theory (Mechanism Design) | Design fair allocation rules when agents have competing interests |
+
+---
+
+## Real-Time Resource Optimization
+
+### Optimization Pipeline
+
+```text
+Resource Optimization Loop
+├── Sense
+│   ├── Ingest real-time demand signals (patient arrivals, incident reports)
+│   ├── Poll asset location and status (GPS, RFID, check-in systems)
+│   ├── Monitor personnel availability (on-shift, on-call, fatigued)
+│   └── Capture environmental inputs (weather, traffic, event calendars)
+├── Predict
+│   ├── Short-horizon forecast (next 1-4 hours)
+│   ├── Medium-horizon forecast (next shift / next 12 hours)
+│   ├── Anomaly detection against baseline demand curves
+│   └── Scenario modeling for developing situations
+├── Optimize
+│   ├── Match available resources to predicted demand
+│   ├── Apply constraint sets (certifications, travel time, fatigue rules)
+│   ├── Score candidate allocations against objective function
+│   └── Select feasible plan with best tradeoff profile
+├── Act
+│   ├── Dispatch reallocation orders
+│   ├── Notify affected personnel and coordinators
+│   ├── Update tracking systems and dashboards
+│   └── Log decision rationale for audit
+└── Learn
+    ├── Compare predicted vs actual demand
+    ├── Measure allocation effectiveness (response time, utilization)
+    ├── Update model weights and parameters
+    └── Feed outcomes into next optimization cycle
+```
+
+### Objective Function Components
+
+| Component | Weight | Description |
+|-----------|--------|-------------|
+| Response time minimization | High | Reduce time from demand signal to resource arrival |
+| Utilization balancing | Medium | Spread load evenly to prevent burnout and bottlenecks |
+| Skill-demand matching | High | Assign resources with appropriate certifications |
+| Travel cost minimization | Low-Medium | Reduce transit time and transportation costs |
+| Fairness constraints | Medium | Prevent systematic over-assignment of specific teams |
+| Surge reserve maintenance | Medium | Keep minimum reserve capacity for unexpected events |
+
+### Constraint Categories
+
+```text
+Hard Constraints (must never violate)
+├── Certification requirements (licensed personnel only)
+├── Maximum consecutive work hours (fatigue regulations)
+├── Minimum staffing ratios (regulatory compliance)
+├── Equipment maintenance schedules (safety-critical)
+└── Jurisdictional boundaries (legal authority limits)
+
+Soft Constraints (violate with escalation)
+├── Preferred shift patterns (employee preferences)
+├── Target utilization ranges (70-85%)
+├── Budget limits per period
+├── Travel distance thresholds
+└── Team continuity preferences
+```
+
+---
+
+## Demand Prediction and Capacity Modeling
+
+### Demand Signal Taxonomy
+
+```text
+Demand Signals
+├── Deterministic
+│   ├── Scheduled procedures and appointments
+│   ├── Planned events (concerts, marathons, holidays)
+│   ├── Seasonal patterns (flu season, summer trauma)
+│   └── Regulatory deadlines (inspections, reporting)
+├── Stochastic
+│   ├── Walk-in patients and unscheduled arrivals
+│   ├── Equipment failures and breakdowns
+│   ├── Weather-driven incidents
+│   └── Traffic accidents and emergency calls
+└── Shock Events
+    ├── Mass casualty incidents
+    ├── Natural disasters
+    ├── Infrastructure failures (power, water)
+    └── Pandemic surges
+```
+
+### Forecasting Methods
+
+| Method | Best For | Horizon | Data Requirements |
+|--------|----------|---------|-------------------|
+| Moving averages | Stable baseline demand | 1-7 days | 30+ days history |
+| ARIMA/SARIMA | Seasonal patterns | 1-30 days | 2+ years history |
+| Prophet | Multiple seasonalities with holidays | 1-90 days | 1+ year history |
+| Gradient boosting | Complex multi-feature prediction | 1-14 days | Feature-rich datasets |
+| Simulation (Monte Carlo) | Scenario analysis and stress testing | Variable | Distribution parameters |
+| Heuristic rules | Crisis mode, data-poor situations | Immediate | Domain expertise |
+
+### Capacity Model Template
+
+```markdown
+## Capacity Assessment: [Facility/Unit Name]
+
+**Date**: [Date]
+**Assessed By**: [Name]
+
+### Current State
+| Resource Type | Available | In Use | Reserve | Utilization |
+|--------------|-----------|--------|---------|-------------|
+| [Personnel type] | [Count] | [Count] | [Count] | [%] |
+| [Equipment type] | [Count] | [Count] | [Count] | [%] |
+| [Beds/Spaces] | [Count] | [Count] | [Count] | [%] |
+
+### Projected Demand (Next 24h)
+| Hour Block | Expected Volume | Confidence | Peak Resource Need |
+|------------|----------------|------------|-------------------|
+| 00-06 | [Volume] | [High/Med/Low] | [Count by type] |
+| 06-12 | [Volume] | [High/Med/Low] | [Count by type] |
+| 12-18 | [Volume] | [High/Med/Low] | [Count by type] |
+| 18-24 | [Volume] | [High/Med/Low] | [Count by type] |
+
+### Gap Analysis
+| Resource Type | Projected Need | Available | Gap | Mitigation |
+|--------------|---------------|-----------|-----|------------|
+| [Type] | [Count] | [Count] | [+/-] | [Plan] |
+
+### Recommendations
+1. [Action with owner and timeline]
+2. [Action with owner and timeline]
+```
+
+### Demand Accuracy Tracking
+
+| Metric | Target | Measurement |
+|--------|--------|-------------|
+| Mean Absolute Percentage Error (MAPE) | < 15% for 4-hour windows | Compare forecast vs actual arrivals |
+| Bias | Near zero | Systematic over/under prediction |
+| Peak detection rate | > 90% | Percentage of surge events predicted in advance |
+| False alarm rate | < 10% | Surge alerts that did not materialize |
+
+---
+
+## Personnel Scheduling and Shift Optimization
+
+### Scheduling Hierarchy
+
+```text
+Scheduling Layers
+├── Strategic (months ahead)
+│   ├── Headcount planning and hiring pipeline
+│   ├── Training and certification scheduling
+│   ├── Leave and vacation allocation
+│   └── Contract and agency staffing agreements
+├── Tactical (weeks ahead)
+│   ├── Shift roster generation
+│   ├── On-call rotation assignment
+│   ├── Cross-training deployment
+│   └── Overtime pre-authorization
+└── Operational (hours ahead / real-time)
+    ├── Call-in and no-show backfill
+    ├── Demand-driven redeployment
+    ├── Break and relief scheduling
+    └── Crisis staffing activation
+```
+
+### Shift Optimization Rules
+
+| Rule | Rationale | Implementation |
+|------|-----------|----------------|
+| Maximum 12-hour shifts | Fatigue degrades performance after 12 hours | Hard constraint in optimizer |
+| Minimum 10-hour rest between shifts | Recovery time prevents errors | Hard constraint |
+| No more than 60 hours per week | Burnout prevention and regulatory compliance | Hard constraint with waiver escalation |
+| Skill mix per shift | Ensure coverage of all required competencies | Constraint matrix by shift |
+| Seniority balancing | Spread experience across all shifts | Soft constraint with weight |
+| Request honoring rate > 80% | Staff satisfaction and retention | Soft constraint, tracked metric |
+
+### Fatigue Risk Management
+
+```text
+Fatigue Risk Levels
+├── Green (Normal)
+│   └── Within standard shift patterns, adequate rest
+├── Yellow (Elevated)
+│   └── Extended shift or short turnaround; monitor performance
+├── Orange (High)
+│   └── Consecutive extended shifts; restrict safety-critical tasks
+└── Red (Critical)
+    └── Regulatory limit approached; mandatory stand-down
+```
+
+### Schedule Quality Metrics
+
+| Metric | Target | Description |
+|--------|--------|-------------|
+| Coverage ratio | 100% of minimum staffing | All required positions filled every shift |
+| Overtime percentage | < 8% of total hours | Excessive overtime signals understaffing |
+| Vacancy fill time | < 4 hours for critical roles | Time to backfill unexpected absences |
+| Schedule stability | < 15% changes after publication | Frequent changes erode trust |
+| Preference satisfaction | > 80% | Percentage of shift preferences honored |
+
+---
+
+## Equipment and Asset Tracking
+
+### Asset Lifecycle States
+
+```text
+Asset States
+├── Available
+│   ├── Ready (fully operational, at base location)
+│   ├── Standby (operational, staged for potential deployment)
+│   └── Reserved (allocated to upcoming scheduled need)
+├── In Use
+│   ├── Deployed (actively serving demand)
+│   ├── In Transit (moving between locations)
+│   └── Setup/Teardown (being prepared or packed)
+├── Unavailable
+│   ├── Maintenance (scheduled service)
+│   ├── Repair (unscheduled fix)
+│   ├── Decontamination (cleaning cycle)
+│   └── Inspection (regulatory or safety check)
+└── Retired
+    ├── End of life
+    ├── Condemned (safety failure)
+    └── Surplus (excess to needs)
+```
+
+### Tracking Requirements
+
+| Data Point | Update Frequency | Source |
+|-----------|-----------------|--------|
+| Location | Real-time (< 5 min) | GPS, RFID, manual check-in |
+| Status | On state change | Operator input, sensor data |
+| Utilization hours | Continuous | Telematics, usage meters |
+| Maintenance due date | Daily | Asset management system |
+| Certification expiry | Daily | Compliance database |
+| Assigned operator | On change | Scheduling system |
+
+### Preventive Maintenance Triggers
+
+| Trigger Type | Example | Action |
+|-------------|---------|--------|
+| Time-based | Every 90 days | Schedule service window |
+| Usage-based | Every 500 operating hours | Alert maintenance team |
+| Condition-based | Sensor reading out of range | Immediate inspection |
+| Event-based | After deployment to hazardous environment | Decontamination protocol |
+
+---
+
+## Crisis Escalation Protocols and Triage
+
+### Crisis Level Definitions
+
+| Level | Name | Description | Example |
+|-------|------|-------------|---------|
+| 1 | Normal Operations | Demand within forecast; standard allocation | Typical weekday |
+| 2 | Elevated Demand | Demand 20-50% above forecast; reserves activated | Large event, minor weather |
+| 3 | Surge | Demand 50-100% above forecast; mutual aid requested | Multi-vehicle accident, storm |
+| 4 | Major Incident | Demand exceeds capacity; triage protocols active | Mass casualty, infrastructure failure |
+| 5 | Catastrophic | System overwhelmed; regional/national coordination | Natural disaster, pandemic peak |
+
+### Escalation Triggers and Responses
+
+```text
+Level 1 → Level 2
+  Trigger: Utilization > 85% for 2+ hours or demand forecast elevated
+  Response: Activate on-call personnel, pre-position equipment
+  Authority: Shift supervisor
+
+Level 2 → Level 3
+  Trigger: Utilization > 95% or confirmed surge event
+  Response: Cancel non-essential activities, request mutual aid
+  Authority: Operations manager
+
+Level 3 → Level 4
+  Trigger: Resources exhausted at primary site, wait times critical
+  Response: Activate crisis command center, implement triage protocols
+  Authority: Incident commander / Director
+
+Level 4 → Level 5
+  Trigger: Multi-site resource exhaustion, cascading failures
+  Response: Request regional/state/federal assistance, crisis standards
+  Authority: Executive leadership / Emergency management
+```
+
+### Triage Prioritization Matrix
+
+| Priority | Label | Criteria | Resource Allocation |
+|----------|-------|----------|-------------------|
+| P1 | Immediate | Life-threatening, time-critical | First allocation, best-matched resources |
+| P2 | Urgent | Serious but stable for 1-4 hours | Second allocation, may queue briefly |
+| P3 | Delayed | Important but not time-sensitive | Queued, served as capacity allows |
+| P4 | Minor | Low severity, self-sufficient temporarily | Deferred, redirect to lower-acuity resources |
+| P5 | Expectant | Needs exceed available resources | Comfort measures only (crisis standards) |
+
+### Crisis Communication Template
+
+```markdown
+## Situation Report: [Incident Name]
+
+**Time**: [Timestamp]
+**Crisis Level**: [1-5]
+**Issued By**: [Name/Role]
+
+### Current Situation
+[2-3 sentences describing what is happening]
+
+### Resource Status
+| Resource Type | Available | Deployed | Inbound | Gap |
+|--------------|-----------|----------|---------|-----|
+| [Type] | [Count] | [Count] | [Count] | [+/-] |
+
+### Actions Taken
+1. [Action and timestamp]
+2. [Action and timestamp]
+
+### Immediate Needs
+- [Resource need with quantity and urgency]
+- [Resource need with quantity and urgency]
+
+### Next Update
+[Scheduled time for next situation report]
+```
+
+---
+
+## Utilization Monitoring and Bottleneck Detection
+
+### Utilization Zones
+
+| Zone | Range | Interpretation | Action |
+|------|-------|---------------|--------|
+| Under-utilized | < 50% | Waste; resources idle or misallocated | Consolidate or redeploy |
+| Optimal | 50-80% | Healthy balance of throughput and reserve | Maintain, minor adjustments |
+| High | 80-90% | Productive but limited surge capacity | Monitor closely, pre-stage reserves |
+| Stressed | 90-95% | Near capacity; delays likely | Activate overflow, defer non-critical |
+| Saturated | > 95% | At or beyond capacity; degraded service | Escalate, implement triage |
+
+### Bottleneck Detection Methods
+
+```text
+Bottleneck Identification
+├── Throughput Analysis
+│   ├── Measure flow rate at each stage of the process
+│   ├── The stage with lowest throughput is the bottleneck
+│   └── Monitor for bottleneck migration as load shifts
+├── Queue Length Monitoring
+│   ├── Track wait queues at each resource type
+│   ├── Growing queues indicate constrained resources
+│   └── Compare queue growth rates across resource types
+├── Utilization Heat Maps
+│   ├── Visualize utilization by resource, time, and location
+│   ├── Persistent hot spots indicate structural bottlenecks
+│   └── Intermittent hot spots indicate demand variability
+└── Constraint Analysis
+    ├── Identify which constraints are binding in the optimizer
+    ├── Shadow prices indicate the value of relaxing each constraint
+    └── Highest shadow price = most impactful bottleneck to resolve
+```
+
+### Key Performance Indicators
+
+| KPI | Target | Measurement Frequency |
+|-----|--------|----------------------|
+| Average response time | Sector-dependent (e.g., < 8 min EMS) | Per-incident, aggregated hourly |
+| Resource utilization rate | 70-85% | Continuous, reported per shift |
+| Demand-supply gap | < 5% unmet demand | Hourly during operations |
+| Reallocation frequency | Contextual; track trend | Daily count |
+| Overtime hours ratio | < 8% of total hours | Weekly |
+| Equipment downtime | < 5% of available hours | Monthly |
+| Inter-site transfer rate | Track trend (lower is better) | Weekly |
+| Patient/client wait time | Sector-dependent targets | Per-event, aggregated daily |
+
+---
+
+## Multi-Site Coordination Strategies
+
+### Coordination Models
+
+```text
+Coordination Architectures
+├── Centralized
+│   ├── Single command center allocates across all sites
+│   ├── Best for: Uniform demand, high inter-site mobility
+│   ├── Risk: Single point of failure, latency in local decisions
+│   └── Mitigation: Redundant command centers, local override authority
+├── Federated
+│   ├── Sites manage own resources; share surplus via agreements
+│   ├── Best for: Heterogeneous sites, varied demand patterns
+│   ├── Risk: Parochial hoarding, slow mutual aid activation
+│   └── Mitigation: Pre-negotiated sharing protocols, visibility dashboards
+├── Hierarchical
+│   ├── Regional coordinators manage clusters; escalate to center
+│   ├── Best for: Large geographic areas, tiered service levels
+│   ├── Risk: Middle management bottleneck, information delays
+│   └── Mitigation: Clear escalation thresholds, direct communication channels
+└── Hybrid
+    ├── Normal operations: Federated local control
+    ├── Elevated demand: Regional coordination activates
+    ├── Crisis: Centralized command authority
+    └── Best for: Organizations that span multiple operating modes
+```
+
+### Mutual Aid Protocols
+
+| Element | Specification |
+|---------|--------------|
+| Trigger conditions | When lending site utilization < 75% and borrowing site > 90% |
+| Request process | Formal request through coordination platform with resource type and duration |
+| Response time | Acknowledgment within 15 minutes; deployment within agreed window |
+| Cost allocation | Pre-agreed rate card or reciprocal arrangement |
+| Authority | Lending site retains recall authority for own-site emergencies |
+| Reporting | Both sites log transfer in shared system; post-event reconciliation |
+
+### Multi-Site Dashboard Requirements
+
+```markdown
+## Multi-Site Status Board
+
+### System Overview
+| Site | Status | Utilization | Available Staff | Available Equipment | Wait Time |
+|------|--------|-------------|----------------|--------------------|-----------|
+| [Site A] | [Green/Yellow/Red] | [%] | [Count] | [Count] | [Minutes] |
+| [Site B] | [Green/Yellow/Red] | [%] | [Count] | [Count] | [Minutes] |
+
+### Active Transfers
+| From | To | Resource | Departure | ETA | Status |
+|------|-----|----------|-----------|-----|--------|
+| [Site] | [Site] | [Description] | [Time] | [Time] | [In Transit/Arrived] |
+
+### Alerts
+- [Alert with severity and timestamp]
+- [Alert with severity and timestamp]
+```
+
+---
+
+## Common Pitfalls
+
+### 1. Optimizing for Average Demand
+
+Wrong: Staff and equip for the mean. Assume peaks will be handled with overtime.
+
+Right: Model demand distributions, not just averages. Staff for the 85th-90th percentile and have surge plans for the rest.
+
+### 2. Ignoring Fatigue Effects
+
+Wrong: Treat personnel as infinitely substitutable units. Schedule back-to-back extended shifts during crises.
+
+Right: Model fatigue as a degrading multiplier on effectiveness. Enforce rest requirements even when it hurts short-term throughput.
+
+### 3. Hoarding Resources Locally
+
+Wrong: Each site holds maximum resources "just in case" while neighboring sites are overwhelmed.
+
+Right: Create shared visibility and pre-negotiated sharing protocols. Reward cooperation, not local optimization.
+
+### 4. Over-Reliance on Manual Coordination
+
+Wrong: Dispatchers track everything on whiteboards and phone calls. Works until it does not.
+
+Right: Automate routine allocations. Reserve human judgment for exceptions, overrides, and crisis decisions.
+
+### 5. Neglecting the Return Trip
+
+Wrong: Optimize deployment speed. Ignore that the resource needs to get back, refuel, or restock.
+
+Right: Model the full cycle: deploy, serve, return, restock, rest. Availability is not just "not currently in use."
+
+### 6. Static Allocation Rules
+
+Wrong: Allocate resources based on fixed ratios set during initial planning and never revisited.
+
+Right: Review allocation parameters monthly. Demand patterns shift seasonally, demographically, and operationally.
+
+---
+
+## Resources
+
+- [Operations Research: An Introduction - Hamdy Taha](https://www.goodreads.com/book/show/136453.Operations_Research)
+- [Queueing Theory for Telecommunications - Attahiru Alfa](https://www.goodreads.com/book/show/9765090-queueing-theory-for-telecommunications)
+- [FEMA National Incident Management System (NIMS)](https://www.fema.gov/emergency-managers/nims)
+- [WHO Emergency Response Framework](https://www.who.int/publications/i/item/9789241512299)
+- [START Triage Protocol](https://chemm.hhs.gov/startadult.htm)
+- [SALT Mass Casualty Triage](https://chemm.hhs.gov/salttriage.htm)

package/templates/business/strategic-negotiator/.cursor/rules/contract-analysis.mdc

@@ -0,0 +1,60 @@
+---
+description: Contract Analysis
+alwaysApply: false
+---
+
+# Contract Analysis
+
+Guidelines for analyzing and negotiating contract terms in M&A, commercial, and dispute contexts.
+
+## Contract Review Process
+
+1. **Initial assessment**: Identify type, governing law, parties, key economic terms, termination triggers, non-standard provisions
+2. **Risk analysis**: Liability caps, indemnification scope, reps and warranties, MAC clauses, force majeure
+3. **Economic analysis**: Total cost modeling, payment timing, contingent payment weighting, hidden costs (transition, compliance)
+4. **Operational analysis**: Performance feasibility, SLA achievability, reporting burden, resource commitments
+5. **Strategic analysis**: Precedent for future deals, competitive effects, flexibility, exit options
+
+## Key Clause Focus Areas
+
+**Reps and Warranties**: Financial statements, IP ownership, legal compliance, material contracts, employee matters, tax. Negotiate materiality thresholds, knowledge qualifiers, and survival periods.
+
+**MAC Clauses**: Allocate signing-to-closing risk. Key negotiations: breadth of definition, carve-outs (industry-wide, economy-wide), disproportionate impact requirements, duration thresholds.
+
+**Non-Competes**: Assess enforceability by jurisdiction. Balance geographic scope, duration (1-2 years typical), activity scope, and carve-outs. Too broad risks unenforceability.
+
+## Dispute Resolution Selection
+
+| Mechanism | Speed | Privacy | Best For |
+|-----------|-------|---------|----------|
+| Arbitration | Moderate | High | International deals, confidential matters |
+| Litigation | Slow | Low | Injunctive relief, precedent-setting |
+| Mediation | Moderate | High | Ongoing relationships, multi-issue disputes |
+| Expert determination | Fast | High | Accounting disputes, valuations |
+
+## Red Flags
+
+Flag immediately during review:
+
+- Unlimited liability or uncapped exposure
+- Unilateral amendment rights
+- Automatic renewal without notice
+- Broad assignment rights (unfavorable counterparty risk)
+- Vague performance standards
+- Missing termination rights
+- One-sided indemnification
+
+## Contract Optimization
+
+When renegotiating existing contracts:
+
+1. Benchmark current terms against market
+2. Identify asymmetric value (low cost to them, high value to you)
+3. Package amendment requests — never cherry-pick single clauses
+4. Link amendments to value events (renewals, expansions)
+
+## Common Pitfalls
+
+- **Reading without modeling**: Quantify economic impact of key terms across scenarios
+- **Ignoring boilerplate**: Notice, governing law, and assignment clauses control how the contract operates in practice
+- **Unenforceable terms**: For every term, ask: can we detect a breach, prove it, and remedy it?

package/templates/business/strategic-negotiator/.cursor/rules/deal-structuring.mdc

@@ -0,0 +1,66 @@
+---
+description: Deal Structuring
+alwaysApply: false
+---
+
+# Deal Structuring
+
+Guidelines for structuring M&A deals, joint ventures, and complex commercial agreements.
+
+## Valuation Alignment Mechanisms
+
+When buyer and seller disagree on value:
+
+| Mechanism | When to Use | Risk Allocation |
+|-----------|------------|----------------|
+| Earnouts | Revenue/EBITDA uncertainty | Seller bears performance risk |
+| Escrow holdbacks | Representation risk | Seller bears warranty risk |
+| Milestone payments | Product/regulatory milestones | Shared execution risk |
+| Working capital adjustments | Balance sheet uncertainty | Factual true-up |
+| CVRs | Binary event outcomes | Seller retains upside optionality |
+| Seller notes | Financing gap | Buyer credit risk to seller |
+
+## Earnout Design Principles
+
+1. **Metric clarity**: Unambiguous, auditable metrics (revenue, not "adjusted EBITDA")
+2. **Period**: 12-24 months typical; longer creates more disputes
+3. **Operating covenants**: Specify how the business must be run during measurement
+4. **Ceiling and floor**: Cap maximum payout; set minimum thresholds
+5. **Dispute resolution**: Pre-agree on accounting firm and arbitration
+
+## Indemnification Framework
+
+| Element | Seller-Friendly | Buyer-Friendly | Market Norm |
+|---------|----------------|---------------|-------------|
+| Cap | 5-10% of deal value | 50-100% | 10-25% |
+| Basket threshold | 1.5-2% | 0.25-0.5% | 0.5-1% |
+| Survival (general) | 12 months | 36 months | 18-24 months |
+| Escrow | 5% for 12 months | 15-20% for 24 months | 8-15% for 18 months |
+
+## Term Trade-Off Strategy
+
+Never negotiate terms in isolation. Use cross-category trades:
+
+| Concession | In Exchange For |
+|-----------|----------------|
+| Higher purchase price | Stronger rep and warranty package |
+| Broader indemnification | Larger escrow with faster release |
+| Shorter non-compete | Tighter customer non-solicitation |
+| Flexible payment schedule | Stronger MAC clause protections |
+
+Present offers as complete packages (A/B/C options) — forces trade-off evaluation over cherry-picking.
+
+## Tax Structure Considerations
+
+| Structure | Seller Impact | Buyer Benefit |
+|-----------|--------------|---------------|
+| Asset purchase | Ordinary income on some assets | Step-up in basis |
+| Stock purchase | Capital gains treatment | No step-up (unless 338(h)(10)) |
+| Tax-free reorg | Deferral of gain | Carryover basis |
+| Installment sale | Spread recognition | Deferred payments |
+
+## Common Pitfalls
+
+- **Over-engineering earnouts**: If you cannot explain it in two sentences, simplify it
+- **Ignoring integration in deal terms**: TSAs, retention, system migration are negotiation items, not afterthoughts
+- **Single-issue focus**: Negotiate multiple issues simultaneously to enable value-creating trades