Gio Olavarria — Revenue Architecture for PE-Backed MSPs

Your Growth Plan Has a Client-Size Problem

Gio Olavarria — Mon, 31 Aug 2026 00:00:00 GMT

Every value creation plan for a managed services company says the same thing about growth: add clients, raise prices, attach more services. Almost none of them say which size of client, which is the one decision that governs whether any of the rest works.

Here is the argument in plain words. Demand for outside IT help rises with the size of the customer. The average MSP’s client list runs in the other direction. Most of the book sits in the band that buys least, buys least often, and takes almost as much work as the accounts that buy properly.

The demand curve nobody prices

GTIA surveyed 720 people who make technology decisions at companies under 250 employees in North America last May. About half use a managed services provider. Split by size, the picture changes: 37 percent of the smallest firms, those with fewer than ten people, against 62 percent of firms with 100 to 249.

The same survey asked how often they lean on outside help rather than whether they do at all. Among the smallest firms, 36 percent use it frequently or regularly. Among the two larger bands, 51 and 56 percent.

So the difference between a nine person company and a two hundred person company is not a rounding error in your pipeline. One is roughly twice as likely to hire you, and once hired, far more likely to keep asking for things. That second part is what recurring revenue actually is.

The book runs the other way

Now look at what the average provider carries. In Kaseya’s benchmark survey of 984 MSPs, more than a quarter said their typical managed services contract brings in up to a thousand dollars a month per client. Another quarter sit between one and two and a half thousand. Two percent, one in fifty, average more than ten thousand a month per client. And the movement over that year was toward the lower bands, not the higher ones.

A thousand dollars a month is a ten or fifteen seat company. That client still gets onboarded, still gets a quarterly review if you run them, still calls when the printer stops, still needs the same security stack because attackers do not check headcount first. The work does not shrink in proportion to the invoice.

This is the cliff. Demand density climbs as clients get bigger, and the book is concentrated where density is lowest.

Moving up costs money that nobody writes down

The obvious move is to sell to bigger companies. That is a real strategy and it has a real price, most of which does not appear in the plan.

Larger buyers ask for evidence. They send security questionnaires, they want an attestation you can hand to their auditor, and in regulated work they want it before they will sign. A SOC 2 examination from a named audit firm runs from twenty thousand dollars into six figures, with a median around thirty thousand, and that is the invoice, not the year of readiness work that comes before it.

Then there is the question of whether the client pays for any of it. Barracuda asked two thousand organizations that buy from providers what they would pay for compliance support. Thirty six percent would pay up to ten percent more. Another thirty six percent would not pay more at all. Compliance is a reason clients hire you. It is not automatically a reason they pay you more, and the difference between those two sentences is a whole business case.

The number that does not exist

Here is what makes this hard to govern. Nobody publishes what an MSP’s client book looks like by client size. Not the distribution of accounts by employee count, not revenue per client by band, and above all not cost to serve or gross margin by band. Kaseya publishes contract values, GTIA publishes buyer behavior, and neither joins the two.

The one organization certain to have the answer is Service Leadership, which benchmarks the operating metrics of hundreds of these companies. That data sits inside a paid report and a peer group product. The industry’s most important segmentation question has an owner, and the answer is not public.

You cannot buy this number. You already own the only copy that matters, which is your own general ledger.

The work, starting this quarter

Sort every client by employee count and put revenue and gross margin next to each one. Not average revenue per client, which hides the shape. The distribution, so you can see how much of the business sits under twenty seats.

Cost a small account honestly. Take three clients under twenty seats and add up technician hours, onboarding, tooling, and the account manager’s time. Compare that to what the same effort returns in a hundred seat account. If nobody in the company can produce those numbers this week, that is the finding.

Decide the target band and write it down, then price and staff for it. A provider built for ten seat clients does not become a provider for two hundred seat clients by winning one. It gets there by paying for the attestation, the coverage, and the people the larger buyer expects, and by saying no to accounts below the line while it does.

Watch concentration as you climb. Deal trackers in this market are consistent that buyers pay a premium for books where no client is more than five to eight percent of revenue, and discount books that lean on a handful of relationships. The goal is not one large client. It is a denser band of medium ones.

Your growth plan has a client-size problem if it names a revenue target without naming a customer size. One question for the next operating review: what share of our revenue and our gross margin comes from clients with fewer than twenty employees, and what would it take to move the next twenty accounts up one band?

The Business Runs on What Nobody Wrote Down

Gio Olavarria — Fri, 28 Aug 2026 00:00:00 GMT

The diligence covered everything countable. Contracts and renewal dates, revenue by client, margin by service line, the tool stack, the org chart, three years of financials. Nobody pulled a ticket from eighteen months ago to see whether the fix was written down anywhere.

That is the part of the company that decides whether it can absorb anything. A new technician. A bad quarter. An acquisition. The Friday resignation of one person who has been there since the beginning.

So here is the argument in plain words. You bought a business whose real operating system is what its people remember. It works, in the sense that tickets close and clients renew. It does not scale, because every new hire and every acquired company has to be trained by someone whose hours you are already selling to a client.

The industry admits the gap in an odd place

Kaseya asked 1,061 MSPs last November what makes winning new customers hardest. Difficulty creating and keeping consistent client documentation climbed from 10 percent to 17 percent in a year.

Look at where that answer showed up. Not in a question about internal tidiness. In the sales question. When a prospect asks how you will run their environment, a provider whose method lives in four people’s heads has nothing to hand over. The undocumented shop is slower on Tuesday and it also loses the deal on Thursday.

Automation stopped part way, and everybody is comfortable

The same survey asked how much of the workload MSPs had automated over the past two years. Nine percent added none at all. Most of the rest added a little: 55 percent automated up to a quarter of the work. One percent are anywhere near fully automated.

Then the number that explains the other ones. Fifty-nine percent say they are satisfied with the automation they have.

Satisfaction is the right feeling if the company stays exactly this size. It is the wrong feeling for the plan you underwrote. A shop that automates a quarter of the work and calls it done has decided, without saying so, that growth comes from adding people. That is the plan you are paying a multiple to change.

What automation actually moved

The same MSPs were asked which numbers improved as a result of automating. First response time led at 35 percent. Then customer satisfaction, technician efficiency, fewer errors, less burnout. Profit margin came near the bottom at 18 percent, and billing accuracy sat below that.

That ordering is worth an hour of your next operating review. Written-down, automated process buys capacity first and margin later. It shows up as work absorbed without hiring, and only after that as a better P&L. If the value creation plan books the savings in year one, the plan is wrong about the mechanism, not just the timing.

The knowledge has legs

Service Leadership, the benchmarking arm ConnectWise owns, reports that technicians with one to three years of experience leave at three times the rate of technicians with eight or more.

Put that next to an undocumented shop and the problem states itself. The senior people are load bearing. The junior people, the ones who would eventually take that load, leave before they get there. Every departure in the first group takes a piece of the operating system with it, and every departure in the second one wastes the training you paid for. Meanwhile the company pays a retention premium to keep a filing system that happens to be a person.

Two ways to run a platform, and no way to price either

Ask what the acquirers do about this and the honest answer is that they disagree.

Evergreen Services Group, one of the largest buyers in the market, has said plainly that it does not push its companies onto shared systems. Its head of acquisitions put it this way to a trade outlet: “We’re not mandating solutions, tech stack, things like that.” New Charter Technologies makes a similar promise to sellers, and says so on its own site.

Others integrate. Ntiva moved an acquired company onto one shared professional services platform, and the consultant who ran that project describes roughly sixty people working on it daily for about a year. Magna5 appears in its software vendor’s own case study putting nine acquired units on one platform in as little as two months.

Same task, two months against a year, and no one publishes what either cost. There is no timeline here you could underwrite. There is not even a benchmark for the underlying question: nobody publishes what share of an MSP’s work is documented, and nobody publishes tickets per technician or time to resolve for this industry either. You cannot buy that number. You have to measure it inside the company you already own.

The work, starting this quarter

Take the ten accounts that produce the most revenue and test them. Could a technician who has never touched that client run a week on what is written down today. Not in principle. Actually, on a Tuesday, with the person who normally handles it unreachable.

Count the automated work honestly before you count the money. Ask what percentage of tickets close without a human touching them, and compare that to what the plan assumed when it promised margin from efficiency.

Decide whether you are standardizing or leaving them alone, and write the decision down. Both models are running at scale in this market. Drifting between them is not a third model, it is an expensive absence of one.

Put documentation in the purchase agreement, not on the wish list. The window when a seller will still write things down closes the day their attention moves to what comes after the deal.

You bought recurring revenue, a client list, and a set of habits nobody has ever described out loud. The first two transfer on the closing date. The third one is the reason the plan slips. One question for the next operating review costs nothing to ask: if the best technician resigns on Friday, which clients feel it on Monday, and what leaves the building with him.

Half the Industry Sells Through the Owner

Gio Olavarria — Thu, 27 Aug 2026 00:00:00 GMT

The data room had everything. Contract copies, tool inventories, technician tenure, recurring revenue by month for three years back. One question no tab answered: who sells here.

Ask it late and the answer is usually the person who just signed your purchase agreement. MSP Success, a trade outlet owned by Kaseya, surveyed its readers in December 2025 and found MSPs almost evenly split between having a dedicated sales team, or even one dedicated salesperson, and sales run strictly by the CEO or owner. Half the industry has no seller except the founder. If you bought an MSP and never asked this question, flip a coin.

So here is the argument in plain words. In about half of these businesses the sales organization is one person. That person is the seller you just paid. And the deal you signed probably schedules that person’s exit. The plan calls the revenue recurring. The part of it that grows walks out on a clock.

An old problem, not a new one

Datto asked roughly 2,300 MSPs about their business model in 2018. Fifty-three percent called lead generation, hiring sales talent, cold calling, and market differentiation a weak spot. Kaseya asked 1,061 MSPs in November 2025 and the picture came back sharper: acquiring new customers is the top business issue in the industry at 71 percent, ahead of cybersecurity, ahead of profitability. Seven years apart, the same answer.

The bench behind the founder is empty too. ConnectWise and ChannelPro’s 2026 marketing report found that 57 percent of MSPs have zero or limited marketing experience in house. There is no demand team waiting to take over when the founder’s calendar stops producing new deals.

The intent to fix this is real. In the same MSP Success survey, 82 percent said they plan to invest more in customer acquisition over the next twelve months. Spending more through the same one person is not an engine.

Selling was never this industry’s craft. The founder covered for that personally, with a network and twenty years of being in the room. That cover does not transfer with the stock.

The clock is in your own deal documents

M&A Signal, a deal tracker covering MSP transactions, describes the standard structure: 10 to 30 percent of proceeds rolled into platform equity, and in integrated roll-ups the selling owner typically exits within six to twenty-four months. Permanent-hold shops keep founders around for three to seven years. But if your model is integration, the seller leaves inside two.

Put the two facts in one sentence and the problem states itself. Half the industry sells through the owner, and the standard deal removes the owner within twenty-four months. The rollover is supposed to keep incentives aligned, and on paper it does. The founder wants the second bite of equity to be worth something. Wanting it does not staff a pipeline.

A value-creation plan prices the contracts and assumes the pipeline. The contracts renew on their own. The pipeline was a person.

The work, starting this quarter

Measure one number first: the share of current pipeline the founder sourced personally. Not what the CRM lists as the source. Sit with the deal list and ask, one by one, whether this buyer would be here without the founder’s name attached. If nobody can produce the number, that is the finding.

Move the relationships while the founder is still paid to help. Every large account gets a second name from your side in the room before the exit date, on real work, not on an introduction lunch. Expect resistance here. The founder built these relationships, and handing them over feels like the job ending early. Schedule it anyway. The alternative is learning how strong those relationships were from the churn numbers after the exit.

Write down what the founder does in a sales conversation. The pitch that works, the objections that get waved off, the price that holds, the price that gets traded. In a founder-led shop that playbook lives in one head, and the industry’s own numbers say nobody else in the building has run one.

Hire against the install base before hiring a hunter. The first seller into a founder-led MSP inherits warm accounts, renewal conversations, and room to sell more to clients already paying. That job is account management with a quota. Cold-market hunting comes later, once the engine has parts.

What the market pays for the finished engine

Drake Star’s July 2026 market update prices small MSPs, those under $1.5 million a year in profit as Drake Star measures it, at 5 to 7 times that profit. Platforms above $15 million with strong recurring revenue get 16 to 18 times. Scale explains part of that spread. But scale sits downstream of the same question, because nobody reaches platform size on one person’s network. The part of the spread you control is whether revenue arrives without the founder in the room.

You were sold recurring revenue. What you bought, half the time, was a seller. The difference between those two is the multiple you exit at. The board question for the next operating review costs nothing to ask: what share of this quarter’s pipeline did the founder source personally, and who takes over the quarter after the exit date?

The Growth Engine You Bought Was the Founder

Gio Olavarria — Mon, 24 Aug 2026 00:00:00 GMT

The deal model had a slope on the growth line. Retention was strong, most of the revenue repeated every month, and the founder agreed to stay two years, so the slope looked safe. Two years later the add-on acquisitions are carrying the number and the company on its own is flat. The board meeting turns into a sales meeting. A sales hire gets approved, then a second one. Most of that spend will miss, because the diagnosis is wrong. Nothing in the sales function broke after close. The growth engine was the founder, and the deal is what took him off the road.

Where the customers came from

Ask an MSP where its clients come from and you get one answer. In the ConnectWise 2026 MSP marketing report, 72 percent of MSPs called referrals a key driver of business, and no other channel came close. A campaign is something you buy. A referral is a relationship, and at a founder-built firm the relationships belong to the founder: the peer who runs a company across town, the accountant who sends over two clients a year. That engine is real, it is nearly free, and it built the business you bought. It has one moving part. The deal did not include it.

Nobody wrote the engine down

Here is the number I would put in front of a board. Only 43 percent of MSPs have a formal referral program, meaning an owner, an ask, an incentive, and a line in a monthly report. The industry’s best channel mostly runs on habit and goodwill. And where a program does exist, the dependence runs deep: among MSPs with referral programs, one in three reports that referrals produce more than half of total revenue. Take both numbers together as an owner. The typical MSP’s best source of new business is unmanaged, and when it is managed, it often carries half the company.

Nothing sits underneath it

The natural question is what takes over once the founder’s network is spent. Usually, nothing. Half of MSPs in the same report, 51 percent, spend less than ten thousand dollars a year on marketing in total. The best-in-class benchmark, drawn from Service Leadership data, is 1.8 percent of revenue, which works out to eighteen thousand dollars for a million-dollar firm. Even the top of the class funds demand like a hobby. So it is no surprise that in Kaseya’s 2026 survey of more than a thousand MSPs, 71 percent named acquiring new customers their biggest challenge, ahead of every other problem in the business. The industry is telling you, in its own numbers, that it never built a machine for winning customers. It had founders instead.

The people pricing your debt have noticed

PitchBook’s private-credit coverage put the pattern in print back in 2024: MSPs typically show little organic growth under sponsor ownership, growth the company makes on its own, because most of the customers worth having already have a provider and prying them loose is slow work. Reed Van Gorden, head of originations at the lender Deerpath Capital, said it plainer in the same piece: “if some of these MSPs can figure out what new services to offer to increase organic growth, that would be the holy grail. We just haven’t really seen that happen yet.” Lenders keep financing MSPs anyway, because the cash flow is that dependable. They have simply stopped underwriting the growth. An equity case cannot afford the same shrug.

What the owner does about it

Four moves, all boring, all doable inside a quarter.

Map the engine while its parts still work. Take every client won in the past five years and write down who made the introduction. Do it while the founder is still under contract; the map is worth little once the goodbye tour ends.

Make referrals a channel instead of a habit. Give the channel an owner, a budget, a standing ask in every client review, and a report that counts introductions the way a sales report counts calls.

Fund demand like a line of business. If eighteen thousand dollars per million is what best-in-class spends, treat that as a floor, and measure the spend in customers won, not in leads.

Then ask one question at the next board meeting: of the new clients we signed in the past twelve months, how many came by referral, and who made each introduction? If the answer is a list of names with the founder’s at the top, the growth stall has a different name. It is succession, sitting inside the revenue line.

Build it during the hold

The rare platform that grows without buying says the same thing from the other side. “If you can’t grow what you own, you shouldn’t be buying more,” Evergreen’s Ramsey Sayhoun told CRN in February. What the fund bought was a company that never needed a growth engine, because for twenty years it had something better: a founder people trusted, selling to people who trusted him. That engine leaves in every deal, on a schedule the deal itself sets. The replacement does not arrive with a hire. It gets built, during the hold, and building it is the work.

Your Vendors Reprice on a Calendar. You Don't.

Gio Olavarria — Mon, 24 Aug 2026 00:00:00 GMT

On July 1, Microsoft raised the price of Microsoft 365, between 5 and 16 percent depending on the plan, and published the mechanics alongside the numbers: existing customers keep their price until renewal, then the new one lands. The same day, Sophos took its firewall hardware and the subscriptions attached to it up a flat 10 percent and named the component shortage behind it. Atera spent the summer moving every grandfathered account to current rates, monthly accounts in June, annual accounts at renewal. Three vendors, one quarter, and every increase came with a date, a mechanism, and a reason. That is what pricing looks like when a company runs it as a system.

Now look at the company you own. The MSP in your portfolio almost certainly runs pricing as an annual act of nerve.

The nine percent

