How much does your SAP staffing agency actually keep?

Here is the single most important thing an SAP consultant has to unlearn when they go independent: the rate the client pays and the rate you receive are two different numbers.

As an employee, there was one figure, your salary, and it was yours. In contracting, there is a rate the end client has budgeted for your seat, and there is the rate that lands in your company’s bank account, and between the two sits a chain of intermediaries, each taking a slice. Sometimes that chain is one link and the slice is modest. Sometimes it is three links deep, and by the time the money reaches you, a third or more has been taken along the way, perfectly legally, often for genuine services, and almost always without anyone telling you the numbers.

I saw this from the inside before I was ever a contractor. In one of my early roles at one of the Big Four firms, I worked in the PMO of a very large SAP program, running the margin analysis. My job involved tracking what the client paid, what the firm paid its own people and its subcontractors, and the spread in between. So when I went independent and found myself at the bottom of that same chain, I already knew what sat above me, and roughly how big the gap was.

Most SAP contractors never get that view. They see one number, their own, and negotiate against it. This post makes the chain visible enough to work with.

The chain has more players than you think

Almost every SAP engagement involves some combination of four parties: the end client, a system integrator, a staffing agency, and you (usually as a company, not a person). Those four combine into a handful of recognizable configurations, from the shortest (you direct to the client, most profitable and hardest to obtain) to the longest (multi-tier vendor chains routed through a VMS, three or more intermediaries deep).

Every link takes a slice. Three light margins in a row are not light by the time they reach the bottom.

Margin vs. markup: the language matters

The intermediary’s cut goes by several names, and the framing is often designed to obscure the size.

There is a client rate (what the end client pays for your seat) and a contractor rate (what your company receives). The difference can be expressed two ways, and the two sound very different for the same money:

• Margin on the client rate: “the agency takes 15%” means for every 100 the client pays, you get 85.
• Markup on your rate: “the agency marks up 18%” means on your 85, they add 18% to reach ~100 for the client.

Same spread, different-sounding number. Intermediaries naturally quote whichever sounds smaller. When someone tells you their margin, always pin down margin of what, so you’re comparing like with like.

Why the SI spread is usually bigger than the agency margin

This is the part most SAP contractors get wrong. Agency margins and SI spreads are different animals, and the SI spread is usually the larger of the two.

A staffing agency is fundamentally passing along a body. Its margin is constrained by competition. Market pressure keeps it within a range.

A system integrator is not passing along a body. It’s selling the client a branded deliverable at a rate card (a fixed price per grade of consultant) and staffing that seat with a mix of its own employees and subcontractors. The SI keeps the difference as the price of its brand, its methodology, its delivery risk, and its client relationship.

The spread between an SI’s rate card and what it pays a sub can be substantial, and it’s noticeably larger than a pure agency margin. The SI isn’t selling access to you. It’s selling a promise: if this program fails, we’re on the hook.

I still get a version of the inside view. Alongside contracting, I do some recruiting on the SAP staffing side, sourcing consultants for firms and end clients, which has only confirmed how real and how wide that spread can be. The specific numbers are commercially confidential and vary widely, but the pattern is consistent: contractors at the end of a long chain frequently see well under two-thirds of what the end client is actually paying for the seat.

What the margin actually buys

Once you see the spread, it’s tempting to fixate on the margin as pure extraction. It usually isn’t. The intermediary’s cut pays for real, specific services: finding the work, absorbing payment and credit risk, handling worker-classification compliance in markets that require it (IR35, PSB, Scheinselbstständigkeit), and, in the case of SIs, plugging you into programs and pipelines you couldn’t reach alone.

The right posture is not “eliminate all margin.” It’s knowing the margin and making sure you’re actually getting the service you’re paying for. An agency that finds you continuous work, pays you in 14 days, and shields you from client credit risk has earned its cut. One that placed you once, adds nothing, and pays you slowly on 60-day terms has not.

The structural disadvantage every SAP contractor faces is information asymmetry: intermediaries know both numbers, you know one. You cannot eliminate that gap, but you can erode it.

---

If this diagnosis lands, the full playbook (the five contract chain configurations in detail, how to benchmark rates independently, how to renegotiate margin openly, and how to consciously choose your route through end clients, SIs, and agencies as your practice matures) is in Chapter 4 of the book: The Independent SAP Contractor: A Practical Guide to Building a Freelance Career in the SAP Ecosystem.

Available now on Amazon in Kindle and paperback editions.

— K.C.L.