Every candidate, every client, one clear next step.
A recruiter may be working a dozen open requisitions for several clients, each with its own screening rules, interview rounds and feedback habits. We build software that keeps candidates, client feedback and decisions together, and we run our own product for first interviews.
From requisition to joining day.
Requisition
A client sends a role by email: title, budget, location, must-haves and a few unwritten preferences. If intake doesn't capture the notice-period limit or the salary band, the recruiter learns it after several rejected profiles.
Sourcing and screening
Applicants arrive from job boards, referrals and your own database. Screening calls are the slowest part of volume roles, and their notes often shrink to one line in a spreadsheet.
Client shortlist
Selected profiles go to the hiring manager. Feedback comes back by phone, or as 'not suitable' with no reason, and the candidate is left waiting.
Offer and joining
Offer letter, documents, background checks and a joining date. Drop-offs here hurt most, and someone needs to know who has gone quiet.
LessRounds takes the first interview.
In volume hiring, the screening call is where recruiters lose most of their week. With LessRounds you describe the role and choose the questions, and applicants take a spoken interview in their browser whenever it suits them. Your team receives each recording and transcript, with the reasons behind every score, and people decide who goes forward.
- Applicants interview on their own schedule
- A recording and transcript for each answer
- Every score shows its reasoning
- Recruiters make each decision

What we would build for an agency.
Candidate records that travel
CV versions, screening notes, interview recordings, client feedback and consent in one record, so the next recruiter can pick it up without calling the last one.
A client review view
A restricted customer portal where hiring managers see their shortlist, compare candidates and leave feedback with a reason, in place of a phone call nobody logs.
Duplicate and ownership rules
When two recruiters submit the same person, or one person goes to two clients, the system flags it and shows who submitted first under the rules you set.
Contract staff admin
For temporary and contract placements: timesheets, client approval of hours and the details payroll needs, linked to the placement instead of retyped.
Personal data needs rules up front.
- What candidates agree to when they apply, and how they withdraw that agreement.
- Which fields a client may see: skills and experience early, contact details and current salary only at a later stage.
- How long candidate records are kept after a role closes, and who may delete them.
- When a client's access to a shortlist ends, ideally automatically once the role is filled or cancelled.
- Who may move a candidate between stages, configured through roles and permissions.
- How any AI score or summary can be traced back to the answer it came from.
Agency questions.
Do we have to use LessRounds to work with you?
No. If you already run an interview process you trust, we build around it. LessRounds is there if first interviews are the bottleneck.
Can AI reject candidates automatically?
We don't design it that way. AI can transcribe, summarise and score against your questions with its reasons visible, but a person decides who progresses. Our page on AI for hiring covers where AI helps and where it stays out.
What would a first release look like?
Usually the candidate record and the client shortlist view for one or two key accounts, with LessRounds added if screening is the slow step. Timesheets and contract staff admin come later, once recruiters are working from the new record every day.
Can it work with our existing applicant tracking system?
Often, yes. We look at what your ATS exposes and connect to it, so recruiters aren't maintaining two candidate databases.
Tell us where your placements slow down.
Whether it is screening, client feedback or joining, we will suggest the smallest useful thing to build first.