Across the industry, 95 percent of MSPs put their clients on contracts, and 9 percent put a price increase in them. The figures come from a reader survey of MSPs published last year, and they describe the whole problem in one line: everyone signs paper, almost nobody writes the increase into it. The rest handle pricing by holding a review once a year and deciding whether to have the conversation.

So the cost side of the business moves by calendar and the price side moves by courage. Picture one renewal: the client’s licenses cost the MSP more in July than they did in June, and the MSP’s own price for that client is whatever the contract said two years ago. Multiply by every seat and every account. Each renewal that passes without the increase passed through is a quiet cut to gross margin, and it never shows up as a decision, because nobody made one. It happened one renewal at a time, which is exactly how Microsoft designed its side of the trade.

Why the fear is rational

The objection from management will be that raising prices loses clients, and the data says the fear is earned. WatchGuard surveyed MSP customers this spring and asked what would make them leave their provider. The answers start with a tie at 39 percent each: rising costs without added value, and a major security incident. Read that pairing again. A price increase with nothing attached to it sits in the same tier as getting breached.

What the same buyers accept

Ask the same market a different question and the answer flips. In Barracuda’s survey of two thousand organizations that buy from MSPs, 92 percent said they are prepared to pay more for help integrating their security tools, and about 70 percent put a number on it: up to 10 or up to 25 percent more. The client who leaves over a bare increase will fund a larger one that arrives attached to a capability with a name. The clause clients punish is cost without added value. So attach the value, and say its name in the increase letter.

What the owner does about it

Four moves, none of which need a new client to pay for themselves.

Audit the paper. Pull every client contract and count the ones with an escalation clause. The count will be low. Now you know the size of the retrofit.

Put the increase in writing. New contracts and every renewal get an escalation clause with a date, the way your vendors do it. An increase that arrives by calendar is infrastructure. An increase that arrives by phone call is a negotiation.

Never ship a bare increase. Pair every uplift with something the client can name, and let the security work carry it, since that is what buyers already say they will pay more for.

Put one number in the board pack: realized price against list across last quarter’s renewals, split between accounts that got a named capability with their increase and accounts that got a letter. That number is the company’s pricing discipline, measured. Nobody else measures it; there is no public benchmark for escalator adoption or realized increases anywhere in this industry. Run the metric for two quarters and the company holds better pricing data than the market it competes in.

The calendar test

Your vendors will do this again. Component costs, licensing changes, a new bundle: the reason varies and the calendar does not, and next summer’s increases are already being drafted in Redmond and Abingdon. The question for the next operating review is whether the company you own reprices with them, on paper and on schedule, or keeps absorbing its vendors’ increases into its own margin while it works up the nerve to have a conversation.

Buying Was the Easy Part

Gio Olavarria — Thu, 20 Aug 2026 00:00:00 GMT

Almost every company that wants a managed service provider already has one. Barracuda asked two thousand organizations between fifty and two thousand employees whether they hand their security to an MSP, and seventy-three percent already do. For almost any provider, a new client is somebody else’s client.

Winning those accounts one at a time takes a sales motion most MSPs never built. So the industry found another way. There were 466 MSP acquisitions in 2025, roughly twenty percent more than the year before, and private equity was on the buy side of most of them.

That part works. Buying is the easy part. What you own the morning after is a book of clients somebody else priced, sold by an owner who is now your employee and probably will not be for long, running on tools that are not your tools, under contracts that do not look like your contracts. None of that turns into revenue by itself.

The morning after

Start with what you can lose, because it moves faster than anything you can gain.

When a client leaves an MSP, they rarely leave partly. Barracuda found that eighty-nine percent of departing clients also strip out the other IT services bundled alongside security, forty-six percent immediately and forty-two percent later. One relationship goes bad and the whole account unwinds with it.

Now look at what makes a client start shopping in the first place. The most common answer buyers give is that they cannot see evidence their provider has the expertise and the round-the-clock coverage they were sold. Forty-five percent named that.

Put those two together and the integration risk is obvious. The months right after close are exactly when service gets shaky, when the person who used to answer the phone stops answering it, and when the client cannot see who is minding the store. Dave Sobel described the sequence plainly: “Response times that used to be personal become ticketed. The owner who knew every client by name is now a regional director, or gone.”

That is not a service problem. It is a revenue problem wearing a service problem’s clothes, and it lands in the exact quarter the model assumed you would be selling more.

Two ways to do it, and both are defensible

The industry has settled into two camps, and both say so publicly.

Evergreen Services Group leaves the acquired business alone on purpose. Sydney Hockett, who runs their M&A, put it directly: “We don’t integrate and roll up our businesses. We retain the brands and teams.” On technology: “We’re not mandating solutions, tech stack, things like that.”

Thrive does the opposite and is just as blunt. “We are not an aggregator, we’re a true integrator.” Their stated timeline is twelve months to move an acquired firm onto the platform’s service management system, its playbooks, and its sales and delivery process.

Both are real strategies. The first protects the client relationship and gives up the cost savings and the cross-sell. The second buys those and pays for them in disruption. What is not a strategy is doing neither on purpose, which is what happens when nobody owns the decision and the acquired firm simply drifts.

Russ Reeder, who runs XTIUM, described where drift ends up: “When you grow through acquisition, you have all these systems and all these technologies, and that part is difficult. They haven’t implemented new, scalable financial systems. They haven’t consolidated the tools on the back end, and there’s just so much tech debt that they are just waiting to pass on to the next owner.”

Where the revenue actually is

The sponsor’s case for buying small MSPs is that they are underpriced and under-secured, and that a platform can fix both. That case is mostly right, and it deserves to be stated more precisely than it usually is.

Underpriced is the easiest to verify. Ninety-five percent of MSPs use contracts. Nine percent have an automatic price increase written into them. Most of the rest review price by hand once a year, if they get to it. Buy a firm like that and you have bought a book that has been drifting below market for years, not because the owner was generous but because raising price was never anybody’s job.

Under-secured is where the client will actually pay. Ninety-two percent of MSP clients say they would pay more for help integrating their security tools, and around seventy percent will absorb an increase of up to ten or twenty-five percent for services they want.

But read the same survey’s list of reasons clients leave and the trap shows up. Cost increases without added value, and a competitor offering better security, sit at exactly the same height. Thirty-eight percent each. The lever that raises revenue and the lever that loses the account are the same lever pointed in different directions, and what separates them is whether the client can see what changed before the invoice changes.

Which gives you the order of operations. Fix the service and prove it. Then attach what the client is missing. Then price the whole thing. A platform that reprices in the first ninety days is collecting on trust it has not earned yet, in the one quarter when the client is already looking for a reason to leave.

Nobody keeps score

Here is the part that should bother a buyer most.

None of this is measured. There is no published figure for how many clients an acquired MSP loses in its first year under new ownership. There is no published cross-sell attainment rate for any platform. There is no evidence-based integration timeline either; every hundred-day plan in this category is an advisor’s opinion with nothing behind it. I went looking for all three. They do not exist.

The growth number itself is barely more available. Evergreen’s co-founder told CRN in February that the firm grew roughly thirty to forty percent last year with a double-digit organic piece, which is more than anyone else offers and is still a founder talking to a trade magazine, with no method attached. The industry’s own benchmark reported that MSP revenue grew 9.6 percent last year without once using the word organic.

An industry running tens of billions of dollars of consolidation has no scoreboard for whether the consolidation is working.

The scoreboard

So build one. Four numbers, reported monthly, none of which requires an acquisition to produce.

Same-store revenue. Take the clients owned at the start of the year, set aside everything bought since, and compare what they spend now against what they spent then. It is the only number that says whether the revenue engine runs.

Retention inside each acquired book, tracked on its own for at least eight quarters after close. Blended retention hides the exact thing you are trying to see.

What the acquired base has bought since close. A platform that has done twenty deals and sold nothing new into any of them has bought twenty companies and one revenue engine.

Price on renewal, kept separate from price on new business. Those are two different businesses and an average hides which one is sick.

The market has proven it can buy. The harder claim, and the one almost nobody in this industry can currently make, is that a platform can grow what it already owns. The number that would settle it costs nothing to produce, and nobody publishes it.

The Question Nobody Asks

Gio Olavarria — Thu, 20 Aug 2026 00:00:00 GMT

Every year somebody surveys about a thousand managed service providers and asks them to name their biggest problem. Every year they give the same answer. In the most recent one, 71 percent said acquiring new customers, ahead of everything else on the list.

It is not for lack of people selling the solution.

The largest marketing program in this industry filled a room this year with more than 1,300 MSP owners, its eighteenth annual event, sold out. One agency in the category runs more than a hundred employees, has appeared on the Inc. 5000, and says it has served over a thousand MSPs. A subscription program out of the UK has seven hundred members paying a couple hundred dollars a month. A peer association has thirteen hundred member companies. Underneath all of it sits the marketing money software vendors hand their partners to run campaigns with, which no vendor has ever added up in public.

This is a real industry, two decades old, competitive enough that its firms buy search ads against each other’s names.

So here is a fair question to put to it. What does it cost an MSP to win a client?

Nobody has ever published the number.

What I went looking for

I checked eight of these firms for anything that would count as evidence: a result covering more than one client, a stated number of clients behind it, and a method somebody outside the company could follow.

There is none. Not a cost per lead, not a cost per client, not a conversion rate, not a response rate. What exists instead is case studies, one client at a time, written by the vendor or by the client, with the flattering figure in the headline. About half do not say what the company was doing before. Most do not say what was spent. Several credit a marketing program for a year in which the same paragraph also mentions a new vendor partnership and a price increase.

The literature

There is one exception, and it deserves to be described precisely, because it is the whole of the published record.

An MSP wrote a post on its marketing vendor’s blog reporting that it costs the firm $4,532 to acquire a client, and that every dollar it spends on marketing comes back as seven dollars of recurring revenue. The post explains the method. The owner tracks it in an Excel sheet.

That is the entire published cost-per-client literature for this industry. One company, one spreadsheet, on a supplier’s website.

The closest thing to data is a contest

The largest program runs an annual competition. Six finalists take the stage in front of the twelve hundred and present what they grew and how they did it. The companies are named. The dollar figures are specific. The periods are stated. Last year’s winner drove away in a new electric truck.

It is the closest thing to published outcome data this industry has, and it is not data. There are no published judging criteria. There is no verification or audit of the numbers. Entrants write their own accounts of their own results. And nobody says how many MSPs entered, so there is no way to know whether the six on stage are the best six out of twenty or the best six out of two thousand, which is the only thing that would tell you what an ordinary result looks like.

A leaderboard of winners is not a benchmark. It is a testimonial with a stage.

What a guarantee turns out to be

One firm markets itself on guaranteed leads, so I went to read the terms. The guarantee, in full, is that the firm guarantees growth for its clients will not be a fleeting surge but stable growth, securing a consistent flow of leads.

There is no number in it. No quantity, no timeframe, no refund, no remedy. There is no fine print because there is nothing that could be voided.

Why the number stays missing

I do not think any of this is sinister, and the piece would be worse if it pretended otherwise.

A cost per client only means something as an average across every engagement, including the ones that did not work. No firm in a competitive category volunteers that figure, and no MSP that spent forty thousand dollars for nothing writes it up afterward. The only people holding the data are the people selling the service, and they have every ordinary commercial reason to publish their best case and stop there. That is not a conspiracy. It is what happens when nobody independent is counting.

The effect is the same as if it were deliberate. An industry has been buying this service for twenty years without knowing what it costs when it works.

The part that should bother a buyer

There is a harder fact underneath all of it.

In the same survey where 71 percent call client acquisition their biggest problem, only 12 percent say their new clients are mostly first-time buyers of managed services. A third say their new clients come mostly from competitors. Roughly nine in ten prospects already have somebody.

Which means marketing spend in this industry, added up across all of it, cannot grow the market. It can only move share. Every MSP buying more of it is bidding against every other MSP buying more of it, often with the same templates, aimed at the same accounts. Operators report getting the identical letter from the competitor across town. One had a client hand him a rival’s mailer with LOL written on it.

So an investor looking at a target’s marketing line is looking at a number with no benchmark behind it, spent into a market where the industry’s total spending nets out to something close to zero, on a service whose vendors have never published a result anyone could check.

The question

Somebody should ask what it costs to win a client, and then answer it in public, with a method.

It would not take much. One platform, its own accounts, its own spending, how many of those prospects became clients, and what happened to each year’s new clients after they signed. Published in a form somebody else could check. That firm would immediately know more about this market than any of its suppliers has ever disclosed, and more than the surveys have ever thought to ask.

The question has been sitting there for twenty years while an entire industry sold the answer. It is still nobody’s job to ask it.

The Market Split in Two

Gio Olavarria — Wed, 19 Aug 2026 00:00:00 GMT

Kaseya asked the same 1,061 managed service providers about their profit margin, one year apart. Read the headline number and it looks like a story about MSPs losing ground. Read the full results and it is a different story: MSPs are splitting into two groups, and both groups grew.

The losing group grew first. The share of MSPs running at a loss doubled, from 5 percent to 10 percent.

That matches what you would expect from a tighter year: harder deals, slower growth, thinner margins. Most coverage of this data stops there.

It should not, because the winning group grew too. In the same survey, the share of MSPs keeping 16 to 20 percent of every revenue dollar as profit rose from 15 percent to 18 percent. The very best performers barely moved. So this is not a story about the industry getting worse. It is a story about the middle emptying out, some companies sliding down and others holding steady, in the same market, in the same year.

Why costs are not the real answer

The obvious explanation is cost. Thirty percent of MSPs say rising labor, tool, and infrastructure expenses are hurting growth, and Kaseya’s own report calls the split a combined effect of slower revenue and rising costs.

But costs were already rising last year, before the split opened up. If costs alone explained it, both groups would have felt it equally. They did not. What actually separated the two groups was growth.

Here is why that matters. Picture two MSPs with the same payroll and the same software bill. Last year, both were growing fast enough that the bill was easy to cover. This year, one kept growing and the other did not. The bill did not get bigger. The company that stopped growing simply lost the revenue that used to cover it.

That is the whole mechanism. A cost base looks fine at one growth rate and looks like a crisis at a slower one, even though nothing about the costs changed. This is a growth problem wearing a cost problem’s clothes.

What a revenue leader should check

Treat a margin drop as a revenue question before a cost question. Three checks come before any conversation about cutting spend.

Compare this year’s revenue growth rate to last year’s. If growth slowed by more than costs rose, the fix belongs in pricing and sales, not in the expense report.

Check whether contracts are renewing at their full price, separately from what new deals close at. A renewal that quietly loses price is bleeding the same margin a cost review is out looking for.

Look at what it actually costs to win each new deal. Closing more small deals for the same selling effort dilutes margin one contract at a time, and no expense line will show it, because the problem lives on the revenue side of the business.

Report the split, not just the average

A single margin number hides which of the two groups a company belongs to. Track both the losing share and the winning share every quarter, the same way Kaseya tracks the industry, and a board sees which direction a company is drifting before it needs a rescue plan.

The MSPs keeping 18 percent did not get there by spending less than everyone else. They got there by growing faster than their own costs, which is a revenue team’s job description. A board that reads this data and sends it to procurement is asking the wrong department to solve it.

Four Dollars in Ten Start Over

Gio Olavarria — Tue, 18 Aug 2026 00:00:00 GMT

Every June the managed services industry publishes its honor roll. Channel Futures’ MSP 501 ranks the 501 best-run providers in the world, and the 2026 class, announced in June, averaged more than $32 million in revenue with 10 percent growth. One line further down sits the number that matters more than either: recurring revenue made up almost 60 percent of the total.

Read that from the other side. The most celebrated tier of an industry named after managed services starts every January with four dollars in ten unsold. Those dollars are projects, hardware resales, break-fix hours, one-off cleanups. They arrived last year because somebody sold them, and they come back this year only if somebody sells them again.

A year earlier the list averaged about 54 percent recurring, so the line is moving the right way. The question is where the bar sits, and on that the people who buy MSPs have been unusually clear.

What the buyer already told you

JFS Partners, a firm that brokers these deals, wrote the bar down in July: buyers want 80 percent or more of revenue from recurring managed services contracts, and project or break-fix work compresses the price, often by one to three turns of profit (EBITDA, in deal terms). N2M Capital’s 2026 valuation report, built from 120 MSP transactions, goes further: it calls 90-plus percent recurring “the single strongest valuation driver in current deal flow.”

The market agrees with the memo. In Drake Star’s second-quarter deal tape, small MSPs traded at five to seven times profit while scaled platforms with strong recurring revenue commanded sixteen to eighteen. Part of that spread is size. The part an operator can move this year is the mix.

You do not need to be selling the company for this to matter. The buyer’s bar is a professional opinion about risk, formed by people who pay for being wrong. The 80 percent floor exists because buyers have watched what the other four dollars do to a business.

What the other four dollars do

A recurring dollar and a project dollar look identical on this year’s income statement and behave nothing alike afterward. The recurring dollar is under contract. It renews unless something goes wrong, and when something goes wrong you can usually see it coming. The project dollar ends when the work ships. Next year’s version of it is a deal you have not won yet.

That difference lands in two places. The first is churn exposure. A book at 60/40 carries two retention problems: the clients who might leave, and the 40 percent that leaves automatically, every year, by design.

The second is the forecast. The recurring share of next year is arithmetic. The project share is a pipeline bet dressed up as a baseline, and when four dollars in ten re-book only if they are re-sold, the annual plan quietly assumes a sales performance nobody scoped or staffed.

Nobody has published a study tying revenue mix to churn or forecast accuracy in this industry, and I am not going to invent one. Walk your own ledger instead. Mark every dollar from last year that came back this year without a salesperson touching it. Everything else is quota you did not know you had set.

