Tag: #MSP

  • If You’re a Staffing Firm Inside Someone Else’s Managed Program, Here’s What Moves the Needle

    Working inside a client’s MSP or VMS is different from working a client directly. The relationship is no longer just you and the hiring manager. There is a program, a set of rules, a scorecard, and often a provider sitting between you and the buyer.

    I have spent decades on the supplier side of these programs as well as the program side. Here is what I have seen separate the firms that grow inside managed programs from the ones that slowly lose share.

    1. Learn the program, not just the client

    Read the program guide. Know the submission rules, rate structure, timelines, and escalation paths. Firms that win are rarely the ones with the loudest pitch. They are the ones that make no avoidable mistakes in the process.

    2. Speed and fit beat volume

    Submitting many candidates quickly is not the goal. Submitting a few well-matched candidates quickly is. Programs measure submittal-to-hire, and a weak submittal costs you credibility with the people reviewing your work.

    3. Know your scorecard

    Most programs measure suppliers on a short list of metrics, such as time to submit, fill rate, quality of hire, and compliance. Ask what is measured, how often, and how it affects your share of requisitions. Then manage to those numbers on purpose.

    4. Keep the data clean

    Incorrect rates, late timecards, and missing paperwork cause friction that is easy to avoid. Reliable administration is a competitive advantage because so many firms treat it as an afterthought.

    5. Build the relationship behind the system

    A managed program does not remove people from the process. Program managers, account leads, and hiring managers all notice who is responsive, honest, and easy to work with. Show up for meetings and business reviews and bring ideas, not just excuses.  The program team is looking for a partner.

    6. Be honest about where you are strong

    You will not win every category. Tell the program which roles and locations you can fill well and say no to the rest. A supplier with a high fill rate on a narrow set of roles often does better than one chasing everything.

    The takeaway

    Managed programs reward reliability, clarity, and fit. The firms that treat the program as a partner, rather than an obstacle, tend to earn more over time.

    If you are a staffing firm looking to strengthen your position inside managed programs, email becky@ennisbader.com.

  • MSP, MVP, and VMS: What They Are and How They Differ

    These three acronyms get used interchangeably. They shouldn’t be.

    I hear “we need an MSP” when someone means software, and “we need a VMS” when someone means a partner to run the program. Mixing them up leads to the wrong conversations with the wrong vendors. Here is a plain-language comparison.

     VMSMSPMVP
    Stands forVendor Management SystemManaged Service ProviderMaster Vendor Program
    What it isSoftwareA service partnerA single lead supplier
    What it doesHandles requisitions, approvals, rates, timekeeping, and reporting in one platformRuns the program day to day: supplier management, requisition handling, reporting, compliance supportManages the supplier relationship and fills orders first, typically aiming to fill at least 80% itself, then passes the rest to other suppliers
    Who runs the workYour team, using the toolThe provider’s team, on your behalfThe master vendor, as part of a staffing relationship
    Best fit whenYou have a defined program and need structure and dataYou want the program managed with less internal effortYou want a simpler structure with one accountable supplier

    Provider models vary, so the details of any real agreement matter more than the label. Treat the table as a starting point for your questions.

    How they fit together

    They are not always alternatives. A VMS is a tool. An MSP or MVP is a way of running the program, and either can use a VMS. Some MSPs bring their own technology. Others work inside the one you already own.

    Questions to ask any provider

    1. Who owns the data, and can I take it with me if we part ways?
    2. Does the provider also supply workers, and how are conflicts of interest handled?
    3. How are suppliers selected, tiered, and measured?
    4. What does the fee cover, and what does it not?
    5. What will I be able to see, and how often?

    Choosing between them

    Start with the problem, not the product. If you lack visibility, you may need data and a system. If you lack capacity to manage the program, you may need a service partner. If you want a lighter structure, a master vendor model may fit. The right answer depends on your size, your suppliers, and how much you want to run yourself.

    If you are weighing these options and want an independent view, message me or reach out through this site.

  • Your Next Great Full-Time Hire Might Already Be Badging In Every Morning

    Think about the last time you struggled to fill a full-time role. Now think about the contingent workers in your building today. Some of them already know your systems, your team, and your customers. You have watched them work for months.

    Most companies treat contingent labor as a cost line. The companies that get the most from it treat it as a talent pipeline.

    Why conversion deserves a strategy

    When you hire from outside, you are making a decision on a resume and a few interviews. When you convert a contingent worker, you are deciding based on real performance, real fit, and real ramp-up time already behind you. That is a rare amount of information to have before making a hiring decision.

    What gets in the way

    • Nobody is tracking it. If tenure, performance, and manager interest are not visible in one place, strong candidates are never flagged.
    • Contract terms are unclear. Conversion fees, minimum assignment lengths, and notice requirements vary by supplier agreement. If hiring managers do not know the terms, they avoid the conversation.
    • Hiring managers and HR work separately. The manager knows who is excellent. HR owns the requisition. Without a simple handoff, the conversion never starts.
    • No goal attached. What gets measured gets managed. If conversions are not a stated objective of your contingent program, they happen by accident or not at all.

    A simple starting framework

    1. Know your terms. Pull conversion language from every supplier agreement and put it in one summary.
    2. Flag candidates early. Ask managers, at a set point in each assignment, whether this is someone they would hire.
    3. Create a clear handoff between the hiring manager, HR, and the supplier.
    4. Track the numbers. Conversions per year, time on assignment before conversion, and retention after conversion.

    Note: conversion rules and classification questions can carry legal implications. Check your approach with your legal counsel.

    The question to ask

    Does your company track conversions? If you cannot say how many contingent workers became employees last year, or whether they stayed, there may be a hiring pipeline you are not using.

    If you would like to talk through what a conversion program could look like for your organization, message me or reach out through this site.

  • The Invoice Is the Tip of the Iceberg

    Most companies can tell you exactly what they paid their contingent workers last month, because the invoices say so. What the invoices don’t tell you is far more important.

    After 30 years in the staffing industry, I see the same pattern in company after company. Full-time payroll is tracked to the penny. Contingent spend is tracked to the invoice. Those are not the same level of visibility, and the gap between them is where money and risk hide.

    What the invoice shows you

    The invoice shows what you were billed. It does not show whether that was the right amount, for the right people, doing the right work, under the right terms.

    What sits below the waterline

    • Rate creep. Bill rates drift upward over the life of an assignment, and over multiple assignments, without anyone deciding they should. Without a rate card and someone watching it, increases go unquestioned.
    • Off-contract usage. Hiring managers bring in workers through suppliers or arrangements that were never part of your program. The spend is real, but it is invisible to the people responsible for managing it.
    • Missed conversions. Strong contingent workers who would make excellent employees stay contingent because nobody is tracking tenure, performance, or conversion terms.
    • Compliance risk. Worker classification, assignment length, and co-employment questions are easy to overlook when no one has a complete picture of who is on assignment and why. (Questions like these belong with your legal counsel.)

    Five questions to test your visibility

    1. How much are we spending on contingent labor across the whole company?
    2. Who is on assignment right now, and for how long?
    3. What are we paying per hour, and why?
    4. How many contingent workers have we converted to employees in the past year?
    5. Do our managers understand how managing contingent workers differs from managing employees?

    If you hesitated on any of them, you are in good company. Most organizations do. It is also fixable.

    Where to start

    Visibility does not require a new system on day one. It starts with defining what counts as contingent labor in your company, finding every place that spend lives, and agreeing on the handful of measures that matter. Technology comes after that, not before.

    If you would like help finding where your biggest gaps are, I offer a 20-minute conversation to walk through them. Message me or reach out through this site.

    Leave a Reply

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

  • Why MSP Programs Don’t Fail, They Drift

    |

    Year one of a new MSP program feels great.

    The savings come in. Rates are standardized. For the first time, someone can tell the CFO how many contingent workers are on site and what they cost. The QBR deck is full of green arrows, and everyone who fought for the program feels proven right.

    Then year three arrives.

    Fill rates are slipping, but slowly enough that nobody raises an alarm. The same two suppliers get almost every order. Hiring managers have found ways around the VMS. The QBR deck looks exactly like it did last year, and the meeting gets shorter every quarter.

    Nobody can point to the day the program broke, because it didn’t break. It drifted.

    I’ve spent 20 years building and running managed service programs, from $10M to $150M in spend, and led an MSP division to $220M under management. In that time, I’ve seen very few programs fail outright. I’ve seen a lot of them drift. Drift is harder to spot, and it can cost just as much.

    One client stays with me. We came in as the second-generation MSP, taking over from the original provider, and the headcount was half of what we expected. We soon found out why. Several sites had been going around the program entirely, and those suppliers were sending invoices straight to Accounts Payable. When we dug in, the off-program suppliers were charging 20–30% more than the suppliers inside the program.

    On paper, the program looked fine. It just couldn’t see a large share of the workforce it was supposed to manage.

    What drift looks like

    Drift is hard to spot because each sign looks small on its own. Taken together, they tell you the program is running on autopilot:

    • Fill rates and time-to-submit are slipping a little each quarter. No single month is bad enough to escalate.
    • Order distribution has concentrated. Two or three suppliers get most of the work while the rest stop competing, so you’re paying for competition you no longer have.
    • Rogue spend is creeping back. Managers go straight to an agency they like or bring on “consultants” outside the program.
    • Sites that always used contingent workers suddenly have no orders. The work rarely just disappears. More often, those sites are filling outside the program.
    • The VMS reflects how you worked three years ago. Approval chains still route to people who left. Job titles and rate cards haven’t been updated.
    • QBRs have turned into status updates. The same slides every quarter, no decisions and no actions with owners.
    • Savings are reported against a baseline from launch. Nobody has asked what the program should be delivering now.

    Why programs drift

    In my experience, drift almost always traces back to four causes.

    1. Nobody on the client side owns the program anymore. The executive sponsor who championed the MSP moves on. The program manager who knew every detail gets promoted or leaves. Without an owner, the program gets managed, but nobody is steering it.

    2. Scorecards exist, but nobody acts on them. Most programs measure supplier performance. Far fewer actually do something with the results. When a low performer keeps getting orders and a top performer isn’t rewarded, suppliers learn the scorecard doesn’t matter.

    3. The technology froze at go-live. The VMS was configured for the business as it was at launch. The business has changed since then: new sites, new roles, new approvers. The system hasn’t kept up, so people work around it, and every workaround is spend the program can’t see.

    4. Success was defined once and never redefined. Year-one goals are usually about consolidation and rate savings. Once you hit them, the program needs new goals: quality, conversion, tenure risk, total cost. Without them, the team keeps defending results it already delivered.

    Who pays for it

    Drift costs both sides of the program.

    The client pays in money and risk it can’t see. Rates creep up through exceptions. Long-tenured workers build up without anyone reviewing them. Spend leaks outside the program. Then a new procurement leader asks why they’re paying an MSP fee, and nobody has a good answer.

    The staffing firm or MSP provider pays at renewal. A program that has drifted is easy to rebid. The relationship looks fine on the surface, then the RFP lands and the provider finds out the client has been quietly unhappy for a year. If you’re a staffing firm running an MVP, this risk is even sharper. You won the account by promising to manage it, so drift reads as a broken promise.

    The frustrating part is that drift is almost always fixable, and usually without starting over.

    How to catch it

    You don’t need a new MSP or a new VMS to fix drift. You need to look at the program with fresh eyes, then put a rhythm in place that keeps it from happening again.

    Start with a program health check. Review four areas:

    1. Contract and goals. Does the statement of work still match what the business needs? Are the KPIs the right ones for this stage of the program?
    2. Supplier performance. Pull 12 months of order distribution, fill rate, time-to-submit and quality data. Who’s actually delivering, and who’s getting orders anyway?
    3. VMS configuration. Check approval chains, job catalogs, rate cards and site setups against how the business runs today. Find where people are working around the system, and why.
    4. Governance. Who owns the program by name? What decisions came out of the last three QBRs? Were any of them acted on?

    Then put a governance cadence in place:

    • Monthly: an operational review between the program team and the client owner. Look at metrics and exceptions and assign actions with owners.
    • Quarterly: a business review focused on decisions, not status. Cover supplier tiering, rate changes and new goals.
    • Annually: a program reset. Revisit the goals, the supplier base and the technology setup as if you were launching again.

    Finally, close the back doors. Governance meetings catch drift. Controls stop it. That means partnering with two teams that program owners often overlook:

    • Accounts Payable: No invoice for staffing or contract labor gets paid unless it comes through the program or has Procurement’s approval. AP should also flag any new vendor billing for labor.
    • Contracts: Every new staffing, consulting or statement-of-work agreement goes through the program team before it’s signed. Supplier agreements should require suppliers to work through the program.
    • A quarterly spend sweep: AP pulls all payments to labor vendors made outside the program, and the program team reviews them. Whatever turns up is either brought into the program or approved as an exception, on purpose.

    None of this is complicated. It just has to be someone’s job.

    Remember the second-generation program from the start of this article? Fixing it took partnership more than technology. We worked with the client’s Procurement and HR teams, and the client changed one key process: Accounts Payable could no longer pay a staffing vendor without Procurement’s approval. Within 18 months, every remaining supplier was inside the program.

    Everyone came out ahead. The suppliers in the program gained market share. The client saved hundreds of thousands of dollars through rate adjustments and volume rebates. None of that money had been visible until someone went looking.

    The bottom line

    Your MSP program probably isn’t failing. But if your QBRs feel routine, your supplier mix hasn’t changed in a year, and nobody can say what success should look like this year, it’s drifting.

    The programs that last aren’t the ones with the best launch. They’re the ones someone keeps steering.

    Which of these warning signs have you seen in a program you’ve run or worked with? I’d love to hear in the comments.

    Becky Ennis-Bader is the founder of Ennis-Bader Workforce Strategies, which helps staffing firms and companies design, launch and govern contingent workforce programs. Services include MSP/MVP Program Design & Launch, VMS Selection & Implementation Support, and Program Governance & Operations. Learn more at ennisbader.com or follow the company page for more on building programs that last.

    Leave a Reply

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