Revais ← All insights
Insights · Staffing

Hire the workload, not the headcount.

July 02, 2026 · Revais

When the CRM needs an owner, the reflex is to open a requisition. But the honest question comes first: do you need another employee, or do you need fifteen good hours a week from someone who already knows the platform cold?

Most platform workloads are a part-time job wearing a full-time salary. The CRM needs ten to fifteen hours of real administration a week. The ERP needs a workflow fixed this month and a reporting pass next quarter. Hire a 40-hour employee for that, and here's what you're actually buying:

The 40-hour week you're paying for The work · ~15 hrs Paid idle capacity · ~25 hrs A part-time contractor is priced from the blue part only.
Typical mid-market platform administration load. Yours may differ — that's the point: buy the hours the work needs.

And the salary is the visible part. Payroll taxes, benefits, PTO, recruiting fees, tooling, training, and management overhead push the true cost of an employee to roughly 1.25–1.4× base salary — the standard loaded-cost rule of thumb — before a single hour of work is delivered. A contractor is one number: the rate, times the hours the work required.

What one productive year actually costs Full-time hire Base salary · 1.0× Taxes+benefits ≈ 1.25–1.4× salary, every week of the year · green = recruiting + overhead Contractor Rate × hours used No benefits load, no recruiting fee, no idle weeks — scales to zero when the work does Bars illustrative; the loaded-cost multiple is the widely used planning benchmark.

The third problem with headcount is that it can't breathe. Platform demand swings — an implementation quarter needs sixty hours a week, the quarter after needs twelve. A salaried seat holds flat through both: idle in the troughs, drowning in the peaks, which is when the consultants get called anyway.

Demand moves. Headcount doesn't. Full-time capacity — over-staffed here, under-staffed there Contract hours, re-set to the work Actual platform demand Illustrative year. 20 hours this month, 60 the next — the engagement flexes; a salary can't.

There's a compounding edge, too: when the contractor comes from a bench that retrains quarterly on platform releases and agentic AI, you skip the ramp-up a new hire needs and inherit the training budget you never had to spend.

When the full-time hire wins

Sometimes the requisition is right, and pretending otherwise would make us the pitch deck we keep telling you to distrust. A true 40-hour recurring load, work that needs deep internal ownership, or a role embedded in daily operations and institutional politics — those belong to an employee. The test isn't philosophy, it's arithmetic: if the workload fills the week every week, hire it. If it fluctuates, specializes, or peaks — contract it.

The best technology operations don't have the most seats. They deploy the right expertise at the right hours.

You don't always need another employee. Sometimes you need the right expert for the right number of hours — and a partner whose job is keeping that expert current.

Request talent   Book 30 minutes