Today we announced that Layer27 has been acquired by Katalyst. You can read the formal announcement here, along with a client FAQ and the executive statements.
This post is the other half of that: the practical version, from me, about what actually changes in your day-to-day relationship with us. If you are a Layer27 client, this is the one to read.
The short answer
Nothing about how you are supported changes.
Same engineers. Same phone number. Same email. Same portal. Same agreement, same rates, same invoice. If you called us last Tuesday and you call us next Tuesday, the experience is identical — because it is the same people answering.
I want to lead with that because I have been on the client side of an acquisition before, and the first thing you want to know is whether the team you hired is still the team you have. In this case, they are. Retaining the Layer27 team was not a nice-to-have in this deal. It was the point of it.
Why we did this
I will be direct about the business reasoning, because you deserve better than a press release answer.
Running a high-quality managed services and security practice has gotten more expensive every year. A credible 24/7 security operations center, a deep Microsoft engineering bench, current compliance expertise, vendor relationships that actually carry weight — these have real fixed costs, and those costs do not scale down for a smaller provider. They scale up. Every year the bar for "good enough security" rises, and every year the investment needed to clear it rises with it.
We had two honest options. Stay independent and slowly ration that investment across a growing client base. Or join a platform that already carries those costs at scale and put our team on top of it.
The second option is better for you, and it is not close. It means the engineering depth behind your account grows instead of thinning out. It means our security tooling gets refreshed on someone else's capital plan rather than ours. It means when you need a specialist we do not have on staff, there is one down the hall instead of a subcontractor we have to go find.
Katalyst was the right partner specifically because they are an operating company, not a holding company. They run managed services themselves. They are not buying us to strip and consolidate — they are buying us to expand a Research Triangle presence with a team that already knows how to do the work.
What changes, and when
Here is how the integration will actually be run, so nothing lands on you as a surprise.
Nothing changes in the first phase. Your service delivery, contacts, agreements, and billing continue exactly as they are. There is no migration project waiting behind this announcement.
Back-end systems integrate over the coming weeks. Technology, vendor relationships, and internal tooling move onto Katalyst's platform. That work happens behind the curtain. Where it touches something you would notice — an agent update, a portal change, a monitoring migration — you will hear from us in advance with a specific date and a specific reason.
New capability shows up over the following quarters. Expanded security services, additional automation, more solution options. These arrive as things you can choose to adopt, not as things that get switched on for you.
The rule we are holding ourselves to is simple: you should never learn about a change to your environment from the change itself. If we cannot explain it to you before it happens, we are not ready to do it.
What gets better
Being specific about this matters more than adjectives.
- A deeper engineering bench. More specialists across Microsoft, network, cloud, and security means less "we will get back to you" and more "we have someone who has done this exact thing."
- Expanded security operations. Layer27 already runs 24/7 detection and response. Combining that with Katalyst's security practice adds coverage depth — more analysts, more tooling, more eyes on the same threat landscape.
- Better vendor leverage. Purchasing at platform scale means better licensing and hardware economics, and faster escalation paths into vendor support when something is genuinely broken on their end.
- A real answer on AI. Building an AI-powered MSP platform is explicitly what e4n and Katalyst are doing, and that work lands on our side as governed AI adoption — identity, data boundaries, and monitoring decided before the tooling shows up, not after. Most of you are already being asked about AI internally. We would rather help you answer that deliberately than watch it arrive through a shadow-IT signup.
- Continuity risk goes down. This is the unglamorous one, and for a lot of you it is the most important. A small provider is one key-person departure away from a bad quarter. A platform is not. Your IT partner just got structurally more durable.
What stays the same on purpose
Some of what makes Layer27 work is not something scale improves — it is something scale usually breaks. So we are naming it explicitly.
The 3.5-minute average response time stays. The habit of explaining things in plain language instead of hiding behind acronyms stays. Your named account contacts stay. My direct involvement in critical escalations stays.
If any of that starts slipping, I want to hear about it from you, loudly and early. That is a fair thing to hold us to.
Common questions
I have answered the most frequent ones in the FAQ on the announcement page — contracts, rates, data, billing, support paths. A few that come up in conversation rather than in writing:
"Is my account going to get handed to someone junior?" No. Account assignments are not changing.
"Are you leaving?" No. I am staying with the business and continuing to run critical escalations and key accounts personally.
"Should I be looking at alternatives?" That is always your call, and I would not insult you by pretending otherwise. But I would ask you to judge us on the next two quarters of service rather than on the word "acquisition." The measurable things — response time, ticket quality, incident handling, project delivery — are the same measurements we have always asked to be judged on.
Talk to us
If you have a question this does not answer, do not sit on it. Call 919-825-0312, email connect@layer27.com, or reach out to your account contact directly. If it is something you would rather raise with me, ask for me by name.
We built this business on being straight with people. That does not change today.
— Brad Pierce, CEO, Layer27