Expand with Intent: How MSPs Scale Beyond the Founder Without Losing Control

Expand with Intent is the E in SCALE — the fifth and final phase of the BSP transformation. By the time the firm reaches Expand, it has a foundation, a factory, an engine, and a system. What it doesn’t have yet is optionality — the property that lets the founder decide what the next chapter of their life looks like, instead of having the business decide for them.

Expand is where optionality gets built. The phase has four workstreams:

The Hats Chart — clarifying who owns what function
Performance management — holding people accountable to those functions
The leadership cadence — the meetings that run a real leadership team
365 planning — annual strategy that actually executes

Done well, the output is a business that the founder can run — but doesn’t have to. The founder can step back, sell, run two firms, hand it to a successor, take a sabbatical, or just take a vacation that lasts more than a long weekend. None of those options exist in a workshop-grade MSP. All of them exist in a BSP that has finished Expand.

Why Expand is the optionality phase

The single most common founder regret in the MSP industry isn’t building the wrong business. It’s building a business that requires the founder’s continued presence forever.

Even a healthy, profitable MSP, if it depends on the founder operationally, traps the founder. The founder can’t sell at a real multiple, can’t step back, can’t hand it to anyone, can’t be sick for a week without things falling apart.

Expand is the structural fix. Every workstream below moves operational ownership out of the founder and into a system, a role, or another person — without losing the founder’s ability to set direction.

For most BSPs, Expand starts around month 10 and continues effectively forever — it’s the phase the business never stops being in, once it enters it.

Workstream 1: The Hats Chart

The Hats Chart is the BSP replacement for the traditional org chart. The difference matters.

An org chart shows titles and reporting lines. It answers “who reports to whom?” That answer is administratively useful and operationally weak.

A Hats Chart shows functions and ownership. It answers “who owns the outcome of this function?” That answer is what makes accountability legible.

The seven core functions

Most BSPs organize around seven core functions:

Visionary / Strategy — direction-setting, market positioning, strategic decisions
Sales / Business Development — net-new client acquisition
Marketing — pipeline development, content, positioning, demand generation
Delivery / Operations — service delivery, ticket flow, project execution
Client Success — retention, SBRs, account growth
Finance / Administration — bookkeeping, financial reporting, contracts, HR
People / Talent — hiring, performance, culture, development

In a small firm, one person wears multiple hats. The founder might wear five. That’s not a problem — what is a problem is when no one knows which hat is being worn at any given moment, or when the same hat is partially worn by three different people.

The Hats Chart resolves this by making the ownership explicit. Each hat has exactly one owner. The owner’s success metrics for that hat are written down. If two functions belong to the same person, that’s named — and the firm has a path to splitting them when growth allows.

The hardest hat to delegate

The hat founders hold longest is usually Sales. The hat they should delegate earliest is usually Delivery or Operations.

The reason: as long as the founder is in delivery, the founder is the operational ceiling. Sales can be founder-led for far longer — the founder is often the firm’s best closer — but only if delivery doesn’t also depend on the founder. Get delivery off the founder’s plate first; sales can come later.

Watch:

Workstream 2: Performance management

Once hats are assigned, the firm needs a way to hold people accountable to the hats they wear. That’s performance management — and most MSPs run it badly or not at all.

What a real performance management rhythm looks like:

Weekly one-on-ones. 30 minutes, every direct report, every week. Not a status update — a conversation about what’s working, what’s stuck, and what support is needed.

Monthly check-ins on the function. Every hat-owner reviews their hat’s metrics with their manager. Are we hitting the success metrics? If not, what’s the issue?

Quarterly reviews. Each team member’s quarterly performance against their hat — formal, written, with a clear “are we on track?” answer.

Annual review and compensation. Once a year, a comprehensive review tied to compensation and development.

The cadence matters less than the consistency. A firm that runs weekly one-on-ones for six months straight will have different performance than one that runs them when there’s time. The consistency is the discipline.

The values check

Performance management is also where the Factory phase’s values do real work. Performance has two dimensions:

Results — did the person hit the metrics on their hat?

Values — did they hit those metrics in a way that aligns with how this company operates?

Someone who hits results but violates values is more dangerous than someone who misses results but lives the values. The former corrodes the culture; the latter just needs coaching. Performance management has to evaluate both.

Workstream 3: The leadership cadence

The leadership cadence is the meeting rhythm that runs the BSP at the leadership level. Some of it overlaps with the rhythms installed in Lock in Systems; the difference at the Expand level is who’s in the room.

