Previously – https://blog.ciaops.com/2026/08/01/the-recurring-problem-a-managed-services-story-chapter-7/

Denise Okafor called again in October, fourteen months after she’d left. Meridian Health IT, the healthcare specialist she’d switched to, had been acquired by a larger regional platform in the interim, and the transition had gone badly: her dedicated account team had been reassigned twice in five months, her monthly reporting had become generic boilerplate, and a recent phishing-simulation failure across two of her nine locations had gone unaddressed for three weeks.

“I saw your new compliance offering mentioned by another practice administrator at a conference,” she said, sounding almost embarrassed to be making the call. “I didn’t expect Bridgepoint to have become the thing I left Bridgepoint looking for.”

The proposal Jordan walked her through six weeks later bore almost no resemblance to the flat monthly bundle Lakeside had once had. It included a named security lead who would sit in on Lakeside’s own compliance committee meetings quarterly; documented incident-response procedures with contractual response-time guarantees, backed, for the first time in Bridgepoint’s history, by a real penalty clause; and an AI usage policy specifically written for a healthcare practice where several physicians had already started experimenting with AI transcription tools without anyone’s approval.

“What changed?” Denise asked Dave directly, at the contract signing.

“We stopped assuming that showing up mattered more than showing up for the right thing,” Dave said. “For a long time, I thought the job was being available. It turns out the job is knowing, better than the client does, what they’re actually going to need protection from next. We had to become the kind of company that could tell you that, instead of the kind that just answered the phone quickly after something already went wrong.”

Lakeside signed a three-year contract at a rate 34 percent higher than its original agreement. Denise didn’t blink.

Previously – https://blog.ciaops.com/2026/07/31/the-recurring-problem-a-managed-services-story-chapter-6/

The transformation that followed took the better part of eighteen months, and it was messier and slower than any tidy retelling makes it sound. Priya led it, with a whiteboard in her office that eventually filled an entire wall.

The first and hardest change was financial. Bridgepoint stopped selling hourly project work as its default and began requiring every new client, and every renewing one, to move onto a tiered managed-services contract with a three-year term — not because Priya loved locking clients in, but because Renata’s numbers had made the logic unavoidable: longer, deeper contracts weren’t just more predictable, they were worth measurably more, and clients who wouldn’t commit to a real partnership usually weren’t clients worth keeping anyway. It cost Bridgepoint two accounts that flatly refused the new terms. It gained the company, within a year, a recurring-revenue base that had climbed from 46 percent to 71 percent of total revenue, on its way toward the 85-percent target Priya had written at the top of the whiteboard and circled twice.

The second change was strategic focus. Rather than continuing to be everything to everyone, Bridgepoint made a deliberate bet on two verticals where it already had real experience: healthcare and light manufacturing. It hired a part-time compliance consultant with a HIPAA background, built a documented incident-response playbook mapped explicitly to healthcare regulatory requirements, and began marketing itself, for the first time in its history, as something other than a friendly generalist. The pitch decks stopped saying “we support any business” and started saying “we understand what a HIPAA auditor is going to ask you, because we’ve already answered it forty times.” Pricing for the healthcare tier came in meaningfully higher than the old flat rate — clients paid it without much argument, because for the first time, the price reflected expertise they could see, not just hours they were trusting someone to bill honestly.

The third change was the one Tom Baptiste’s plant-manager scare had made unavoidable: Bridgepoint built an actual AI governance offering, something that hadn’t existed anywhere in its service catalog eighteen months earlier. It started small — a one-time “AI readiness assessment” that inventoried every AI tool a client’s employees were already using, sanctioned or not, and flagged where sensitive data might be leaking to public tools nobody in leadership had approved. It grew into an ongoing service: written AI usage policies tailored to each client, ongoing monitoring for unsanctioned tool use, and, for the healthcare and finance clients who needed it, documentation aligned with emerging frameworks their own auditors were starting to ask about. It was Aisha’s idea, developed with a compliance consultant Priya brought in, and it became, within a year, one of the highest-margin services Bridgepoint had ever sold — not because it required expensive infrastructure, but because it required exactly the kind of judgment Jordan and his fellow senior technicians actually had, applied to a problem clients didn’t know how to solve themselves.

“We spent eight years being the people who fixed what broke,” Priya said, at the leadership offsite where she presented the first full year of results. “We’re spending the next eight being the people who tell clients what’s about to break, and what they’re not allowed to plug into their network without asking us first. That’s a completely different business. It just happens to be run by the same people.”

Previously – https://blog.ciaops.com/2026/07/30/the-recurring-problem-a-managed-services-story-chapter-5/

Dave called Aisha into his office the following Monday, alone, no leadership meeting audience. “Tell me honestly,” he said. “If we actually did this — really did it, not a five-hundred-ticket trial license — what would it take, and what would break?”

Aisha, to her credit, didn’t gloat. She pulled up a proposal she’d apparently been quietly refining for months on the assumption nobody would ever ask to see it. A tiered rollout: automated triage and resolution for the top eight ticket categories that accounted for nearly sixty percent of volume; predictive monitoring that could flag failing hardware and unusual network behavior before clients ever noticed a problem, instead of after; and, critically, a real security escalation path with automated paging, not a shared inbox and a prayer.

“What would it take?” she said. “Budget, about $140,000 in tooling and integration over the first year. What would break — that’s the harder question. Not the technology. The technology works; I’ve been running the proof of concept for months and the failure rate on auto-resolved tickets is under two percent, and every one of those gets caught and escalated to a human, not silently dropped. What breaks is the team, if we don’t handle this right. Jordan thinks this is about replacing him. It isn’t. But if we don’t say that out loud, clearly, more than once, he’s going to be right to be angry, because nobody will have told him otherwise.”

Dave took that seriously enough to have the conversation with Jordan directly, which was, in its own way, harder than the conversation with Renata Cole had been. They sat in the break room after hours, two coffees going cold.

“I’m not going to pretend some of this doesn’t automate work you currently do,” Dave said. “It does. Password resets. Basic troubleshooting. The stuff that’s been eating your week. What I need from you isn’t to compete with it. It’s the thing it can’t do — sit with Tom Baptiste and tell him honestly what his plant manager’s AI habit is going to cost him if nobody manages it, or walk into a room with a healthcare compliance officer and speak their language because you’ve done it for eleven years. I can’t automate the part where clients trust you. I can only automate the part where they don’t need to wait nineteen hours for a password reset while they’re deciding whether they still do.”

Jordan didn’t answer right away. “So my job changes,” he finally said. “From doing the work to explaining the work.”

“Your job changes from being the guy who shows up,” Dave said, “to being the guy clients call before they know they have a problem. That’s a better job than the one you have now. It’s just not the one you were trained to think you were signing up for.”

It wasn’t a clean resolution. Jordan stayed skeptical for months, and two of Bridgepoint’s other senior technicians left over the following year — one retired early, one took a role at a competitor that hadn’t changed anything and, as far as anyone could tell, was quietly struggling because of it. But Jordan stayed, and by the following spring he had become, somewhat to his own surprise, the person clients most wanted running their onboarding calls for the company’s new security offering, because he was the one person in the building who could explain, in plain language and without a sales pitch, exactly why it mattered.