{"ok":true,"engine":"aicost.msp-technician-capacity","inputs":{"ticketsPerMonth":550,"ahtMinutes":35,"escalationPct":18,"projectHoursPerMonth":90,"acctMgmtHoursPerMonth":50,"technicians":5,"productiveHoursPerTechMonth":117,"targetUtilizationPct":80,"aiDeflectionPct":0,"monthlyDemandGrowthPct":1.5,"loadedTechMonthlyUsd":9800},"result":{"demandHoursPerMonth":519,"capacityHoursPerMonth":468,"utilizationPct":88.6,"fteGap":0.54,"monthsToCapacityWall":0,"hireCostPerMonthUsd":9800,"decision":"AUTOMATE FIRST, THEN HIRE","decisionDetail":"You are short 0.5 FTE, but AI deflection at 25% of routine tickets would return ~95 hrs/mo — run the AI Automation ROI calculator on triage before signing an offer letter.","verdict":"CAPACITY SHORTFALL","verdictReason":"519 demand hrs/mo vs 468 sustainable capacity (5 techs × 117 productive hrs × 80% target) — running at 89% raw utilization.","memo":"Sustainable capacity reserves headroom on purpose: the gap to 100% is what absorbs escalations, incidents, training, and turnover. Ticket demand is net of AI deflection; hire-vs-automate compares loaded hire cost against automation ROI (cross-link).","questions":["Which ticket categories drive the volume — and are the top three automatable or eliminable at the source?","Is after-hours coverage inside these hours or a separate rotation?","What is the real recruiting lead time for your market? Start that clock, not the burnout clock."],"assumptions":["117 productive hrs/tech/month ≈ 1,400/yr ÷ 12 (PTO, training, meetings removed).","Never plan to 100% utilization — 75-85% is the sustainable band*."]}}