MSP Advice

Building a successful Managed Service Provider is about much more than technical expertise. If you are looking for MSP Advice, you will find the commercial challenges even greater as an MSP grows: winning the right clients, maintaining healthy margins, standardising service delivery, retaining customers, developing your team, and building a business that can scale without depending on its founders.

The most useful MSP advice therefore isn’t about the latest tool, certification, or cybersecurity acronym. It’s about building a strong, profitable service business that consistently delivers value to its clients.

SecuVeo was founded by Luis Navarro following more than 15 years spent building and growing a successful MSP. As co-founder of Totality Services, Luis helped take the business from an idea and a small team to a highly profitable MSP serving more than 150 clients, with operations in London and Johannesburg. The business was ultimately acquired, providing firsthand experience of the entire MSP journey from startup and growth through to exit.

This guide shares practical lessons from that experience, covering MSP growth, profitability, standardization, sales, client relationships, Security Reviews, recurring revenue, and ultimately building a more valuable business.

Key Takeaways

Standardization enables scalability. Supporting a different technology stack and process for every client creates complexity and increases the cost of service delivery. Greater consistency can make an MSP easier to operate and scale.

Think commercially about security. Clients rarely want to buy another security product simply because the technology is impressive. They want to understand the business risk it addresses and why acting matters.

Profit matters more than revenue alone. A large MSP isn’t necessarily a valuable MSP. Recurring revenue, margins, client quality, operational efficiency, and the ability to operate without excessive founder dependency all matter.

Client reviews should create accountability. Security Reviews should help clients understand risks, make informed decisions, and provide a record of recommendations and outcomes.

Learn from other MSPs. Peer groups, coaches, industry communities, and experienced operators can provide perspective that is difficult to gain when you’re immersed in the day-to-day operation of your own business.

The Foundation of Practical MSP Advice

During the early stages of building an MSP, saying “yes” to almost everything can help generate momentum.

You support the technology the client already has. Smaller customers come on board, unusual problems need solving, and the founders get involved in almost everything because that’s what is required to build the business.

But what works at 10 clients can become a major problem at 50 or 100.

Every exception introduces complexity. Supporting additional products requires additional knowledge, while bespoke processes make it harder to train people and deliver a consistent service.

At some point, growth requires structure.

That means defining the type of client you want, standardizing your technology stack, documenting processes, understanding the economics of individual accounts, and creating clear responsibilities throughout the business.

This is where MSP owners increasingly need to think like business leaders rather than simply technology providers.

Understand the Economics of Your MSP

Revenue is important, but revenue without sufficient margin isn’t sustainable growth.

MSP owners should understand metrics such as:

• Monthly Recurring Revenue (MRR)
• Gross margin
• EBITDA
• Cost of Goods Sold (COGS)
• Effective Hourly Rate (EHR)
• Revenue per employee
• Client acquisition cost
• Client retention and churn
• Revenue concentration among major clients

The precise metrics you prioritize will depend on your business model, but the underlying principle is simple:

Know which clients, services, and activities actually make your MSP money.

A client generating significant monthly revenue can still be unattractive if they consume disproportionate support resources.

Likewise, a rapidly growing MSP can find itself under financial pressure if service delivery costs rise as quickly as revenue.

Good growth should improve the business, not simply make it bigger.

Escaping the Owner’s Trap

Many MSPs begin with founders who are deeply involved in service delivery.

That can be a strength initially. Clients receive excellent attention and difficult problems get resolved quickly.

Eventually, however, it can become a constraint.

If every difficult technical problem, important client conversation, sales opportunity, or operational decision requires the founder, the business is limited by that person’s capacity.

Scaling requires transferring knowledge and responsibility into the organization.

Document processes. Create clear escalation paths. Give employees ownership. Develop managers. Automate repetitive activities where appropriate.

The objective isn’t for the founder to become disconnected from the business. It’s to ensure the company doesn’t stop functioning effectively whenever the founder isn’t available.

