Procurement asks for 3 quotes, lines up the monthly rates, and picks the middle one. Nothing in that process touches the terms that decide whether the engagement works, because those sit in clauses nobody printed in the proposal. The questions below are the ones we’d want asked of us. They’re ordered the way a conversation runs, from employment through to exit. A serious outstaffing company answers all 12 in one call without going away to check. Vagueness this early tends to be a preview.
Start with who employs the person
Ask which legal entity signs the engineer’s employment contract, in which country, and whether that entity belongs to the outstaffing company itself or to a local partner. Both arrangements exist. Only one of them puts the provider’s own name on the obligation, and the difference surfaces during a termination, not during onboarding.
The engineer’s own contract matters as much as yours. Assignment of intellectual property, confidentiality, notice period. Your service agreement can promise you IP ownership while the employment contract behind it says nothing of the sort, and that gap is where disputes begin. A provider that offers to show the relevant clauses, redacted, is answering properly.
Questions about the people, not the pipeline
Every provider says it has a pipeline. The useful question is narrower: how many engineers with this exact skill set has it placed in the past 12 months, and in which countries. An honest answer sometimes comes back as none yet, which tells you the search will run longer than the pitch implied.
Screening is the next thing to pin down: who interviews before you do, and what they test. Ask for the interview notes on the candidates you’ll meet. Without them you’re taking the provider’s word for how a conversation went, and the notes also show whether anyone technical was in the room on their side.
The third one in this group is about turnover. Request the retention figure, then ask the question behind it: how many of the engineers placed with clients 2 years ago are still on those teams. Providers of offshore IT staffing services that track this will say so quickly. The ones that don’t come back with an industry average.
| Ask this | A weak answer sounds like |
| 1. Which entity employs the engineer, and where? | We work with partners everywhere |
| 2. What do the IP and confidentiality clauses say? | Standard terms, all covered |
| 3. What notice does the engineer owe? | Depends on the case |
| 4. How many placements like this in 12 months? | We cover all technologies |
| 5. Who screens, and may we see the notes? | Our recruiters pre-vet everyone |
| 6. Retention on placements made 2 years ago? | The market average is around 85% |
| 7. What sits outside the monthly rate? | Everything’s included |
| 8. Who pays during a replacement search? | We’d sort that out together |
| 9. How do raises and reviews work? | We handle HR internally |
| 10. Which hours are contractual? | The team is flexible |
| 11. Can we hire the engineer directly later? | Let’s discuss it when we get there |
| 12. What’s the notice period, both directions? | Same as everyone’s |
Money questions that aren’t about the rate
Equipment, software licences, travel, a workspace if the engagement needs one. These are the items an outstaffing contract treats differently from provider to provider, and they’re small enough individually to escape a procurement comparison while adding up across a year. A provider that itemises them unprompted has made your comparison easier.
Replacement economics deserve their own question. Contracts for offshore IT staffing services treat this variously, so ask directly: if an engineer resigns in month 3, who runs the search, who carries its cost, and do you keep paying while the seat is empty. Put days and numbers on it in writing. Salary review is the twin of that question: a provider that never raises an engineer’s pay will lose them around month 18, and you’ll pay for that in a search you didn’t plan.
Control, hours and the way out
Name the hours you need covered and get them written as contractual. Customary overlap evaporates during the first incident, when the person you need is legitimately off the clock. The same goes for the account manager’s role at the outstaffing company: useful for commercial matters, a problem the moment technical questions start routing through them and the engineer ends up with 2 managers.
Finish on the exit. Notice in both directions, what happens to accounts and equipment, whether direct hire is permitted and at what price. Settling conversion terms before the first placement costs you a sentence in the contract. Settling them 14 months later, when you know you want to keep the person, costs considerably more.
The number we would offer
Ask a provider how many of the engineers it placed 2 years ago are still on those teams, and the answer you want is a count, not a market average. Ours is 30+ long-term client partnerships. Volume of placements only tells a buyer how busy a provider has been; relationships that outlived their second year speak to the thing the question is after, so ask for references from engagements of that age instead of last quarter’s wins.
How to run the call with an outstaffing company
Send the 12 questions ahead. The aim is to get the answers from the people who know them instead of from a salesperson improvising. Write the answers down next to each outstaffing company’s name, and the comparison you end up with beats 3 rate cards.
One habit worth keeping: ask each provider which of the 12 they’d rather you didn’t ask. The ones who name one are usually worth talking to further.
FAQ: checking a provider
How much vendor due diligence is proportionate for one hire?
All 12 questions still apply, since the contract you sign for one engineer is the contract you’ll extend for the next 5. The part you can shorten is reference checking. 2 calls with existing clients are enough for a single placement.
Should we ask for a trial before committing?
A short engagement tells you whether a provider can staff a short engagement. What you’re buying is the second year, and nothing in a 6-week trial reports on it. Read the terms that govern the long version instead.
What should an outstaffing contract say about data access?
Which systems the engineer may reach, under whose accounts, and what happens to that access at the end. Security teams usually want device policy covered too, which matters more when offshore IT staffing services supply the laptop.
Is a cheaper outstaffing company usually a worse one?
Not reliably, and price alone won’t tell you. Check what the quote excludes, how the entity question was answered, and what the replacement clause commits to. A low figure with 3 vague answers behind it is the combination to avoid.
Who should be on our side of the call?
The manager the engineer will report to, plus whoever signs. Legal can read the clauses afterwards, but the technical questions and the commercial ones need to be heard in the same conversation to be compared.