Moving dollars across the line

Five moves, in the order I would run them.

Count it the way a buyer’s accountant will. Recurring means contracted and renewing by default. Repeat project work from a loyal client is good business and it is not recurring. Resold licenses renew but carry a fraction of the margin, so track the mix in gross profit as well as revenue. Most books get smaller under this definition. Start from the honest number anyway.

End every project with a contract line. A migration, a deployment, a security remediation: each one creates something that now has to be maintained, monitored, and renewed. The project is the audition. Never close one without proposing the managed line item that follows it, in the close-out meeting itself, with a monthly price attached.

Price the plan, not the hours. Time-and-materials work converts when the recurring version is on paper: a monthly figure, a defined scope, a renewal date. Offer it at the end of every hourly engagement. Some clients will keep buying hours, and the offer becomes the default anyway.

Give the renewal book an owner with a number. Revenue that renews by itself still needs somebody accountable for the renewal rate and for moving project clients onto contracts. If improving the mix is everyone’s job, it is nobody’s quota.

Report the mix beside revenue every month. One line: share of revenue under contract, trended by quarter. What the board inspects, the company fixes.

The number under the award

For an investor the test costs an hour. Pull the portfolio company’s trailing twelve months and sort every dollar into two piles: renews by contract, or has to be re-won. Then set the pile sizes next to the growth plan. A book at 60 percent is committing to re-sell almost half of itself before growth even starts, and the plan should say so out loud, in headcount and pipeline, not in a footnote.

The MSP 501 measures size and growth, and the industry is right to celebrate both. The buyers of these businesses read a different number first. Revenue says how big the company is this year. The mix says how much of it is still there in March.

Where Did the Big Deal Go?

Gio Olavarria — Fri, 14 Aug 2026 00:00:00 GMT

Ask a thousand MSPs what their typical customer spends in a year, and you can watch the industry’s floor drop in a single chart. A year ago, 75 percent said their typical client spent $25,000 or more. This year, 41 percent. In twelve months, the big client went from the industry’s default to a minority experience.

The top of the chart is worse. Contracts between $100,000 and $250,000 fell from 18 percent of the industry to 6. The quarter-million-to-half-million band fell from 10 to 2. Above half a million: zero. Not smaller. Gone.

Clients did not stop buying. They started buying smaller. The share of MSPs whose typical client spends under $25,000 more than doubled, from 24 to 55 percent, and a quarter of providers say clients are cutting IT budgets outright. The same industry that used to run on a few large commitments now runs on many small ones.

The instinct that fails

The natural response to shrinking deals is to hunt bigger ones. The industry is already trying: adding new clients tops the MSP priority list at 88 percent, ahead of everything else providers say they want this year. So the whale hunt now has more hunters and fewer whales. Chasing a bigger logo in this market is a plan to lose slower.

And the ambition has not adjusted to the tape. In N-able’s survey, 59 percent of MSPs still expect to grow 20 percent or better. On a board where the big deal is disappearing, that kind of growth has exactly one durable source: the accounts you already hold.

If the logo will not get bigger, the account has to.

Grow the account, not the logo

Revenue per account is the number this playbook runs on: what a client pays you per year, and whether that figure climbs. Four moves make it climb.

Draw the attach map. Kaseya’s data shows where expansion money is actually moving: 71 percent of MSPs grew their security revenue last year, and about half grew backup and cloud management. Meanwhile most books still lean on the commodity core; endpoint management is a top revenue source for 64 percent of providers, the crowded category everyone already owns. The map itself is one line per account: the next service this client should logically buy, and the date someone will propose it. An account with no named next service is not a growth account. It is a renewal risk with good manners.

Package the demand clients have already stated. Almost half of MSPs say AI and automation is the top client need for 2026, ahead of security, yet only 13 percent book it as a meaningful revenue source today. That gap is not a reason to lead with AI. It is a reason to write the offer down, put a price on it, and define what the client gets, before someone else answers the question they are already asking.

Build tiers so accounts climb without a fight. Good, better, best, with the differences written down. An account moves up at renewal, when the conversation is natural, and never mid-term, when it reads as a surprise invoice. The tier ladder is how revenue per account grows without inventing a new negotiation from scratch.

Measure it beside the logo count. Revenue per account, by cohort, every quarter. No public benchmark exists for this number in the MSP industry, so your own trend is the benchmark. The cohort cut is what makes it honest: if accounts opened this year are both smaller and flat, you do not have a market problem, you have a packaging problem wearing a market costume.

Two distortions will try to flatter this number. A price increase lifts every account at once and looks like expansion for exactly one year, so tag it separately. And an account that climbs two tiers and then leaves next cycle was not expansion, it was a goodbye tour, which is why the cohort table gets read beside retention. The staircase only counts clients who stay on it.

Run it as a selling motion, not a service one

The attach map needs an owner and a meeting. Every account gets an expansion review on the calendar, and it is a selling conversation, separate from the support check-ins where the relationship usually lives. The person who owns the account brings two things: the next service on the map and the date it gets proposed. The meeting exists so that date survives contact with a busy quarter.

Pay for the climb, too. If account owners are bonused on renewal survival, the attach map stays a spreadsheet. A bonus tied to account growth by cohort makes the expansion review the one meeting nobody reschedules.

This is also the honest answer to the smaller entry point. A book filling up with sub-$25K clients is not a death sentence; it is a wider staircase. Every small account that lands is a future attach, a future tier move, a future expansion. But only if somebody owns the climb.

What the investor sees

Two MSP books can show identical revenue and be different businesses. One holds its number by replacing shrinking accounts with new logos, which means it re-buys its book every cycle in the toughest acquisition market this industry has measured. The other grows the accounts it already holds. Industry revenue still grew 9.6 percent last year even as deals compressed, which means the growth is happening in smaller increments, inside somebody’s base.

The diligence ask is a cohort table: revenue per account, by the year the account landed, across the last eight quarters. A book that expands its accounts survives a slow logo market. A book that cannot is one bad quarter away from flat.

The big deal did not die. It broke into pieces and moved inside existing accounts. The operators who build the staircase get it back, one floor at a time.

Demand Has a Due Date

Gio Olavarria — Thu, 13 Aug 2026 00:00:00 GMT

On July 13, the Pentagon suspended the second phase of its CMMC assessment program, four months before it was scheduled to begin. Defense contractors read the announcement as relief. The department wrote one sentence that should have stopped them: the action does not eliminate the requirement to protect covered information under the existing DFARS clause. The deadline moved. The obligation did not.

That sentence is the most useful thing the compliance news produced all summer, because it describes a class of demand most MSPs never organize: demand with a date attached. Referrals arrive when they arrive. Inbound converts when the buyer gets around to it. Regulated demand is different. Somebody in a government building put a date on it and attached a penalty, then published both.

A revenue organization that builds its territory plan around that calendar gets urgency without inventing it. An investor evaluating that organization gets something rarer: pipeline that can be checked against a public schedule. Here is the calendar as it stands in August 2026, and the operating system that turns it into revenue.

The calendar, four entries deep

September 22, 2026. NIST places every remaining FIPS 140-2 certificate on its historical list. Validated modules already deployed can keep running; the pressure lands on new purchases, which shift to FIPS 140-3. The move: inventory which clients sell into federal supply chains, and open the module-refresh conversation before the fall procurement cycle opens it without you.

The CMMC pause. Phase 2 was scheduled for November 10, 2026 and is now suspended while a task force reviews the program. Scope stays what it was: the defense supply chain, about 220,000 contractors and subcontractors by the department’s own analysis, three-quarters of them small businesses. A Level 2 certification assessment runs $101,752 for a small entity, again by the department’s estimate. The DFARS security clauses stay in force through the pause. The move: build the defense-adjacent account list now and sell readiness against the obligation, because a pitch built on the obligation survives a paused deadline. A pitch built on deadline panic died in July.

The proposed HIPAA overhaul. The Security Rule amendments published in January 2025 remain a proposed rule, and the HHS regulatory agenda now points to July 2027 for final action. The department priced the first year of compliance at roughly $9 billion. The move: healthcare clients get a gap assessment against the proposed text, sold as exactly that, so the remediation backlog gets scheduled before the rule lands instead of after.

The column of dates already passed. PCI DSS 4.0.1’s future-dated requirements became mandatory in March 2025. Indiana, Kentucky, and Rhode Island privacy laws took effect this January 1. Public-company clients have answered to the SEC’s cyber incident disclosure rule since December 2023. A passed date is remediation demand: the client who missed it is further behind than they believe, and an assessment against a live requirement closes faster than one against a rumor.

The demand is funded and under-sold

None of this works if buyers resent the subject, and the record says they do not. WatchGuard’s April 2026 survey found 67 percent of organizations need additional support to meet growing compliance demands. The same survey found 75 percent expecting security budgets to increase over the next two years. The need is stated and the money is planned.

Now the supply side. Kaseya’s 2026 State of the MSP puts regulatory and compliance reporting at 8 percent of the MSP revenue mix. The same report clocks the category’s growth at 36 percent year over year, among the faster lines in the book. Two-thirds of buyers say they need the help; providers book it at 8 percent of revenue. The distance between those numbers is unsold work.

The insurance column

Cyber insurance belongs on the calendar for one reason: renewals recur on a date. Handle the story around it with care. Premiums are falling. Marsh’s index recorded a 4 percent decline in cyber rates in the second quarter, the twelfth consecutive quarterly decline, so the spiraling-premiums pitch is dead, and a buyer who reads the market will hold it against the seller who tries it.

What remains true is better material. Insurers keep tightening the controls they require attested at renewal, a pattern operators report consistently even though no published study quantifies it. And the claims justify the controls: Coalition’s March 2026 claims report found dual extortion in 70 percent of ransomware events, with initial demands up 47 percent to an average above $1 million. The move: a renewal-date field on every account record, and a standing meeting 90 days ahead of each one to walk the attestation together before the broker’s questionnaire arrives.

Running it as a system

A calendar taped to the wall is decoration. The operating version lives in the CRM as four dated fields on every account: regulatory framework and its next date, insurance renewal, contract end, budget cycle. Territory plans and quarterly sequencing get built from those fields, and account reviews open with them.

Ownership matters as much as the fields. Each calendar entry gets one owner on the revenue team, and entry status gets read out in the same weekly meeting that reads out pipeline. A calendar reviewed quarterly is a calendar discovered late.

Pipeline created from a date behaves differently. The close date belongs to the buyer’s regulator or insurer, so neither the rep’s optimism nor the buyer’s stall can move it far. Forecast reviews stop litigating rep conviction and start tracking one number: the share of open pipeline with an external date attached. That share is the figure to put in front of an investment committee, because a date-sourced pipeline survives diligence.

One discipline holds the system together: sell the obligation, never the deadline theater. Deadlines pause, as CMMC just demonstrated. Obligations persist, as the department confirmed in the same announcement. Build on the second and a suspended deadline costs you nothing but a talking point.

The benchmark nobody owns

No analyst report quantifies compliance-driven MSP revenue beyond Kaseya’s single line; the search comes back empty. That absence is an opening. The operator who instruments this motion first will own the benchmark the rest of the industry quotes, and the investor who backs that operator gets a demand engine with dates on it.

Worth an hour of your next operating review: pull ten open opportunities and count how many carry a date the buyer did not choose. A pipeline full of self-set close dates runs on hope. The calendar is public and the penalties are published. The buyers have already said they need the help. Put dates on your demand.

More Heads Is Not a Growth Strategy

Gio Olavarria — Thu, 13 Aug 2026 00:00:00 GMT

In June, the chief executive of ConnectWise, the biggest software vendor in the managed services industry, said something worth taping to the wall: “The equation for growth is breaking. It is human-led, and there’s nothing wrong with that, but the market is shifting.”

He said it in an interview about his company’s AI products, so discount the sales pitch wrapped around it. The observation survives on its own, and you can prove it without any vendor’s research.

Here is the equation he means. For twenty years, growing an MSP worked like this: win a contract, hire a technician to serve it, repeat. Double the customers meant double the staff. Revenue followed payroll. Growth was a hiring plan with a sales team attached.

The next technician stopped showing up

That model has a quiet dependency: every time you sell, somebody qualified answers the job posting. That is the part that broke.

The evidence is national, not industry gossip. The Bureau of Labor Statistics puts the median IT wage at $105,990. CompTIA’s read of the July jobs report puts tech unemployment at 2.8 percent, which in practice means almost everyone good is already working somewhere. An MSP in Omaha is not competing with the shop across town for that talent. It is competing with every IT department in the country.

Ask the industry and it says the same thing. In Kaseya’s survey of about a thousand MSPs, the share who called hiring skilled technicians a daily problem jumped from 9 percent to 16 in a single year.

And here is the twist worth being honest about: pay is not exploding. Service Leadership, which tracks compensation across the industry, says wage inflation peaked back in 2022 and has cooled since. The problem is not that technicians got expensive. They got scarce, and you cannot solve scarce with a raise.

So the growth plan and the hiring plan have to stop being the same document. For twenty years they were.

Somebody already found the exit

Two numbers from this summer show the industry quietly splitting in two.

First: industry revenue grew 9.6 percent last year, while profit, by Service Leadership’s measure, grew 17.1. When profit grows almost twice as fast as sales, operators are finding ways to serve more customers without hiring proportionally more people.

Second: the spread. In Kaseya’s data, 27 percent of MSPs grew their recurring revenue by more than 20 percent last year, and 7 percent shrank. The same market and the same shortage produced wildly different outcomes. Some operators have already figured out how to grow without the next technician.

What no survey tells you is how they staffed it. Nobody measures that. Which brings us to the number this piece is actually about.

One number tells you which side you’re on

Take everything the company billed last year. Divide it by the number of people it took to deliver it. That is revenue per employee, and it is the cleanest test of whether a business grows by building or by hiring.

Nobody publishes a benchmark for it. Service Leadership’s public materials do not carry one. The Channel Futures MSP 501, the industry’s best-known ranking, reports that its average member books $29.4 million in revenue, and it does not collect headcount at all. The industry does not know how many people it takes to produce its own revenue.

That is not a reason to skip the number. It is the reason to own it. Compute it every quarter, ignore the level, and watch the direction. A line that climbs while service quality holds means you are building a machine. A line that only moves when you raise prices means you are not.

Four habits, in plain terms

Put it on the scoreboard. Revenue per employee goes into the quarterly review next to sales and churn, as a trend line. Count everyone honestly: people on payroll plus contractors and the offshore bench. The fastest way to ruin this number is to flatter it.

Make hiring requests carry the math. Anyone asking for a new hire brings two lines with the request: the revenue the hire unlocks and the quarter it lands. A growth plan that only works with one new hire per new customer is a payroll plan wearing a growth costume.

Stop pricing by effort. Billing by the hour or by the ticket sells your scarcest resource at cost and hands every efficiency gain to the client: automate a task and the invoice shrinks. Price new offers on the outcome instead, the covered employee or the audit passed, so the gains land as your margin. Change the anchors on new deals now, move old contracts at renewal, and never reprice anyone mid-term.

Pay your service leaders on the trend. A bonus for keeping everyone busy rewards the old machine. A bonus for growing revenue per employee rewards replacing busywork with systems, one workflow at a time.

The eight-quarter email

For a private equity reader, this number does in one line what forty pages of diligence try to do: it separates growth that was built from growth that was hired. Revenue up while the ratio stays flat means the growth was hired. Revenue up while the ratio climbs means someone built something, and built things command premiums.

The test fits in one email: revenue and average headcount, by quarter, for the last eight quarters. The speed of the answer is a finding by itself. An operator who runs this number sends the spreadsheet the same afternoon. One who has never seen it needs two weeks, because someone has to assemble a number nobody was managing.

The ConnectWise chief is right that the equation is breaking, whatever he happens to be selling alongside the observation. The operators who see it break get to choose what it breaks into. Pull four quarters of revenue, divide by heads, and look at the line. If it stayed flat while revenue grew, the equation is still running you.

The Mid-Market Kept Its IT Team. Sell Beside It.

Gio Olavarria — Wed, 12 Aug 2026 00:00:00 GMT

An MSP can grow through two well-known doors. The first is the small company buying IT service for the first time, and the survey data says those deals keep getting smaller. The second is displacement, winning an account away from another provider, which means beating an incumbent who already holds the keys.

There is a third door: the account that employs its own IT people and hires an outside provider anyway, for the pieces its team cannot cover. The industry calls this co-managed IT. Most MSPs treat it as overflow work that shows up on its own. It should be a designed sales motion with its own offers and its own numbers. This is the playbook.

The market permission is already on record

A company with 400 employees has an IT team on payroll, usually a small one. It still buys from MSPs. In Barracuda’s 2025 survey of 2,000 IT decision-makers, reliance on MSPs for security climbs across the entire size range: 61 percent among organizations with 50 to 100 employees, 85 percent at 1,000 to 2,000. Above the smallest band, most of those buyers have IT staff of their own, so most of that reliance is capability added on top of a team the company already pays for.

WatchGuard’s April 2026 survey sampled organizations from 2 to 2,499 employees: 48 percent use an MSP to supplement their internal team, and nearly half describe their provider as a strategic advisor.

The operators who run co-managed practices put the concentration in the middle of the market: companies from roughly a hundred employees up, big enough to employ one to five IT people, too small to staff the entire function. No survey has measured that curve directly, so hold the band as operator consensus. It is also the plain arithmetic of a small team: five people cannot cover the whole stack around the clock.

