There was a time when the MSP community actually felt like a community.
People shared ideas because they had discovered something useful. They talked openly about mistakes. They swapped scripts, compared vendors, debated pricing and helped competitors solve problems simply because someone needed a hand.
There was no application process.
No carefully curated cohort.
No commitment to attend four meetings a year.
No requirement to reveal your EBITDA before anyone would tell you how they structured their service desk.
And, most importantly, there wasn’t always someone trying to monetise the conversation.
Then came the peer group.
And I would argue that, despite all the good they have done for individual MSPs, peer groups have slowly helped kill the wider MSP community.
First, let me be clear: peer groups work
This isn’t an argument that MSP peer groups are bad.
Quite the opposite.
For many MSP owners, joining a serious peer group can be one of the most valuable decisions they make.
A good group provides something that is incredibly difficult to find inside your own business: perspective.
You get to sit with people running businesses that look remarkably similar to yours and ask questions such as:
- What are you charging?
- How many endpoints does each technician support?
- What does your gross margin look like?
- How do you compensate salespeople?
- Which vendors are actually working?
- How are you structuring your service desk?
- What would you do differently if you were starting again?
That information is enormously valuable.
The accountability can be even more valuable.
If you tell ten other MSP owners that you are going to fix your pricing before the next meeting, you have created a very different incentive from scribbling “review pricing” on your own to-do list.
Peer groups have helped professionalise the MSP industry.
But there has been a cost.
We put the best conversations behind closed doors
This is the fundamental problem.
As peer groups became more sophisticated, the quality of the private conversation improved while the quality of the public conversation declined.
The interesting discussions moved inside the room.
Someone discovers a brilliant way to restructure their agreements?
Peer group discussion.
Someone has real numbers showing why a particular pricing model doesn’t work?
Peer group discussion.
Someone discovers a major problem with a vendor?
Peer group discussion.
Someone develops a better way of running their service desk?
Peer group discussion.
It makes perfect sense for the people involved.
Why wouldn’t you take your most commercially valuable insights to the people you trust?
But multiply that decision across thousands of MSP owners and something important happens.
Knowledge stops circulating through the industry.
It circulates through tribes.
We replaced community with cohorts
There is an important difference between a peer group and a community.
A peer group says:
These are my people.
A community says:
These are our people.
That distinction matters.
Peer groups necessarily create boundaries. Membership has value partly because not everyone is inside.
The discussions become confidential.
The relationships become deeper.
The trust becomes stronger.
All of those things are individually positive.
Collectively, however, they fragment the industry.
Instead of one large MSP ecosystem, we increasingly have dozens or hundreds of overlapping micro-communities.
People know their peer group extremely well but may barely interact with the MSP down the road.
We have become better connected to our group, while becoming less connected to the industry.
The economics changed too
There is another uncomfortable truth.
Community became a business model.
MSP owners are valuable customers.
They buy technology. They attend conferences. They purchase consulting. They consume training. They influence other MSPs.
That makes an audience of MSP owners commercially valuable.
So naturally an ecosystem developed around helping them.
Consultants.
Coaches.
Vendors.
Events.
Masterminds.
Peer groups.
Communities.
None of that is inherently wrong. People deserve to be paid for creating value.
The problem arises when almost every useful interaction eventually encounters a commercial boundary.
The question subtly changes from:
“How can we help the MSP community?”
to:
“How can we monetise access to the MSP community?”
Those are not the same question.
We also became afraid of giving away the good stuff
Something else happened along the way.
Knowledge became intellectual property.
That spreadsheet could be part of a consulting engagement.
That process could become a course.
That presentation could become conference content.
That pricing model could be reserved for paying members.
That operational insight belongs inside the peer group.
Again, every individual decision is completely rational.
Collectively, however, they create scarcity where previously there was generosity.
Ironically, this happened at exactly the time technology should have made community easier.
We have Teams, LinkedIn, Reddit, Discord, Slack, YouTube, podcasts, webinars and endless ways to communicate.
The MSP industry has never had more communication channels.
Yet sometimes it feels as though we have less genuine conversation.
The newcomers pay the highest price
Established MSP owners may not notice the change.
They already have networks.
They know who to ring.
They belong to private groups.
They see each other at conferences.
But imagine entering the MSP industry today.
Where do you go?
Many of the industry’s best conversations are happening behind doors you don’t yet know exist.
And even if you find the door, there may be a significant price of admission.
That creates a strange ladder:
Build an MSP → become successful enough to join the right group → gain access to the knowledge that helps successful MSPs become more successful.
The people arguably most in need of community can therefore be the people least able to access its best conversations.
Vendors helped accelerate it
Vendors also discovered the power of community.
Build a partner program.
Create a user group.
Sponsor a community.
Host an event.
Fund a peer group.
Create an advisory council.
None of these things are necessarily cynical. Many produce genuine value.
But they also create gravitational fields around vendors.
People who once identified primarily as members of the MSP community increasingly become members of ecosystems.
The Microsoft MSP.
The ConnectWise MSP.
The Kaseya MSP.
The HaloPSA MSP.
The Pax8 MSP.
The Huntress MSP.
Again, those communities can be excellent.
But each additional orbit fragments the broader conversation a little further.
The irony is that MSPs desperately need a wider community
The challenges facing MSPs increasingly extend beyond individual businesses.
Cybersecurity threats don’t care which peer group you belong to.
Artificial intelligence is reshaping services for everyone.
Microsoft platform changes affect thousands of partners simultaneously.
Vendor consolidation affects the entire channel.
Regulation, cyber insurance, privacy obligations, skills shortages and changing customer expectations are industry-wide issues.
These problems require something bigger than a table of twelve MSP owners.
They require a functioning professional community.
And that community needs places where someone can say:
“We learned something important. Here it is. You don’t owe us anything.”
Perhaps peer groups didn’t kill the community
Maybe that headline is unfair.
Peer groups didn’t deliberately kill the MSP community.
They simply solved one of its biggest weaknesses.
They created trusted environments where MSP owners could have conversations that were difficult to have publicly.
The problem is that they solved it too well.
We moved trust inside the walls.
We moved insight inside the walls.
We moved vulnerability inside the walls.
And eventually much of the value moved inside the walls too.
The answer isn’t to dismantle peer groups.
It is to rebuild the commons outside them.
We need to start giving something back
If you belong to an MSP peer group, keep it.
If you have a trusted circle of MSP owners, treasure it.
If you pay for coaching and get value from it, fantastic.
But perhaps every MSP professional should also deliberately contribute something to the wider industry.
Publish the script.
Share the lesson.
Explain the mistake.
Answer the beginner’s question.
Write the blog post.
Record the video.
Challenge the vendor publicly when necessary.
Tell people what worked.
And sometimes, give away the really useful thing rather than saving it for the room.
Because a strong peer group can make twelve MSPs better.
A strong MSP community can make the whole industry better.
We became very good at building the first.
Perhaps it is time we started rebuilding the second.