Contract rates and extension odds

The offer is on the table. The rate is a little above what you were on, the start date is three weeks out and the agency wants an answer by Friday. What the offer does not tell you is whether the program will still be funded in nine months, whether your seat is on the critical path or the first to go at the next re-baseline, and whether the rate is good because you are scarce or because the program is in trouble.

Experienced S/4HANA, Dynamics 365, Salesforce and Workday people know the rate is the least informative thing about a contract.

How rates are actually set

Program phase. Design and architecture seats are priced early, when the program is well funded and the sponsor is optimistic. Build and test rates are set against a schedule already under pressure. Cutover and hypercare rates can be the highest of the cycle for the few roles the program cannot go live without, and the shortest.

Scarcity of the module or role. A finance lead with the industry, an integration lead who knows the legacy estate, a data migration lead who has done it twice: these are priced by how few of you there are in the city that quarter.

Funding through go-live. Programs funded phase by phase pay well for the current phase and renegotiate at each gate. Programs with budget approved through go-live pay more evenly and extend more predictably.

Direct or through the SI. Working directly to the client usually means a higher rate and a seat at the client’s table. Working through the integrator usually means a margin taken, a longer run of work and a view of the next program.

What drives extensions

The phase you join in matters most. People who join at design or early build and are still there at test have become part of the program’s memory, and memory is expensive to replace. People who join late in build for a specific deliverable are extended if it grows and released if it does not.

Being on the critical path matters nearly as much. If the cutover date depends on your work, you will be extended through cutover. If someone else could absorb your work, you are the first saving.

The client’s view of the SI shapes who stays. A client happy with its integrator extends the SI’s people and trims the client-side contractors. A client in a strained relationship builds its own bench, and the independents who know the solution become the insurance policy.

The hypercare plan decides what happens after go-live. A funded hypercare period with a defined handover to a run team is a documented extension for the people who built the solution. If hypercare is “we’ll see”, assume the program ends for you at go-live.

Five questions to ask before signing

Ask these of the hiring manager, not the agency, and notice how quickly the answers come.

1. Is the budget approved through go-live, or to the next gate? The best single predictor of your extension odds.
2. Who owns the cutover decision? A named client executive means the program has a spine. “The steering committee” or the SI means the date will move.
3. What is the SI’s role, and how is it going? The answer tells you whether you are joining a program or a rescue.
4. Has the program been re-baselined, and how many times? One is normal. Two is a pattern. Three means the next one takes your seat.
5. Who is the business process owner for my area, and have they signed off the design? No named owner, or one who has not signed, means the design will change under your build.

The red flags

A rate well above market for the phase. Programs pay above the odds when they are behind or when the work is harder than the role description says. Know why the number is what it is.

A start date before the design is signed off. Building against a design that is still moving means rework, blame and a short contract.

An SI that has just changed. A program that has replaced its integrator mid-cycle has lost its memory and will spend months rebuilding it. It can be a long, well-paid contract and rarely a calm one.

When permanent beats contract

Two moments. The first is the move into a platform lead or architecture seat. These are hired permanent because the business needs someone who will still be there when the integrator leaves, and they carry ownership of the roadmap, which a contractor cannot accumulate. For a senior specialist, the platform lead seat is the path to head of enterprise applications or CIO.

The second is the lull between program cycles. When the large programs in your city finish together, the bench is full and rates ease. A permanent role taken in a quiet market, in an organisation about to start its next cycle, can be a better three-year decision than waiting for the market to turn.

How to position yourself

Lead with the cutover story: which program, which weekend, your role in the go/no-go, what broke in hypercare and what you did about it. One detailed cutover story is worth a page of modules.

Be specific about modules and industries together. “S/4HANA finance” describes thousands of people. “S/4HANA finance for a multi-entity group with intercompany and a legacy consolidation tool to retire” describes you.

Hold references from program directors and client sponsors, not only the SI partner who sold you in. A program director who can say you were the one they relied on before go-live is the reference that moves a hiring manager.

The honest read

When a contractor brings us an offer and asks whether to take it, we give a plain answer on where the program is in its cycle, how the rate sits against the phase, and what the extension odds look like. Sometimes the answer is to take it. Sometimes it is to hold out for the seat that leads somewhere rather than the one that pays best this quarter.

We work the enterprise platform market across programs, so who is funded, who is re-baselining and who is about to start is a pattern we see before it is public. The live roles are one view of it. The conversation is a better one.

Questions candidates ask