That is the target profile. The rest of this piece is what to sell them and how to measure it.

Why staffed teams buy

The gaps are stated on the record, and they are specific. 54 percent of organizations say they cannot deliver continuous 24/7 monitoring and response on their own. 67 percent need outside help meeting compliance demands. 75 percent expect their security budgets to grow over the next two years, so the money to close both gaps is already planned.

The labor market keeps the gaps open. ISC2’s 2025 workforce study found 59 percent of organizations citing critical or significant skills needs, up from 44 percent the year before. A three-person IT team loses its night coverage the day one person resigns.

The sales conversation follows from the org chart. A full-outsourcing pitch tells this buyer to disband a team they chose to build, and the person evaluating you is often the person you are proposing to replace. A co-managed pitch makes the IT director the sponsor: you are offering to take the 2 a.m. pages and the audit prep off a team that keeps the work it wants.

Build the entry offer around one gap

The survey data hands you two entry offers. Build both as products, priced and scoped in advance, so a rep can put a number on the table in the first meeting.

The coverage offer sells against the 54 percent. Scope it to what the internal team cannot staff: after-hours monitoring and response, weekend coverage, tier-one triage, and a written escalation line for what wakes their people and what wakes yours. Price it flat per month so the buyer can budget it as one line item. The first proof artifact is a monthly coverage report with response times the IT director can forward to their boss. It makes your sponsor look good, which is the point.

The compliance offer sells against the 67 percent. Scope it to evidence: control mapping against the framework the client actually faces, a standing evidence calendar, audit preparation the team currently does by hand, and a findings list worked between audits. The proof artifact is the audit that goes smoothly.

One gap per entry. Bundling kills the motion, because the value of the first engagement is a fast, visible win that cost the buyer one decision.

Put the division of labor in writing

The core artifact of a co-managed account is a written split of the stack: who owns patching, monitoring, identity, backup and recovery, vendor escalation, audit evidence. Write it during onboarding and revisit it every quarter.

The document does two jobs. First, it protects the sponsorship. What stays in-house is on paper, so the internal team can see the boundary and stops defending against you. Second, it is the expansion instrument. Every quarterly revisit re-sorts the stack: the pieces the team is ready to shed move to your column with a price attached, and the pieces they want to keep stay theirs. Expansion stops being a campaign and becomes a standing agenda item the client expects.

This is also where the account defends itself at renewal. A client holding a documented year of coverage reports, closed audit items, response times, and a division of labor re-signed four times has very little reason to shop.

Stages, and the numbers to run

Define the stages and hold every account to one of them. Supplement: one scope, flat fee. Shared operations: multiple scopes, with the division-of-labor document governing both sides. Primary: your team runs the stack and the internal staff direct it.

Then instrument the motion with four numbers: the share of new logos entering through the co-managed door, second-scope attach by month twelve, stage conversions per year, and revenue per co-managed account tracked beside revenue per full-service account.

No public benchmark exists for any of these, so set internal baselines in the first two quarters and manage against your own trend. The absence works in your favor at diligence: an operator who can produce these four numbers is showing instrumentation the market cannot buy off the shelf.

The revenue justifies the discipline. In Kaseya’s 2025 benchmark, about 61 percent of MSP executives reported co-managed revenue up year over year, and two-thirds said co-managed work produces as much as half of their revenue. A line that size deserves designed offers and a real review cadence.

Qualify for it deliberately

Build the target list on the profile the data supports: mid-market companies with a small internal IT team, a compliance obligation, no overnight coverage, and a security budget already planned to grow. The signals show from outside: job postings for a second or third IT hire, a regulated industry, a tool stack wider than a small team can manage, and an org chart with no overnight shift.

Then fix the sales behavior that kills these deals. A rep who walks into a staffed account with a full-outsourcing pitch turns a warm conversation into a threat, and the deal dies with the IT director as its opponent. Script the co-managed pitch separately, train reps to spot the staffed account before the first meeting, and comp expansion revenue so the account gets worked after the land.

The operating review

If you hold a platform MSP, put four questions in the next operating review. How many of last quarter’s new logos entered beside an internal IT team? What is revenue per co-managed account, and how has it moved over four quarters? Who owns second-scope attach, and what is the number? Which accounts sit one quarterly review away from a stage conversion?

The timing argument is already made: 75 percent of organizations expect security budgets to grow over the next two years, and the staffed mid-market accounts are where those budgets live. If the co-managed column of the closed-won list is empty, the growth plan is leaving its largest deal sizes on the table. Building the motion costs less than buying the equivalent pipeline.

They Ask, You Answer. Most MSPs Don't.

Gio Olavarria — Mon, 10 Aug 2026 00:00:00 GMT

Customer acquisition is the top business issue in managed services, and it is not close. In Kaseya’s 2026 State of the MSP report, 1,061 providers fielded in November 2025, 71 percent named acquiring new customers their biggest challenge, ranked above every other issue: cybersecurity at 53 percent, revenue growth at 49, profitability at 48, staffing at 32. The leads bought against that problem are expensive. First Page Sage’s cost-per-lead benchmarks, last updated May 2025, put a managed services lead at $503 blended, $617 through paid search. That buys a lead, not a client. Assume one lead in four ever signs and the marketing cost of a single new logo clears $2,000 before anyone has scoped an environment.

The buyer finishes most of the sale alone

Set the buyer’s behavior next to that spend. Gartner’s sales survey published in March 2026 found 67 percent of B2B buyers prefer a rep-free buying experience, up from 61 percent in the prior year’s survey and 43 percent in 2021. The preference shows up in timing: 6sense’s buyer experience report from November 2025, a survey of nearly 4,000 buyers, put the point of first contact with a seller at 61 percent of the way through the buying journey. The structure of this market sharpens both numbers. This site argued earlier this month that almost every MSP deal now has an incumbent in it, and a buyer weighing a switch does the homework more thoroughly, because being wrong costs a second migration.

The newest wrinkle sits on top. G2’s Answer Economy report from April 2026 found 51 percent of B2B software buyers now start research with an AI chatbot more often than with Google, up from 29 percent a year earlier. Software buyers are not MSP buyers, but the direction carries, and the machines have nothing to say about a company that never wrote anything down.

Put the pieces together and the shape is plain. The prospect who finally calls has already done most of the evaluation, alone, wherever their questions found answers. You do not control where the buyer looks. You control whether your answers are there to find.

A pool company wrote the manual

The framework that fits this buyer is seventeen years old and came from outside the industry. In early 2009, Marcus Sheridan’s company, River Pools and Spas, a twenty-employee fiberglass pool installer in Virginia and Maryland, was failing. The New York Times told the story in February 2013: orders had fallen from six a month to barely two, and the company overdrew its bank account three weeks running. Sheridan cut an ad budget of about $250,000 a year to a tenth of it and started publishing direct answers to every question a pool buyer had ever asked him, beginning with the one his industry refused to answer in public: what a fiberglass pool costs.

He told the Times he could track at least $1.7 million in sales to that single article. Retellings since have quoted bigger numbers; the figure the Times printed is $1.7 million, and it is plenty. He also gave the paper his appointment math: prospects who read 30 or more pages of the site before a sales visit bought 80 percent of the time, against an industry appointment average he put at 10 percent. His numbers, self-reported. The same story records the company recovering past its pre-2007 revenue peak. The method became They Ask, You Answer, published by Wiley in 2017 and revised in 2019.

The framework has two working parts.

The first is what Sheridan calls the Big 5, the questions every considered purchase generates: what it costs, what problems come with it, how it compares to the alternatives, what its reviews say, and which providers are best. Buyers ask all five whether or not you answer. The instruction is to answer them in public, with real numbers, including the comparisons that name your competitors.

The second is assignment selling. The book defines it as intentionally using educational content to resolve a prospect’s major concerns before the sales appointment. In practice: the pricing guide goes out ahead of the first meeting, with a direct ask to read it. The prospect who reads it arrives informed and mostly decided. The prospect who will not read it has told you something about the deal too. The 30-page close rate is this effect, measured.

The page MSPs will not build

Run the Big 5 against a typical MSP website and the gap is widest exactly where the framework starts: cost. How many MSP sites publish pricing? No credible audit exists; it was searched for this piece, and the number is not in public. Walk twenty competitor sites in your metro and run the count yourself. The objections behind the blank page are the same two everywhere: competitors will see our rates, and prospects will rule us out early. Your competitors already know your rates. And the prospect a price range scares off was never going to sign at your price.

The buyer’s side of the argument is on the record. In TrustRadius’s 2026 B2B Buying Disconnect report, a survey of 1,862 technology buyers published in July, transparent pricing has been buyers’ number one request of vendors four years running. AI search raises the stakes on the same request. A chatbot answering what managed IT costs for a sixty-person firm can only assemble what someone published. The MSP whose site says what co-managed runs per user, and names what moves the number, can be quoted by the machine. The MSP whose pricing page is a contact form is absent from the answer.

Run it as a sales program

Write the cost page first. Ranges with drivers, never a bare rate card: seat count, server estate, compliance load, co-managed against full stack. Say where your floor is and what you decline to do at the floor. The page does not need to quote your next proposal; it needs to teach the buyer how your pricing works and prove nobody is hiding the ball.

Answer the other four in the same register. What breaks in co-managed arrangements and when they fail. When a company should hire internal IT instead of hiring you. Your firm against the national providers, compared plainly. Where your reviews live and what the worst one says. Sheridan’s instruction on comparisons is the uncomfortable one: write about your competitors honestly, because the buyer is comparing you anyway, in a tab you cannot see.

Wire assignment selling into the sales process. The pricing guide goes out before every first appointment, with a direct ask to read it and a sentence about why. The prospect who reads it arrives qualified on budget and half-decided. The prospect who will not read it has signaled something worth knowing before you spend the drive. On a sales cycle operators typically put at 90 to 180 days, content that settles cost and scope before the first meeting is cycle time removed, not marketing overhead. The same motion works inside the base: assigning next year’s budget guide ahead of a quarterly business review is assignment selling on an account you already hold.

Write for the machine as well as the reader. Plain statements a model can lift: what you charge and where you stop. If AI-first research keeps climbing at the rate G2 measured, the pricing page is no longer only for humans, and prose that hedges everything quotes as nothing.

Instrument it. Four numbers, all from systems already running: leads sourced by content page, guide-read rate ahead of first appointments, close rate for prospects who read against those who did not, and revenue attributed to content-sourced deals. The third number is Sheridan’s 30-page metric rebuilt on your own book. No industry benchmark exists for any of the four, which is a gift. Your trailing numbers become the standard, and most competitors have never looked at theirs.

The objection writes itself: 2009 was a different internet, and a pool is not a managed services contract. But the buyer data reads like it was staged for the framework’s benefit. Two-thirds of buyers prefer to avoid the rep. First contact arrives 61 percent of the way through the journey. Half of software buyers now ask a machine before they ask a person, and the machine can only repeat what someone wrote down. Pricing has topped the buyer wish list four years straight. The questions have not changed since the pool business. The open variable is whose answers come back.

Your Next Client Already Has an MSP. Sell Like It.

Gio Olavarria — Fri, 07 Aug 2026 00:00:00 GMT

Ask a thousand MSPs where their new clients come from and the honest answer is: from each other. In Kaseya’s 2026 State of the MSP survey, 1,061 providers fielded in November 2025, only 12 percent say their new clients are mostly first-time MSP users. A third say new clients mostly switch from another provider. Half see a mix. The report’s own sentence carries the thesis: growth depends more on winning clients from competitors than on signing first-time users. The market is not minting customers anymore. It is circulating them.

Once that shape is visible, the rest of the survey reads differently.

Acquisition got harder because every deal has an incumbent

Acquiring new customers is the top business issue for MSPs at 71 percent, well ahead of cybersecurity at 53 and revenue growth at 49, in a survey where respondents pick exactly three concerns. Acquisition got harder for a structural reason: almost every deal now has an incumbent in it, and the incumbent holds the contract, the documentation, and the switching friction.

Incumbency is a real moat, and it is worth naming what sits inside it. The incumbent knows the renewal date; the challenger has to guess it. The incumbent holds the admin credentials, the network documentation, and the institutional memory of every exception the client ever asked for. Above all, the client remembers what the last transition cost in disruption, and prices that memory into every pitch a challenger makes. A displacement seller is not really selling against the competitor’s service quality. The seller is selling against the buyer’s memory of the last migration.

Deal economics confirm the squeeze. Clients spending $25,000 or more a year fell from 75 percent to 41 percent of the typical book, while sub-$25,000 clients more than doubled to 55 percent. A third of providers cite slower new client acquisition as a key economic drag, and a quarter report clients cutting IT budgets outright. And the share of MSPs struggling to demonstrate value to prospects quickly nearly doubled, from 10 to 19 percent, which is what selling against an incumbent feels like: the prospect already has a baseline, and vague value claims lose to a baseline every time.

Every book in the market is in play

The buyer side says the door is open. Barracuda’s MSP Customer Insight Report, a Vanson Bourne survey of 2,000 senior security decision-makers at organizations of 50 to 2,000 employees, fielded in spring 2025, asked buyers what would make them leave their MSP. Two percent said nothing would. Everyone else named a condition. The top deal-breaker is not price: 45 percent would leave an MSP that cannot back up its security skills and its 24/7 support setup with evidence. A cost increase on security services and a better security offer from a rival MSP tied at 38 percent.

WatchGuard’s 2026 survey of 842 IT and security decision-makers, fielded in April, points the same direction: 58 percent plan to switch providers within the next three years. Both figures are stated intent, and intent is softer than observed behavior. Read them as a seller anyway. The market’s entire installed base sits with its door unlocked, and that includes yours.

The same research shows the door swings on capability, not on rate cards. In the WatchGuard data, 47 percent of those decision-makers will pay a premium for 24/7 monitoring and faster response. Hold that against the deal-breaker list. Buyers leave over missing proof and pay extra for present proof. A displacement deal is a capability deal wearing price-deal clothing: the incumbent who believes it lost on price usually lost on evidence months earlier, and the price objection showed up after the decision was already made.

Offense and defense are one discipline

Barracuda’s cascade figure raises the stakes on the defensive side. Among departing customers who bundle IT services with security, 89 percent take the rest of the relationship with them, 46 percent at the same time and 42 percent later. Losing the security conversation forfeits the book.

The willingness-to-pay data cuts the other way, in the incumbent’s favor: 92 percent of those buyers are prepared to pay more for help integrating their security tools, and roughly 70 percent are prepared to pay 10 to 25 percent more. Loyalty in this market is conditional on proof, and buyers will fund the proof. The provider who keeps demonstrating skill gets paid a premium to stay; the provider who stops demonstrating it becomes the 45 percent statistic in someone else’s pipeline review.

In practice the proof is a one-page quarterly artifact, not a project: response times against the contract, incidents closed and time to close, the security posture changes since last quarter, and what the roadmap commits to next. That is an hour of assembly per client per quarter, priced against what the 45 percent statistic costs when it fires inside your own base.

Here is the strange part: the industry does not instrument the fight it is in. The flagship provider survey measures no churn, no retention, no client tenure, and no acquisition channel. No published benchmark separates win rates against incumbents from open-field deals, and no named study quantifies what share of new MSP clients arrive by referral. All of it was searched for this piece; the numbers do not exist in public. Operators are fighting a displacement war with acquisition-era instruments.

Sell like the market actually works

Map the triggers. In a displacement market, the productive question is which accounts just hit a switching condition: a renewal window, a price increase, a service failure at the incumbent, an ownership change on the client side. Most of these are buildable from public and near-public signals: an acquisition announcement, a leadership change on the buyer side, a competitor’s publicized outage, insurance renewal season in the client’s industry, and the oldest signal of all, a contract anniversary. Assign each named target account a trigger owner and a next-review date, the way delivery assigns a technician to a ticket. A trigger list per competitor beats a bigger cold list every quarter, because timing decides displacement deals and volume does not.

Lead with the evidence pack. The number one deal-breaker buyers name is an evidence failure. Certifications, the 24/7 roster, response-time receipts, escalation paths in writing: a proposal in a displacement deal is an audit the prospect runs on your claims, and the incumbent fails it by default if you make the audit easy. Build the pack once as a library and tailor it per deal in an hour: the roster page with real names and shifts, the response-time distribution pulled from the PSA, reference clients matched to the prospect’s industry, and a transition plan that answers the fear the buyer will not say out loud, which is that switching hurts more than staying.

Run the same evidence at renewal. The 2 percent figure means almost no client is structurally safe, so retention is a performance with a quarterly schedule. The same pack that wins a takeout deal, presented to your own base before anyone asks, is the cheapest defense available. The quarterly business review is the natural stage for it. Run the QBR as proof, and the renewal conversation stops being a negotiation about rate and becomes a review of receipts.

Guard the security line like it is the whole relationship. It is: 89 percent of bundle clients leave entirely when the security relationship breaks. Whatever gets monitored most closely in delivery, the security conversation deserves the same instrumentation in the revenue org.

Instrument the displacement. Track which competitor each new logo left and why, the win rate when an incumbent is present, and the save rate after a trigger fires inside your own base. Save rate means: of the accounts where a switching condition occurred, a price increase you initiated, an incident, a stakeholder change, what share renewed anyway. No benchmark exists to compare against, which is a gift. Your own trailing numbers become the standard, and most competitors have never looked at theirs.

One more reason to build the instruments, for operators who plan to face a buyer someday: a displacement-aware book reads differently in a process. Source-of-logo data tells a diligence team the growth is repeatable takeout rather than luck, and a documented save rate turns the retention story from a claim into a table. The same instruments that win quarters survive a data room.

