Sourcing Pilot vs Full-Funnel Pilot
Both pilots run on the same Mokka platform. The difference is whether we connect to your ATS — and that decision drives both the IT/IS footprint and what we can prove.
Sourcing Pilot
Validate Mokka's passive sourcing on a hard-to-fill role. No integration, no procurement lift.
- Outbound passive sourcing on 1–2 roles
- AI screening criteria from a pasted job description
- Ranked shortlist delivered in the Mokka app
- Profile and answer integrity flags
- Candidate experience: text or voice, candidate-controlled
- No ATS connection
- No automatic candidate import or sync-back
- Recruiters paste job descriptions manually
Full-Funnel Pilot
Validate Mokka end-to-end — inbound screening plus passive sourcing — on roles you're already running today.
- Everything in the Sourcing Pilot, plus:
- Live ATS integration (Greenhouse, Lever, Workable, Huntflow direct; 100+ via integration platform)
- Inbound applicant screening at scale
- Job descriptions and candidates auto-imported from your ATS
- Scores, evidence, and AI interview transcripts synced back to the ATS
- Funnel reporting against your existing pipeline
- Detection signals for AI-generated applications
How to choose
Pick the Sourcing Pilot if…
You need to fill specific hard-to-source roles (clinical, technical, niche) and your bottleneck is finding qualified passive candidates — not screening volume. You also want a fast start with no IT/IS or procurement involvement beyond signing standard terms.
Pick the Full-Funnel Pilot if…
Your bottleneck is the volume and quality of inbound applicants — generic, AI-optimized, or hard to triage — and you want Mokka to read your existing pipeline, score it, and write evidence back to your ATS. Screening cannot be evaluated end-to-end without an ATS connection.
What the Sourcing Pilot cannot prove
Without an ATS connection, some things are structurally out of scope. Better to flag them now than have you discover them mid-pilot.
Out of scope for the Sourcing Pilot
• Inbound applicant screening — we can't read what we can't see.
• Candidate auto-import — JDs and any reference candidates are pasted manually.
• Sync-back of Mokka scores, evidence, or AI interview transcripts to your ATS.
• Funnel reporting against your existing pipeline.
• Disposition tracking (advanced/rejected/hired) tied to your ATS stages.
If any of those matter for your evaluation, the Full-Funnel Pilot is the right starting point — and we'll lead with the integration rather than retrofit it later.
For your IT, security & procurement teams
The pilot meta on each card above tells you what each path requires. Below is what your IT and procurement teams will actually want to read.
Standard Terms & Conditions
Applies to both pilots. Covers acceptable use, service levels, and commercials.
Read terms →Privacy Policy
Applies whenever Mokka processes candidate data on your behalf, including the Sourcing Pilot.
Read policy →Trust Center
SOC 2 Type II report, penetration test summary, sub-processor list, and bias audit.
Open Trust Center →How a pilot runs
Week 1 — Setup
Sourcing Pilot: paste 1–2 JDs, confirm screening criteria, and we go. Full-Funnel Pilot: ATS marketplace install, sync the first roles, calibrate criteria with your team.
Weeks 2–4 — Run
Mokka sources, screens, and ranks. Recruiters review shortlists in the app and reach out as they would today. Weekly sync to triage edge cases and tighten criteria.
End of pilot — Decide
Joint readout: shortlists delivered, hires made, time-to-shortlist, and a comparison vs the rest of your toolkit. No qualified candidates in 14 days? You walk. No charge.
Ready to start?
Tell us which pilot fits and which roles you want to run. We'll take it from there.
Schedule a 30-min call