When MSP Coaching Can Help

There are points in the MSP journey where an experienced outside perspective can be extremely valuable.

MSP coaching can help owners identify operational bottlenecks, improve sales processes, strengthen management structures, analyze financial performance, and establish accountability around strategic objectives.

A good coach shouldn’t tell you how to fix a server. They should help you build a business where the founder doesn’t need to fix it.

The same principle applies to sales, account management, finance, and operations.

The Commercial Side of Cybersecurity

One of the biggest opportunities for modern MSPs is cybersecurity.

It’s also an area where technical businesses frequently struggle to communicate effectively.

A technical team may identify a genuine security weakness and recommend the correct solution. But if the client doesn’t understand the risk, the recommendation can easily become another proposal sitting in an inbox.

Imagine telling a client:

“We recommend implementing MFA because of the risk of credential-based attacks.”

That’s technically reasonable.

But compare it with:

“If an employee’s password is compromised, an additional identity check can help prevent an attacker from using that password to access systems such as email, company files, or financial information.”

The second explanation gives the client context.

The technology hasn’t changed. The communication has.

Translate Technology Into Business Risk

Clients don’t need every technical detail.

They need enough information to make an informed business decision.

A useful security conversation should help them understand:

• What is the risk?
• Why does it matter to their business?
• What are you recommending?
• What could happen if they decide not to proceed?
• What does the recommended improvement cost?

When the client understands those points, the conversation becomes a business decision rather than a technical lecture.

That’s an important distinction.

The role of an MSP isn’t necessarily to make every decision for the client. It’s to provide clear professional recommendations and give the client the information required to make an informed choice.

Make Security Reviews Part of Account Management

Security Reviews shouldn’t be an occasional exercise performed only when something goes wrong.

They can form a structured part of the ongoing relationship between an MSP and its clients.

A good Security Review can achieve three things:

1. Risk Management

Identify gaps in the client’s security posture and explain what they mean.

2. Value Demonstration

Show clients the work being performed and the security controls already protecting their organization.

3. Commercial Opportunity

Identify legitimate improvements that may require additional projects, products, or recurring services.

The third point matters.

Generating additional revenue from a Security Review isn’t about manufacturing problems or frightening clients into purchasing unnecessary technology.

It’s about identifying genuine risks, clearly communicating them, and allowing the client to decide whether to address them.

Done properly, that’s good for the client and good for the MSP.

Create Accountability Around Security Decisions

There’s another benefit to structured Security Reviews: accountability.

If an MSP recommends an important security improvement and the client declines it, that decision should be recorded.

The objective isn’t to create an adversarial relationship. It’s to make sure both parties understand what was recommended and what was decided.

A clear history of recommendations and client decisions can also make future reviews considerably more useful.

Instead of starting again every quarter or year, the MSP can show:

• What was identified previously
• What the client approved
• What was declined
• What has subsequently changed
• How the client’s overall security posture has improved

This is one of the principles behind SecuVeo. Security Reviews become more useful when they’re structured, understandable, repeatable, and tied to clear client decisions.

Standardization Is a Major Driver of MSP Scalability

Profitability can disappear quickly when an MSP supports highly inconsistent client environments.

One client has one firewall vendor. Another uses something completely different. A third has an aging server that nobody wants to replace. Another insists on retaining a security product your technicians rarely use.

Every exception has a cost.

Technicians require more knowledge. Troubleshooting takes longer. Documentation becomes more complicated. Automation becomes harder. Procurement becomes fragmented.

Standardization helps reduce that complexity.

Define Your Preferred Technology Stack

A growing MSP should know what a well-configured client environment looks like.

That doesn’t necessarily mean forcing every customer into an identical configuration regardless of their requirements.

It means establishing preferred technologies and standards wherever practical.

For example:

• Endpoint protection
• Endpoint Detection and Response
• Backup
• Email security
• Identity protection
• DNS or web filtering
• Microsoft 365 configuration
• Networking
• Monitoring and management
• Documentation