The 12-33-49 shape is not a bad year. It is the structure of the market now. Selling like the market mints first-timers means waiting for buyers who mostly do not exist. Selling like it circulates means picking the moment, arriving with evidence, and holding your own base to the same standard you attack someone else’s with. And the math favors whoever moves first, because 98 percent of the buyers in every competitor’s book say something could make them switch.

The Vertical Premium Is Real. The Proof Is Narrower Than the Pitch.

Gio Olavarria — Wed, 05 Aug 2026 00:00:00 GMT

A healthcare MSP with HIPAA expertise and its BAA templates in order can charge 20 to 40 percent more than a generalist competitor. The range comes from M&A Signal’s 2026 MSP M&A report, updated this March, and the report is blunt about why: compliance complexity creates a client moat and pricing power, and acquirers pay for the expertise. The premium is real, it is priced, and most generalist MSPs walk past it at every renewal.

The pitch for verticalization makes three claims. Specialists charge more. Specialists keep clients longer. Specialists close faster. Go looking for the numbers behind all three, through the industry’s benchmark surveys, the professional-services research firms, and the analysts who price MSPs for a living, and the honest result is that the proof covers one claim. Pricing is measured. Retention has a single decent analog, from software. Speed has nothing. The case for each is below, sorted honestly, because a reader deserves to know which claims are measured and which are reasoned. Most content in this industry never makes the distinction.

Price is the proven part

Start with price. The 20 to 40 percent healthcare figure is the cleanest published number. CT Acquisitions, in its 2026 IT and managed services multiples report, comes at the same effect from the margin side: a vertical specialist can defend gross margin four to eight percentage points above a generalist of the same size, because clients pay for compliance-adjacent expertise. Take the conservative end and run the arithmetic on a $5 million book: four points of gross margin is $200,000 a year, collected every year, without signing a single new logo.

The backdrop makes the premium urgent rather than optional. Kaseya’s 2026 State of the MSP report, a survey of 1,061 providers fielded in November 2025, found the share of clients spending $25,000 or more a year fell from 75% to 41%. Generalist deal sizes are compressing. A premium you can defend is the counterweight.

Why regulated verticals pay it

Industry is the strongest force in IT budgets. Avasant’s Computer Economics benchmarks put IT spending in financial services between 4.4 and 11.4 percent of revenue across the middle half of firms, against 1.4 to 3.2 percent in discrete manufacturing, and state flatly that no factor matters more to IT spending as a share of revenue than industry sector, not company size, not geography. Their own illustration makes the sales case: a small bank can easily spend over 10 percent of revenue on IT, while a large construction firm would be unusual above 2. Celent’s banking research expected retail banks to reach $273 billion in IT spending in 2024, with growth driven by mandatory requirements. Mandatory is the operative word. Demand created by regulators arrives on deadlines, and dated demand is the easiest demand to sell into.

Healthcare shows the premium has a second engine, because it is not a big IT spender. Definitive Healthcare puts hospital IT expense around 2.3 percent of operating expense in 2024. What healthcare has is compliance exposure: HHS’s proposed overhaul of the HIPAA Security Rule, published in January 2025 and not yet final, carries an estimated $9 billion in first-year compliance costs across roughly 1.8 million regulated entities. Defense is the same story with dates attached. DoD’s CMMC rule prices a Level 2 certification assessment at about $101,752 for a small contractor, before any remediation, and the companion acquisition rule counts about 338,000 affected entities, over two-thirds of them small, with assessments phasing in from about 1,100 in year one to more than 18,000 by year three. Every one of those deadlines is a meeting a compliance-fluent MSP gets invited to and a generalist does not.

Insurance pushes from a third side, and the mechanism deserves precise wording: cyber insurance premiums are falling, down 3 percent in Q4 2025 for an eleventh consecutive quarterly decrease per Marsh, while underwriters keep tightening the security controls they require. The pressure on the buyer is the checklist, and the readiness gap is wide. In Coalition’s 2025 survey of a thousand small businesses, 74 percent allocate less than a tenth of their budget to cybersecurity, and 79 percent have been hit at least once in five years.

Then the strange part: almost nobody sells the fix as a product. In the same Kaseya 2026 survey, 71 percent of MSPs report year-over-year growth in cybersecurity revenue, the top category for expansion, yet only 8 percent name regulatory and compliance reporting among their top revenue sources. The demand is documented in federal rulemaking. The supply side has barely productized it.

Churn and speed run on logic

Churn first. No MSP benchmark measures retention for specialists against generalists, so the closest measured evidence comes from software. SaaS Capital’s retention benchmarks, drawn from more than 1,500 private B2B SaaS companies, found in both 2022 and 2023 that vertically focused products held a gross retention edge of about two points over horizontal ones, and no edge in net retention. Read it straight: in the nearest industry where anyone measured, vertical focus buys a modest retention advantage, in exactly the metric acquirers read as durability, and nothing more dramatic. For MSPs the mechanism has to carry the rest of the argument, and the mechanism is switching cost. A generalist running a standard tool stack can be swapped out in a quarter, because the replacement does the same things. Replacing a specialist who knows the client’s practice management system, the examiners’ habits, and the questions the cyber insurer will ask at renewal means re-teaching all of it to a stranger, and the client can price that cost before signing a termination letter.

Cycle time has no measurement anywhere, so reference density has to be argued from the referral evidence. Hinge Research Institute’s referral study with the Exit Planning Exchange, covering 262 professional-services participants, found visible expertise the largest single driver of referrals, accounting for 27.4 percent of the factors that produce them, and the absence of visible expertise the top referral killer, named by 45.5 percent. Referrers motivated by specialized expertise also simply referred more: 8.6 additional referrals against 5.3 for general reputation. That is professional services, not managed services, so carry it as an analog. The mechanism it supports is familiar to anyone who has sold into a vertical: office managers in medical practices talk to each other, law firm administrators sit in the same association meetings, and a specialist’s case study is a phone call the prospect can make rather than a PDF. Nobody has clocked the effect on cycle length, so sell it to yourself as logic, then test it against your own CRM dates.

The exit pays the premium again

The valuation case ran on this site in July under the title Vertical Specialization Is the Cheapest Multiple Expansion Available. The short version, updated against the source: M&A Signal puts the median MSP at 9.0x EBITDA for 2025, with the spread between top-quartile firms and the median widening from roughly 1.5 to 2 turns of EBITDA in 2022 and 2023 to 2.5 to 4 turns in 2024 and 2025. Its value-driver table credits vertical specialization in healthcare, legal, and finance with one to three additional turns. Other analysts size the same premium smaller; across sources the estimates run from under one turn to three. Read the disagreement honestly: the premium shows up in every source, and the measurement is soft. What the deal data agrees on is the shape: concentrated enough in the vertical to be credible, which CT Acquisitions pegs at roughly 40 to 60 percent of revenue, and diversified enough at the client level that no single logo can sink the thesis.

The operating premium and the exit premium compound. The 20 to 40 percent is collected monthly. The turns are collected once, on the whole EBITDA base the monthly premium helped build.

Run it as a revenue program

Pick the vertical the install base already picked. Sort revenue by client industry and the shortlist writes itself. The vertical where eight clients already sit comes with the references built in; the vertical that looks attractive in a market report comes with none.

Re-document before you re-sell. Most generalists already deliver half of a compliance stack and describe none of it in the vertical’s language. A BAA template, an examiner-ready evidence pack, a CMMC readiness checklist: the deliverables are documentation, and the premium starts at the next quote.

Reprice at renewal, not someday. A premium that never reaches a proposal is a blog post, not a strategy.

Build reference density on purpose. One association membership, one speaking slot, and one case study a quarter inside the vertical beat ten generic campaigns, because they reach buyers who already know your clients.

Instrument the claim. Track ARPU, win rate, and revenue share by vertical from the day the program starts. No benchmark in this industry measures the churn and speed claims, which means an operator who instruments them owns a number the market does not have.

The generalist across the street charges 20 to 40 percent less for similar work and calls it competitive. Specialization prices the expertise instead of the hours. That is the entire trick, and it is sitting inside most MSPs’ existing books, waiting to be named.

Your QBR Is a Sales Meeting. Run It Like One.

Gio Olavarria — Tue, 04 Aug 2026 00:00:00 GMT

An MSP that wants a new client pays for the introduction. The blended cost of one IT services lead is $503, per First Page Sage’s May 2025 index, and that buys a lead, not a client. Assume one lead in four ever signs and the marketing cost of a single new logo clears $2,000 before a rep has scoped anything. Now look at the other meeting on the calendar. Four times a year, most MSPs sit down with a client who already trusts them with their infrastructure, already has budget in motion, and already answers their calls. Then they spend the hour on ticket counts.

That meeting is the quarterly business review, and it is the cheapest, highest-intent sales meeting in managed services. Most operators run it as a service report.

Everyone runs it, few believe in it

ScalePad’s 2026 MSP Trends Report put numbers on the habit. Among MSPs running business reviews, quarterly is the most common cadence at 49%, with another 23% reviewing monthly. The typical preparation investment is three to five hours, reported by 41% of MSPs. The self-assessment is the interesting part: 40% rate their own QBRs as very effective, while 44% will only commit to somewhat effective. The industry runs the meeting, invests half a workday preparing it, and fewer than half of operators believe it works well.

The same report suggests the doubters are leaving money in the room. Well-executed QBRs are correlated with higher ARPU and higher client satisfaction in ScalePad’s data, and MSPs who call their reviews very effective, and who are confident showing clients measurable business value, report higher revenue. That is correlation, and self-reported besides. But when the operators who take one meeting seriously keep turning up richer, the meeting deserves a closer look.

Expansion needs a room to happen in

Growth in managed services is shifting toward the accounts MSPs already serve. In the same ScalePad report, growing existing client accounts jumped from the #4 ranked growth driver to #2, cited by 49% of MSPs for 2026 against 35% a year earlier. New client acquisition still ranks first at 60%. But expansion is the fastest climber, and expansion revenue has a geography problem: it needs a real meeting, with a real decision-maker, and the ticket queue is neither. The natural venue is the one recurring session where the client’s leadership, your roadmap, and next year’s budget sit at the same table.

The buyer has been asking for that session. In Kaseya’s 2025 Global MSP Benchmark Report, 64% of MSPs said their clients want guidance on best practices, beyond the tools themselves. A client asking for guidance is requesting a strategy conversation. The QBR is where you either deliver one or confirm that you are a vendor.

The ticket-report trap

The default QBR deck is an operations readout: tickets opened and closed, response times, patch compliance, uptime. All of it is proof of effort. None of it moves a decision. A ticket chart answers a question the client stopped asking years ago, which is whether you are doing the job. The questions that decide renewals and expansion are different: what is exposed, what comes next, what should we budget. An agenda built on ticket data trains the client to read you as a line item, and line items get shopped.

An agenda that sells

No survey publishes the winning agenda, so what follows is operator guidance: the version of the meeting built to produce decisions.

Open on risk, not on tickets. Security is the one subject the client already budgets for: 76% of MSPs say their clients are most concerned about security, per Kaseya’s 2025 benchmark, and 67% count security among their five fastest-growing revenue categories. A risk-gap review, covering what is protected, what is exposed, and what closing each gap costs, is client service and pipeline generation in the same ten minutes. Buyers put money behind the concern: in WatchGuard’s 2026 survey of IT buyers, 47% said they will pay more for 24/7 monitoring and faster response. Every open gap the client accepts in writing today is a project the roadmap carries tomorrow.

Walk the roadmap, with dates. A twelve-month technology roadmap, sequenced, with owners and rough costs, converts you from a maintenance expense into a planning partner. It also schedules revenue: a roadmap line approved in the August review is a Q4 project sold without a single cold touch.

Talk budget before budget season. The review that lands ahead of the client’s fiscal planning cycle is worth double. Bring next year’s technology spend as a draft and let them react. Their finance team hears your numbers before any competitor’s.

Teach them something about their own business. This is the block most agendas skip, and it is the one that changes what the client thinks you are. Bring one exhibit that is about their company, built from numbers outside your PSA: where their IT spend sits against their industry, what an hour of downtime costs their operation, what their sector’s insurers and regulators will ask for next year. Flexera’s 2020 State of Tech Spend report put average IT spend at 8.2% of revenue, with financial services near 10% and healthcare near 5%; a client running far below their industry’s line should hear it from you, with the catch-up path already sequenced into the roadmap. Downtime works the same way: ITIC’s 2024 survey put an hour of downtime above $300,000 for 90% of the firms polled, and those firms skew enterprise, which is exactly why the useful move is handing the client their own number, computed from their payroll and their revenue per hour. A generic stat is a slide. Their number is a decision.

End with decisions. A review that ends with “any questions” produced a presentation. A review that ends with a project approved, a risk accepted in writing, or a date committed produced revenue motion. Count the decisions per review and you have the only QBR effectiveness metric that matters.

The ticket data still travels, in an appendix, available on request. Proof of work belongs in the room. It stopped deserving the agenda.

Insight is what buyers reward

The advice to teach is not folklore. Corporate Executive Board research from 2011, the study behind The Challenger Sale, found that more than 53% of what drives B2B customer loyalty is the sales experience itself: what the seller brings to the conversation, with teaching the customer something new about their own business at the center of the winning profile.

Gartner reached a matching conclusion from the buyer’s side in 2019. Buyers are saturated with vendor information, most of it individually credible and much of it contradictory. When they cannot make sense of what they encounter, Gartner found buyers 153% more likely to settle for a smaller, less disruptive purchase than they had planned. Read that as an operator: a confused client shrinks the deal. In the same research, 80% of sellers who practiced what Gartner calls sense making, helping the buyer evaluate and weigh the information in front of them, closed high-quality, low-regret deals. The QBR is an MSP’s standing appointment to be that seller: the one hour a quarter where the noise about spend, threats, and tooling becomes a clear picture of what this client’s business should do next.

Cadence is a lever

One more ScalePad finding worth sitting with: the top performers in the report run their reviews monthly. Monthly for the top account tier, quarterly for the middle of the book, annual for the tail is a defensible default. The principle underneath: review cadence is a revenue decision, and most of the industry prices it like a calendar courtesy.

The meeting is already paid for

Frederick Reichheld’s research at Bain, cited in Harvard Business Review, found that a 5% improvement in customer retention lifts profit by somewhere between 25% and 95%. The figures are decades old and the range is wide, and the direction has survived every re-examination: kept clients compound. The QBR is where keeping and growing happen on purpose, at the marginal cost of a few prep hours, with a counterparty who already buys from you. Compare that with the $503 the next lead costs before anyone returns your email.

Most MSPs give away their best sales meeting four times a year. Price it, prepare it like the pipeline depends on it, and it becomes the one meeting on the calendar that reliably pays for the quarter.

Churn Is a Contract-Design Problem

Gio Olavarria — Fri, 31 Jul 2026 00:00:00 GMT

An MSP that loses 10% of its recurring revenue in a year has to sell 10% just to end the year flat. That replacement revenue is the most expensive revenue there is. The blended cost of one IT services lead runs $503, per First Page Sage’s May 2025 index, and that buys a lead, not a client. Leads do not all close. Even if one in four turns into a signed agreement, a generous rate for replacement work, the lead spend alone on one new client clears $2,000 before discovery calls, proposals, and the weeks a sales cycle takes. Every point of churn puts a rep on a treadmill that produces nothing the P&L can keep.

Churn gets discussed as a service problem: tickets, response times, the relationship gone quiet. Some of it is. But by the time service complaints surface, most of the exits were already designed in, at signing, in an agreement nobody has read since.

Nobody is measuring the leak

Start with an uncomfortable pair of facts. ScalePad’s 2026 MSP Trends Report found that only a little over one-third of MSPs track client churn at all, even though losing contracts hits MRR directly. And when operators go looking for an industry benchmark to compare against, there isn’t one: I went looking. No major industry report publishes an average MSP churn rate. The figures that circulate online, a confident 12% here, a 10-to-15% range there, trace back to blog posts that cite nothing. The industry’s most important leak has no agreed gauge.

That absence matters less than it seems, because the benchmark that pays is your own: churned MRR over starting MRR, tracked monthly, alongside logo churn so a hundred small exits can’t hide inside one big save. Two-thirds of the industry cannot produce that number today. Producing it is a one-spreadsheet project.

The market is restless

Whatever your churn is now, the environment is not working in your favor. In WatchGuard’s 2026 survey of IT and cybersecurity buyers, 58% said they plan to switch providers within the next three years. That is stated intent, not realized churn, and buyers say things in surveys they never do. But it describes the temperature of the market: a majority of the people signing managed services agreements consider the relationship provisional.

You do not control the market’s restlessness. You control the agreement it collides with.

The contract is the retention system

MSP agreements are nearly universal: in an MSP Success reader survey from January 2025, 95% of MSPs said they run on client contracts, with 60% offering one-year terms, 54% offering three-year, and 38% offering monthly arrangements. So the instrument is already in everyone’s hands. What separates books that hold from books that leak is what is written inside it. Five terms do most of the work.

Match the term to the relationship. An annual contract schedules an annual renegotiation, and a renegotiation is an exit ramp: a date on which the client is invited to shop. Month-to-month is a permanent sales cycle. Longer terms trade some pricing flexibility for stability, and the trade is usually worth making for the accounts you cannot afford to lose. The point is not that one term is right; it is that term length is a churn decision, and most MSPs price it as if it were only a billing decision.

