Set the Foundation: How MSPs Build a Real Business Base Before Anything Else

Set the Foundation is the S in SCALE — the first phase of the BSP transformation framework. It’s also the phase most MSPs think they’ve already completed and almost never have.

Foundation is not “we picked a target market and set our prices.” That’s a stack of generic decisions any competitor could make. A real foundation has four pieces, each operationally specific, each load-bearing for everything that comes after. Get them right and the next four phases compound. Get them wrong and every later effort amplifies the foundation’s weaknesses.

This page walks through all four — what they are, what most MSPs get wrong about them, and what “right” actually looks like.

Why Foundation comes first

Every other phase of the BSP Framework assumes the Foundation work is done. The factory you build in C is a factory for what? The marketing engine you build in A is selling what, to whom, at what price? The systems you document in L are documenting what process? The team you structure in E is structured to deliver what?

If the answers to those questions are vague, every later phase produces vague output. Foundation is where the answers get sharp.

For most MSPs, Foundation is roughly a 90-day effort. Some pieces (ICP, packaging) move fast; pricing and prescriptive sales take longer because they require change to how the founder actually sells. The phase is done when the firm can answer four questions, in one sentence each, without hedging:

Who exactly do we serve?
What outcome do we sell them?
What does it cost, and why is that the right number?
How do we sell it?

Piece 1: A genuinely narrow Ideal Client Profile (ICP)

Most MSPs’ “target market” is some flavor of “small to mid-sized businesses.” That is not an ICP. That is everyone, with a polite filter.

A real ICP passes four tests:

You can describe it in one sentence specific enough that a stranger at a networking event could point you to the right person. “Dental practices with 4–12 chairs in the mid-Atlantic” passes. “SMBs that need IT” doesn’t.
They share one business problem you solve — stated as a business problem, not a technology problem. “Their staff spends two hours a day on insurance verification that AI could automate” is a business problem. “Their network is slow” is not.
You know where they congregate — physically (conferences, associations, chambers) and digitally (forums, podcasts, LinkedIn groups, publications).
All your sales and marketing point at them, not at “anyone who’ll pay.” This is the test that fails most often. If your website still reads as a generic MSP page, your ICP isn’t real yet — it’s an aspiration on a strategy doc.

The fear MSPs have about narrowing the ICP is that it shrinks the market. The opposite is true: narrowing makes the market findable. A generic MSP fights every other MSP for any business that walks through the door. A vertical-focused BSP fights almost no one for the businesses that match its ICP and the close rate goes up by an order of magnitude.

Practical exercise to start the ICP work: interview your three to five best current clients. Ask, “what is the business problem we solve for you?” Listen for the language they use. The ICP you write should describe those clients, in their words.

Piece 2: A solution named for the outcome, not the technology

After ICP comes packaging. The deliverable here is a named offer — one that describes the business outcome the client buys, not the technology that produces it.

Examples of the shift:

Technology-named (MSP)
Outcome-named (BSP)

Managed IT services for law firms
The Legal Practice Growth System

Cybersecurity package
The Compliance Confidence Program

Cloud migration project
Operating-Cost Reduction Sprint

Managed services + vCIO
The Practice-Owner Operating System

The names look like marketing. They’re more than that. The naming forces the firm to articulate what the client is actually buying — and once articulated, it becomes possible to price on it.

Three discipline checks on the package:

Standardized delivery. Same tech stack, same processes, repeatable and teachable across clients. If every client gets a custom configuration, you can’t scale and you can’t price on outcome.

The name describes the outcome. If the name still has “IT” or “managed services” in it, you’ve named the work, not the result.

It’s transferrable. Could a new team member follow your delivery process without needing you in the room? If not, the package isn’t a package — it’s still tribal knowledge.

This is also where many MSPs realize they’ve been delivering five different things to five different segments. Packaging forces the choice: which one do we systematize first?

Piece 3: Value-based pricing — the floor and the ceiling

The third Foundation piece is pricing. And pricing in the BSP model is not a number. It is a discipline that lives between two boundaries.

