Practical thinking on building and running contingent workforce programs that hold up after launch. Drawing on 30 years in workforce staffing and strategy, I write for staffing firms launching MSP and MVP offerings, and for companies trying to get control of their contingent workforce. No theory, just what works, what breaks, and how to fix it.
The word “governance” makes most mid-sized companies wince. It sounds like committees, binders and approval chains that slow everyone down.
But without some governance, a program drifts. Rates creep up. Suppliers multiply. Managers work around the process. Within a year or two you are back where you started, now with a system on top. I’ve seen it happen- a program owner leaves the organization, the oversight is no longer a priority since no one is managing it, and hiring managers were allowed to skirt the program.
Good governance at this size is small and simple. It exists to answer four questions: who decides, what are the rules, how do we know it is working, and what do we do when it is not.
The single most important governance step is naming one person accountable for the program. Not a committee, and not “procurement and HR together.” One person, with enough authority to enforce standards and enough time to do the job.
At $10-50 million in spend, this is often a part-time role for someone in procurement, HR operations or finance. If it is part-time, protect the time. Programs fail when the owner’s real job crowds out the program.
Behind the owner, set up a light steering group: the owner, a finance representative, an HR or talent leader, and an executive sponsor. Meet quarterly, not monthly, unless something is wrong.
You do not need a 40-page manual. A two-to-three-page policy that covers the following is enough:
The test of a good policy is whether a hiring manager can read it in ten minutes and follow it.
Most mid-sized programs have too many suppliers. A tiered approach brings order without needing an elaborate process.
| Tier | Who | How you manage them |
| Preferred | A small group of suppliers with the most spend and best performance | Standard agreements, agreed rates, regular reviews |
| Approved | Suppliers used for specific skills or locations | Standard agreements, reviewed annually |
| Exception | One-off or niche suppliers | Requires owner approval, reviewed for consolidation |
The goal is not to cut suppliers for its own sake. It is to concentrate volume where you get better rates and service, and to know why every supplier is on the list.
A scorecard that tracks 30 metrics gets ignored. One that tracks eight to ten gets used. Choose a few in each of four areas:
For each metric, define what it means, where the data comes from and who is responsible. Review the scorecard monthly at the owner level and quarterly with the steering group.
Invoice accuracy and timeliness are worth watching closely. When it slips, the impact it can have on your financials can become problematic.
This takes a few hours a month. If it takes much more, the design is too heavy.
A few habits prevent governance from turning into bureaucracy:
Governance only works if people follow it, and that depends on adoption. Article 6 covers how to get hiring managers on board and how to show results in the first year.
If you want help designing a policy, scorecard or supplier tiers that fit your company, I am glad to talk. Email me at becky@ennisbader.com to schedule a 20 minute discussion..
A vendor management system (VMS) is the technology backbone of most contingent workforce programs. It handles requisitions, supplier submissions, approvals, onboarding, time and invoicing, and gives you the data to see what is happening.
For a company at $10-50 million in spend, choosing one is a big decision, and the buying process is often tilted against you. Demos are built to impress. Feature lists run to hundreds of lines. Pricing is hard to compare.
Here is how I would approach it.
If you did the baseline in Article 3, you already know your spend, suppliers, rates and process. Use that to write requirements before you see a single demo. Make sure that you understand what your current pain points are and what you are trying to solve with the technology and the program.
Split them into three groups:
Most mid-sized programs need fewer must-haves than they think. Typical ones include requisition workflow, supplier management, approval routing, time and expense, invoicing, reporting, and integration with your finance or HR systems.
Fit for your worker types. If you use staff augmentation and project-based or statement of work labor, confirm the system handles both well. Some handle one far better than the other.
By the numbers: project work is moving into the VMS
Spend flowing through vendor management systems rose 7% to $303 billion in 2025, up from 4% growth in 2024, according to SIA’s VMS Global Landscape Summary. Statement-of-work spend made up 39% of the 2025 total, and SIA’s analyst notes that platforms are investing in SOW management and interoperability, so buyers see more value in bringing projects into the VMS. Single-country programs were 72% of VMS clients and 38% of spend, while the 9% of clients running global programs accounted for 36% of spend.
Source: SIA, “VMS spend rises to $303B with increase in SOW,” Sept. 2, 2026.
Coverage for where you operate. Check countries, currencies, languages and local compliance needs. If any of your workers or hiring managers work in another language, test the experience in that language, not just a checkbox that says it is supported.
Reporting you can use. Ask to see standard reports with your kind of data and find out what it takes to build a custom one. Reporting is why most companies buy a VMS, so test it hard.
Integration. Ask exactly how the system connects to your finance, HR and payroll systems, who builds and maintains the connection, and what it costs.
Ease for hiring managers. If managers find the system hard to use, they will work around it, and your program loses visibility. Ask for hands-on time, not a scripted walkthrough.
Enterprise features add cost and complexity. Be careful with:
This is not a rule against growth features. It is a reminder to buy for the program you will run in the next two to three years, with a path to add more.
Pay attention to how specific the answers are. Vague answers to question 2 or question 4 usually mean surprises later.
VMS pricing varies: a fee based on spend, a per-worker fee, a flat license (or subscription), or a mix. Ask each vendor to price the same scenario, using your own numbers, so you can compare like with like. Include one-time implementation, ongoing fees and the cost of anything you need that is not in the base package.
In my experience, the system a company selects matters less than how it is implemented and adopted. A good system, poorly rolled out, delivers poor results. A solid system with a clear plan, trained managers and a committed owner delivers strong ones.
When you compare vendors, weigh the quality of their implementation support at least as heavily as the feature list. Ask who will actually do the work, how many projects they run at once, and what happens when something goes wrong.
A system without good governance is just an expensive database. Article 5 covers how to keep control of your program without building a bureaucracy.
If you are comparing vendors and would like a second set of eyes on requirements or demos, I would be glad to help. Email me at becky@ennisbader.com to schedule a 20 minute discussion.
Every program decision I have seen go wrong had the same root cause: someone made it before they knew where they stood.
Companies pick a technology, issue an RFP, or sign with a provider based on a general sense of their spend. Then the real numbers surface, and the design no longer fits. I have seen many implementations over the years where the procurement leader was convinced they only had 10 suppliers across the country. A month later, when we were getting ready to communicate to the business and the supplier community that the program was being implemented, we uncovered 15 more suppliers that managers have been getting talent from. Leadership was shocked.
A baseline fixes that. It is not a big project. For a company with $10-50 million in contingent spend, it usually takes a few weeks of part-time effort, and it makes every later decision cheaper and better.
Four questions:
Everything else, including model, technology and governance, builds on those answers.
By the numbers: why it pays to know your picture
In the same People2.0 survey of larger enterprises:
Source: People2.0 research, reported by Staffing Industry Analysts, Sept. 25, 2026.
Spend. Pull 12 months of contingent labor spend from accounts payable and finance. Break it down by supplier, department, location and worker type (staff augmentation, project-based, statement of work, independent contractors). Do not expect it to be clean. Contingent spend often sits across several accounts and cost centers, and some of it is coded as services or consulting.
Suppliers. List every supplier you paid in the period. For each, note total spend, number of workers, who manages the relationship, and how long you have worked together. Most companies find a long tail: many suppliers with small spend, a few with most of it.
Rates. For your highest-volume roles, compare what you pay across suppliers and departments. Look at bill rates and markups. Where the same role carries different rates, find out why. Sometimes there is a good reason, such as location or skill level. Often there is not.
Contracts. Collect every agreement with every supplier. Note the term, markup or fee structure, conversion fees, insurance and indemnification requirements, and anything unusual. Also note which suppliers have no current agreement.
Workers. Where you can, find out how many contingent workers you have at any point in time, how long they have been with you, and who they report to. Long-tenured contingent workers are both a cost and a compliance question.
Process. Write down how a hiring manager actually engages a contingent worker today: who approves, which supplier they call, how onboarding works, how invoices get approved. Describe what really happens, not what the policy says.
You need a small group: someone from finance or accounts payable who can pull the data, someone from procurement, contracts or HR who knows the suppliers, and a sponsor with the authority to ask hiring managers for information. A baseline led by one person with no sponsor stalls at the first department that does not respond.
Three outputs matter:
The baseline also gives you a starting point for measuring results. If you do not record where you started, you cannot show what changed.
Once you know where you stand, you can evaluate technology with real requirements instead of a vendor’s feature list. That is Article 4.
If you would like help running a baseline, I am happy to talk about how I can help. Email me at becky@ennisbader.com to schedule a 20 minute discussion.
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.
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
Source: SIA, “Global MSP spend rises 4% to $244B,” Sept. 21, 2026.
| Fully managed (MSP) | Hybrid | Self-managed | |
| Who does the daily work | Provider | Internal owner + VMS | Internal team |
| Internal capacity needed | Low | Moderate | High |
| Cost structure | Provider fees, often tied to spend | Technology fees + internal time | Mostly internal time |
| Visibility | High | High | Depends on your discipline |
| Speed to launch | Moderate to slow | Moderate | Fast |
| Best when | Spend is complex and your team is stretched | You want control with real data | Needs are simple and you have a capable owner |
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.
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.
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.
If your company spends between $10 and $50 million a year on contingent labor, you probably have more of a program than you realize and less control than you think.
I have spent 30 years building and running these programs. The companies that struggle most are rarely the ones with no program at all. They are the ones where the program grew by accident: a few staffing vendors added over the years, hiring managers who each negotiate their own rates, and nobody who owns the whole picture. For example, I had a customer once who thought they spent $11 million a year on contingent workers and that they had 4 suppliers that they were utilizing. What they didn’t realize was that they had 3 other vendors billing an additional $5 million annually in 1 department and the workers have all been there long enough to be converted to full time employees because no one was managing to the contracts with the suppliers.
Here is how to tell whether that describes you.
Below about $10 million, spreadsheets and a good relationship with a couple of suppliers can carry you. Above $50 million, most companies already have a formal program because the cost of not having one is too visible.
The middle is where problems hide. The spend is large enough that small inefficiencies add up to real money. But it is small enough that no one is hired to manage it, so it falls to procurement, HR, finance or the hiring managers themselves, all of whom have other jobs.
By the numbers: vendor sprawl and visibility
A survey of 700 senior decision-makers at enterprises with more than 500 employees and over $100 million in revenue, across six countries including the US and Canada, found:
Source: People2.0 research, reported by Staffing Industry Analysts, Sept. 25, 2026.
This was right in line with what I saw from the customer in my earlier example.
Here are seven warning signs that you might need a program to manage your contingent labor.
One or two of these is normal. Four or more means you are paying for the lack of a program, even though you never chose to.
When I say “program” to a company at this size, people picture a large outsourced managed service provider and a long, expensive rollout. That is one version, and it is often more than a $10-50 million company needs.
At its core, a program is just four things:
How you deliver those four things, with an outside provider, with technology, or mostly with your own team, is a separate decision. I cover that in the next article.
Answer yes or no:
Four or more “no” answers mean a program would likely pay for itself. Two or three means targeted fixes may be enough. Zero or one means you are in better shape than most.
You do not need to make big decisions yet. The best first step is to find out where you actually stand: your total spend, your suppliers, your rates and your contracts. I will walk through that baseline in Article 3. Before that, Article 2 covers how to choose a model that fits a company your size.
If you would like help figuring out where you stand, I am happy to talk it through. Email me at becky@ennisbader.com to schedule a 20 minute discussion.