The more consistently your team works with the same technologies, the more expertise it can develop around them.

That can lead to faster resolution, better automation, more effective training, and lower service-delivery costs.

Know When to Say No

One of the hardest transitions for a growing MSP is learning that not every prospect is a good prospect.

A potential client who refuses to address major technical debt, won’t adopt reasonable standards, constantly negotiates on price, and expects unlimited flexibility may generate revenue while simultaneously damaging profitability and employee morale.

Growth becomes much easier when you understand your ideal client profile.

Sometimes the commercially correct answer is no.

Learn From Other MSP Owners

Running an MSP can be surprisingly isolating.

Your employees don’t necessarily see the financial and strategic pressures of ownership. Your clients certainly don’t. And your friends outside the industry may have little understanding of the challenges involved.

This is why peer groups and MSP communities can be valuable.

Peer Advisory Groups

A strong peer advisory group gives MSP owners an opportunity to compare their businesses with organizations facing similar challenges.

Useful discussions can include:

• Financial benchmarking
• Compensation structures
• Sales performance
• Technology stacks
• Vendor experiences
• Employee retention
• Pricing
• Operational efficiency
• Acquisitions
• Exit planning

Perhaps most importantly, peer groups provide accountability.

It’s easy to identify a problem in your own business and then spend another six months doing nothing about it because client issues continually take priority.

A good peer group will ask whether you actually made the change.

Build a Predictable Sales Engine

Many MSPs grow initially through referrals.

That’s a great way to acquire clients. A recommendation from an existing customer carries enormous credibility.

But referrals aren’t entirely predictable.

An MSP that wants sustained growth should eventually build a repeatable sales and marketing process rather than waiting for the phone to ring.

That may include:

• A clearly defined ideal client profile
• Consistent lead generation
• Referral programs
• Search marketing
• Content marketing
• Partnerships
• Outbound prospecting
• Structured discovery
• Proposal processes
• Pipeline management
• Defined follow-up

The exact mix will vary enormously between MSPs.

What’s important is that sales becomes a process rather than an event.

Sell the Why Before the What

One lesson from building Totality Services was that great technology alone isn’t enough.

Clients need to understand why something matters before they’re likely to invest in it.

That applies to managed services generally, but it’s especially important in cybersecurity.

The technical team may know exactly why a product is required. The client may simply see another monthly charge.

Good commercial communication closes that gap.

You need to sell the why before expecting the client to buy the what.

Focus on Client Retention

Winning a new managed-services client can require months of marketing, sales meetings, proposals, negotiation, onboarding, and technical work.

Losing an established client can undo that work remarkably quickly.

Retention therefore deserves as much attention as acquisition.

The strongest MSP relationships tend to move beyond ticket resolution.

The MSP understands the client’s business, knows its priorities, provides strategic guidance, identifies emerging risks, and demonstrates progress over time.

That is much harder for a competitor to replace than basic IT support.

Make Client Meetings Strategic

Quarterly Business Reviews (QBRs) and other strategic client meetings shouldn’t become presentations filled with ticket counts and uptime statistics.

Those metrics can have value, but the conversation should go further.

What is changing in the client’s business?

Are they hiring?

Opening another office?

Moving systems to the cloud?

Changing compliance requirements?

Planning acquisitions?

Trying to reduce costs?

What security risks need attention?

What technology investments should be included in next year’s budget?

Those are business conversations.

The more your MSP can participate in them, the more valuable the relationship becomes.

Build a Sellable MSP Even If You Don’t Plan to Sell

One of the best pieces of MSP advice is to build your company as though somebody might want to buy it one day, even if you currently have no intention of selling.

A sellable business is generally a well-run business.

Potential acquirers want to understand whether earnings are sustainable and whether the company can continue performing after the founders leave.

Areas they may examine include:

Recurring Revenue

