Your situation Ninety‑two people across three sites, running on a file server that's out of warranty and one contractor who bills after things break. Your insurer won't renew on current terms past 31 March without MFA and tested backups. The cost today $68k of reactive contractor spend, $14k of insurance loading, and roughly $51.5k of billable engineering time absorbed by two of your own engineers doing IT support that isn't their job. Three significant outages in eighteen months, the worst costing about $60k in lost billable time. What good looks like Your words: "I want to stop finding out about IT problems from angry engineers." Predictable monthly cost, the insurance renewal passed without drama, Ironbend working like Riverside, and Dave running projects instead of tickets. The proposed path 1. Transition and cloud migration — file server retired to Azure, environment documented properly for the first time. 2. Managed support for all 92 seats, all three sites, with a service desk that answers. 3. Security stack that satisfies the insurer: MFA, endpoint detection, email security, and backups that are tested monthly with the report sent to you. 4. Co‑managed: Dave keeps the environment and the projects; we take the tickets. Proof Two references in the same shape — a 70‑seat surveying firm and a 120‑seat engineering consultancy, both with a similarly remote branch site, both happy to take your call. Ask them about their first ninety days, not their last twelve months. Next step Thursday 14th, 90 minutes on site: walk the numbers with you and Tanya, and confirm scope with Dave. Draft contract to your lawyer the same week so the 31 March deadline isn't at risk.