Write onboarding into the agreement. The first 90 days decide how the next three years feel. Put the deliverables in the contract: documentation completed, monitoring live, backup tested, first review scheduled. When onboarding is contractual, it happens; when it is aspirational, it competes with tickets and loses. A client who watched you hit every committed milestone in the first quarter renews differently than one who is still waiting for the network diagram.

True up the seats. On per-user agreements, headcount shrinkage is churn nobody noticed: the logo stays, the revenue leaks. A true-up clause makes contraction visible on a schedule, which does two things: it protects the revenue line, and it hands you an early-warning signal. An account shedding seats is an account with a story you need to hear about long before the renewal date.

Put the review cadence in writing. A committed quarterly review in the agreement means the relationship has a rhythm that does not depend on anyone’s calendar discipline. The client who sits in four business reviews a year is hearing your roadmap, seeing the risk register shrink, and watching the value accumulate. The client who has not seen you since onboarding is comparing you to a line item.

Build the escalator in. Nothing sends a client shopping like a surprise renewal increase. A contractual price escalator, modest, automatic, disclosed on day one, removes the annual shock conversation entirely. Renewal should be a non-event. The moment it becomes an event, it becomes an evaluation.

The math on the other side

The reason to do this work is what retention is worth. Frederick Reichheld’s research at Bain, cited in Harvard Business Review, found that improving customer retention by 5% lifts profits by somewhere between 25% and 95%. In a recurring revenue business the mechanism is compounding: every contract that holds is margin that arrives next month without a lead, a proposal, or a discount. It is the same logic that made existing-account expansion the industry’s fastest-climbing growth driver, and churn is its mirror image. A leak repairs nothing on its own.

The operators who win this are not the ones with the fewest service complaints. They are the ones who treated churn as a design input: measured it monthly, wrote the retention mechanics into the agreement, and made leaving harder than staying, not with lock-in tricks but with a contract that keeps proving its value on schedule. Fix the bucket before pouring faster.

The Growth Engine Moved

Gio Olavarria — Tue, 28 Jul 2026 00:00:00 GMT

Every January the MSP industry gets a fresh look at itself. In ScalePad’s 2026 MSP Trends Report, published in January, the top-ranked growth driver is the familiar one: acquiring new clients, cited by 60% of MSPs. The number worth attention sits right below it. Growing existing client accounts jumped from the #4 growth driver to #2, named by 49% of MSPs this year against 35% last year.

That is a big one-year move for a survey ranking that usually shifts a point or two at a time. Half the industry has noticed something the math has said for years: the cheapest revenue an MSP will ever close is sitting inside its install base.

The rest of the board is worth reading too. Offering new services came in third at 39%, improving marketing efforts fourth at 38%, making service delivery more efficient fifth at 34%, partnership opportunities sixth at 30%, and acquiring another MSP last at 20%. Most of those drivers need new budget before they produce a dollar. Expansion starts from revenue you already earned and a relationship you already paid to build.

What net-new actually costs

First Page Sage tracks cost per lead across industries, and its May 2025 update puts the blended figure for IT and managed services at $503, with paid channels at $617 and organic at $385. That money buys a lead, not a client. Between the lead and a signed agreement sit qualification, discovery, a proposal, references, and however many weeks the sales cycle runs. Every stage leaks.

The broader benchmark most operators reach for comes from a 2014 Harvard Business Review piece: acquiring a new customer costs five to 25 times more than retaining an existing one. A caveat belongs next to that number: HBR states it without citing an underlying study, so treat it as directional. The research the same article does cite, Frederick Reichheld’s work at Bain, found that improving retention by 5% lifts profits by 25% to 95%. Direction and magnitude point the same way. Selling to clients who already trust you costs less than convincing strangers.

The number most MSPs cannot see

Expansion has a visibility problem. The same ScalePad report found that only 44% of MSPs track net revenue retention, and only a little over one-third track client churn. NRR is the metric that tells you whether the existing book grows or shrinks on its own: starting MRR plus expansion, minus churn and contraction, divided by starting MRR. Above 100%, the base compounds before a single new logo signs. Below 100%, new sales are refilling a leaking bucket. An MSP that does not measure NRR is guessing at both.

Industry economics make that blind spot expensive. Service Leadership’s benchmark of 2025 performance, published this June, shows IT solution provider revenue grew 9.6% while adjusted EBITDA grew 17.1%. Profit is growing nearly twice as fast as revenue, which tells you the winners are selling more efficiently. Expansion is the most efficient revenue there is: the lead cost is zero and the delivery relationship already exists.

Why the motion stalls

Half the industry now says expansion matters. Far fewer run it as a motion, and the failure pattern is consistent enough to name.

Nobody owns the number. Expansion revenue sits between account management and sales and often reports to neither, so it becomes everyone’s second priority. Compensation pays for hunting: when the plan pays more for a dollar of net-new than a dollar of expansion, rep energy follows the plan, whatever the strategy deck says. The QBR gets colonized by service: ticket recaps and SLA charts fill the agenda because they are easy to produce, and the one meeting that should open expansion conversations closes them instead. And the whitespace itself is invisible: the PSA knows what each client buys, the RMM knows what each client runs, and almost nobody joins the two tables.

These are design problems, not talent problems, and design problems have known fixes.

Map the whitespace

Build a grid: accounts down one side, the service catalog across the top, a mark in every cell an account already buys. The empty cells are the expansion pipeline. That is the whole concept, and a spreadsheet is enough to start.

The useful version pulls from systems you already run. Agreement lines from the PSA say what each client pays for. The RMM inventory says what they actually operate. The delta between the two is your first pass at whitespace. Then rank the cells on two axes: fit, meaning how much the gap costs the client to leave open, and readiness, meaning contract anniversaries, budget cycles, and where the relationship stands today. Take the top ten, put an owner and a date on each, and review the grid quarterly.

Seat counts belong in the same review. Per-user billing is now the predominant model for about a fifth of MSPs, per Kaseya’s 2023 benchmark, with a blended per-user and per-device model at another quarter. On those contracts, headcount growth inside an account is expansion revenue nobody has to sell, and headcount shrinkage is churn nobody noticed.

Run technology alignment reviews

Write down a reference standard: what a well-run environment looks like for the segments you serve. Security stack, backup coverage and tested restores, hardware age, licensing posture, identity and M365 configuration. Then assess every client against it on a set cadence, twice a year for most books.

Score each line red, yellow, or green, and resist the urge to editorialize. The power of the document is that it reads as engineering, not sales. Every red cell is a risk conversation with a project attached, and the conversation opens with the exposure, not with a product: the firewall is end of life, the restore has never been tested, the tenant has no conditional access. Done this way, the review produces the most honest pipeline an MSP can own, because the client watched it get built.

Make the QBR earn its seat

The quarterly business review is the highest-intent meeting on the calendar: the client shows up expecting to talk about their business. Most MSPs spend that intent on ticket counts.

Structure the agenda in three parts instead. The scorecard from the alignment review. The risk conversation the red cells demand. A twelve-month roadmap with a budget window attached. Close every QBR with a named next step that has a number on it: a project scoped, a proposal date, a seat-count change, a renewal term. One discipline protects all of it: the service recap gets ten minutes at the top and no more. If tickets colonize the hour, the sales meeting you were owed becomes a status call. Handled well, four QBRs a year become four expansion conversations the client asked for.

The motion scales up-market

None of this is small-business-only advice. Co-managed IT, where the MSP runs monitoring, patching, tooling, and after-hours coverage alongside an internal team, is a growing share of the business: in Kaseya’s 2025 Global MSP Benchmark, 61% of MSP executives said their co-managed revenue grew year over year.

A co-managed account carries whitespace just like a fully managed one, usually more of it, because the surface area is bigger: the security layer internal IT does not want to staff, the backup estate nobody has tested, the license sprawl a 400-seat company accumulates. The map is different but the motion is identical. Know what they run, know what they buy, and put the gap on an agenda.

Instrument it

Three numbers tell you whether the motion is real. Expansion MRR: new monthly recurring revenue added inside existing accounts, tracked as its own line, never blended into total new business. Net revenue retention: the compounding check, defined above; watch the trend, not a single reading. Whitespace coverage: the share of your top accounts with a current alignment review and a mapped grid.

The first number says the motion produces. The second says the base compounds. The third says the inputs exist. An MSP that looks at those three monthly will not need a survey to tell it where growth comes from.

Keep hunting, start farming

None of this argues for abandoning net-new. Grand View Research sizes the managed services market at $401.2 billion in 2025, headed for $437.3 billion in 2026 and growing near 10% a year. There are plenty of new logos to win. That said, when half an industry moves existing accounts into its top two growth drivers in a single year, the signal is hard to miss. The growth engine moved. The operators who win the next stretch will be the ones who built the motion to run it.

Black-Box AI Won't Survive Client Diligence

Gio Olavarria — Tue, 21 Jul 2026 00:00:00 GMT

Simon Chappel, CEO of Assured Data Protection, made a prediction for 2026 that reads less like a forecast and more like a procurement memo: “Organizations will no longer tolerate black-box AI.”

The interesting part is where that intolerance shows up first. Not in regulation, and not in public opinion. In vendor diligence, where it’s already happening.

The questionnaire is coming for everyone

Vendor risk assessment has a gap you could drive a truck through. Grip Security’s research found that 98 percent of organizations use SaaS applications with embedded AI, while fewer than 30 percent have any formal process for assessing AI vendor risk. For a few years that gap was invisible, because nobody was asking.

Buyers have started asking. Security questionnaires that spent a decade fixated on encryption at rest and SOC 2 scope now carry new sections: which AI models process our data, is our data used for training, who reviews AI-influenced decisions, how do we opt out. The companies sending those questionnaires mostly can’t evaluate the answers yet. That doesn’t matter. A vendor that can’t answer at all fails the smell test, and in a competitive deal, the vendor with clean answers wins the tiebreak.

This is how SOC 2 spread. Not because every buyer understood trust service criteria, but because asking for the report became free and not having one became expensive. Explainability is on the same path, moving from compliance checkbox to sales objection.

The certification wave has started

The standard emerging under this is ISO/IEC 42001, the first international management system standard for AI governance. It covers the unglamorous machinery: AI risk management, transparency requirements, human oversight, lifecycle monitoring. Certification signals that a vendor’s AI usage is documented and governed rather than improvised.

Watch who’s getting certified. Presidio, a global IT solutions integrator, announced its ISO 42001 certification on July 15, 2026. Its CISO, Greg Hedrick, framed the point precisely: the certification confirms that AI initiatives “are not ad hoc experiments” but run inside a management system.

When a company that size certifies, it isn’t chasing a plaque. It’s answering questions its enterprise customers already ask, and it’s setting the bar its competitors will be measured against. Requirements like this roll downhill. The integrator certifies, then the integrator’s procurement team starts asking its own suppliers, and within a couple of budget cycles the questionnaire lands on the desk of a 40-person MSP that has never inventoried its own AI usage.

Regulation reinforces the direction without driving it. The EU AI Act’s transparency obligations take effect in August 2026, even after the omnibus agreement deferred the high-risk system deadlines to December 2027. Any client with European customers, parents, or partners inherits those expectations early.

MSPs sit on both sides of this

For an MSP, the black-box problem cuts in two directions, and both of them are worth money.

The first direction is defensive. Your own stack is full of AI now: RMM platforms with AI features, ticket triage automation, documentation assistants, the Copilot licenses your own engineers use against client environments. When your client’s new CFO orders a vendor review, or their cyber insurer sends the renewal questionnaire, you are the vendor being diligenced. An MSP that answers the AI section with silence or hand-waving is inviting a competitor into the account.

The fix is cheap relative to the risk. Inventory the AI in your own delivery stack. Write the data-flow statement for each tool: what client data it touches, where it goes, whether it trains anything. Put human oversight in writing for anything that acts on client systems. Package it as a one-page AI transparency summary that rides along with your standard security documentation. The first time a client’s auditor asks and you hand it over the same day, you’ve converted a threat into proof of maturity.

The second direction is the revenue line. Every client you serve that sells into larger companies is about to face the same questionnaire, with less preparation than you have. The mid-market manufacturer with two AI-enabled products, the law firm quietly using a research assistant, the healthcare group whose intake team lives in a chatbot: none of them can currently answer what models they use and what data flows in.

Diligence readiness is a packageable service. AI inventory, data-flow mapping, policy drafting, questionnaire response support, and a path to ISO 42001 alignment for clients whose buyers will eventually demand it. The skills are the ones MSPs already use for SOC 2 prep and cyber insurance applications. The subject matter is new; the motion is not.

Transparency as a wedge

There’s a competitive reading of this that goes beyond defense. In any deal where you’re up against another MSP, the AI section of diligence is now a place to win.

Most of your competitors will treat AI questions the way vendors treated security questions in 2015: something to get past rather than something to lead with. If your proposal includes your AI transparency summary unprompted, names the AI in your stack, and explains the oversight around it, you’ve reframed the conversation. The prospect’s takeaway is that you run a tighter shop, and the incumbent suddenly has questions to answer it never prepared for.

Chappel’s prediction will look obvious in two years, the way “buyers will demand SOC 2” looks obvious now. The window that matters is the one before it becomes obvious, when transparency still differentiates because most vendors can’t produce it on request.

Black-box AI isn’t a technology problem for the MSP market. It’s a trust problem, and trust is the product MSPs have always actually sold. The ones that document theirs first will take deals from the ones that didn’t.

The First Public AI-Model Breach Will Reprice Every MSP

Gio Olavarria — Tue, 21 Jul 2026 00:00:00 GMT

Michael Gray, the CTO at Thrive, made a prediction for 2026 that most MSP executives read and moved past: a coming “moment of truth” when a major public breach of an AI model forces companies to treat AI as critical infrastructure.

It’s worth stopping on that one, because the mechanics behind it are already proven. The only thing missing is the headline.

The quiet breaches have already happened

In June 2025, researchers at Aim Security disclosed EchoLeak (CVE-2025-32711), a zero-click prompt injection vulnerability in Microsoft 365 Copilot. An attacker could embed instructions in an ordinary email. When a user later asked Copilot a question that caused it to retrieve that email, the embedded instructions executed and exfiltrated confidential data. No click, no attachment, no credential theft. The user did nothing wrong except use the assistant as designed.

In April 2026, Vercel disclosed a breach that started in February. An employee at Context.ai, an AI vendor in Vercel’s supply chain, was infected with infostealer malware. The attacker used stolen OAuth tokens, including a Google Workspace integration that had been granted broad permissions, to move into Vercel’s systems and stay there for roughly two months. Source code, API keys, and 580 employee records ended up listed for sale at $2 million.

Neither event produced the repricing Gray is talking about. EchoLeak was patched before public exploitation was confirmed. Vercel was one company’s bad quarter. But look at what the two incidents prove together: AI assistants can be turned into exfiltration channels by anyone who can send an email, and AI vendor integrations create standing access that survives long after anyone remembers granting it.

That combination, applied to a company whose name your clients’ CFOs recognize, is the moment of truth.

Clients are adopting faster than anyone is governing

The exposure math is lopsided. Metomic’s data security research found 68 percent of organizations have experienced data leaks tied to AI tool usage, while only 23 percent have a formal security policy addressing it. Gartner found that only 24 percent of enterprises maintain a dedicated AI security governance function. Cyberhaven measured what employees actually paste into chatbots and found 11 percent of it is confidential.

Now narrow that to the mid-market companies MSPs serve. These are businesses without a CISO, without a security committee, and often without anyone who could produce a list of the AI tools in use across the company. Their employees adopted ChatGPT, Copilot, and a long tail of AI-enabled SaaS the same way they adopted Dropbox in 2012: individually, quietly, and without asking.

The MSP is the only party in that relationship positioned to see the whole picture. Which is why the top questions MSPs are asking each other, according to Cynomi’s June 2026 analysis of practitioner communities, are things like “Are clients leaking sensitive data into AI tools?” and “How do we say no to client AI requests without losing the account?”

Those are governance questions. The industry is circling the offering without naming it.

What repricing actually looks like

When the public breach lands, the response won’t be panic about AI. It will be a sudden demand for the boring apparatus of control, arriving from three directions at once.

Insurance carriers will add AI governance questions to cyber renewal applications, the way they added MFA questions after the ransomware wave of 2020-21. Answer them badly and premiums move, or coverage carves out AI-related incidents.

Procurement and vendor-risk teams will push AI questionnaires down the supply chain. Fewer than 30 percent of organizations have a formal AI vendor risk process today, according to Grip Security’s research, while 98 percent use SaaS with embedded AI. That gap closes fast once a headline provides the budget justification.

Regulators are already moving on their own schedule. The EU AI Act’s transparency obligations take effect in August 2026 even after the omnibus agreement pushed the high-risk system deadlines to late 2027. US clients with European operations or customers will feel that pull regardless of what Washington does.

Every one of those pressures lands on companies that cannot answer basic questions about their own AI usage. Someone has to do that work. The only question is whether it’s their MSP or a stranger.

The offering to build now

The service line writes itself once you stop thinking of it as an AI product and start thinking of it as governance delivered through tools you already run.

Start with an AI usage audit. Inventory the AI tools in the environment, the browser extensions, the OAuth grants, the SaaS platforms with embedded AI features. Map what data flows into each. This is discovery work your RMM and identity tooling already supports, and the deliverable shocks most clients into action on its own.

Second, a written acceptable-use policy. Which tools are approved, which data classes never leave the building, who approves new AI vendors. Most clients have nothing. A two-page policy beats a blank stare in front of an insurance auditor.

