Staffing supplies people who are available. Search finds the people who can do the job, most of whom are not available.
Both are legitimate. They solve different problems, they cost different amounts, and using the wrong one is the most common reason an SAP role sits open for six months.
Here is how to tell them apart, and how to work out which one your requirement actually needs.
How does SAP staffing work?
A staffing firm maintains a bench and a database. When a requirement arrives, it is matched against people who are already known, already looking, and already available.
The mechanics are volume-driven. The role is advertised. A keyword search runs against the database and the job boards. Resumes are screened for matching terms. A batch is submitted, usually quickly, often within days.
Several firms typically work the same requirement at once, on a contingent basis, and whoever submits an acceptable candidate first gets paid.
That model works well when three things are true: the skill is reasonably common, speed matters more than precision, and there are enough available people that a database match is likely to land.
For contract roles on a defined scope, it is frequently the right answer. Data migration support, testing surge, additional configuration capacity during a build phase. The requirement is clear, the work has an end date, and the candidate does not need to be persuaded to leave a career they are happy in.
How does SAP search work?
How does SAP search work?
A search firm starts from the opposite end. Not from who is available, but from who exists.
The market is mapped: the organizations running comparable SAP programs, the named individuals inside them, and who has worked alongside that profile before. Every relevant person is approached directly and confidentially, whether or not they are looking.
Assessment is a conversation rather than a keyword match. What the person actually owned on a program, not what their resume lists. Their motivation, their circumstances, their compensation in full, what else is live in their process, and how exposed they are to a counteroffer.
Fewer candidates are presented. Three to five is normal. Each one has been spoken to properly, and the reservations are stated openly alongside the strengths.
That model is necessary when the person you need is not looking. Which, for senior SAP roles, is almost always.
Staffing or search: which does your role need?
| SAP staffing | SAP search | |
|---|---|---|
| Starts from | Who is available | Who exists |
| Finds people by | Advertising and database matching | Mapping and direct approach |
| Candidate is usually | Actively looking | Employed and not looking |
| Volume presented | Many, screened | Three to five, assessed |
| Commercial basis | Usually contingent, often multiple firms | Retained, exclusive or engaged |
| Speed to first submission | Days | Two weeks |
| Best for | Contract, defined scope, common skills | Permanent, scarce skills, decision-making roles |
| Fails when | The right person is not looking | The role is genuinely commoditised |
Why does the distinction matter more in SAP than in general IT?
Why does the distinction matter more in SAP than in general IT?
Three reasons, and all of them are specific to this market.
Specialist SAP roles take more than twice as long to fill. The market average is over ninety days, against roughly forty-four days for general IT. That gap is not inefficiency. It is supply.
The scarcity is specific, not general. There are plenty of people whose resume says SAP. There are very few who have delivered a live ECC-to-S/4HANA conversion end to end. On paper those two groups look identical. The difference only emerges in conversation, which a keyword match cannot have.
SAP terminology defeats keyword search. Finance appears as FI, CO, FICO, Finance, Central Finance and Treasury, depending on who wrote the profile and when. HR appears as HCM, HXM, SuccessFactors and Human Capital. The word SuccessFactors also turns up in profiles describing the success factors of someone's career, which has nothing to do with the platform.
The result is noise in both directions. Relevant people are missed because they described the same work in different language. Irrelevant people fill the results because a term matched by accident.
That is why a database-first approach underperforms here in a way it does not in, say, Java development. The database is only as good as the language the candidate happened to use.
When is staffing the right answer?
Worth saying plainly, because most articles on this subject are written by search firms and conclude that search always wins. It does not.
Use a staffing approach when:
- The role is contract, with a defined scope and an end date
- The skill is genuinely available in the market
- You need capacity rather than authority
- Speed of submission matters more than depth of assessment
- The work can be picked up by a competent person without extensive context
Configuration support during a build phase, testing capacity before a cutover, additional Basis cover through a go-live. These are real needs, they are common skills, and paying for a mapped search would be paying for precision you do not require.
When does staffing fail?
What should you ask a supplier before engaging them?
Four questions. The answers tell you which model you are actually buying, regardless of what the firm calls itself.
Who did you approach, and what came back? A search firm can name the organizations it mapped, who was contacted, who engaged and who declined with the reason given. A staffing firm can tell you who responded.
How many candidates will I see? Three to five assessed is a search. Fifteen screened is staffing.
What did this person actually own? Ask about a submitted candidate. If the answer repeats the resume, nobody has had the conversation.
What are the risks with this candidate? A proper assessment surfaces the hesitations, the competing processes and the counteroffer exposure up front. Enthusiasm with no reservations attached usually means nobody asked.
The short version
Staffing answers "who is available?" Search answers "who could do this?"
For contract capacity on defined work, availability is the right question and staffing is the efficient answer.
For anything that holds decision rights or has to survive go-live, availability is the wrong question entirely. The people who could do it are employed, and the only way to reach them is to go and find them.
Is SAP search more expensive than SAP staffing?
Per hire, usually. Against a role sitting open for six months, rarely. The cost of an empty seat on a live programme, of a contractor covering it, or of a hire who cannot hold design authority, generally exceeds the difference.
Can one firm do both?
Yes, and many claim to. What matters is which process they are actually running on your requirement. The four questions above establish it in about ten minutes.
Does contract work always mean staffing?
No. Senior interim roles, particularly programme leadership and architecture cover, are scarce enough to need a mapped approach even on a contract basis.
How long should a senior SAP search take?
Six weeks from first conversation to start date is achievable on a permanent search: two weeks to present assessed candidates, two weeks for your interview process, two weeks notice. The market average for a specialist SAP role is more than ninety days, and the variable that usually decides it is the speed of the client's own process.
