MSP Organisational Structure

The Functional Pillars of a Mature MSP

To reach a stage where your MSP is highly profitable and attractive to acquirers, you must move away from a flat hierarchy. You need specialised "pillars" that focus on specific outcomes. Here is how those pillars should be organised.

1. Service Delivery (The Engine Room)

This is where the day-to-day managed services happen. It is usually the largest department and is focused on uptime and responsiveness. A mature Service Delivery team is typically split into Tiers:

• Tier 1 (Support Desk): Rapid response, basic troubleshooting, and user administration. The goal here is high volume and quick resolution.
• Tier 2 (NOC/Technical Support): More complex issues that require deeper investigation, such as networking problems or server errors.
• Tier 3 (Senior Engineering): Escalation point for the most difficult technical challenges and infrastructure design.

2. Professional Services (The Project Team)

One of the biggest mistakes MSPs make is forcing their Help Desk techs to also handle projects. This is a recipe for disaster. Projects get delayed because of "emergencies" on the Help Desk, and Help Desk wait times skyrocket because the lead tech is onsite for a migration.

Professional Services should be a separate P&L (Profit and Loss) centre. Their job is to deliver high-quality project work—like cloud migrations or security stack implementations—on time and under budget. This separation ensures that recurring revenue (managed services) and project revenue don't cannibalize each other.

3. Centralised Services & Standards

This is the "secret sauce" of high-growth MSPs. This role (often called a Standards Officer or Technical Alignment Manager) is responsible for ensuring that all 150+ clients are set up exactly the same way.

If every client has a different firewall, a different backup solution, and a different antivirus, your Help Desk will never be efficient. Centralised Services audits clients against your "Best Practice" standards. This role provides the data that Account Managers need to have meaningful commercial conversations with clients about upgrades and risk mitigation.

4. Account Management & vCISO

In a commercially minded MSP organisational structure, the Account Manager is the bridge between the technical team and the client's business goals. They aren't just there to "check in." They are there to run Security Reviews and QBRs that translate technical risks into business consequences.

As Luis Navarro often emphasises, a client doesn't care about the technical specifications of a firewall; they care about whether their business will be offline for three days if they get hit by ransomware. The Account Management layer ensures that these commercial realities are communicated clearly, leading to better client retention and steady project pipelines.

The Evolution of the Founder’s Role

In the early days, the founder is the MSP organisational structure. You are the lead tech, the salesman, and the bookkeeper. To scale, you must systematically fire yourself from these roles.

Phase 1: Firing yourself as a Technician

Your first hires should be Tier 1 and Tier 2 technicians. This allows you to stop answering the phone for password resets and start focusing on winning new clients. Your role shifts to "Lead Engineer & Sales."

Phase 2: Firing yourself as a Project Manager

Once you hit $1.5M - $2M in revenue, you can no longer manage every migration. You need a dedicated Project Lead. This is where you begin to see the separation between reactive support and proactive project work.

Phase 3: Firing yourself as the Primary Relationship Manager

This is often the hardest step for founders. You’ve built deep relationships with your first 50 clients. However, if you are the only one who can conduct a Security Review, you are the bottleneck for growth. Hiring a professional Account Manager allows you to focus on high-level strategy and M&A opportunities.

Commercial Benefits of a Structured Organisation

A well-thought-out MSP organisational structure isn't just about making the org chart look pretty; it has a direct impact on the valuation of your business. When private equity firms or larger MSPs look to acquire a company, they aren't just buying your contracts—they are buying your management system.

By organising the team this way, you create a predictable revenue engine. When the Account Manager identifies a security gap during a review (facilitated by the Centralised Services audit), it creates a lead for the Professional Services team. This cycle is what drives profitability without requiring the founder to intervene in every transaction.

Common Structural Mistakes to Avoid

Even with the best intentions, many MSPs fall into structural traps that stunt their growth. Recognising these early can save years of frustration.

1. Making the "Best Tech" the Service Manager

This is the most common mistake in the industry. Your best engineer loves solving complex problems; a Service Manager needs to love managing people, watching ticket metrics, and refining processes. Often, by promoting your best tech, you lose your best engineer and gain a mediocre manager. Look for leadership skills and empathy, not just technical certifications.

2. Blurring Sales and Account Management

Sales is about "hunting"—finding new logos and bringing them into the business. Account Management is about "farming"—nurturing existing relationships and ensuring long-term value. While there is overlap, the skill sets are different. A salesperson might be too aggressive for a long-term client relationship, while an Account Manager might not be aggressive enough to hit new business quotas.

3. Neglecting the Finance/Admin Function

MSPs are complex billing machines. With dozens of vendors, hundreds of users, and various project milestones, billing errors are common. A structured MSP needs a dedicated finance role early on to ensure that agreement profitability is tracked. If you don't know which clients are costing you money, you can't fix your structure.

Transitioning Your Current Team

If you currently have a flat structure where everyone does everything, you can't change overnight. The transition should be phased. Start by identifying who is naturally better at "heads-down" technical work versus who is better at talking to clients.

Begin by designating a "Lead" for the Help Desk and a "Lead" for Projects, even if they are still working in the roles themselves. This establishes the lines of accountability. Over time, as you hire new staff, place them into these specific buckets rather than hiring more "generalists."

How MSP Agenda Supports Your Structure

The goal of a great MSP organisational structure is to deliver consistent results. However, even the best structure can fail if the tools don't support the roles. This is why Luis Navarro built MSP Agenda.

In a departmentalized MSP, the Account Manager needs a way to take the technical data from the engineers and present it to the client in a way that makes sense. MSP Agenda standardises the Security Review process, ensuring that regardless of which Account Manager is in the room, the client gets a clear, commercially minded recommendation. It creates the accountability that a professional structure requires—tracking which risks were identified, which recommendations were made, and which decisions the client actually signed off on.