Predictable contractual revenue can be more attractive than a business heavily dependent on irregular project income.

Profitability

Revenue without sufficient profit isn’t particularly compelling.

Client Concentration

Heavy dependence on one or two major customers can increase risk.

Contracts

Clear, appropriate customer agreements can make revenue more predictable and reduce uncertainty.

Standardization

A standardized client base can be easier to operate and integrate than dozens of completely different environments.

Management

A business that operates through a capable management team is less dependent on its founders.

Processes and Documentation

Documented systems make the company easier to understand, manage, and ultimately transfer.

Customer Retention

Stable long-term relationships can provide evidence that revenue is durable.

Even if you never sell, improving these areas is likely to create a stronger company.

Profit Over Vanity Metrics

MSP owners naturally talk about revenue.

“We’re a $5 million MSP.”

“We just passed $10 million.”

Those milestones can be impressive, but revenue tells only part of the story.

A smaller, highly profitable MSP with strong recurring contracts and efficient operations may be a much healthier business than a significantly larger provider with poor margins.

The objective should therefore be quality growth.

Ask:

• How much profit does additional revenue generate?
• How much additional headcount is required?
• Are new clients adopting the standard stack?
• Are support requirements increasing?
• Is recurring revenue growing?
• Are employees becoming more or less productive?
• Is customer satisfaction holding up?

Growth should create value, not simply workload.

Common MSP Growth Mistakes

Certain challenges repeatedly appear as MSPs scale.

Competing Primarily on Price

There will almost always be another provider prepared to offer a lower price.

Trying to be the cheapest MSP can lead to weak margins, underinvestment, employee pressure, and difficulty delivering the service clients expect.

Compete on value, expertise, outcomes, responsiveness, security, and the quality of the relationship.

Overcomplicating the Technology Stack

New tools appear constantly.

Some are genuinely valuable. Others overlap with capabilities you already have.

Every additional platform introduces licensing, training, management, integration, documentation, and support requirements.

Regularly ask whether each product in your stack creates enough value to justify its complexity.

Ignoring Sales and Marketing

Technical excellence doesn’t automatically generate predictable growth.

If the MSP depends entirely on referrals and the founder’s personal network, the sales engine isn’t really a system.

Treat sales and marketing as business functions with processes, objectives, measurement, and accountability.

Allowing Too Many Exceptions

One exception rarely causes a major problem.

Hundreds of them do.

A non-standard firewall here, unusual billing arrangement there, unsupported application somewhere else, and bespoke process for another client eventually creates an organization that’s extremely difficult to operate efficiently.

Standardize wherever doing so makes commercial and technical sense.

Failing to Demonstrate Value

Clients frequently see the MSP’s monthly invoice but don’t necessarily see everything happening behind the scenes.

If the MSP is doing an excellent job, there may actually be fewer visible problems.

That’s why regular strategic communication matters.

Show the client what you’re doing, what has improved, what risks remain, and what should happen next.

Should Your MSP Specialize?

Vertical specialization can be an effective growth strategy for some MSPs.

An MSP focusing on legal firms, financial services, healthcare, manufacturing, or another sector can develop expertise beyond general IT.

That might include:

• Industry-specific applications
• Regulatory requirements
• Common security risks
• Typical workflows
• Procurement processes
• Sector terminology
• Business continuity requirements

This can strengthen positioning because the conversation changes from:

“We understand IT.”

to:

“We understand businesses like yours.”

However, specialization isn’t mandatory.

A well-defined ideal client profile based on size, technology requirements, geography, security needs, or another characteristic can also provide valuable focus.

MSP to MSSP: Put Security at the Center of the Relationship

Security has become increasingly central to managed services.

Whether or not an MSP chooses to describe itself as an MSSP, clients increasingly expect their technology provider to help them understand and manage cyber risk.

That doesn’t mean every MSP needs to build a Security Operations Center or become a specialist cybersecurity consultancy.

It does mean security should be incorporated consistently into service delivery and client conversations.