Third, technical guardrails. DLP rules covering AI endpoints, permission scoping on AI integrations, and a standing review of OAuth grants. The Vercel breach traveled through an over-permissioned integration that nobody was watching. That review is billable work every quarter.

Fourth, fold ongoing AI risk monitoring into your vCISO or managed security offering. New tool requests, vendor assessments, incident tabletop exercises that include an AI scenario. This turns a one-time project into recurring revenue.

None of this requires hiring AI researchers. It requires the compliance and security muscles MSPs already have, pointed at a category clients haven’t organized yet.

Position before the headline

After the breach goes public, this market gets loud. Every security vendor will ship an AI governance SKU within a quarter, and buyers will be rightly suspicious of anyone who discovered the problem the same week they did.

The MSPs that win that moment will be the ones with an offering already on the price list, reference clients already governed, and a methodology they can show. When a client calls in a panic asking whether they’re exposed, the answer “here’s the audit we ran for you in Q3, here’s your policy, here’s what changed since” is worth more than any marketing budget.

Gray’s moment of truth is coming on someone else’s timeline. The offering that answers it can be built on yours.

Vertical Specialization Is the Cheapest Multiple Expansion Available

Gio Olavarria — Tue, 21 Jul 2026 00:00:00 GMT

The median MSP changed hands at 9.0x EBITDA in 2025. Top-quartile firms commanded 2.5 to 4.0 turns more than median peers, a spread that has roughly doubled since 2022-23. Every owner and every PE operating partner looks at that gap and asks the same question: what moves a firm from one quartile to the other?

Most of the honest answers are expensive. Recurring revenue mix takes years of contract migration. Scale takes acquisitions. Margin expansion takes operational surgery. But one lever in the 2026 valuation data is priced like a rounding error and pays like a strategy: vertical specialization.

What the data says focus is worth

M&A Signal’s 2026 MSP report quantifies what buyers pay for industry depth, and healthcare is the cleanest case. Healthcare IT specialization adds 1 to 3 turns of EBITDA at exit, and healthcare-focused MSPs charge 20 to 40 percent more than generalist competitors for equivalent endpoint coverage. The compliance complexity that scares generalists away is exactly what creates the client moat and the pricing power.

Legal IT earns its premium from bar association data-security guidance that keeps tightening, plus a fresh wave of AI infrastructure demand as firms adopt research and drafting tools they don’t know how to govern. Financial services rides a compliance-driven demand surge as the SEC, FINRA, and NYDFS keep raising minimum cybersecurity standards for firms that used to treat IT as overhead.

The common thread is regulatory gravity. Wherever a regulator makes bad IT an existential problem, clients stop shopping on price, switching costs rise, and the MSP that speaks the compliance language stops competing with the two-man shop down the street. The report’s phrasing is blunt: vertical depth creates a moat that holds against generalist platforms.

Run the arithmetic on a $3M EBITDA firm. Two additional turns is $6M of enterprise value. The investment required to earn it, which I’ll get to below, is a fraction of what that same $6M would cost through acquisitions or headcount.

The concentration trap

Before the playbook, the caveat that kills deals. Client concentration is the most common valuation reducer in MSP transactions, and the penalties are severe: a book where five clients make up more than half of revenue gives back 2 to 3 turns, per the same 2026 data. The books that attract the most competitive bidding keep every client below 5 to 8 percent of revenue.

Verticalizing done lazily walks straight into this. The temptation is to land two whale accounts in the target industry, let them grow to a third of revenue, and call yourself specialized. A buyer will call you something else: risky.

The discipline is to verticalize the offering while diversifying the logos. Twenty healthcare clients at 4 percent each is a moat. Three healthcare clients at 15 percent each is a hostage situation. Same industry focus, opposite valuation outcomes. Set a concentration ceiling before the vertical push starts and let it govern pacing: when an anchor account grows too large, that’s the signal to accelerate new-logo acquisition in the vertical, not to celebrate.

Verticalizing without rebuilding delivery

The expensive mistake is treating specialization as a delivery project. It mostly isn’t. Your RMM, your PSA, your security stack, and your service desk carry over nearly untouched. What changes sits in a thinner layer on top.

Pick the vertical from your existing book, not from a market map. Pull revenue by industry. Almost every generalist MSP discovers it already has five or more clients in one regulated industry, acquired by accident through referrals. That accidental cluster is your beachhead: reference clients, staff who already know the workflows, and proof you can service the segment.

Build the compliance wrapper. This is the real product. For healthcare it’s HIPAA risk assessments, BAA management, and audit-ready documentation. For financial services it’s mapping your existing security services to SEC and FINRA expectations and packaging the evidence. For legal it’s aligning with bar guidance and the client-confidentiality story. You’re not inventing new services; you’re re-documenting existing ones in the language the client’s regulator speaks, and charging for the translation.

Make a small number of vertical-specific stack decisions. The EHR integrations you support, the document management systems you know, the trading-adjacent platforms you’ll touch. Depth in five industry applications beats shallow familiarity with fifty.

Hire one anchor domain expert. A practice administrator turned account manager, a compliance officer turned vCISO. One credible industry hire changes every sales conversation, because prospects hear their own vocabulary.

Then accept that the hard part is the sales motion, not the tech stack. Verticalizing means walking away from off-vertical prospects, rewriting the website so the industry sees itself, showing up at the industry’s own events instead of generic IT channels, and building case studies with compliance outcomes rather than uptime stats. Most verticalization efforts fail here, in the marketing and qualification discipline, long before delivery is ever tested.

One timing note for anyone eyeing the defense vertical: the opportunity is real, but the regulatory clock just moved. CMMC’s Phase II third-party assessment requirement, originally set to begin in November 2026, was paused in July 2026 for 60 days while a reform task force reworks the program. Contractors still carry their NIST 800-171 obligations under existing DFARS clauses, so sell the underlying security work on its own merits rather than selling a deadline that may shift again.

The exit story writes itself

Eighteen to twenty-four months of this discipline changes what a buyer sees in the data room. Instead of a generalist book competing on responsiveness, they find an MSP with documented compliance methodology, industry reference density, pricing 20 to 40 percent above market with retention to match, and a client list where no single loss dents the thesis.

Buyers pay for growth they can predict. A vertical moat makes revenue durable and expansion legible: same playbook, adjacent geography, adjacent sub-segment. That’s why the premium exists, and why it has survived even as headline multiples cooled from their peak.

The 9.0x median and the 2.5 to 4.0 turn spread will both move with the market. The gap between focused firms and generalists is the part you control. Of everything on the value-creation menu, focus remains the cheapest item, and the market is currently paying one to three turns for it.

The Revenue Architecture Problem Nobody Talks About

Gio Olavarria — Sat, 04 Apr 2026 00:00:00 GMT

Walk into the average PE-backed MSP or IT services firm and you’ll see a recognizable pattern: a sales leader, a handful of reps, a CRM nobody trusts, and a revenue number that should be higher given the market and the effort. The team is rarely the problem. The system underneath it usually is.

Most services companies have built a sales organization. Very few have built a revenue architecture.

The distinction matters. An organization is people and titles. An architecture is the infrastructure that turns business strategy into predictable, repeatable revenue. Having a boat gets you nothing without navigation, a crew, and maintenance. The boat is an asset. The rest of it is what produces results.

This gap between what these companies spend on sales talent and what they get back is a hidden tax on PE-backed services portfolios. It costs hundreds of millions annually across the industry, and most leadership teams can’t see it.

The typical failure pattern

The cycle runs like this:

You hire a strong sales leader or VP of Sales. She builds a team of competent reps. For the first 6 to 9 months, growth accelerates. Then the curve flattens. Deals take longer to close. Win rates decline. Forecast accuracy becomes a punchline in board meetings.

The board’s response is predictable: “Hire better salespeople. Implement a new CRM. Tighten forecasting.”

So the company hires again. Implements the CRM again. Maybe brings in a sales consultant. For a brief window, things improve. Then the pattern repeats.

What’s missing is hard to see because it’s neither a person nor a tool. It’s the underlying system that turns leads into pipeline into revenue. Without it, sales depends on individual talent instead of repeatable process. And individual talent eventually hits a ceiling, or leaves.

The infrastructure gap

Services companies that miss this gap typically lack four things.

Pipeline analytics. Most MSPs have a CRM but no real pipeline. They know how many opportunities sit in “negotiation,” but they don’t know conversion rates by stage, sales cycle length by customer segment, or win-loss patterns by solution type. They can’t predict revenue to within 20%. They can’t tell you which deals are actually going to close.

Lead scoring and qualification. Without formal criteria, reps qualify leads on gut feel. One rep works a prospect for eight months that should have been disqualified in week two. Another passes on qualified accounts because they “don’t feel right.” The company loses predictable deal flow.

Process documentation. The top rep has a process that works, and it lives in her head. When she leaves, that process walks out the door with her. Every new rep has to reverse-engineer success from scratch. Sales becomes tribal knowledge.

Enablement and accountability. Reps don’t know what good looks like. There’s no consistent messaging, no objection-handling playbooks, no deal-review discipline. Managers spend their time firefighting instead of coaching. Training, when it happens, is ad hoc and rarely reinforced.

The result: revenue that plateaus, forecasts that miss, and board meetings that devolve into finger-pointing about “market conditions” or “quality of the pipeline.”

What real revenue architecture looks like

Companies that have solved this problem operate across four integrated layers.

The metrics layer defines what success looks like and how you’ll measure it. Not “close more deals” but: average sales cycle by segment, conversion rate by pipeline stage, customer acquisition cost by channel, lifetime value by cohort, and the leading indicators that predict quarterly attainment. It’s a dashboard that tells you, in early March, whether you’re going to hit April or September quota.

The process layer is the repeatable sequence of activities that moves a prospect toward a buying decision. Defined stages (discovery, needs analysis, proposal, negotiation, close) with explicit entry and exit criteria. Playbooks for the biggest objections and the biggest opportunities. A cadence for pipeline reviews, forecast calibration, and deal coaching. This layer is written down and enforced.

The enablement layer makes sure every rep has the tools, knowledge, and accountability to execute the process. One-on-ones focused on deal quality, not just volume. Messaging that differentiates in a crowded market. Recorded call examples of what good discovery sounds like. Role-plays and objection drills. When a rep joins, she inherits success instead of reverse-engineering it.

The technology layer supports the other three, never the reverse. The CRM doesn’t dictate the process; the process is reflected in the CRM. Reports come from data captured according to the metrics framework. Workflows automate the repeatable parts (task assignment, forecast rollup, pipeline trending) so humans focus on relationship building, deal strategy, and coaching.

These four layers work together. Remove one and the others weaken.

The ROI of getting it right

According to Forrester research, organizations with documented, repeatable sales processes generate 28% more revenue per salesperson than those without them. They also keep experienced reps longer (fewer cycling out every 18 months), ramp new hires faster (productive in 4 to 5 months instead of 9 to 12), and forecast more accurately (variance under 10% instead of 30%+).

For a PE-backed MSP with $50M in revenue and 15 sales reps, a 28% improvement in revenue per rep is $23M in additional annual revenue. Even with conservative assumptions about incremental cost of goods sold, that’s $15M to $18M in additional EBITDA. That translates to 1.5 to 2.0x multiple expansion on exit.

The investment required (a dedicated revenue operations hire, process documentation, CRM optimization, and ongoing discipline) runs $500K to $1M annually. The math is lopsided in your favor.

Why this gets missed

PE firms underinvest here because revenue operations is less visible than hiring a new sales leader or rolling out a new tool. Nobody gets excited about stage-exit criteria. The work doesn’t fit neatly into a 100-day plan, and it pays off in quarters, not weeks.

Which is exactly why the edge is still available. Companies that build revenue architecture get growth that survives leadership changes, market shifts, and competitive pressure, because the machine keeps running when any one person walks out.

For PE firms managing services portfolios, this is the bet worth making before the next sales hire and before the next CRM migration. Those treat symptoms. The architecture is the cure.

The Revenue Architecture Problem Nobody Talks About

Gio Olavarria — Sat, 04 Apr 2026 00:00:00 GMT

PE-backed services companies have sales teams but no revenue system. Here's what real revenue architecture looks like—and why it matters.

What PE Operating Partners Get Wrong About AI in Portfolio Companies

Gio Olavarria — Wed, 01 Apr 2026 00:00:00 GMT

The AI mandate arrives predictably. A PE firm acquires an MSP or IT services company and, within 90 days, the operating partner sends a memo: “We need to implement AI to reduce cost and improve efficiency. Here’s a consultant to help.”

The company does what follows: They hire the consultant. They hold an all-hands on “AI transformation.” They pilot a chatbot, experiment with an AI coding assistant, maybe deploy an automated scheduling tool. The demo looks impressive in a board meeting.

Then nothing happens. The chatbot answers 40% of questions correctly and frustrates customers. The coding tool produces code that requires more review than it saves. The scheduling tool runs for six months, then gets turned off because adoption was low.

The team is demoralized. The operating partner is frustrated. The AI initiative becomes a scar instead of an advantage.

This is the wrong mental model, and it’s costing PE portfolios tens of millions in unrealized value.

The cost-cutting trap

The fundamental mistake is framing AI as a replacement technology. “How can we do X with fewer people?” is the question that leads to implementations that threaten the people who have to use them, that oversell and underdeliver, and that create organizational cynicism around technology investment.

Better operators ask: “How can we do X more effectively with AI amplifying the expertise we already have?”

Those two questions produce different roadmaps, different budgets, and different failure modes.

In services companies (MSPs, IT consulting firms, managed security providers), the real competitive advantage is human judgment, not raw labor. It’s the experienced technician who diagnoses a problem in a client’s infrastructure and recommends a solution. It’s the sales engineer who understands the customer’s business deeply enough to position a complex proposal. It’s the delivery manager who anticipates project risk before it becomes visible to the client.

AI deployed correctly amplifies those functions. AI deployed as a replacement for them fails, and takes organizational trust down with it.

Amplifier vs. replacement

The distinction is worth codifying because it changes how you evaluate, build, and fund AI initiatives in a services portfolio.

The replacement frame says: “This task currently requires a human. Can a machine do it instead?” You’re looking for automation, head count reduction, and labor arbitrage. You’re also taking on real risk, because you’re asking a system to operate independently in domains where judgment matters. The track record is poor.

The amplifier frame says: “This human needs better information, faster decisions, or less administrative burden to perform their core function. Where can AI provide that?” The human remains accountable. The AI provides leverage.

An example in services: The sales engineer currently spends 30% of her time researching competitors to position deals. She does this research in her head, from memory, talking to peers. It’s inconsistent. The best reps build better competitive intelligence than average reps.

An amplified approach: Implement a system that ingests public information about customer accounts, competitor positioning, recent analyst reports, and proposal outcomes. When the sales engineer enters a deal, the system surfaces relevant competitive intelligence, win-loss patterns from similar deals, and gaps in the customer’s current solution. The sales engineer reviews this in 10 minutes instead of spending three hours researching. She makes a more informed recommendation. She closes faster. Her judgment is better, not eliminated.

Ask the replacement question of the same workflow (“can we automate this entire function?”) and the honest answer is no. So the initiative fails. Ask the amplifier question and the path is usually clear.

Where AI actually works in services companies

Real deployments in services companies follow a pattern. They work where three conditions are met: the task is high-volume, high-friction, and information-intensive. And most importantly, getting it wrong imposes a cost that the system and the human can tolerate.

Competitive intelligence and proposal intelligence. Gathering customer and competitor context before a proposal or pitch. AI surfaces relevant information: recent news about the customer, competitive losses in their industry, analyst reports about their technology direction, internal notes from previous interactions. A human reviews this and synthesizes it into a strategy. Deployment effort: 2 to 3 months. ROI: 15 to 25% shorter sales cycles.

Proposal automation and composition. Services companies spend enormous time rebuilding proposals. An MSP proposal often reuses 70 to 80% of the language and structure from previous proposals, customized for the specific customer. A system that ingests previous proposals, understands your service offerings and standard terms, and generates a first draft that a human reviews and customizes can save 10 to 15 hours per proposal. For a company running 50 proposals a year, that’s one headcount’s worth of work. Deployment effort: 3 to 4 months. ROI: $150K to $250K annually in recovered utilization.

Customer health scoring and churn prediction. A system that ingests service usage data, support tickets, NPS scores, and recent deal activity to surface accounts at risk of churn. The account manager, armed with this intelligence, can reach out proactively. The human relationship and judgment determine whether the account can be saved. Without the system, the account manager finds out about churn when she gets a cancellation notice. Deployment effort: 2 to 3 months. ROI: 2 to 5% improvement in retention, which is $500K to $5M annually depending on the company’s revenue base.

Administrative automation. Email triage, meeting scheduling, expense categorization, CRM data entry. These are high-friction, low-judgment tasks that eat into revenue-producing time. AI handles 70 to 80% of them automatically. A human still reviews and handles exceptions. Deployment effort: 1 to 2 months. ROI: 5 to 10 hours per person per week recovered. Real but modest compared to the other buckets.

None of this is hypothetical. These are deployed at scale in services companies today.

The three-tier deployment framework

Most PE firms can accelerate ROI by organizing AI deployment into tiers, based on risk and impact. This creates a roadmap that shows management where the easy wins are, where the bigger payoffs come later, and where you need to be cautious.

Tier 1 is automatable admin tasks. These are the lowest-friction, lowest-risk wins. Email filtering, meeting scheduling, data entry, report generation: tasks where AI can operate mostly independently, where errors are recoverable, and where humans review the output. These are psychological wins that build organizational appetite for AI and create immediate time recovery. They require 4 to 8 weeks to implement and generate measurable but modest ROI ($50K to $150K annually per 100-person company).

