Crown Computers Turned Tribal Knowledge Into Team Capacity — Without Adding Headcount

Introduction

Every MSP has the same quiet problem: the people who know the most are the ones with the least time to write it down. Crown Computers, a San Diego MSP, had strong senior engineers and a service-first culture. What they didn't have was a way to get what those engineers knew into the hands of everyone else — at the moment a ticket was open and the clock was running.

Derek Jeppsen, Crown's Service Manager, spent years trying to solve it the manual way. Then he stopped trying to build documentation and started building a system that builds it for him.

The Challenge

Crown's knowledge was scattered across multiple places at once; SharePoint client folders, Hudu, and PSA ticket notes. None of them worked well under pressure.

"Engineers don't want to go back spelunking through tickets," Derek said. PSA search wasn't built for it. So the real knowledge base became the one place it always becomes — inside the heads of the senior engineers who'd solved the problem before.

That created single points of failure. If the person who knew was out, or slammed, the work stopped.

The cost showed up as a pattern Derek could describe precisely even though nobody was tracking it. A junior tech would work a ticket for 30 to 60 minutes, hit a wall, and escalate. A senior would take it and close it in a few minutes — because the answer was simple, and had always been simple, and had just never been written down anywhere findable.

Three to five of those a week. Three to five hours, minimum, of work that already had an answer.

The obvious workaround made things worse: route those tickets straight to the one person who knows. That deepens the silo and kills the training moment. As Derek put it, all a junior tech needs is to see the problem and the solution — but if they don't arrive together, on time, the learning opportunity is gone.

Crown had tried the manual fix. Ask the engineers what they know, write it all down. It didn't work. Technicians operate on muscle and feel; they can solve a problem expertly without being able to describe the steps. And anything they did write went stale within three to six months, or the moment a project changed a client's setup.

It wasn't that documentation didn't matter. It's that it could never be the highest-value thing on the board when clients needed service right now.

The Solution

Crown initially evaluated other AI tools, but found they were largely designed to automate help desk tasks or displace technicians rather than empower them. Recognizing that his team was the company's greatest asset, Derek sought a human-first solution that addressed the root cause of their challenges.

Derek saw the distinction clearly saying, "We wanted to make sure that we were making institutional knowledge instead of making individual knowledge."

Crown chose HelpGhost — a more stable product, shipping faster, and aimed at the root cause instead of the symptom.

Hero installs as a pod inside the ticket. That placement turned out to matter more than any feature. Senior engineers who don't need help simply don't look at it — their workflow doesn't change at all. Junior engineers get an immediate orientation to the problem and to that specific client's setup, right where they're already working. The learning curve, in Derek's words, was gentle.

Organizational instructions gave Derek managerial control in one or two sentences. His favorite example: users constantly request admin credentials when what they actually want is software installed. So he told Hero to catch it. Now, before a technician has to stop and think about it, Hero flags the request, points to who is actually authorized to approve access changes, and — when a legitimate request does come in — validates it instantly against the documentation.

"It's not a failsafe. It's proactive," Derek said. Instead of reviewing a ticket a day later, after something has gone wrong.

The Hudu integration with HelpGhost solved Derek’s biggest bottleneck. As a manager, he lacked the bandwidth to review every new article — a task that required several hours per week he couldn't spare. By integrating the HelpGhost Scholar directly with Hudu, Crown captured that value without turning the approval process into a roadblock.

Then Crown found a use nobody at HelpGhost had specified. When a ticket gets resolved in a way they want repeated, they simply ask Hero to write the procedure. Hero already has the full ticket context, so it drafts it from time notes the engineers were going to write anyway. One review, one paste into Hudu, and it's a standard.

"That was a revelation for us."

The Impact

The clearest measure of what changed came from two new hires — experienced MSP technicians, not brand new ones.

Derek added HelpGhost Hero to their day-one onboarding, asking them to open a ticket to see the tool in action. The reaction was immediate. One of the new hires remarked that with every technician armed with this level of insight, Crown’s time-to-resolution should be virtually unmatched.

This reaction is consistent. Technicians joining from shops that lack this support immediately realize they're operating at a higher level, often half a tier to a full tier up, simply because they no longer have to manually hunt for answers and hope the documentation is up to date.

For Crown, that's a hiring and retention advantage because new team members see on day one that the company has already invested in helping them succeed, ticket by ticket.

The second shift was strategic. Hero became Crown's quality-control layer for knowledge itself. When Hero can't answer well, that's the signal — the gap is in the knowledge base, not the tool. Instead of trying to document everything, Crown now knows exactly which gaps are worth closing next.

"HelpGhost is showing me some gaps, and it’s a tool that can help me fix it."

That feedback loop compounds. Documentation gets more mature. HelpGhost gets sharper. And because the model brings real depth of its own — Derek points to CVE and vulnerability guidance his team can use despite having limited dedicated security-operations background — Crown only has to document what's genuinely unique to them.

Escalations to management dropped. Engineers stopped being expected to hold every client's preferences, approvers, and exceptions in memory. And Crown's capacity went up without anyone being displace.

The framing Derek provided is what ultimately resonates the most:

"It's not just getting people to solve harder problems. It's taking the load off of them from being responsible for types of information that they probably shouldn't be responsible for. It's... unburdening."

When asked for his advice to an MSP considering HelpGhost — particularly one hesitant because they feel their internal documentation isn't ready — Derek stated, “That's backwards. HelpGhost is the thing that guides you to make the documentation good.”

"That's why I wish we would have done it sooner."