A mature approach can include:

• Defined security standards
• Regular Security Reviews
• Documented recommendations
• Clear client decisions
• Appropriate security products
• Ongoing evidence
• Historical tracking
• Strategic planning

Security then becomes part of the relationship rather than an occasional product sale.

Frequently Asked Questions

What is the best MSP advice for a growing provider?

Focus on building repeatable systems. Standardize your technology and service delivery, understand client profitability, develop a predictable sales process, invest in management, and reduce unnecessary dependence on the founders.

Growth becomes much harder when every client and every internal process is different.

When should I consider MSP coaching?

MSP coaching can be valuable when you know what isn’t working but are struggling to change it, or when you’ve reached a stage of growth you haven’t experienced before.

The right coach can provide outside perspective, structure, experience, and accountability.

Are MSP peer groups worthwhile?

They can be extremely valuable if the group contains comparable businesses and members are willing to share meaningful information.

The ability to benchmark financial performance, discuss operational challenges, compare vendors, and learn from other owners’ mistakes can save significant time.

How can I increase my MSP’s value?

There isn’t a single formula, but generally you want to build predictable recurring revenue, healthy profitability, strong customer retention, appropriate contracts, low client concentration, standardized operations, capable management, and a company that isn’t excessively dependent on its founders.

Why do clients ignore security recommendations?

Sometimes the recommendation may simply not be a priority for the client. But poor communication is also a common problem.

If recommendations are presented primarily in technical language, the client may not understand their significance.

Explain the business risk, potential impact, recommendation, cost, and consequences of doing nothing. Then allow the client to make an informed decision.

Do I need to be technical to run a successful MSP?

No.

Technical leadership is clearly essential within an MSP, but the founder or CEO doesn’t necessarily need to be the most technical person in the organization.

Luis Navarro’s role at Totality Services was primarily focused on sales, marketing, client relationships, and the commercial side of the business rather than technical delivery.

Having strong technical people and strong commercial people working together can be a powerful combination.

What MSP metrics should I track?

There isn’t one metric that tells you everything.

Useful measures can include MRR, gross margin, EBITDA, EHR, client churn, revenue per employee, ticket volume, service delivery cost, client concentration, sales pipeline, and customer satisfaction.

The important thing is to use metrics to make decisions rather than simply collect them.

How often should MSPs conduct Security Reviews?

The appropriate frequency depends on the client’s size, risk profile, regulatory environment, rate of change, and the MSP’s service model.

For some clients, an annual review may be appropriate. Others may benefit from semiannual or quarterly reviews.

Consistency is more important than treating every client identically.

Should MSPs charge separately for Security Reviews?

There is no universal answer.

Some MSPs include Security Reviews within their managed-services agreement because they support retention, risk management, and account development.

Others provide more extensive assessments as a separately charged service.

Either model can work. What matters is that the review provides genuine value and results in clear, actionable recommendations.

Final Thoughts on MSP Strategy

Building a successful MSP requires the combination of technical excellence and commercial discipline.

As the business grows, the founder’s role inevitably changes. The challenges move from winning the first few customers and resolving technical problems to developing people, improving margins, standardizing operations, building a sales engine, retaining clients, managing risk, and making strategic decisions about the future.

One of the biggest lessons from building Totality Services was that technology is only part of the equation.

You can have an outstanding technical team and excellent products, but clients still need to understand the value you’re providing.

That’s particularly true with cybersecurity.

A client who understands a risk can make an informed decision. A client confronted with pages of technical terminology may simply do nothing.

That principle ultimately led to SecuVeo.

SecuVeo was built from real-world MSP experience to help providers standardize Security Reviews, communicate security risks clearly, demonstrate value, document client decisions, and turn legitimate security recommendations into actionable conversations.

Because ultimately, some of the best MSP advice is remarkably simple:

Build a business that’s easy for your team to operate, easy for your clients to value, and capable of growing without everything depending on you.