Reliable Remote Staffing
Since 2004
Engagement models
How an account is set up before any work begins. The model decides who is assigned, how capacity is agreed and what the first weeks measure — not what the work costs, which is set per engagement.
Most accounts start on one and move to another as the volume settles.
Named people working only your account, on your systems, to your SOPs. The model behind every client story on this site.
A share of a pod rather than whole people — for work that is real but does not fill a desk.
A defined scope with a start and an end: a catalogue migration, a backlog clearance, a one-off audit.
A small, time-boxed run on your real data before either side commits.
Four steps, in this order, before anyone is assigned.
What the work is, what systems it lives in, what good looks like.
A slice of real work, so the estimate is measured rather than guessed.
Named people assigned, the SOP written down and agreed with you.
The first weeks set the baseline; reporting runs against it.
What a buyer asks before anything else. The rate itself is quoted per engagement; everything around it is answered here. Clause numbers refer to the Terms and Conditions, which govern — and where a Service Agreement says something different, the Service Agreement wins.
Most accounts are priced per dedicated team member, per month, by role and by the hours covered — a catalogue associate, a Vendor Central specialist and a reporting analyst are not priced the same because the training and oversight differ. Hourly, milestone, fixed-price, transaction and retainer bases are all available where the shape of the work suits them better.
There is no setup fee. After a scoping call you get a written quote naming the roles, the shift pattern and the monthly cost, in a form you can hand to your finance team. Invoices are payable within thirty days.
Three to four weeks is typical: about a week to document your workflow, one to two to recruit or reassign and train against it, and a supervised first week on live work before the team runs unaided.
Where the process is already documented and system access is ready, we have started inside ten working days. The constraint is almost never recruitment — it is how long it takes to write down what good looks like, which is why that step is not compressed.
Operationally: every process has a written QA rubric agreed before go-live, and the error rate is reported alongside the work rather than on request. If quality slips, StaffCloud retrains or replaces at its own cost.
Contractually, the remedy is to re-perform the service or correct the deliverable within a reasonable time, and where that is not commercially practicable, to refund the fees paid for the non-conforming part (Terms 20.2). That is the exclusive remedy for a breach of the service warranty.
Either side may end a Service Agreement for convenience on sixty days' written notice, unless that agreement sets a different period (Terms 23.2). Either side may end it immediately for a material breach the other has not fixed within thirty days of being told about it (23.3).
On termination you pay for work performed up to that date, and where you terminate for convenience, the notice-period fees for assigned people remain payable — they are salaried staff, not contractors who can be stood down. Transition assistance is available for up to thirty days afterwards (23.4).
Every client story on this site came out of a live account — a listing nobody could unblock, a chargeback nobody had time to dispute, a support queue that had outgrown the person holding it.
Tell us the workload
We will map the roles, the hours and the cost, and come back within one working day.
Or submit an enquiry — the full form, with a service line