EP. 62: Building a Better MSP: 15 Lessons from the Owner’s Seat - Part 1: Founder Bottlenecks, Pricing, and Cash Realities
If your MSP cannot function without you, growth can feel less like progress and more like a punishment. More clients mean more questions, more decisions and more responsibility landing on the same desk. Yours. Over 30 years of building and scaling Australian MSPs, Nick and I have learned that a better business is not created by the owner working harder. It comes from changing how responsibility, client relationships, pricing and delivery are managed. Those changes can be uncomfortable, particularly when being helpful and technically capable is what built your reputation. In this episode of MSP Mastery Podcast, joins us for the first conversation in our three part series, Building a Better MSP: 15 Lessons From the Owner’s Seat. His service leadership experience reinforces something Nick and I have seen repeatedly: sustainable growth requires deliberate operating habits, not constant personal intervention.
MSP Mastery
10/26/20265 min read
Building a Better MSP: Five Lessons From the Owner’s Seat
If your MSP cannot function without you, growth can feel less like progress and more like a punishment. More clients mean more questions, more decisions and more responsibility landing on the same desk. Yours.
Over 30 years of building and scaling Australian MSPs, Nick and I have learned that a better business is not created by the owner working harder. It comes from changing how responsibility, client relationships, pricing and delivery are managed. Those changes can be uncomfortable, particularly when being helpful and technically capable is what built your reputation.
In this episode of MSP Mastery Podcast, Brendan Rose joins us for the first conversation in our three part series, Building a Better MSP: 15 Lessons From the Owner’s Seat. His service leadership experience reinforces something Nick and I have seen repeatedly: sustainable growth requires deliberate operating habits, not constant personal intervention.
Stop Being the Answer to Every Question
One of the hardest transitions for an MSP owner is accepting that a different approach is not necessarily a worse approach. Nick struggled with this himself. When someone tackled work differently, his instinct was to step in and correct it.
The problem was not a lack of capable people. It was the expectation that capable people should work exactly as he did.
Our lesson is to separate the required outcome from personal preference. Clients need reliable service and a business that supports them consistently. They do not need every task performed according to the founder’s favourite method. Clear expectations and documented processes matter. So does giving people room to improve those processes.
Brendan experienced the same pressure from a management position. He was handling service management, sales support, procurement, scheduling and dispatch until the workload became unsustainable. Additional people were hired, but the more revealing moment came later, when a team member asked him to stop helping with procurement. The process had evolved, and his intervention was creating problems.
That is what successful delegation can look like. The team becomes more capable than the person who originally built the function. Your job is to support that progress, not reclaim the work whenever you feel uncomfortable.
Transfer Client Trust Without Abandoning the Relationship
Nick and I have seen owners build excellent client relationships that eventually become barriers to growth. Clients bypass the ticketing system, email the owner directly and insist that nobody else understands their business.
The answer is not to disappear. It is to transfer operational trust while preserving the relationship.
Brendan described a gradual approach: introduce another person, work alongside them and have that person send the responses and deliver the outcomes. As the client experiences reliable service, the owner becomes less involved. Trust moves through repeated positive experiences rather than a single announcement.
Nick’s transition out of account management provides a practical example. Account managers initially joined his client meetings, then took responsibility for agendas, notes, arrangements and follow up. Nick gradually reduced his attendance to quarterly strategic conversations.
The important decision was transferring ownership of the work surrounding the meeting, not simply changing who attended. Clients could see who was responsible, and the account manager had opportunities to demonstrate competence.
For MSP owners, this is the distinction between maintaining a relationship and remaining its operational centre. You can still discuss business direction, family or future plans without becoming the route through which every support request must pass.
Price the Service, Not Your Personal Confidence
Pricing becomes difficult when owners confuse what they feel comfortable charging with what their business needs to deliver responsibly. Nick remembers setting early rates around his own perception of the value of his time. That perspective became less useful as the business grew.
An MSP is not selling an isolated hour of technical effort. It is providing trained people, maintained capability, documentation, accountability and the ability to resolve problems when delivery does not go to plan.
Brendan’s example of repeatable firewall installations illustrates the opportunity. His team increased pricing without seeing demand slow, then improved delivery through training, scripts and standardisation. The client still received a valuable outcome, while the business benefited from becoming more efficient.
The lesson is not to double every price indiscriminately. It is to identify repeatable services, understand their delivery requirements and stop automatically giving away every efficiency improvement.
For more complex projects, Brendan suggested fixing the price of predictable components while treating uncertain work separately. That creates a practical starting point without pretending every project carries identical risk.
Nick also acknowledged a gap in his own approach: insufficient visibility into delivery costs. Pricing confidence must be supported by contract and project profitability reporting. Otherwise, a healthy bank balance or encouraging profit and loss statement can conceal work that is not commercially sustainable.
Make Scope Visible Before the Budget Disappears
Good service delivery needs boundaries. Without them, helpful engineers can quietly turn a well priced project into an unprofitable one.
I remember a team member reporting that a client had asked for extra work while suggesting they should not tell Nick or me. Our team understood that this was not simply being helpful. It was work being requested outside the agreed boundaries.
Nick’s experience also showed how scope problems can start internally. He could underestimate how long work would take, while engineers could absorb missed tasks themselves rather than admit the original estimate was wrong. In one case, an engineer completed substantial additional work after hours because he was embarrassed about an omission.
That is why we advocate separating scoping, delivery and oversight wherever the business structure allows. It introduces challenge before a quote is issued and visibility once delivery begins.
Brendan reinforced the importance of daily time recording and review. Accurate entries allow managers to identify discrepancies while there is still time to act.
When additional scope becomes clear, prepare the facts, speak with the client and follow with written confirmation and approval. Do not let the first conversation happen after the work is finished.
His team’s risk assessment spreadsheet offered another useful lesson: documented risk criteria can replace repeated appeals to a senior leader’s judgement. That improves consistency while removing another leadership bottleneck.
Treat Cash Flow as a Delivery Responsibility
Profit and cash are connected, but they are not interchangeable. Nick and I learned that money in the bank can create false confidence when it relates to work the business still needs to deliver.
Nick recalled clients purchasing project credits in advance. The cash arrived, but the delivery obligation remained. Without clear oversight, it was too easy to view that balance as available money rather than funding committed work.
The reverse problem is work completed but not invoiced. When project delivery has no clear billing milestones or accountable owner, the business can be busy while cash remains trapped in unfinished administration.
We improved this by introducing project milestones and connecting delivery management with invoicing. Completing an agreed stage triggered a bill rather than waiting indefinitely for the entire project to finish.
Brendan’s advice supported the same principle: secure deposits where appropriate, agree hardware billing arrangements and follow up overdue invoices promptly.
In my business manager role, I also worked to a scorecard measure that limited overdue receivables. The conversations were straightforward. Did the client have the invoice? Was there a problem with it? If not, when would payment arrive?
Cash collection became a managed responsibility, not something we hoped would happen after the technical work was done.
Build a Business That Does Not Depend on Heroics
The first five lessons in this episode share a common thread. A stronger MSP replaces personal dependence with clear ownership, visible information and consistent processes.
Nick and I are not suggesting that owners stop caring or become distant from their clients. We are suggesting that care should show up in the business you build: capable people, sustainable pricing, controlled delivery and enough financial discipline to support the promises you make.
If these conversations sound familiar, consider where your business still relies on you to keep everything moving. Connect with Nick, me and the MSP Mastery team to continue the discussion about building an MSP that is both profitable and fulfilling.
