For RPO Services

RPO Services Snapshot

White-label recruiting infrastructure for RPO providers — multi-tenant pipelines, client SLA tracking, and revenue-per-hire reporting for embedded recruiting teams.

Built for the RPO delivery model

RPO is unique — you’re an embedded function inside someone else’s company. Your candidates interact with the client brand. Your SLAs are contractual. Your delivery team needs to deliver across multiple clients simultaneously without confusion. The RPO Services snapshot is built around all of it.

  • Multi-tenant pipelines — each client gets their own pipeline, their own brand, their own candidates. Your team sees the unified view; candidates and hiring managers see only their client.
  • Client-branded candidate experience — sender ID, email domain, candidate portal, and offer letter template are all per-client. Candidates feel like they’re interacting with the client.
  • SLA dashboard — time-to-shortlist, time-to-fill, hiring-manager satisfaction, candidate NPS — tracked per client and aggregated for your delivery lead.
  • Recruiter capacity allocation — each recruiter’s time budget is split across clients. The system flags when a client is consuming more than allocated.
  • Revenue-per-hire reporting — for fee-per-hire models, see revenue per role / per recruiter / per client. For managed-service models, see effective hourly rate.

Designed for delivery leads

The RPO delivery lead has the hardest job in recruiting: deliver to multiple clients, manage recruiter capacity, hit SLAs, expand accounts, and report to executives. The snapshot gives them the dashboard they need.

At a glance: “Acme is on track. Beta is yellow on time-to-shortlist for the engineering req. Gamma’s NPS dropped to 7.4 — let’s get a hiring-manager call set up.” The data they need to manage delivery is one screen away.

Compliance across multiple clients

When you’re an embedded recruiting function, you inherit each client’s compliance posture: their EEO categories, their OFCCP obligations (if federal contractor), their state-specific requirements. The snapshot per-client-configures EEO data collection, retention policies, and audit-log access.

For multi-state, multi-client RPO providers, this is the single biggest pain point we solve. No more “what does this client need us to track?” — it’s baked into their pipeline configuration.

What this typically replaces

For RPO providers, this commonly replaces a custom-configured Bullhorn or iCIMS instance per client (with the operational headache of running parallel ATSs). The snapshot unifies your team’s tooling while keeping the client experience separated. Your delivery lead gets a single screen. Your recruiters context-switch less. Your finance team gets the per-client reporting your contracts demand.

RPO Services

Common questions

Can each RPO client have their own branded experience?

Yes. Every client gets their own branded candidate-facing portal, SMS sender ID, and email domain. Candidates experience your client's brand, not yours. Behind the scenes, your team works in one unified ATS.

How do you measure SLAs?

Each client has SLA targets (e.g., time-to-shortlist ≤ 5 days, time-to-fill ≤ 30 days, candidate NPS ≥ 8.5). The dashboard shows red / yellow / green status per client and per role, with breach alerts to your delivery lead.

Can clients see their own dashboard?

Yes — each client gets a read-only dashboard showing their requisitions, candidates in flight, and the SLAs you're tracking against. Increases trust and reduces 'where are we?' emails.

How do you handle recruiter capacity across clients?

Each recruiter has a capacity allocation per client (e.g., 60% Acme, 40% Beta Corp). The system shows utilization and helps your delivery lead rebalance when a client's volume spikes.

Configured for RPO Services, day 15 live.

Same snapshot. Your specialty. Calibrated during your 10 dedicated hours.

Get Snapshot
Book Demo