Per-Mobilized-Employee Pricing: Why HR SaaS Should Match Your Operating Model

Most HR SaaS is priced per active employee, per seat, per month. That works fine for a 200-person tech company where headcount drifts up or down by 5% a year. It works terribly for a 2,000-person manpower-supply business where headcount swings 30% a quarter as projects start and end.

That’s why StimesERP Lite is priced per mobilized employee, and why it’s the right fit for businesses where people, not seats, are the unit of work.

What “mobilized” means

A mobilized employee is one who is actively deployed during the billing month: on a project, at a client site, on a roster. Not someone who left in February but is still sitting in your HR system. Not someone on long unpaid leave. Not a candidate in the visa pipeline.

It’s the same metric that already runs your operations dashboards. Now it runs your software bill.

Why per-seat pricing breaks for manpower businesses

Per-seat pricing punishes the wrong things:

• End-of-project demobilizations: you still pay for the seat after the project ends.
• Overseas pipelines: candidates being mobilized but not yet on site inflate the count.
• Conservative HR practices: keeping a clean record of all past employees costs more under per-seat.

So teams either pay more than they should, or hide records to keep the bill down, which destroys data quality and compliance.

Per-mobilized aligns incentives

Per-mobilized pricing rewards:

• Clean off-boarding: demobilize cleanly, remove from the active deployment register, the bill drops.
• Accurate deployment records: the same number drives both your client invoices and your SaaS bill.
• Honest reporting: your operations dashboards and finance dashboards converge.

It also makes capacity planning easy. “If we ramp up the Marsa Tower project by 200 carpenters next month, what’s our HR software bill?” Multiply the carpenters by AED 10 and you have your answer.

What about the months where mobilization swings hard?

For most manpower-led businesses, the swings cut both ways across a year: projects start, projects end, fresh batches mobilize, demobilized employees redeploy. The average smooths out, and your bill ends up tracking the real economic activity of the business.

For businesses with very long, very stable headcount, Lite Starter (free trial) or a custom Lite Pro contract is usually a better fit than the per-mobilized model.

The catch

The model works only if the underlying mobilization data is clean. If your deployment register lives in Excel and updates on a Tuesday afternoon when someone remembers, per-mobilized pricing will surprise you in both directions.

The good news: the manpower supply module inside StimesERP Lite is what generates the mobilization data in the first place. Same source, same numbers, for operations, for client billing and for your SaaS bill.

Want to model your monthly bill against your real deployment register? Book a demo and we’ll do it with you.