By
Mendy Green
June 9, 2021
•
20 min read
Business
In any business where you’re not billing Time and Materials, the amount of time you spend on a project directly correlates to how profitable you are. In an MSP, this applies even more. MSP Businesses were designed years ahead of their time, bringing into practice concepts such as recurring revenue, outsourcing, efficient resources, and more; before people even realized the value. It’s the reason that today the MSP Businesses are blowing up with everyone you meet starting their own. Unfortunately, there’s a complex side to the framework of an MSP that is very often overlooked, especially by those just starting out.
Let’s discuss how the MSP business model is built. MSPs pitch to their prospective clients that they can provide the same level (or often times better) IT Services to their organization than they themselves can find if they go with someone internally. They ask for less money, and offer a bigger team with greater experience. These same MSPs then have to turn around and hire the same people that would have been hired directly, and not just one, but two or three or more depending on the size of the MSP.
MSPs have to pay the same salary with a smaller budget. How can these numbers possibly work?
This is where efficient resources come in; an MSP needs to stack multiple clients reusing the same resources for each client so that together all the clients combined pay enough money for the MSP to pay the technicians salary and make a profit. The income also needs to cover all base expenses of the MSP which includes infrastructure such as an RMM, PSA, Email, Phones, over-night team for emergencies and so on.
With an internal IT resource, that resource would be solely focused on the business they were working for and getting paid a full salary of say $52k/year, now the same resource at an MSP is getting paid $52k/year and needs to stay on top of not one company IT needs, but actually 3 or 4 (or more depending on the contract size of each). This kind of expectation is unreasonable and when maintained results in high-stress work environments and eventual burn out for the technician. The saying “trial by fire” is very applicable to the technicians who work at an MSP. They are under constant barrage of tickets and stress, jumping from company to company each ticket wildly different from the next. This makes them unusually skilled and also rapidly exposes them to a wide range of experience they may not have received working for just one company. A good MSP technician of the lowest tier can easily go head to head in ability (if not knowledge) to a mid-tier internal IT resource.
Now keep in mind that when MSPs started we were a new phenomenon. There was no standard to follow, no existing business to copy, except for the existing internal IT department within a Company. We didn’t know what kind of pay structure was fair to offer a Tier 1 or Tier 2 technician because there was no “average pay” metric. The only thing we did know is that we are building a business with a stress on smaller dollar amounts per client, and more total clients. This means what we paid our technicians had to be less too, or that we keep the MSP as lean as possible with only the amount of technicians truly needed. Following the 80/20 rule we determined that 80% of the time with our clients running smoothly we would be fine and only 20% of the time when some kind “perfect storm” would occur we would need to motivate our technicians to put in more effort (or what was generally called “figure something out”).
What’s being described is not a sustainable long term plan. Simon Sinek likes to stress that business is an Infinite Game and that those who are not playing by those rules are doomed to failure eventually. The only way to stay in the game is by having resources, and the will to keep playing. We’ve already established that MSPs do not have the same pockets as a normal business, not without drastically imposing upon “will”, our employees, making them work in stressful environments and constantly being battered by the next broken issue.
The fix for this is easy, and its an iteration of what we already started. Efficient use of resources. Efficiency can help us spend less time per ticket, less time per client, and improve our technicians stress in the environment. There are two side to the efficient use of resources, one of which we already started (Sharing resources among companies) but the other is often overlooked “Work load management”. If we can make our work load efficient we can easily improve upon all the issues we just brought up. Here are some ideas that can be used to help facilitate the efficient workload.
Efficient resources is way more than just sharing resources. Making your workload efficient is just as important. Remember how profitable you are directly correlates to how efficient you can be
Remember, in the MSP business time isn’t a loss of potential profit, its actual profit lost as your contracted rate is the same every month. Automation and bulk actions are extremely important as the less time you spend doing something the more your Per Hour amount goes up.
This discussion guide is part of Rising Tide’s Fall 2025 book club, where we’re reading The Go-Giver by Bob Burg and John David Mann.
If you’re just joining us, start with Chapter One – The Go-Getter for an introduction on how to use these Discussion Questions and you may also find our conversation on why we started a book club for a technical team here: Book Clubs, Conversations, and Curiosity.
In Chapter Two, Joe finally learns ‘The Secret’ from Pindar and it’s not what he expected, at all. The idea that success comes from giving sounds simple, but it seems Joe will need to put each principle into action to truly unlock the heart of the Secret of being a Go-Giver.
Use these open-ended prompts to guide reflection and conversation. Remember, there are no right answers!
Rising Tide helps MSPs and service-focused teams build better systems: the kind that align people with purpose.
Every Friday at 9:30 AM ET, we host Rising Tide Fridays as an open conversation for MSP owners, consultants, and service professionals who want to grow both professionally, technically, and emotionally. In Fall/Winter 2025, we’re walking through The Go-Giver, chapter by chapter.
If that sounds like your kind of crowd, reach out to partners@risingtidegroup.net for the Teams link.
Bring your coffee and curiosity…no prep required.
If you’ve already read Book Clubs, Conversations, and Curiosity, you know that at Rising Tide, we don’t host book clubs for the sake of reading. We use them as an excuse to talk, to listen, and to practice curiosity together.
The Go-Giver by Bob Burg and John David Mann is the first book that we've chosen to explore together in this way. Each week, we’re reading one short chapter together and using a few open-ended questions to spark real conversation: no lectures, no wrong answers, just reflection.
Below are our discussion prompts for Chapter One: “The Go-Getter.”
They’re written for teams like ours: busy, service-minded, sometimes too practical for their own good...who want to slow down long enough to notice what these stories have to teach.
How this guide is different from others you'll find online: We keep it chapter-focused. Every set of questions focuses only on the current chapter so there is no foreshadowing, no jumping ahead, no “we’ll get to that in Chapter 7.” The goal is to slow down and savor the smaller ideas that get lost when you rush to the big themes, and we're going to make sure that team members that are "behind" have enough data points to connect the dots and contribute even if they're not caught up to the current reading.
Use them however you like. Whether you’re reading along with us or just looking for a fresh team conversation starter, we hope these questions help you stretch a little, think differently, and see something new in yourself or your work.
If you tweak or add questions, tell us at partners@risingtidegroup.net. We’ll keep improving this tool for other MSP teams.
In this chapter, we meet Joe, a go-getter who doesn't seem to be getting what he's going for. We are also introduced to his coworkers: Melanie and Gus, who help connect him with Pindar, or the Chairman, who agrees to tell Joe the huge trade secret that will surely be his key to success.
Creatures of a day! What is anyone?
What is anyone not? A dream of a shadow
Is our mortal being. But when there comes to men
A gleam of splendour given of heaven,
Then rests on them a light of glory
And blessed are their days. (Pindar, Pythian 8)
Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.
Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.
In By the [run]Book Episode 9, Connor and Robbie power through the rest of HaloPSA v2.2 — unpacking dozens of quality-of-life updates, automation improvements, and admin refinements that make daily operations smoother. From new calendar defaults and contract history tabs to long-requested rule enhancements and KB management upgrades, the pair keeps the banter light and the insights practical.
Perfect for MSPs, admins, and implementation teams who want to understand not just what’s new, but why it matters in real-world use.
Watch Now: By the [run]Book: Episode 9
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
This new Other Uses tab shows every place an email template is used — from rules to mailboxes to notifications.
A new system action logs each time qualification matching runs on a ticket.
CAB selection in approval processes can now reference a custom field.
Portal users can start a ticket and save progress as a draft.
A new trigger fires whenever a quote is revised.
Runbooks can authenticate via Halo API Bearer Token.
Simplifies calendar management for agents.
Administrators can update review dates for multiple KBs at once.
Add KB fields to approval forms for better context when reviewing changes.
Improves data visibility for developers working with email template records.
Sales emails can be attached as CRM notes to keep records complete.
Introduces SKU validation during stock receipt.
New tabs track every edit made to contracts.
Calls no longer end automatically when linked or logged to a ticket.
Quick Time entries now respect ticket-type charge rate rules.
Canned Text can include file attachments.
Control Quick Close visibility per ticket type.
PDF Templates now respect access controls.
The team demonstrates Renada’s custom “Log Site Visit” action as a cleaner alternative to Halo’s arrive/leave process.
Show the Main Contact directly in Site views.
The Team label is clickable and opens the team configuration.
A new system use allows receiving all POs from a ticket in one action.
Event management can map incoming data to the ticket Source field.
The Add Note to Parent option can now be combined with other system uses.
Custom SQL single select fields can now auto-populate with their first value.
A new User field is available for actions.
Rules can evaluate total time logged to trigger pop-ups or actions.
Backend optimizations enhance ServiceNow sync reliability and speed.
Mail campaigns can leverage dynamic distribution lists.
Large reports now load page-by-page to avoid browser timeouts.
Adds criteria-based indexing controls for AI and search.
Different holiday types can have their own allowances and carry-over rules.
Rules can now check if a checkbox is not selected.
You can insert dynamic values into recurring invoice notes and references.
Charge rate controls can now be applied at the top-level entity.
Lookup profiles can now trigger based on checkbox fields.
Choose which mailbox sends automated reports.
Dashboard filters support multiple selections at once.