Freelance recruiter network
Post a role. A network of specialist recruiters starts on it in days.
You're trying to fill a role without drowning in irrelevant CVs, and right now two doors look like the only ones open. Behind one is an agency: one firm, one consultant, and whatever already sits in that firm's own database. Behind the other is a job board that costs almost nothing and buries you in three hundred applications for a role that needed four good ones. Both are the same shape underneath — one channel at a time, matching on the words in a CV instead of the work the person can actually do.
VVeRecruit is the third door. Post a role, and a network of specialist recruiters — matched to your industry, seniority and location — starts working it in parallel, screening candidates against the real tasks of the job instead of keyword overlap. Submissions arrive already organized and masked, you interview when you're ready, and nothing is billed until someone you hire actually joins.
This page is the mechanism: how a role gets worked, what you see and deliberately don't, when you pay, and where an agency or a job board is honestly still the better call.
What an open role actually costs you every week it stays open
Most people size a vacancy wrong, in a specific way — they treat the unpaid salary as money saved.
The cost nobody puts on a P&L
Run the logic through properly. You opened that role because the output is worth more to the business than the CTC you're offering for it. If the output were worth exactly the salary, hiring would be a break-even exercise and nobody would have raised the requisition. So the gap between the value of the work and the paycheque is the number that quietly disappears every day the chair stays empty. Nobody puts it on a P&L, which is precisely why nobody manages it.
Take an Accounts Manager on ₹9,00,000 fixed CTC. Across roughly 264 working days, that's about ₹3,400 a day of budgeted work the business isn't getting done. Let the role run 90 days instead of a tighter 45, and those extra 45 days are close to ₹1,53,000 of unproduced work — reconciliations that didn't happen, MIS that wasn't ready, GST filings pushed to the deadline instead of a week before it.
The second-order costs
Add what the vacancy quietly pushes onto other people, and it's usually the bigger number.
- Your senior person covers the gap. A Finance Head doing an Accounts Manager's reconciliations is expensive labour spent on cheap work, and the Finance Head's own deliverables slip while it happens.
- The team absorbs the load. Three months of covering a gap is how good people start taking calls from recruiters themselves.
- Things quietly stop. The audit prep that starts late. The collections follow-up nobody owns this month.
- Your own hours. If you're an HR lead sourcing, screening and coordinating alongside your actual job, that time is real even if no invoice says so.
Time-to-fill is the lever that moves the most money on an open role. That's the number this page is built around, and it's why everything from here on is about speed, fit and how the pipeline is organized — not what you're billed.
Where the old way breaks — and what actually fixes it
You already know both models. It's worth being precise about where each one fails, because the fix has to address the mechanism, not just promise to try harder.
One agency, one busy consultant, no visibility
You get an account manager and, behind them, usually one or two consultants who are also carrying six other clients. Your role sits in a queue. When your consultant is tied up on a bigger account, your role simply isn't worked, and you have no way of knowing whether it is. The commercial structure quietly works against you too — a consultant with limited hours puts them on whichever requisition closes fastest, which is rarely the one you keep chasing them about.
The quality is often genuinely good. The throughput is the problem.
The job board and the 300-CV flood
You post, and volume arrives. Volume was never the deliverable you actually wanted. You wanted six people who can do the job, and instead you have three hundred CVs matched on string overlap — every résumé containing the word "Tally" surfaces, whether the person ran a full ledger or copied entries someone else prepared.
Then you become the recruiter. The shortlisting, the screening calls, the notice-period conversations, the salary negotiations — all of it lands on your desk. The invoice was small. The cost wasn't.
The gap: judgement and throughput, working in parallel
An agency gives you judgement without throughput. A job board gives you throughput without judgement. What neither gives you is a group of people with judgement, working your role at the same time, screening against what the job actually requires.
That's the gap VVeRecruit fills — a network of specialist recruiters, matched to your role, working it in parallel instead of one desk at a time.
You never face a blank JD box
Job descriptions are the single most avoidable point of failure in Indian hiring, because most of them are copied from a posting three years old, written by someone who has since left the company. The requirements are stale, the "must-haves" are aspirational, and the actual daily work of the job appears nowhere in the document.
So there's no blank box to procrastinate over.
One flow, two outputs
The assistant asks you one question at a time, in plain English, and you answer by picking an option or typing a short sentence. No HR jargon required. You describe what the person will do; it handles the drafting.
A partial sequence for a mid-level accounts role runs roughly: What should this person be called? Which department? How senior — entry, mid, or top? Years of experience, minimum to maximum? Minimum qualification? Location and shift? Salary band? And then — what will they do on a normal Tuesday?
That last question is where the useful part happens. Your answers do two jobs at once: they produce a polished JD you can publish without rewriting, and they populate the structured parameters that drive matching underneath — designation, industry, seniority, department, experience band, location, salary range, and three skill tiers.
Must-Have / Should-Know / Nice-to-Have
Those three tiers matter:
- Must-Have — hard filters. Without these, the person can't do the job at all.
- Should-Know — the daily tasks, and the heavily weighted tier. The next section is entirely about it.
- Nice-to-Have — genuinely optional, useful only for tie-breaks.
Separating them stops the most common JD mistake in Indian hiring: stuffing twelve items into "required" and then wondering why the pipeline is empty. You review and edit everything before it publishes — the assistant drafts, you sign off.
What is Should-Know competency matching, and why does it beat keyword matching on a CV?
Should-Know competency matching breaks a role into the plain-English tasks it actually involves, then asks the candidate to self-rate against those exact same tasks — not a keyword scan of their résumé. It beats keyword matching because two CVs can both say "Tally" while only one person has actually run the process, and task-level ratings tell them apart on the same screen where a word search can't.
Tasks in plain English, rated by the candidate on the same list
For an Accountant, the Should-Know list starts something like: generate invoices, make entries in Tally, follow up with pending creditors, reconcile bank statements, prepare monthly MIS, file GST returns. The system suggests these from the designation, department and level, drawing on a shared knowledge base of what each role actually does. You tick what applies, edit the wording to match how your business runs, and add anything specific to you.
The candidate sits with the same list and rates themselves on each line: Never used, Have knowledge, Used rarely, Used daily. They also note where they did it and at what level, so the answer carries context instead of sitting as a bare claim.
Two CVs both say "Tally" — how the match tells them apart
Candidate A rates: invoices used daily, Tally entries used daily, creditor follow-up used daily, bank reconciliation used daily, MIS used rarely, GST returns have knowledge. Candidate B rates: invoices used rarely, Tally entries have knowledge, creditor follow-up never used, bank reconciliation never used, MIS never used, GST returns never used.
Both CVs contain the same keyword. Only one has actually run your process. A keyword engine can't tell them apart. A task-level engine separates them in one screen.
Gaps become visible before the interview, not in month two
If GST filing sits on your list and a strong candidate has never done it, you see that before the interview, not after they've joined. Sometimes you'll decide it's trainable and proceed anyway — that's now a decision you make on purpose, not one that surprises you three months in. Self-rating also holds up under pressure in a way prose CVs don't: claiming "used daily" against a specific task is a statement that falls apart in the first ten minutes of a real conversation, and candidates know it. The recruiter working your role probes those ratings during screening as a matter of course.
How your role reaches a whole team of specialists at once
When your role publishes, the network is ranked against it on the axes that actually matter — industry or domain, seniority level, function, and location. A recruiter who has placed manufacturing plant supervisors for a decade is a different asset from one who places fintech backend engineers, and the matching treats them that way. Only the recruiters whose declared specialisation genuinely fits ever see your role; the rest of the network never does, which keeps it away from anyone who'd work it badly.
From that matched group, a working set of specialists takes it on and starts sourcing and screening at the same time — typically a mix of recruiters based near the role, who know the local salary bands and can meet a candidate, and specialists from other cities who know where to find people willing to relocate for the right offer. If a recruiter working your role goes quiet, another matched specialist backfills the slot automatically. Your role doesn't sit idle because one person got busy — that's the specific agency failure this design removes.
Each recruiter also carries a cap on how many candidates they can submit to your role. That cap matters more than it sounds: without it, a group of recruiters competing on the same opening would flood you with dozens of CVs, and you'd be back to job-board triage with extra steps. With it, you get a handful of considered submissions from each, because their only incentive is to send the ones who convert.
What you see, and what you deliberately don't
This part surprises people, so it's worth being direct.
What you see: submissions on your own roles — candidates that recruiters have sourced, screened and put forward for the specific requirement you posted, with their Should-Know ratings, screening answers, notice period, current and expected CTC, and the recruiter's own assessment.
What you don't see: a candidate database you can search or browse, any candidate who wasn't submitted to one of your roles, or the identity of any recruiter working on your behalf.
Each of those is a deliberate design decision, and each protects you rather than limiting you.
No candidate database. A searchable pool sounds like a feature until you think about what it does to who's in it. Candidates in India are cautious about visibility for a concrete reason — they don't want their current employer discovering they're looking. The moment any company can browse candidate records, every candidate has to assume their own employer might be one of the ones browsing. Good passive candidates stay out, and the pool fills with people already on every job board. By making the pool unbrowsable, VVeRecruit can credibly tell a candidate that no company will stumble across them — which is what brings the passive candidate in, and the passive candidate is usually the one you actually want.
No recruiter identities. You never learn which recruiter produced which candidate, and no recruiter learns which company posted the role until the process requires it. That prevents a specific problem: a recruiter who knows your name can approach you directly next quarter and cut the process out, and the same recruiter can just as easily be approached by anyone else who wants to know who you're hiring and why. Masking keeps your hiring plans yours, and it means recruiters compete on the quality of who they submit, not on the relationship they've built with you.
The trade-off is honest and worth weighing: you can't go hunting yourself. If searching a database at midnight is central to how you like to hire, this will frustrate you. What you get instead is a group of people doing that hunting in parallel, with live networks in the market, while you have a login.
Identities are revealed at interview, and only there
Through sourcing and screening, the candidate deals with a VVeRecruit persona and doesn't see your company name. The recruiter working the role sees the candidate's real identity — you can't screen a ghost — but stays masked from you throughout, including after the hire.
When an interview is scheduled, the masking lifts between you and the candidate. You see who they are. They see who you are. You interview exactly as you would anyone else, on your own process, your own panel, your own judgement.
There's a reason for the timing. Candidates share far more, and far earlier, when the disclosure isn't public. Someone content in their current job will answer a screening questionnaire about expected CTC and notice period long before they'd apply to a named company, because answering costs them nothing and applying openly costs them exposure. Revealing at interview stage means you meet people who were never going to appear in your inbox otherwise.
From the interview reveal onward, both you and the candidate are bound by non-circumvention terms with twelve-month hire tracking — straightforward, because the platform did the work of putting you in a room together, and hiring the person off-platform three weeks later isn't meant to be a loophole.
When do you pay, and what's the guarantee?
Free to post, pay only on a verified join
Posting a role costs nothing. Reviewing submissions costs nothing. Interviewing costs nothing. There's no monthly subscription and no per-post fee. Nothing is billed to you until a candidate you've hired actually joins — and even then, the join is verified through an uploaded offer letter and a UAN check before anything is invoiced. If someone accepts an offer and doesn't join, there's nothing to invoice.
Post a role you later cancel, and you've spent nothing. Get submissions you don't like and close the requisition, and you've spent nothing.
The 90-day guarantee
If the person leaves within 90 days of joining, you get a free replacement, worked by the same recruiter at no additional cost to you. Where a replacement isn't practical — the role got restructured, the budget got pulled, the requirement changed — you get a credit note instead. Forcing a replacement into a role that no longer exists helps nobody.
This connects directly to recruiter behaviour. Recruiters are paid their share only after the 90-day guarantee clears, so anyone who pushes a candidate they suspect won't last has done the work for free and then has to do it again. The guarantee isn't a customer-service add-on. It's the mechanism that makes a stranger care whether your hire actually works out.
When an agency or a job board is genuinely the better choice
Three situations where VVeRecruit isn't the right tool, stated plainly, because you'd work it out yourself in week two anyway.
Bulk volume hiring at entry level. Forty telecallers, or thirty field executives on the same profile in the same city. A job board plus a walk-in drive, or a bulk-staffing vendor working on volume, moves faster for that shape of hiring. VVeRecruit is built for roles where the fit of the individual matters, not for filling a floor.
A CXO or board-level search. For a CFO, a CEO, or a board seat, you want a named retained search partner who maps the market, approaches specific people personally, and manages a process over months, staking their own reputation on it. That's a different craft, and masked marketplace mechanics don't fit it.
Roles you consistently fill through your own network. If you post internally and good referrals arrive within a week, that's the cheapest and highest-converting channel there is. Keep doing it. Bring in outside recruiters for the roles where your network runs dry — which for most companies means specialist functions and locations you have no presence in.
Where this earns its keep: mid-level and senior individual roles, one to fifty hires a year, where the fit of the specific person materially affects the outcome, and where the same requisition seems to take three months every single time.
Hiring for a fixed project or a seasonal ramp instead of a permanent seat is a different arrangement entirely — see contract staffing for how that works.
What actually happens in your first week
Day 1. Create an account and post your first role through the guided flow. Expect fifteen to twenty minutes for the first one — most of it spent on the Should-Know tasks and the salary band. Later roles go faster because the system remembers the shape of what you've posted before.
Day 1, an hour later. The network is ranked against your role and the matched specialists start working it. You don't do anything during this step.
Days 2 onward. Recruiters source and screen against your Should-Know list, running the screening questionnaire — CTC fixed and variable, in-hand, expected, notice period, buyout, competing offers. Everything a recruiter would normally spend a call collecting is collected before the CV reaches you.
As they arrive. Masked submissions appear in your pipeline, with task-level ratings against your requirement instead of a keyword score. You shortlist.
Interview stage. Identities reveal between you and the candidate. You run your own process.
Offer and join. Offer letter uploaded, UAN verified, and only then is anything billed.
Day 90. The guarantee clears.
You're involved at exactly two points — reviewing submissions and interviewing. That's the design.
Frequently asked questions
How fast will I get a shortlist?
Once your role publishes, matched specialists start sourcing and screening the same day, and most companies see their first organized submissions within days, not weeks — because screening for CTC, notice period and task-level fit happens before the CV reaches you, not after.
Why can't I search for candidates myself?
Because a searchable pool would drive away the candidates you most want. Anyone quietly exploring options has to assume that if companies can browse candidate records, their own employer might be among them. A pool nobody can browse is one a passive candidate will actually enter. You give up a search box and gain access to people who were never going to apply publicly. All sourcing and screening is done by the specialists working your role, and you see submissions on your own roles only.
What if the person leaves in the first 90 days?
You get a free replacement, worked by the same recruiter at no extra cost. Where a replacement isn't practical, because the role was restructured or the budget withdrawn, you get a credit note instead. Recruiters are paid only after the 90-day period clears, so nobody has an incentive to place a candidate they expect to fall off.
Do I have to write the job description?
No. There's no blank JD box anywhere in the product. The assistant asks simple questions one at a time and you answer by picking options or typing plain English. It produces the finished JD and fills the structured matching parameters — including the Should-Know task list — from the same answers. You review and edit before it goes live.
When do I actually pay anything?
On the candidate's join date, verified by offer letter and UAN check, and not before. Posting roles is free, receiving submissions is free, interviewing is free, and there's no subscription. If a candidate accepts an offer and then doesn't join, nothing is invoiced.
Can I pick which recruiters work my role?
No, and that's deliberate. Selection runs on match score across industry, seniority, function and location, plus experience and track record — you also never see recruiter identities. Letting you choose would mean seeing them, which would let recruiters win work through relationships instead of results, and would expose your hiring plans outside your company. The masking runs both ways and holds throughout.
Post your first role
Take the role that's been open longest. Put it through the guided flow and see what a task-level requirement looks like next to the JD you've been reposting for months.
Nothing is billed until someone joins.
Nothing is billed until someone joins.
Looking for people on contract instead of a permanent hire? See contract staffing. Are you a recruiter rather than a hiring company? See how freelance recruiters work with us.
VVeRecruit is a Pillai InfoTech LLP product.