How to buy a VMS for consultants

A buying guide for procurement teams: what to settle before you talk to vendors, what to ask yourselves and every vendor, how to evaluate, and a decision matrix you can fill in on this page.

Plan before you talk to vendors

The decisions you make here narrow the field more than any feature list. Write them down before the first demo.

  • ScopeConsultants and SOW work only, or every kind of contingent worker, from temps to freelancers? A tool built for one is rarely the best at the other.
  • Owner and teamOne owner in procurement who decides, plus the people who will live with the result: hiring managers, HR, finance, IT and security, and legal for the contract.
  • Your baselineHow many consultants you have today, how many suppliers, how many requests a year, and how requests arrive now: email, forms, phone or a system.
  • Success criteriaFor example: the share of eligible requests that go through the system, the time a manager spends per request, the time procurement spends coordinating, rate and contract deviations caught, and invoice errors found.
  • ConstraintsThe systems it must connect to (HR, ERP and finance, identity, e-signature, e-invoicing), where data may be stored, and rules that apply to you, such as public procurement (LOU) or contractor compliance.
  • Commercial frameThe pricing models you can accept (per user, per consultant, share of spend or fixed fee), the contract term, exit terms and who owns the budget.

Questions to ask yourselves

Answer these as a team before you shortlist. They decide which kind of tool you need, or whether you need one at all.

  1. Who raises consultant requests, and how often does each person do it?Occasional requesters need a different experience than a central team that buys every week.
  2. What happens after a request is sent today, and where does it stall?
  3. Where do people go around the process, and why?
  4. Do you want to hold supplier relationships and rate data yourselves, or hand them to a provider such as an MSP or a broker?
  5. Is a module in a suite you already run good enough for consultants, or are consultants a category of their own for you?
  6. Which decisions must a person always make, and which follow-up could a system take over?
  7. Who will run the system day to day, and how much time do they have for it?
  8. What would make you keep things as they are?Staying is a valid outcome. Say what would have to be true for a change to be worth it.

Questions to ask every vendor

Ask the same questions of every vendor, and ask them to show rather than tell where they can.

Show us

  1. Show an occasional manager completing a real request from our list, without help.
  2. Show what happens when a decision is waiting: who is reminded, when, and what procurement sees.
  3. Show how a contract that differs from the request is caught before it is signed.
  4. Show an extension and an end date being handled.

AI and control

  1. What does the AI do on its own, and what always needs a person to approve?
  2. Can we see and change those rules ourselves?

Data and security

  1. Where is our data stored, which sub-processors touch it, and is it used to train models?
  2. Which certifications do you hold, and can we see your data processing agreement?
  3. How do we export everything, in which format, and at what cost?

Delivery

  1. What is the elapsed time from signature to the first live request, and what does it take from our side?
  2. Who owns each integration, and what happens when the other system changes?

Commercial

  1. What makes the price grow: users, consultants, spend or modules?
  2. What do suppliers pay to work through the system, and how does that reach our rates?
  3. What are the term, notice period, price increase terms and help at exit?

Proof and support

  1. Can we speak to two customers of our size and region, one of them with more than a year of use?
  2. Which results were measured in your pilots or rollouts, and how were they measured?
  3. Which languages and hours does support cover, and how accessible is the product (WCAG)?

How to evaluate

Four methods, each good at something different. Most teams combine them.

RFP

Good for comparing scope, terms and price on paper. Weak at showing how the product works for an occasional user.

Scripted demo

Give every vendor the same script built from your own cases, including a stalled decision and a contract exception, and score each step.

Reference calls

Ask about the first six months, what still needs manual work, and what they would do differently.

Pilot

Run real hiring needs through the system. Agree the success criteria first, measure manager effort and procurement coordination separately, and count participation against every eligible request.

A common order: a short list, scripted demos with two or three vendors, reference calls, then a pilot with the one you lean towards. In the public sector, check how a pilot fits your procurement rules before you start.

Decision matrix

Set how important each criterion is for you before you score. Then score each option from 1 to 5 after demos, references or a pilot. Nothing is sent anywhere: the matrix stays in this page, and you can download it as a CSV.

The total is the weighted score as a share of the highest possible score, counting only the criteria you have scored. "Not relevant" removes a criterion from the total.

Buying a VMS, questions answered

How long should a VMS evaluation take?

Plan for a few weeks of planning, a short list, demos and references, and then a pilot over one or more real hiring needs. The pilot length depends on how often you hire: it should cover enough requests to see follow-up and at least one exception.

Should we run an RFP or a pilot?

Often both. An RFP compares scope, terms and price; a pilot shows how the product works for the people who will use it. A scripted demo with your own cases sits in between and is a good way to choose who gets the pilot.

How should we weight the criteria?

Start from your success criteria. If most requests come from occasional managers, weight their experience and follow-up higher; if spend control is the main problem, weight reporting and cost higher. Set the weights before you score, so the scores do not shape them.

Should we choose a VMS or an MSP?

A VMS is software your own team runs, so you keep the supplier relationships and the rate data. An MSP runs the program for you, usually for a share of spend, and takes the coordination work off your hands. Choose by who you want to do that work and who should hold the data.

What drives the cost of a VMS?

The pricing model (per user, per consultant, share of spend or fixed fee), the modules, integrations and implementation services you need, and what suppliers are charged, since supplier fees can find their way into rates. Ask each vendor to price the same scenario.

Who should be on the evaluation team?

A procurement owner who decides, two or three hiring managers who raise requests, and people from HR, finance, IT and security, and legal. Hiring managers should take part in the demos and the pilot, not only see the result.

Fill is one of the vendors you can evaluate this way. To score Fill in the matrix, start with a pilot on a real hiring need. Book a demo

Take procurement off the spreadsheets.

See the product