Tag: #WorkforceStrategy

  • Governance Without Bureaucracy

    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.

    1. Name an owner

    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.

    2. Write a short policy

    You do not need a 40-page manual. A two-to-three-page policy that covers the following is enough:

    • Who can engage contingent workers and for what purposes
    • Which suppliers to use and how to request an exception
    • Approved rate ranges for common roles
    • Required agreements and onboarding steps
    • Maximum tenure, and what happens when a worker reaches it
    • How invoices are approved

    The test of a good policy is whether a hiring manager can read it in ten minutes and follow it.

    3. Tier your suppliers

    Most mid-sized programs have too many suppliers. A tiered approach brings order without needing an elaborate process.

    TierWhoHow you manage them
    PreferredA small group of suppliers with the most spend and best performanceStandard agreements, agreed rates, regular reviews
    ApprovedSuppliers used for specific skills or locationsStandard agreements, reviewed annually
    ExceptionOne-off or niche suppliersRequires 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.

    4. Build a one-page scorecard

    A scorecard that tracks 30 metrics gets ignored. One that tracks eight to ten gets used. Choose a few in each of four areas:

    • Cost: total spend, spend by supplier, average rate versus approved range
    • Quality: time to fill, submission-to-hire ratio, manager satisfaction, early terminations
    • Compliance: workers without a current agreement, workers over tenure limits, exceptions granted
    • Supplier performance: invoice accuracy, on-time submissions, responsiveness

    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.

    5. Set a review rhythm

    • Monthly: the owner reviews the scorecard and follows up on exceptions
    • Quarterly: the steering group reviews results and decides on changes to suppliers or policy
    • Annually: a fuller review of the model, technology and supplier tiers

    This takes a few hours a month. If it takes much more, the design is too heavy.

    Keeping it lean

    A few habits prevent governance from turning into bureaucracy:

    • Every rule should have a reason you can explain in one sentence.
    • Make the right way the easy way. If following the process is harder than going around it, people go around it.
    • Review exceptions. A growing pile of exceptions means the rule is wrong, or enforcement is weak.
    • Retire what is not used. A report nobody reads should be removed.

    Next step

    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..

  • Choosing a VMS at Mid-Market Scale: What to Require, What to Skip

    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.

    Start with requirements, not vendors

    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:

    • Must-haves: things that, if missing, make the system unusable for you
    • Should-haves: things that would save time or reduce risk
    • Nice-to-haves: things that look good in a demo but you would rarely use

    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.

    What to require

    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.

    What to skip, or at least not pay for

    Enterprise features add cost and complexity. Be careful with:

    • Deep configurability you will not use in your first two years
    • Elaborate workflow engines for approval chains you do not have
    • Modules for worker types you do not engage
    • Advanced analytics and AI features that depend on data volume you do not have yet

    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.

    Questions I would ask every vendor

    1. How many clients at my spend level do you serve, and may I speak with two?
    2. What does implementation look like for a company our size: timeline, your team, our team?
    3. Who supports us after go-live, and what happens when that person changes?
    4. What is included in the price, and what costs extra: integrations, reporting, additional users, additional countries, support?
    5. How does pricing change as our spend grows or shrinks?
    6. What happens to our data if we leave?
    7. What are the three most common reasons clients are unhappy, and how do you address them?

    Pay attention to how specific the answers are. Vague answers to question 2 or question 4 usually mean surprises later.

    Evaluating mid-market pricing

    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.

    Implementation and adoption matter more than features

    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 simple selection process

    1. Finalize requirements from your baseline.
    2. Shortlist three to four vendors that serve your size.
    3. Send a short written questionnaire rather than a long RFP.
    4. Hold scripted demos using your own scenarios.
    5. Check references, including a client who had a difficult implementation.
    6. Compare pricing on the same scenario.
    7. Decide with a small group that includes someone who will use the system daily.

    Next step

    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.

  • Start With the Baseline: What to Gather Before You Decide Anything

    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.

    What a baseline answers

    Four questions:

    1. How much are we spending, and on what?
    2. Who are we buying from?
    3. What are we paying?
    4. What have we agreed to?

    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:

    • 75% said contractors, freelancers and temporary workers make up at least 11% of their workforce, and 43% said more than 20%.
    • 53% ranked controlling costs while keeping workforce agility as their biggest contingent workforce challenge.

    Source: People2.0 research, reported by Staffing Industry Analysts, Sept. 25, 2026.

    What to gather

    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.

    Baseline checklist

    • ☐ 12 months of contingent spend, by supplier, department and worker type
    • ☐ Complete supplier list with spend and worker counts
    • ☐ Rates for top 10-15 roles, compared across suppliers
    • ☐ Copies of all supplier agreements, with gaps noted
    • ☐ Current headcount and tenure of contingent workers
    • ☐ The real engagement process, from request to invoice
    • ☐ Names of everyone who manages a supplier relationship
    • ☐ Open compliance questions (classification, tenure, co-employment)

    Who should be involved

    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.

    What to do with what you find

    Three outputs matter:

    • A one-page summary of total spend, supplier count, rate variation and contract gaps. This is what leadership needs to approve the next step.
    • A list of quick wins, such as consolidating suppliers on the long tail, fixing missing agreements or correcting obvious rate outliers.
    • A set of requirements for the model and technology decisions that follow.

    The baseline also gives you a starting point for measuring results. If you do not record where you started, you cannot show what changed.

    Common mistakes

    • Waiting for perfect data. It will not be perfect. Aim for good enough to see patterns.
    • Skipping the process review. Spend data shows what happened, not why.
    • Treating it as a one-time project. Keep the baseline updated, because it becomes your reporting foundation.

    Next step

    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.

  • 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.

  • Do You Need a Contingent Workforce Program Yet?

    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.

    Why this spend range is different

    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:

    • 46% manage six or more outside vendors for their contingent workforce, and 17% manage more than 10.
    • 28% named a lack of visibility into workforce data and reporting as a challenge.

    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.

    1. You cannot say, quickly, how much you spend on contingent labor. If the answer takes a week and three people, you do not have visibility.
    2. You work with many staffing suppliers and nobody can say why. Vendor sprawl usually means each manager picked their own.
    3. The same role is billed at different rates. Check two departments using the same job title. Rate variation without a reason is lost margin.
    4. Contracts are missing, outdated or inconsistent. Terms, markups and conversion fees differ by supplier, and some workers are engaged with no agreement at all.
    5. Nobody owns the program. If you ask who is accountable for contingent workforce cost, quality and compliance and get several answers, the real answer is no one.
    6. Invoices are a recurring headache. Disputes, corrections and late approvals are rarely just an accounting issue. They point to unclear rates, weak onboarding or poor supplier communication.
    7. You worry about compliance but cannot prove you are covered. Worker classification, tenure limits and co-employment risk all get harder to manage without a central view.

    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.

    What a program actually is

    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:

    • Visibility: one view of who is working for you, through which supplier, at what rate
    • Standards: consistent rates, contracts and onboarding
    • Ownership: a named person accountable for results
    • Measurement: a short list of metrics reviewed regularly

    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.

    A quick self-assessment

    Answer yes or no:

    • We can report total contingent spend by supplier within a day.
    • Our rates for the same role are consistent across departments.
    • Every supplier has a current agreement with standard terms.
    • One named person owns the program.
    • We review supplier performance on a regular schedule.
    • Hiring managers know the rules for engaging contingent workers.

    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.

    What to do next

    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.