The floor: 3x your direct costs. Anything less and the business cannot sustain itself. Direct costs are labor, tools, and license fees attributable to the engagement. Multiply by three. That number is the absolute minimum at which the engagement is economically viable.

The ceiling: one-third of the value you deliver. Past this point, clients reject the offer no matter how good. If your work delivers $300K of annual value to a client, the ceiling on the engagement is about $100K. Above it, the client cannot rationalize the spend, even if the ROI is obvious on paper.

The space between is wide — for most BSP engagements, the gap between floor and ceiling is 3-5x. That gap is the room you have to set price based on what the outcome is worth to this client, not on what the work cost to deliver.

A few practical notes:

Quantify the value before you price. If you can’t show the client a number for what the engagement is worth, you cannot price on it. Build a value model — even a rough one — for the engagement.

The first conversation about price is not negotiation, it’s calibration. If no client is pushing back, you’re underpriced. If everyone is pushing back, you’ve outrun the value story.

Review pricing annually. As your delivery improves and your client outcomes scale, both the floor and the ceiling move. Pricing is a discipline, not a spreadsheet you save once.

The pricing shift is the biggest single lever in the BSP transformation. Most firms see per-client revenue 2-5x after this piece is done correctly. The most common reason it fails is that the firm raises prices before doing the ICP and packaging work — at which point the higher prices have nothing to stand on.

Piece 4: Prescriptive sales — the PASTA framework

The final Foundation piece is how the firm sells. Most MSPs sell consultatively — “what are you looking for?” — and respond to the prospect’s framing of the problem. The BSP sells prescriptively, like a doctor.

Read more about Prescriptive Sales.

A doctor doesn’t ask, “what medicine would you like?” The doctor asks the symptoms, diagnoses the problem, and prescribes the treatment. Prescriptive selling works the same way.

We teach a five-step structure called PASTA:

P — Problem. State the specific problem you solve for a specific market. Not your problem with selling; the prospect’s business problem you solve.

A — Accentuate. Make the cost of leaving it unsolved tangible. Lost revenue, regulatory risk, competitive disadvantage. The prospect needs to feel the cost.

S — Solution (generic). Describe what the solution looks like, generically. The prospect agrees on the need before they ever hear your offer.

T — Transformation. Paint the post-solution state. Use social proof — show another client who lived it.

A — Amazing offer. Now, and only now, present your specific offering with its specific price.

The research backs the approach: CEB/Gartner found prescriptive selling increases purchase ease by 86%. In practice, we see BSP sales cycles run 6-10 weeks versus an MSP norm of 3-6 months, and close rates roughly 2-3x consultative selling.

The structural reason it works: the consultative “what are you looking for?” approach gives the prospect control of the framing — and prospects almost always frame their problem as a technology problem. The prescriptive approach lets you frame it as a business problem. The frame is the sale.

PASTA is also a script, in the working-document sense. It should be written out, drilled, role-played, and used by every salesperson in the firm. If the prescription depends on the founder’s intuition, the firm can’t scale sales.

What “done” looks like for the Foundation phase

You know you’ve completed S when:

You can describe your ICP in one sentence to a stranger and they could point you to one tomorrow.

Your offer has a name that describes the outcome, not the technology — and you can hand the delivery process to a new team member without your involvement.

Your pricing is at least 3x direct costs and well under one-third of value delivered, with a written value model behind each engagement.

Every salesperson — including the founder — can run the PASTA framework from memory and uses it on every prospect call.

All new marketing and sales activity points at the ICP, not at “anyone who’ll pay.”

If any of those is “almost” or “mostly,” the phase isn’t done. Go back to the gap and finish it before moving to Construct the Factory.

Where you are right now

The fastest way to know whether your Foundation is real is the BSP Readiness Assessment. It scores you on each Foundation piece and tells you which one is weakest. Most MSPs score weakest on ICP — they’ve narrowed the market on paper but not in their sales and marketing. The assessment catches that mismatch fast.

When the Foundation is done, the next phase is Construct the Factory — turning what you sell from an artisan craft into a standardized, scalable delivery system.

For the full framework overview, see The BSP Framework. For the definition of the model, see What Is a Business Solution Partner.