The Reference Architecture

Two MSPs quote the same sixty-seat manufacturer. The first sends a proposal that says it will support the client’s existing firewall, its existing backup, the server in the closet, and the three vendors the client already pays. The second sends a two-page document before the proposal: the design every one of its clients runs, product by product, with a sentence next to each explaining why that product and not another, and a note that the manufacturer’s environment will be moved onto it in the first ninety days. The first MSP has offered to be the client’s IT department. The second has told the client what good looks like. The prices are close. The second one wins, and it wins the next one too, because the document does not change from prospect to prospect.

That document is a reference architecture.

What it is

Service Leadership, the firm behind the Service Leadership Index, gave the term its MSP definition in a 2016 paper: “a single design that spans multiple layers of the technology stack that every IT-using business has implemented: the specific hardware and software products that a given client uses at each layer of its computing infrastructure, from networks to servers to desktops and mobile devices, typically specified by vendor and model number.” That is narrower than the way most operators use the phrase. It is not a set of principles or a preferred vendor list. It is a parts list, with a rule attached: every client gets the parts on the list, and a client that wants something else pays for the exception or goes elsewhere.

What it does to the numbers

Service Leadership’s finding was about profit. From 2008 through 2015, the top quarter of MSPs in its Index earned 19.1 percent of revenue as profit, after paying the owner a market salary, against 7.4 percent for the median firm, and the paper named the deliberately narrow technology stack as a key reason. The mechanism is not complicated. Every product a firm supports is a set of things its technicians have to know, a set of tickets that look like no other tickets, and a set of integrations that break on their own schedule. Ten products in ten layers is one training plan. Forty products across the same ten layers is an operation that runs on whoever happens to remember.

Paul Dippell, who ran Service Leadership, described the firms that go the other way to ChannelPro in 2020. They hire smarter people to cope with the variety, “so customers are happier, the employees are happier,” and then, in his words, “they go broke.” The industry knows this about itself. In Datto’s State of the MSP survey published in late 2024, which counted 1,262 providers, 63 percent said they prefer to use fewer vendors, and 46 percent called vendor consolidation a priority for the next twelve months. Philip de Souza, founder of Aurora IT, told ChannelPro in May 2026 how firms drift the other way anyway: a new client arrives with requirements, then another, and “you wake up one morning and you’ve got 40 platforms,” none of which talk to each other.

Why it differentiates

Every prospect asks the same question, in one form or another: why you and not the other three firms that quoted. An MSP that supports whatever the client already owns has no answer to that, because “we will work with what you have” is the sentence all four firms say. The reference architecture is the one answer that only one firm in the room can give. “Every client we run is built this way, here is the design, and here is why” is a position. It tells the buyer the firm has an opinion about how a business should run, and that it has held that opinion across every client it serves.

A position also says no. The prospect who insists on keeping its own stack gets an exception price high enough to cover the cost of the variety, or gets turned down. Firms without an architecture take that deal, because the revenue is real and the cost is spread across the next five years of tickets. Firms with one have already made the decision, in writing, before the prospect walked in. Service Leadership’s paper put the sales result in one sentence: the best firms win “by exerting tighter control over what technology the client can have.”

Why it signals expertise

A buyer cannot evaluate an MSP’s engineering. What a buyer can evaluate is whether the firm has made decisions. A two-page architecture with products named and a reason beside each is a record of decisions, and it can be read before the first call, by the owner of the prospect, by the board of the prospect, and by the cyber insurance carrier the prospect is trying to satisfy. It proves the firm chose, and can explain the choice, and applies it the same way everywhere. Certifications say the firm’s people passed a test. The architecture says the firm knows what it believes.

It also changes who can sell. A salesperson who has never built a network cannot improvise expertise on a call, and the gap shows. Handed the architecture, she can walk a buyer through the design and the reasons, and the expertise the buyer hears is the company’s, written down, not hers. Service Leadership’s paper listed the result: “more referrals, more confident salespeople, and richer deals.”

What the acquirers do

The private equity owners of MSP platforms have split on this. Evergreen Services Group’s Sydney Hockett told ChannelE2E in May 2024 that the firm sets “a base level line of cybersecurity requirements” for the MSPs it buys but is “not mandating solutions, tech stack, things like that.” Magna5 went the other way; in its PSA vendor’s account of the work, it brought nine acquired business units onto one platform in as little as two months, with customer environments, in the vendor’s words, “set up the same way.” Both are defensible. Only one of them produces a document the sales team can hand to a prospect.

What an owner should ask

At the next operating review, ask for the reference architecture. If the answer is “we have standards,” ask for the page, and if the page does not name products by vendor and model with a reason for each, it is a preference list, not an architecture. Then take the client list and sort it into accounts built to the design and accounts built some other way. The second column is the cost of every exception the firm ever agreed to, and the number of products it contains is a fair measure of the distance between the firm and the top quarter.

Then ask how the architecture is used in sales. If it lives in the engineering folder and no prospect has ever read it, the firm is paying for the discipline and getting none of the differentiation. The document that makes the operation cheaper to run is the same document that makes the firm easier to choose, and it costs nothing to put it in front of the buyer.