Tier 2 is augmented decision-making. These are the high-impact, medium-risk plays. Competitive intelligence, customer health scoring, proposal automation, lead scoring. These require human judgment, but AI provides better information and reduces friction. They require 8 to 16 weeks to implement and generate significant ROI ($250K to $1M+ annually depending on scope). The risk is moderate if you’ve built institutional discipline around data quality and human review processes. Most of the value in a services company comes from getting these right.

Tier 3 is new revenue streams. These are longer-term plays that require cultural change and customer-facing integration. AI-enabled advisory services, proactive customer optimization recommendations, managed security detection and response (MDR) powered by AI. These require 16 to 24 weeks to implement, need significant change management, and carry higher execution risk. But the payoff is a new business line, not just efficiency. ROI can be $2M to $10M+ annually for a company that executes well.

Smart operators start with Tier 1 to build momentum and confidence. Then they move to Tier 2, where 70% of the value lives. Tier 3 comes later, when the organization has proven it can execute and has cultural appetite for innovation.

Why operating partners miss this

The cost-cutting mandate feels urgent. Margins are under pressure. The operating partner wants to show value. Implementing an automation tool that saves 10 headcount looks like an immediate win.

It rarely is. The displaced workers leave. The tool is slower or more fragile than advertised. Customers experience degradation. Morale drops. The initiative gets rolled back.

In a services business, margin improvement comes from making revenue-producing people more productive. A sales engineer who closes 30% faster is worth more than an auto-dialer. An account manager who catches churn earlier is worth more than an automated outbound call system.

Amplification compounds the expertise you already pay for. Replacement bets against it.

The strategic takeaway

For PE firms managing services portfolios, the AI opportunity is immense, but the opportunity is leverage, not cost reduction. Deploy AI where it amplifies the judgment and expertise you already have. Start with high-friction administrative and information tasks. Then move to decision-augmentation systems that make your professionals more effective. And only then, if the organization has proven it can execute, move to longer-term innovation plays.

The companies that get this right end up competing on velocity instead of cost. Faster closes, earlier churn catches, better retention, higher-quality delivery. In a market where every other portfolio company is still trying to replace its help desk, that’s a durable place to be.

What PE Operating Partners Get Wrong About AI in Portfolio Companies

Gio Olavarria — Wed, 01 Apr 2026 00:00:00 GMT

PE firms push AI as cost-cutting. Smart operators deploy it to amplify existing expertise instead.

The First 90 Days as CRO at a PE-Backed Company

Gio Olavarria — Sat, 28 Mar 2026 00:00:00 GMT

When a PE firm appoints you as Chief Revenue Officer at one of their portfolio companies, you inherit a specific kind of dysfunction. The company probably grew to between $20 and $150 million in revenue through a combination of organic sales, multiple acquisitions, and the founder’s relationships. What it likely lacks is repeatable, scalable revenue machinery. Nobody hired you to revolutionize anything. The job is to systematize what’s there, stabilize it, and show growth within quarters, not years.

The first 90 days matter because that’s the window where you have credibility to ask hard questions without being perceived as defensive. After that, you’re accountable for results. Here’s the framework that works.

Phase one: the diagnostic (days 1-30)

Your first priority is radical transparency about the state of the business. PE boards value predictability above all else. They know that heroic sales closes don’t scale. What they need is data.

Start with pipeline and customer acquisition. Request the last 24 months of closed deals, pipeline by stage, and sales cycle length. What you’ll likely find is that your “pipeline” doesn’t exist in any meaningful sense. Most PE-backed services companies don’t have disciplined CRM hygiene. Deals exist in Outlook folders, on napkins, and in reps’ heads. Your first week should be spent reconciling what’s actually in the system versus what’s actually in flight.

Then interview every sales representative, yes, all of them. Ask each person: What did you close in the last quarter? What’s in your pipeline? How many customer conversations are you having per week? Who are your top three accounts? These conversations reveal the gap between documented process and actual behavior. A rep might claim she’s working on five prospects when she’s actually focused on keeping one major customer happy and hoping for a renewal bonus. Another might be running a profitable small-business consulting practice that has nothing to do with your ICP. These insights are gold.

Next, interview your top customers. Get the customer success leader and finance person to identify your five largest accounts. Call the customer contacts directly, not the account executive. Ask them: How did you find us? What problem were we solving? How frequently do we talk with you? Who else at their company knows about you? Would they buy additional services? You’ll discover that half your revenue is built on relationships that barely exist in formal contracts, and you’ll find expansion opportunities your sales team hasn’t surfaced.

Map the actual sales process. Create a document that describes how opportunities get sold in your company today, as opposed to how they’re supposed to be sold. Don’t rely on your sales leader to tell you this. Sit in on customer calls, ask your operations person to pull every stage transition from the CRM, and trace five deals from first conversation to close. You’ll see whether your process is consultative or transactional, whether pricing is standardized or arbitrary, and whether customer success is involved in the close.

Finally, audit financial metrics. Pull P&L by sales rep, by customer, by service line. Calculate CAC, LTV, gross margin by revenue stream, and win rate by segment. Most PE-backed services companies have never done this analysis. You’ll likely find that 70 percent of profit comes from 15 percent of revenue streams, and your sales team has no idea which ones those are.

The diagnostic phase produces a written report for the board: the state of the pipeline, the accuracy of forecast, three to five critical gaps in process or people, and your hypothesis about what’s preventing growth.

Phase two: the design (days 31-60)

Armed with diagnostic data, you now rebuild for predictability.

First, define your Ideal Customer Profile. Use your data: Which customers have the highest LTV? Which deals close fastest? Which services have the highest margin? From this, write a one-page ICP that your entire sales team can actually use. It shouldn’t be a Forrester-style matrix. It should look like this: We sell a lot to established managed service buyers at companies with 500 to 3,000 employees, annual IT budgets over $2 million, and chief information officers who have decision authority. We win more often when the prospect has experienced a breach or compliance incident. We rarely win with startups or government buyers.

Second, rebuild compensation. Most PE-backed services companies have sales comp plans that incentivize whatever the founder was focused on, which may or may not be what drives business value. Design a comp plan that aligns reps to your ICP and your margin profile. If 50 percent of your profit comes from security services, your comp plan should reflect that. If you need to keep an existing customer happy, make retention part of the incentive. Comp plan changes are political, so align your VP Sales and Finance on the new plan before you announce it.

Third, implement pipeline hygiene. This means weekly forecasting calls, opportunity stage definitions that correlate to actual win probability, weekly pipeline reviews with each rep, and a CRM that reflects reality. Assign someone to own CRM discipline. You want someone who understands that bad data creates bad decisions, not a data cop. PE boards want to see a 12-week pipeline with 60+ percent conversion from stage four. If yours is 20 percent, you need to know that within 30 days, not 90.

Fourth, establish customer success integration. Assign a customer success executive to the revenue team’s weekly forecast call. Your customer success data is your early indicator of churn and expansion. A sales leader who isn’t talking to customer success every week is flying blind.

Phase three: the execution (days 61-90)

Now you execute against your plan.

Identify three quick wins. These are opportunities that are winnable in the next 30 to 60 days and that will demonstrate momentum to the board. They might be a large expansion opportunity with an existing customer, a deal that’s been stalled but is close, or a new market segment where you have pent-up demand. Close these wins publicly. Write a case study. Make sure the board hears about them in your first 100-day presentation.

Build a board-ready metrics dashboard. Every PE firm has a template. Yours probably requires: monthly recurring revenue, pipeline by stage and month, win rate, sales cycle length, average contract value, CAC, LTV, net revenue retention, and headcount plan. Build this in month two. Update it weekly. By day 90, this should be automated and accurate. PE boards make decisions based on these metrics. If you’re reporting different numbers in your forecast call than you are to the board, you lose credibility fast.

Establish an operating cadence. This means a weekly sales forecast call (30 minutes, every manager and above), a monthly pipeline review with the CEO and CFO (60 minutes, your team plus customer success), and a quarterly board update. Most PE-backed companies don’t have a disciplined rhythm. The rhythm is what makes your forecast believable, and a believable forecast is what buys you room with the board.

By day 90, you should have answered these questions: What’s the health of our pipeline? Are we on track for the year? What’s preventing us from hitting our number? Which customer segments should we double down on? Which sales reps are truly productive, and which ones coast on relationships? What’s our plan to fix each gap? Do we have the right sales leadership in place, or do we need to make a change?

The PE perspective

PE firms acquire services companies because they see revenue growth opportunities. Most PE deals in services don’t include operational expertise in revenue. You were hired because you understand where revenue in a services business actually comes from: experienced salespeople who understand the customer’s problem, understand your service delivery, and can navigate a six-month buying cycle. Marketing campaigns and inbound leads are a distant second.

What PE sponsors fear most is a CRO who comes in wanting to build a “Sales Development Representative pipeline” or hire a VP Marketing to create brand awareness. Your job is to take what’s working (the customer relationships, the delivery expertise, the installed base) and systematize it so it doesn’t depend on any one person.

The first 90 days set the tempo. If you deliver diagnostic clarity, design specificity, and early execution wins, you’ll have earned the right to lead a larger transformation. If you miss, you’ll spend the next 18 months fighting to regain credibility while the board worries you don’t understand their business.

The companies that do this right typically compound revenue at 15 to 25 percent annually while improving gross margin, because growth comes from executing better with the sales talent they already have rather than from hiring more reps. That’s the multiplier PE really values.

The First 90 Days as CRO at a PE-Backed Company

Gio Olavarria — Sat, 28 Mar 2026 00:00:00 GMT

A practical playbook for diagnostic, design, and execution phases when stepping into revenue leadership at PE-backed services businesses.

Building an M&A Practice Inside a Services Company

Gio Olavarria — Sun, 22 Mar 2026 00:00:00 GMT

Most managed services and IT consulting companies treat M&A as something the private equity sponsor does. The PE firm buys the platform, then sources tuck-in acquisitions to bolt on. The services company executes integration. End of story.

This is a missed opportunity. Services companies are well positioned to build internal M&A capability: to source, diligence, and integrate acquisitions as part of their core growth strategy. The CRO should own this, because the value in a services acquisition comes from revenue acceleration, client relationship multiplication, and talent arbitrage, and those all run through the revenue organization.

Building an M&A practice doesn’t require hiring a three-person corporate development team. It requires rethinking how your revenue leaders spend their time, where you source deal flow, and how you structure acquisitions to require minimal upfront capital. Here’s how.

Why services companies are built for M&A

Consider the advantages you have that pure venture-backed software companies don’t. First, your customer relationships are sticky and multi-year. If you acquire a consulting firm that serves your current customer base, integration means walking a new service offering into an existing relationship that already has trust and contract authority. Selling new products to new customers is a much harder game. Your close rate on cross-sold services post-acquisition can exceed 40 percent in the first year, because the relationship is already established.

Second, you have operational integration expertise. Your delivery teams have implemented systems integrations, migrated infrastructure, and absorbed teams into existing workflows hundreds of times. You understand how to fold a new company’s operations into your own without destroying client value. Many software or professional services acquirers have no idea how to do this. You’ve been doing it as part of normal operations for years.

Third, you have talent arbitrage opportunities that other acquirers don’t. When you acquire a smaller consulting firm or IT services provider, you’re acquiring experienced engineers, architects, and account executives who already know your industry and your customer problems. Instead of training new people on your domain, you’re acquiring people who are already domain experts. You can immediately redeploy them across your customer base, where they become more valuable, not less.

Fourth, deal flow is embedded in your sales process. Your account executives talk to customers about their broader challenges every quarter. You hear about companies in adjacent geographies or verticals that are solving similar problems. Your customer success team identifies gaps in services they wish you offered. Your sales leadership knows the players in your market. A formal M&A program mostly formalizes deal flow you’re already seeing.

The three capabilities you need

Building an M&A practice requires three specific capabilities: deal sourcing, lightweight diligence, and integration playbooks.

Deal sourcing means creating a systematic process for identifying acquisition candidates. That doesn’t mean hiring a business development person to live on LinkedIn all day. It means your sales leadership, customer success leadership, and delivery leadership each have a mandate to source two to three acquisition targets per quarter. It means your account executives, when they spot a potential acquisition, document it in a simple template and pass it to a central list. It means your sales leadership in each vertical or geography understands which tuck-ins make sense in your market, and you’re reading the trade press (CRN, ChannelE2E), attending conferences, and following regional news to spot companies that fit your criteria. The discipline here is separating signal from noise. You’re looking for companies that serve your customer base, have complementary service lines, have strong management teams that will stay post-acquisition, and are profitable or close to it.

Lightweight diligence means two weeks and $15,000 spent on the critical questions, instead of three months and $100,000 on a forensic audit for a $3 million acquisition. The questions: Is this team actually profitable, or are they hiding losses? Do they have customer concentration risk? What’s their customer acquisition cost, and how does it compare to ours? Are there technical or cultural misalignments that would make integration painful? Do their customer contracts have change of control language that might trigger price reductions? Your operations team, your finance team, and your technical architects can answer these quickly. External auditors only come in once you’ve decided to do the deal and need to confirm something specific.

Integration playbooks mean you have a documented standard approach to integrating new companies. This covers the first 100 days post-close: Which leader will oversee integration? How will you communicate with acquired customers? How will you merge CRM systems? How will you handle duplicate customer accounts? How will you redesign commission plans to include legacy acquired company reps? How will you redeploy talent? How will you consolidate vendor contracts? How will you replatform their service delivery? The playbook gets refined after every acquisition, but the fact that it exists and has been tested means your integration velocity is far higher than a company that treats every acquisition as a brand new puzzle.

Funding M&A without a dedicated budget

Here’s the objection: “We don’t have budget for M&A, and our PE sponsor is tapped out.” This is real, but it doesn’t stop you.

First, use your existing business development team. Your VP BD or Director of Strategic Partnerships probably spends 40 percent of their time on things that don’t scale. Give them 20 hours a month to source acquisitions. That’s redirected capacity, not new headcount. This person reports directly to you, generates a monthly update, and owns deal sourcing.

Second, use fractional M&A advisors. Instead of hiring a full-time Vice President of Corporate Development, retain a fractional advisor for 10 hours a month. This might cost $3,000 to $5,000 a month, but it gives you someone who has done dozens of services company acquisitions, who knows what diligence is critical and what’s theater, and who can help you structure deals efficiently. This person attends your M&A sourcing meetings, helps you evaluate candidates, and coaches your team through diligence. The cost is minimal compared to the risk reduction.

Third, use earn-out structures to minimize upfront capital. Instead of paying all cash for an acquisition, structure it as 70 percent cash at close and 30 percent in earnouts over two years based on revenue retention and customer growth. This accomplishes two things: It reduces your upfront capital requirement, and it aligns the selling founder with your success post-acquisition. Founders who have skin in the game post-close actually help you integrate.

Fourth, explore seller financing. Some founders of smaller services companies (sub-$5 million) would rather keep ownership in a growing company than take all cash. Offer the founder a note at an attractive interest rate or preferred equity in the combined company. You reduce upfront cash while giving the founder a path to significant wealth creation if you can compound growth.

Fifth, use operational efficiency gains to fund acquisitions. If you’re improving gross margin by 3 to 5 percent through operational improvements, you’re creating cash flow that can fund acquisitions. A $30 million services company improving gross margin from 45 percent to 50 percent is creating $1.5 million in additional annual cash flow. That cash can fund acquisitions without tapping your credit line.

Building the flywheel

The power of building an M&A practice emerges over time. After your third or fourth acquisition, you have:

A playbook that actually works. Your integration isn’t perfect, but you know what works and what doesn’t. New acquisitions integrate faster. Your speed-to-value improves.

Customer relationships that accelerate growth. On top of the talent and revenue, you’re acquiring customers who fit your profile, and immediately selling them services they didn’t have before. Your revenue multiple on acquired revenue beats your organic growth rate.

Talent that stays. Founders and leaders who see acquisitions working understand that selling to you is a good outcome. They’re more willing to walk their teams through integration because they see the upside. Your retention of key people improves with each deal.

Confidence with your PE sponsor. When you show your sponsor that you can source, close, and integrate acquisitions at better economics than they can, you shift power. You stop executing their deals and start building strategy together. That typically leads to more autonomy and larger check sizes as you scale.

Margin expansion. A $20 million services company with no acquisition experience has gross margin of 40 to 45 percent. A $50 million company with two solid acquisitions under its belt has margin of 48 to 52 percent because you’ve standardized delivery, eliminated duplicate overhead, and redeployed acquired talent at higher billing rates.

The strategic thesis

The highest-growth services companies don’t choose between organic growth and acquisition-driven growth. They do both. Organic growth proves out your business model and creates the foundation for acquisition integration. Acquisition growth accelerates revenue and improves margins when done well.

Most PE sponsors understand this. What they don’t always understand is that services company M&A fails when the CRO isn’t driving it. PE sponsors source deals. CROs drive whether acquisitions succeed. When you own both deal sourcing and revenue integration, you’ve created a flywheel. You’re finding the best targets in your market, closing them at better economics, and integrating them faster than your sponsor could from the outside.

That’s the difference between a company that compounds at 15 percent annually and a company that compounds at 25 percent. None of it is heroic. It’s a system, and it’s entirely within the control of your revenue leader.

Building an M&A Practice Inside a Services Company

Gio Olavarria — Sun, 22 Mar 2026 00:00:00 GMT

How services companies can develop internal M&A capability and combine organic revenue excellence with strategic acquisitions.