Recruitment Process Outsourcing
People decisions with significant organizational, financial, and cultural stakes.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Talent & Outcome Discovery
Confirm hiring goals, volume drivers, target roles, ATS constraints, stakeholders, and measurable success signals.
Discovery Questions
Quick context, why now?
- Tell me in one paragraph what triggered this hiring surge and the timeline you're facing.
- How many permanent hires does your organization average per year, and how many do you expect this year?
- Which roles and job families are driving the majority of the current open requisitions?
- Walk me through a recent high-priority requisition from intake to offer, noting where delays or quality losses happened.
- Who owns requisition intake and prioritization today, and who will sign off on changes to that process?
If leadership demanded a quick win, what would we need to change?
- If a board member demanded a measurable hiring improvement in 90 days, which metric would you need to move to keep them satisfied?
- Which recurring bottleneck most often causes requisitions to age past target time-to-fill?
- How often do candidate quality issues surface after hire, and can you share an example where a hire missed expectations?
- When your internal team is overwhelmed, which steps are skipped or done superficially?
- Estimate the downstream costs or business impacts these hiring failures create in the next 3–6 months.
If volume spikes, where will the operation break?
- If hiring volume doubled next quarter, which part of the process would fail first?
- How many recruiters are currently embedded in hiring teams, and how many hires does one recruiter manage monthly?
- Describe your current recruiter staffing model, including sourcing, screening, and coordination roles.
- Point to the geographies or legal jurisdictions that add the most complexity to scaling recruitment.
- Give the timeline you would need for the first 50 hires versus the next 200 in a ramp scenario.
Who signs, who blocks, and who makes it work?
- Who will sign the final contract, and who needs to be convinced before that happens?
- List the leaders who will be involved in operational handover and day-to-day collaboration with embedded recruiters.
- When there's a recruitment problem, what is the notification and escalation path?
- Identify the SLA terms that are non-negotiable for your procurement and legal teams.
- Please name any internal sponsors who have committed time or resources to enable this change.
If a pilot proved results quickly, what would close the deal?
- What single measurable outcome, shown in a 6-week pilot, would get you to sign a longer engagement that week?
- List the KPIs you already track closely for recruiting performance and weekly reporting.
- How do your leaders define acceptable time-to-fill for critical, revenue-impacting roles?
- Tell me the most common reason SLAs are met but hiring managers still complain.
- Assuming the pilot hits targets, what internal approvals would still be required before contract execution?
The other options you're weighing
- Name the alternative option that would keep you from changing suppliers, and explain why.
- Point to the incumbent or internal approach that currently gives you the most confidence, and tell us what satisfies you about it.
- Has anyone on your leadership team proposed solving this using existing headcount rather than an outside partner?
- Describe the conditions that would have to hold for you to stay with your current recruiting approach instead of switching.
- For a blended model that keeps some internal activities, point to the parts you would insist remain in-house.
Integration, data, and legal gates we must clear
- Identify any technical, legal, or compliance gate that would stop a go-live if unresolved.
- Name the category of ATS or applicant tracking workflow you use, and list the admin contacts who can grant access.
- Are your requisition, offer, and candidate data clean, consistently formatted, and accessible via API or SFTP?
- Please identify the person or team that would own technical integration work, and state how many hours per week they can commit during an eight-week ramp.
- Are there any regulatory approvals, local works councils, or privacy reviews that typically add more than four weeks to your hiring projects?
- What single missing integration, permission, or legal approval would force us to pause or decline this engagement?
Timeline, pilot, and decision blockers
- Assuming a pilot proves our numbers, what internal or external blockers would prevent you from signing a contract that same week?
- Share your target go-live window and list any immovable dates within it.
- How quickly can your ATS admin grant integration access once requested?
- Estimate which internal approval takes the longest and how many days it usually adds.
- Outline the rapid decision process you would expect to activate if a critical blocker emerges during ramp.
Acceptance criteria and the quickest path to yes
- Confirm the person or role that has authority to sign within seven days if the pilot meets agreed KPIs.
- Are there any contractual terms that would require executive approval beyond procurement's signoff, and if so, please name them.
- State the earliest realistic date you could sign if the pilot shows target improvements.
- Provide the names and roles to include on a one-page pilot scope and success criteria document to speed approvals.
- Finally, are there budget cycles or financial approvals that will force decisions into the next quarter?
-
Solution Experience
Walk through how an embedded RPO model delivers predictable time-to-fill, recruiter embedding, ATS integration, and measurable cost-per-hire improvements in the buyer's context.
Solution Experience
- Solution Experience Session
- Confirm the current state and its cost to your team
- You confirm the demonstrated intake-to-offer workflow eliminates the backlog and manual handoffs you described.
- Provide a sample set of recent requisitions and the current ATS time-to-fill report for the proof scenario.
- Run a sample time-to-fill and cost-per-hire forecast using the provided requisition data and deliver the comparison before the follow-up session.
- Agree target operational outcomes
- You agree on concrete time-to-fill and cost-per-hire targets that will define success for a pilot.
- Proof step, recruiter embedding in your intake-to-offer flow
- You and the seller agree the remaining evidence required and a pilot scope and timeline to validate outcomes.
- Confirm the decision-making timeline and list of stakeholders who will evaluate the pilot results.
- Proof step, ATS integration and measurement
- Validate this maps to what you described
- Agree next evidence and pilot scope
- Solution Experience Session
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define scope boundaries: roles and geographies covered, SLA targets, recruiter staffing model, reporting, and ramp/scale rules.
Scope Configuration
- Embed Dedicated Recruiting Team
- Configure Buyer ATS and Workflows
- Import and Reconcile Candidate Records into ATS
- Requisition Intake and Lifecycle Management
- Job Advertising Campaign Management
- Targeted Candidate Sourcing and Outreach
- Screening and Phone Interviewing
- Manage Interview Coordination and Panel Support
- Offer Management and Negotiation
- Onboarding Handoff and Hiring Manager Package
- Recruiter Brand Immersion and Training
- Recruiting Analytics and SLA Reporting
- Rapid Volume Ramp and Scale Support
Scope Questions
Embed Dedicated Recruiting Team
- Which hiring roles (job family and level) should the embedded recruiter team own from day one (provide job family names and seniority levels)?
- How many full-time equivalent recruiters, sourcers, and coordinators do you expect on site or embedded per 100 open requisitions?
- Who will be the named hiring manager partners for the embedded team during ramp (list names or roles and their primary contact method)?
- What recruiter-to-hiring-manager ratio do you require for revenue-generating roles (e.g., 1:6 for sales AE roles)?
- Provide the expected weekly capacity per recruiter in hours for sourcing, candidate screening, and coordination (separate by activity)
- Which background check or assessment vendors must embedded team workflows trigger as part of screening for each role family?
- Which operational tasks do you expect us to own versus keep with your TA team (requisition intake, offer negotiation, interview scheduling, vendor management)?
Configure Buyer ATS and Workflows
- Which applicant tracking system (ATS) do you use as the source of truth for requisition and candidate statuses (include version and any custom objects)?
- What exact ATS field mappings must be created before go-live (example: requisition ID, hiring manager, status, source, offer status)?
- Do you want us to provision API credentials and an integration user for the integration endpoint to perform writes and status updates?
- Which existing ATS workflows should be preserved verbatim and which should be retired (list workflow names and reason)?
- What is the maximum allowed time between our status update and the ATS reflecting that update (desired sync latency in minutes)?
- What acceptance criteria will confirm ATS configuration is complete (for example: 100% of active job templates mapped, webhook test success, and recruiter write-permissions validated)?
Import and Reconcile Candidate Records into ATS
- How many candidate records, by status (active, offer, archived), need to be imported or reconciled into the ATS?
- Which data sources contain candidate records to migrate (legacy ATS export, spreadsheets, sourcing platform exports) and provide file formats?
- What data quality threshold must be met after reconciliation (for example: 95% unique candidate dedupe rate and 98% required-field completeness)?
- Which candidate fields are required to be preserved during import (at minimum: name, email, phone, source, resume PDF, interview history)?
- Who will own the final reconciliation sign-off and what evidence should they review (name and role of owner and documents to review)?
- What acceptance evidence will validate the import and reconciliation is successful (for example: reconciliation report, sample candidate audit of 100 records showing <2% mismatch)?
Requisition Intake and Lifecycle Management
- What requisition intake form fields must be mandatory in your intake workflow (example: job description ID, compensation band, cost center, hiring manager, business justification)?
- Which approval steps exist in your current requisition lifecycle and who are the approvers by role (list role names and typical SLA for each approver)?
- What is the target time-to-approve for new requisitions (in business days) during steady-state and during peak hiring?
- How should we tag or categorize requisitions for prioritization (examples: critical revenue role, replacement hire, strategic growth)?
- Where should we store job description templates and who owns updates to the job description library?
- Which lifecycle events must trigger automated notifications (example: requisition approved, candidate moved to interview, offer extended) and to which distribution lists?
Job Advertising Campaign Management
- Which external channels should campaigns run on (career site, job boards, social channels, employee referral portal) and which require separate creative?
- What budget allocation or media spend constraints exist per campaign or job family (monthly or per-hire limits)?
- Which employer brand assets must be used in campaigns (career site copy, logo files, hiring manager bios, employee testimonial videos)?
- How do you want applicant source tracked for paid campaign conversions in the ATS (UTM parameters, tracked landing pages, manual source tag)?
- What campaign performance KPIs should trigger a campaign change (example: click-through rate under X, application-per-click below Y)?
- Which approval workflow must paid job ads follow before launch and who signs off on creative and spend?
Targeted Candidate Sourcing and Outreach
- Which candidate pools require targeted sourcing (passive senior engineers, sales quotas, niche compliance roles) and what response rate do you expect?
- What sourcing channels should we prioritize for outreach (LinkedIn, niche communities, internal referrals, alumni networks)?
- What message templates or outreach sequences are pre-approved for use and where are they stored (provide folder or doc link location)?
- How many outbound touches per candidate are acceptable before pausing outreach (number of messages and channels)?
- Which sourcing metrics should be reported weekly (response rate, pipeline conversion, time from first outreach to phone screen)?
- Who owns consent and privacy compliance for outreach lists and which data source governs allowed contact frequency?
Screening and Phone Interviewing
- Which screening criteria must be applied on phone screens for each role family (mandatory qualifications, red flags, expected salary band)?
- Provide the standard phone-screen questionnaire or indicate if we should use our template and where the canonical JD resides.
- How long should an initial phone screen be (minutes) and what fields must be captured in the ATS screening form?
- Which interview evaluation rubric or scorecard must be used for screens and where is it stored?
- Who will be the escalation contact if a screener identifies a compliance or background issue during screening?
- Should phone screens include routine checks (right-to-work, minimum notice period) and which exact phrasing do you require?
Manage Interview Coordination and Panel Support
- Which calendar systems should interview scheduling integrate with and what scheduling windows are preferred for hiring managers?
- What is the maximum permissible time between candidate availability and booked interview (in business days)?
- List standard panel compositions for common roles (e.g., hiring manager + peer + technical lead) and required panel members by role.
- Which interview kits or question banks must be attached to panel invites and where are they stored?
- Who approves changes to panel membership for critical roles and what is the approval SLA?
- Which candidate prep materials should be provided before interviews (role brief, travel instructions, panel bios) and what delivery channel do you prefer?
Offer Management and Negotiation
- What is your standard offer approval matrix (levels of compensation authority by role or approver) and where is it documented?
- Which compensation bands and target total rewards must offers adhere to for each job family?
- Do you want us to lead negotiation with candidates up to a defined threshold (specify dollar or percentage limits)?
- What offer letter templates and legal clauses must be used and where are the master templates stored?
- How quickly must an offer be extended after verbal approval (hours) and which stakeholders must be copied on the offer email?
- Which background check, drug screen, or reference checks are gating conditions before offer acceptance is fully approved?
Onboarding Handoff and Hiring Manager Package
- Which onboarding artifacts must be delivered to the hiring manager at handoff (new hire checklist, offer packet, interview notes, first 30/90 day plan)?
- What is the required format for the hiring manager package (PDF, ATS link, shared drive folder) and where should it be stored for access?
- Who on your team will own the post-acceptance onboarding tasks and what are their contact details?
- Which HR or security systems must be notified automatically on hire (payroll, badge access, IT provisioning) and provide integration endpoints if available?
- Within how many business days after offer acceptance should the hiring manager package be delivered?
-
Mutual Commit
Finalize commercial and contractual terms, SLAs, pricing, ramp/scale clauses, and operational handover conditions.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- Pricing and Commercial Schedule
- Ramp & Scale Addendum
- Operational Handover and Transition Agreement
- Data Processing Agreement (DPA)
- Regulatory Compliance Addendum (conditional)
- Change Order Agreement
- Termination and Exit Management Agreement
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm concrete readiness facts: named owners, access to ATS and systems, employer brand assets, data sources, and go-live windows.
Pre-Deployment Questions
Environment and access
- Is the buyer's production ATS environment available for external integrations, or what date will it be available? (so we can schedule integration testing and credential exchange)
- Which integration endpoints will the delivery team need access to? (select all that apply)
- Who will provide and maintain the named admin or API credential owner for integrations? (this is the team responsible for provisioning credentials)
Data and configuration
- What is the authoritative source of requisition and headcount data we must consume for routing and SLA reporting? (e.g., ATS requisition feed, HRIS headcount report)
- Has the field‑mapping approach for core objects (requisition, candidate, hiring manager) been decided?
- Will historical candidate/requisition data be migrated to the delivery environment before go‑live?
People and ownership
- Please provide the named primary owner for each workstream below (full name and role only). These owners will approve access and operational cutover: requisition intake, IT/integration, employer brand/assets, hiring manager approvals, compliance/data security.
- Is there a single authorized approver for SLA exceptions and recruiter embedding decisions?
Timing and constraints
- What is the buyer's target go‑live window? Please provide earliest acceptable date and latest acceptable date (so we can set the staged ramp schedule).
- Are there any blackout windows, hiring freezes, regulatory reviews, or other constraints that would block or delay go‑live during the proposed window?
-
Configuration Details
Capture exact configuration values the delivery team will use — ATS mappings, API credentials, reporting feeds, recruiter schedules, and knowledge-transfer milestones.
Configuration Details
Environments & Endpoints
- Enter the production ATS instance base URL the seller will connect to (format: https://...). This value is consumed by the ATS connector.
Authentication & Integration Identifiers
- Enter the non-secret ATS integration client ID or integration user name (identifier only). The secret/token will be exchanged off-band via your secrets manager at deployment kickoff.
- Select the authentication method used for the ATS integration (the deployment connector will use this to pick the integration flow).
Field Mappings (exact field names expected)
- Exact ATS field name or code for the candidate lifecycle state that maps to 'New Applicant' (e.g., 'Applied' or 'New'). Enter the single canonical value the connector will map.
- Exact ATS field name used as the external Job Requisition ID (this single field is used for cross-system reconciliation).
Reporting & Data Feeds
- Primary reporting feed method the seller will ingest (choose one). Subsequent questions will reference this choice.
- Reporting feed schedule (Default: daily at 02:00 UTC) — enter as 'daily at HH:MM UTC' or cron expression. This schedule is applied to the reporting ingest job.
Recruiter Scheduling & Coverage
- Primary recruiter team time zone for scheduling and SLA calculations (IANA tz name, Default: UTC).
- Standard recruiter weekly coverage per embedded role in hours (Default: 40). Enter numeric hours the deployment should configure as capacity per recruiter.
Knowledge Transfer & Handover Milestones
- Target for 'Recruiter shadowing complete' relative to go-live (Default: 14 days after go-live). Enter as 'X days after go-live'. This milestone drives the ramp plan.
- Credential exchange owner role — who will deliver integration secrets at deployment kickoff (the secret itself is exchanged via your secrets manager).
Limits & Policies (consumed by router and SLA enforcement)
- Maximum active requisitions to assign to a single embedded recruiter (Default: 10). Enter numeric.
- Candidate data retention period for operational reporting (Default: 365 days). Enter number of days.
-
Deployment & Ramp
Execute recruiter embedding, sourcing and screening workflows, ATS configuration, interview coordination handoffs, and staged ramp to steady-state with named owners and milestones.
-
-
Success
Validate outcomes against SLAs and success metrics, review time-to-fill and cost-per-hire, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live Health Check (Week 1-4)
- First KPI Measurement (Week 4-10)
- Acceptance Gate Review (Day ~90)
- Operational Monthly Check-in (Ongoing, monthly for initial 3 months)
- Quarterly Business Review — Realization and Enhancements
Issues & Enhancements
- Produce one-month forecast for time-to-fill and hires pipeline incorporating agreed corrective actions.
- Remediation plan and verification checkpoints scheduled for any unmet criteria.
- Publish the acceptance decision record including per-criterion pass/fail and the buyer signatory.
- Execute the incumbent decommissioning or retention plan and archive or migrate legacy recruiting data per agreed schedule.
- Create the remediation task list with dates for verification and link to the shared dashboard.
- KPI exception review
- Operational issues are reduced or assigned concrete closure dates to remove KPI blockers.
- Enhancement requests triaged and short-term work scheduled where it impacts KPIs.
- Confirm the next month's actions that move metrics toward the Solution Scope targets.
- Update the issue burn-down board and publish status before the next check-in.
- Reconfirm success criteria and owners
- Log prioritized enhancement requests with expected delivery windows.
- Executive KPI summary against Solution Scope
- Validate realized outcomes for core metrics against Solution Scope targets and record any remaining gaps.
- Agree and schedule the prioritized enhancement roadmap for the next quarter.
- Ensure SLA exceptions have clear mitigation plans and verification checkpoints.
- Publish the quarterly KPI deck with trend analysis and identified root causes.
- Finalize the prioritized enhancement roadmap and publish expected delivery windows.
- Document SLA exception resolutions and schedule verification checks for closure.
- All named operational owners confirmed and contact points recorded.
- Critical deployment blockers identified, logged, and scheduled for remediation within agreed timelines.
- Baseline adoption signals captured for comparison at the first measurement meeting.
- Publish go-live health summary including confirmed owners and outstanding blockers.
- Update the issue log with resolution dates for each open blocker.
- Validate ATS access and recruiter embedding for every named recruiter and escalate any missing access.
- Present first validated KPI dataset
- Validate the KPI definitions and dataset used for time-to-fill and cost-per-hire.
- Agree a prioritized remediation plan for any metrics not tracking to Solution Scope targets.
- Confirm the timeline that positions the engagement for the acceptance gate.
- Deliver the validated KPI extract and calculation workbook to the shared channel.
- Publish the remediation plan with milestone dates for each corrective action.
- Update recruitment dashboards to reflect agreed KPI definitions and filters.
- Restate Solution Scope acceptance criteria and numeric targets
- Formal acceptance status recorded for each Solution Scope criterion with a documented buyer signatory where required.
- Incumbent wind-down confirmed, with legacy contract and data disposition documented.
- Present outcome data against each criterion
- Trend analysis and root-cause review
- Deployment and ATS access validation
- Issue triage and burn-down
- Diagnose root causes for any KPI gaps
- Enhancement backlog and prioritization
- Early adoption and usage signals
- Document pass/fail per criterion and record acceptance decision
- Agree corrective actions and timelines
- Enhancement request queue
- Short-term action register
- Blockers and open issues log
- Incumbent wind-down and fallback closure
- Confirm readiness timeline to acceptance gate
- SLA exception and mitigation review
- Agree immediate remediation actions
- Agree remediation items and resolution timeline
- Quarterly action plan and next steps