{"ok":true,"engine":"aicost.msp-contract-repricing","inputs":{"currentMrrUsd":5400,"originalUsers":40,"currentUsers":46,"originalVendorCostPerUserUsd":12,"currentVendorCostPerUserUsd":15,"wageInflationPct":8,"originalTicketsPerUser":1,"currentTicketsPerUser":1.25,"laborShareOfCostPct":65,"originalMarginPct":48,"escalationClausePct":3,"monthsSinceSigning":24},"result":{"pricePerUserNowUsd":117.39,"costPerUserNowUsd":94.1,"marginNowPct":19.8,"marginErosionPts":28.2,"recommendedMrrUsd":8324,"recommendedPerUserUsd":180.96,"requiredIncreasePct":54.2,"userGrowthPct":15,"decision":"REPRICE NOW","decisionDetail":"Margin eroded 28 points since signing — a 54% correction is overdue. Lead the conversation with the client's growth (6 users added), not your costs.","verdict":"MARGIN ERODED","verdictReason":"Signed at ~48% margin; today this agreement runs 20% after 6 added users, vendor cost +$3/user, and 16% cumulative wage drift.","memo":"Cost rebuild: labor scaled by wage inflation and ticket-intensity change; vendor delta passed through; recommended price restores the as-signed margin via cost ÷ (1 − margin). Frame the renewal around business change — added users, added scope — never \"our costs increased.\"","questions":["Which of the added users landed in scope creep vs a signed change order?","Does the agreement bill on the CURRENT user count automatically? (That alone may close half the gap.)","What did after-hours and project spillover add that never hit the agreement?"],"assumptions":["Labor share of delivery cost and margin-at-signing are estimates* if not from your GL.","The platform computes this per client from PSA + accounting data continuously."]}}