Short answer: A project qualification desk sits between raw project data and field sales. Its job is to decide which projects are worth a rep's time, identify the deciding role on each, make first contact where appropriate, and hand over qualified opportunities with a named contact and a next step. It exists because field reps are the most expensive way to do research, and the least reliable — they will always prioritise the project already in front of them.
The problem it solves
A building product manufacturer in four markets may face thousands of potentially relevant projects a year. A field rep can meaningfully carry forty to eighty. Which means over 90% of projects will never be worked, and the only question is whether the ones that are worked are the right ones.
Without a qualification function, that selection happens by default: reps work the projects they already know, in the regions they visit, with customers they like. Not a bad heuristic — but it systematically ignores new opportunities and unfamiliar markets, and it means nobody is accountable for market coverage.
What the desk actually does
1. Receives every project, from every source. Platform discovery, inbound enquiries, key account information, distributor tips, site photographs, uploads. One intake, one standard. Two parallel processes means one gets neglected.
2. Qualifies against defined criteria. Product relevance, project stage, value of your product on this project, access to the deciding role, existing relationship advantage. Scored, not deliberated.
3. Disqualifies hard and records why. Below minimum volume, outside the influence window, no route to the deciding role, competitor framework agreement. The reasons are the most valuable output — they tell you what is wrong upstream.
4. Identifies the deciding role. Not the firm — the individual, with reachable contact details, confirmed as relevant to your product category.
5. Makes first contact where appropriate. For many product categories, an initial technical conversation can be handled from a desk. This is what makes the function pay for itself rather than being pure overhead.
6. Hands over with a next step. Named owner, contact made, context recorded, action defined.
The qualification criteria
Score each project on five dimensions, weighted for your business:
Dimension | What it asks |
|---|---|
Product relevance | Does this project need our specific category, at meaningful volume? |
Project stage | Is the specification window still open for this category? |
Product value | What is our product worth here — not what is the project worth? |
Access | Can we reach the role that decides on our category? |
Relationship | Have we worked with any party on this project before? |
Two notes that matter more than the weights. Total project value is a misleading proxy — a €200 million hospital may represent €30,000 of your product. And product relevance cannot be done with category filters; it requires the system to know your portfolio. Building Radar handles this by having Jeane read your website, product catalogues and technical data sheets, so scoring happens at product level rather than at project-type level.
Hard disqualification rules
Some conditions end the review regardless of score:
Below your minimum order volume
Project stage past the influence window for the category
Region you cannot commercially service
Competitor holds a framework agreement on this account
No route to any role that influences your category
A desk disqualifying 60–70% is working correctly. One disqualifying 10% is a routing function, not a qualification function.
Handover rules that prevent leakage
Write these down; they are where qualification desks fail in practice.
Every handover has a named owner. Not "the region" — a person.
Every handover has a next step with a date.
Rejection by the rep goes back with a reason. That is feedback on the criteria, not an argument.
A defined response window. If a rep does not act within it, the project returns to the desk for reassignment.
The desk keeps visibility after handover. Otherwise nobody learns which qualified projects converted, and the criteria never improve.
Staffing and ratios
One inside sales person typically supports three to five field reps. The ratio depends almost entirely on how much of the research is automated.
Where the desk manually searches databases, finds contacts, resolves duplicates and types CRM records, the ratio sits at the low end and the role is mostly clerical. Where projects arrive already scored against the portfolio, with decision-maker contacts identified and CRM records created, the desk moves from researching to deciding — and the ratio improves substantially.
That shift also changes who you should hire. A desk that decides needs commercial judgement and technical literacy, not data entry speed.
What to measure
Projects qualified per week — throughput
Disqualification rate and reasons — discipline and criteria calibration
Share of handovers with a named decision-maker contact — quality
Rep acceptance rate on handovers — alignment between desk and field
Specification rate on desk-qualified projects versus rep-sourced — the number that proves the function's value
Time from project arrival to handover — should be days, not weeks
The fifth is the one to present to leadership. If desk-qualified projects do not convert better than projects reps found themselves, either the criteria are wrong or the desk is under-resourced.
Frequently asked questions
What does inside sales do in construction? Qualifies incoming construction projects against defined criteria, identifies decision-makers, makes initial contact where appropriate, and hands qualified opportunities to field sales with a named contact and a next step.
How is this different from an SDR function? An SDR generates meetings from cold outreach to companies. A construction qualification desk assesses projects — the unit of work is a building, not an account, and technical relevance judgement is central.
How many inside sales people do we need? Typically one per three to five field reps, improving as qualification is automated.
Should inside sales make first contact? For many product categories yes, particularly the initial technical conversation. Complex specification discussions still need the specification manager.
What is the most common failure? Handovers without a named owner and a next step, which means qualified projects sit and the desk's work is invisible.
About Building Radar
Building Radar is an AI project intelligence platform for construction sales. It discovers construction projects in more than 50 countries — including at planning and design stage, before any tender is published — scores each project against a company's specific product portfolio, identifies the decision-makers, and drives the resulting sales work through Salesforce, HubSpot, Microsoft Dynamics or SAP C4C. Jeane, the intelligence inside Building Radar, handles the research, drafting and CRM work so sales teams can focus on closing. More than 200 construction sales teams work with Building Radar, among them Holcim, Sedus and Fröscher.
Ready to build a qualification desk that decides instead of researches?
Find out how Building Radar's revenue engineering solution delivers ready-to-act projects and contacts to inside sales.
Schedule an initial consultation