Three meetings matter:

Weekly leadership meeting — 90 minutes, the leadership team (hat-owners or their direct supervisors). Metrics, issues, decisions.

Monthly business review — a deeper look at the business in aggregate. Two hours. P&L, pipeline, hiring, project status, client health.

Quarterly off-site — a full or half-day, off-site, to set the next quarter’s rocks and review the last quarter’s outcomes.

In smaller firms, “leadership team” may be the founder plus one or two senior people. That’s fine. The discipline matters more than the size. A founder plus one running a real weekly leadership meeting is operationally more sophisticated than a founder plus five who talk in hallways.

The annual planning rhythm

Once a year, the leadership team runs a longer planning session — typically a full day off-site — to set the next 12 months. This produces the 365 plan: a one-page summary of the year’s strategy, broken into quarterly rocks, with each quarter’s rocks revisited at the quarterly off-sites.

The 365 plan is short on purpose. It’s not a strategy doc — it’s the executable summary of one. If the plan can’t fit on a page, it won’t make it through a quarter of execution.

Workstream 4: 365 planning

365 planning is the operational rhythm that connects annual strategy to weekly execution. The structure:

Annual off-site (once a year). Leadership team sets the year. Outputs: 3-year vision, 12-month financial targets, the year’s strategic priorities, the first quarter’s rocks.
Quarterly off-site (every 90 days). Leadership reviews the last quarter, sets the next quarter’s 3-5 rocks. Each rock has an owner, a definition of done, and a milestone in 30/60/90 days.
Weekly leadership meeting. Rocks are reviewed every week. Track green/yellow/red status. Yellow or red rocks get diagnostic attention, not just status reporting.
Quarterly review. Each rock gets a hit-or-miss outcome. The success rate on rocks is one of the firm’s most important operational metrics.

The discipline that makes 365 planning work: rocks are non-negotiable. They’re the 3-5 things that will get done this quarter regardless of what else happens. They’re chosen because they matter more than the urgent noise — and they’re protected from being displaced by the urgent noise.

A firm hitting 70%+ of its rocks each quarter is operating at BSP velocity. A firm hitting below 50% has either chosen the wrong rocks (too big, too ambiguous, too many) or doesn’t have the operational discipline to execute on what it chose. Both are diagnosable problems.

Exit optionality — what Expand makes possible

The phrase “expand with intent” doesn’t only mean growth. It means deliberate choice about what the next chapter of the business looks like — including the choice to exit.

A BSP that has completed Expand has these options:

Sell at a real multiple — 6-10x EBITDA versus the 3-5x MSP norm. The difference is the asset structure: a factory with documented systems and a working leadership team is a transferable business; a founder-dependent workshop isn’t.

Run two BSPs at once — possible because the first one doesn’t require the founder’s daily presence.

Hand it to a successor — internal or external. Possible because the operational knowledge isn’t trapped in the founder’s head.

Take a real sabbatical — three to twelve months. Possible because the leadership cadence and Lock-phase systems mean the firm can run without the founder making operational decisions.

Stay and operate at half the hours — possible because Expand removes the founder from the operational critical path.

The point isn’t to do any of these. The point is to be able to do any of them. That’s optionality, and it’s what Expand produces.

What “done” looks like for the Expand phase

In truth Expanding with Intent never ends… but you’re doing the right thing when:

The Hats Chart exists, every hat has exactly one owner, and each owner can name their success metrics from memory

Performance management is running on a weekly/monthly/quarterly cadence with written outputs

The weekly leadership meeting runs every week, attended by the leadership team, structured and on-time

A 365 plan exists for the current year, with quarterly rocks, and the rock completion rate is being tracked

The founder could leave the business for two months and operations would continue on track

The last bullet is the test. If the founder can disappear for 60 days and the business is fine, Expand is done. If not, find the workstream where the founder is still the bottleneck and finish it.

Expand never ends, exactly

Expand is the only SCALE phase that doesn’t have a finish line. Foundation, Factory, Accelerate, and Lock all have observable “done” states. Expand keeps running for as long as the business runs — because the business keeps growing, the team keeps changing, and the planning rhythm keeps producing new quarters of execution.

The right way to think about it: Expand is the operating mode the BSP runs in after the other four phases are installed. The work doesn’t stop. The chaos does.

For the full framework, see The BSP Framework. For comparison to the MSP starting point, see MSP vs BSP. To score where you are today, take the BSP Readiness Assessment — the Expand section covers Hats Chart maturity, leadership cadence, and 365 planning discipline.