Right-Sizing Your Program: MSP, Hybrid or Self-Managed?

The most common mistake I see at the $10-50 million level is copying an enterprise design. A company hears “contingent workforce program,” looks at what a $300 million buyer does, and tries to shrink it. It rarely fits.

The better question is not “what do the big companies do?” It is “what does a company like ours need, and what can we realistically support?” I have seen companies implement a program with a VMS tool that is fully integrated with their HRIS system, which took 4 months and multiple resources to get stood up, for a program that never exceeded 80 contingent workers.  All because that is what someone’s previous company had- with their 1500 contingent workers.

The three models

Most mid-sized programs land in one of three places.

1. Fully managed (MSP). An outside provider runs the program: supplier management, requisition handling, reporting, often the technology too. Your team sets direction and reviews results.

2. Hybrid. You use a vendor management system (VMS) for visibility and workflow, with a small internal owner and selective outside support, such as help with supplier management or reporting.

3. Self-managed. You run it yourself, with clear policies, a short list of preferred suppliers, a scorecard and a named owner. Technology may be light: a spreadsheet, a shared tool or a basic platform.

None of these is better in the abstract. Each is right for a different situation.

By the numbers: how common managed programs are

  • 57% of staffing buyers use an MSP, according to SIA’s latest buyer data, so a sizable share run their programs another way.
  • MSP spend under management reached $244 billion globally in 2025, up 4% and the strongest growth since 2022. SIA forecasts another 4% in 2026, and the US accounts for 51% of the total.
  • The market is concentrated: the seven largest providers hold more than 70% of global spend under management.

Source: SIA, “Global MSP spend rises 4% to $244B,” Sept. 21, 2026.

 Fully managed (MSP)HybridSelf-managed
Who does the daily workProviderInternal owner + VMSInternal team
Internal capacity neededLowModerateHigh
Cost structureProvider fees, often tied to spendTechnology fees + internal timeMostly internal time
VisibilityHighHighDepends on your discipline
Speed to launchModerate to slowModerateFast
Best whenSpend is complex and your team is stretchedYou want control with real dataNeeds are simple and you have a capable owner

How to choose

Four questions usually point toward the right model.

How complex is your spend? A single worker type in a few locations is simple. Many job categories, locations and suppliers, or project-based work mixed with staff augmentation, is complex. More complexity pushes toward a managed or hybrid model.

How much internal capacity do you have? Be honest here. If the person who would run the program already has a full job, a self-managed approach will slip. Capacity, not budget, is the most common reason programs fail at this size.

How much do you need data? If leadership wants regular, reliable reporting on cost and compliance, you need technology, even if it is light.

How fast do you need results? A self-managed program with solid policies can start in weeks. A full MSP rollout takes longer and needs more change management.

Quick guide

  • Simple spend, capable owner, limited budget: start self-managed, and plan to add technology as you grow.
  • Moderate complexity, some internal capacity, a need for data: hybrid is usually the sweet spot.
  • High complexity, thin internal team, tight compliance needs: a managed model makes sense, but right-size it so you are not paying for enterprise features you will not use.

Plan for growth

The model you choose today does not need to be the one you keep. Many programs I have worked with started lean and added structure as spend and complexity grew. The key is to avoid decisions that lock you in: long contracts, technology that cannot scale down or up, or processes only one person understands.

A good test: if your program owner left tomorrow, could someone else pick it up? If not, the design is too dependent on one person.

What I would not do

  • Buy technology before you decide on your model.
  • Choose a model because a vendor recommended it.
  • Skip the baseline. You cannot size a program without knowing your current spend, suppliers and rates.

That last point is the subject of Article 3.

If you are trying to decide which model fits, I am glad to talk it through. Email me at becky@ennisbader.com to schedule a 20 minute discussion.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *