Managed contracts scoped to your operation.
Recruiting Buddy is currently sold through founder-led, white-glove onboarding. There is no open self-service checkout. Volume, support, approved provider usage, safety caps, and overage policy are documented before activation.
A controlled first deployment with agreed jobs, volume limits, provider readiness, onboarding owners, and success measures.
- Resume scoring & written summaries
- Approved voice-screening workflow
- Completed-call transcripts, recordings & scores
- Multi-user recruiter workspace
- Managed onboarding & weekly review
Additional branches, campaigns, or volume after the pilot meets its agreed quality, capacity, compliance, and support thresholds.
- Everything in Managed Pilot
- Agreed campaign and volume caps
- Bulk candidate import
- Custom interview topics per job
- Usage and pipeline reporting
- Support terms defined in the order form
A reviewed implementation for organizations that need security diligence, defined support, customer-specific workflows, and a documented expansion path.
- Security and implementation review
- Named onboarding and escalation owners
- Approved integration workflow
- Capacity and architecture review before scaling
- Compliance-support documentation
- SSO, dedicated infrastructure, and SLAs only if explicitly contracted and technically approved
Tracked usage with explicit commercial terms.
The dashboard exposes operational usage. Included units, enforcement, safety caps, overages, invoice terms, and any pause behavior must be approved in the order form and onboarding record before billable activity.
Voice minutes
Screening-call talk time, metered by the minute across all your campaigns.
Resume screens
Each resume scored against a campaign counts as one screen, bulk or individual.
SMS messages
Approved recruiting messages, tracked using the usage semantics defined for the deployment.
The fine print, up front.
Why don’t you publish flat prices?
Because cost and value depend on call volume, duration, retry mix, resume scoring, SMS, onboarding, and support. We use your supplied inputs to prepare a written scope; a demo alone does not create a binding price.
Is there a long-term contract?
Deployments are scoped with your team during the demo process, including term length. We’ll walk through the options that fit your operation — nothing is signed sight-unseen.
What happens if we grow past our plan?
Usage is reviewed against the documented caps and overage policy. Expansion requires a capacity and cost review; horizontal scaling or shared-state work may be required before higher limits are approved.
How quickly can our team get up and running?
Timing is confirmed after the customer, provider, billing, consent, support, and test-campaign checklist is complete. We do not promise a fixed go-live date before those dependencies are known.
Get a number for your operation.
Bring your real roles, expected volume, and support needs. We will map the inputs required for a written scope.