Lead scoring: ranking enquiries without inventing a formula
Lead scoring decides who gets called first. How to build a score from what you can observe, why most models are too clever, and when scoring is not worth doing at all.
A recruitment process is a series of decisions about evidence. Decide what evidence you need before you meet anyone, and most of the usual problems disappear.
A recruitment process is the path from deciding a role exists to somebody starting in it. In a small company it is usually improvised: an advert written quickly, CVs read in gaps between other work, interviews that wander, and a decision made on a feeling that everyone then rationalises. It works often enough to feel fine, and the failures are expensive and slow to appear.
The fix is not more stages. It is deciding, before the first conversation, what evidence would convince you — and then designing each stage to produce exactly that.
Structured interviews — the same questions, asked in the same order, scored against an agreed scale — are consistently better predictors than unstructured conversations, and they are also the more defensible position if a rejected candidate ever challenges the decision. The cost is an hour of preparation per role. Check your local employment law on what you may ask, because the boundaries differ sharply between jurisdictions.
In most small-company hiring the delay is internal, not external: a week before CVs are read, four days to agree availability, a fortnight waiting for a second interviewer, several days deciding. Candidates experience this as disinterest, and the strongest ones — who have options — leave first. Fixing the calendar is usually worth more than improving the interview. Book the interview slots in advance, before you have anyone to put in them.
Ettex CRM works as a lightweight pipeline for candidates: contact profiles with custom fields for source, role and stage, a visual pipeline you move people through, notes and activity logging so every conversation sits on one screen, tags for the shortlist, change history showing who did what and when, and shared records so a colleague can pick up the thread. Applications arrive through Ettex Forms — one form with the questions you actually screen on, file upload for the CV, landing timestamped in a shared inbox with export to CSV or XLS. Scorecards fit Ettex Sheets, the job description and interview guide live in Ettex Docs, interviews go in Ettex Calendar, and the offer is signed through Ettex Signature.
Plainly: Ettex is not an ATS. Nothing here posts to job boards, parses or ranks CVs, offers a candidate portal, schedules interviews automatically, sends templated rejections in bulk, or reports on diversity. Using a CRM for candidates is a deliberate workaround that suits a handful of hires a year. If you hire continuously, buy an applicant tracking system — and note that candidate data is personal data, so decide your retention period and tell candidates what it is.
Two documents do disproportionate work at the start. A job description template stops each hiring manager reinventing the shape of the role, and a competency matrix tells you which capabilities the team is actually missing rather than which job title feels overdue.
Define the role and evidence, advertise, source, screen against criteria, a short first call, a structured interview, a work sample, references, then a decision and a fast offer.
Two to three weeks from advert to offer for most roles. Longer processes lose the candidates with options, which are the ones you were competing for.
Yes — asking every candidate the same questions and scoring against an agreed scale predicts performance more reliably than open conversation, and it is far easier to defend if a decision is challenged.
Where you can make it resemble the real job, yes — it is among the strongest signals available. Keep it short, and pay for it if it takes more than an hour or two.
For a few hires a year, yes: a pipeline, contact records and notes cover it. Continuous hiring needs an ATS for job-board posting, bulk communication and reporting.
Only as long as you have a reason, and tell candidates what that period is. Application data is personal data in most jurisdictions — check your local rules before keeping CVs indefinitely.
A recruitment process works when the criteria exist before the candidates do. Write the scorecard first, ask everyone the same questions, keep the calendar tight, and record why you decided.
Lead scoring decides who gets called first. How to build a score from what you can observe, why most models are too clever, and when scoring is not worth doing at all.
An account plan records who decides, what the customer is trying to achieve, and where the relationship is thin. The version that fits on a page and gets updated.
CRM data hygiene fails as a clean-up project and works as a measured routine. The numbers worth tracking, the fields worth enforcing, and why enrichment often makes things worse.