Short answer: The instinct when pipeline is thin is to buy more project data. It rarely works, because access to data was not the constraint. A manufacturer with 4,000 potentially relevant projects a year does not need 4,000 records — it needs the forty this month where its product category is still open, plus a name. Doubling the input without changing the qualification and workflow produces the same number of conversations and more frustration.
The pattern that repeats
It is predictable enough to describe in advance. A manufacturer buys access to a project database. Onboarding goes well. Three months later usage has concentrated in one or two power users, reps have drifted back to their existing accounts, and at renewal nobody can attribute revenue to it.
The post-mortem usually blames data quality. Occasionally that is fair. More often the data was fine and the tool created work rather than removing it.
Because a project record is not an opportunity. Between the record and a useful conversation sits: judging relevance to your specific portfolio, establishing whether the specification window is still open, finding the individual at the right firm, checking whether a colleague already touched the account, and typing all of it into the CRM.
That gap is where the hours go, and adding records widens it.
The shape of the problem
Picture the funnel as a margarita glass rather than a cone: enormously wide at the top, then a sudden narrowing, then a thin stem. Thousands of projects enter. A handful of conversations come out. The narrowing is not caused by the market — it is caused by qualification capacity.
Widening the rim does not thicken the stem.
Three questions before buying more data
1. How many of your current projects are actually being worked? If reps carry 40 to 80 active projects and you already surface 400, the constraint is capacity, not supply.
2. At which project stage does first contact happen? If most contacts occur at tender stage, more tender data makes the problem worse — you get more projects you were always going to lose on price. The fix is earlier data, not more.
3. How long does it take to get from a project record to a named decision-maker? If it is an hour, that hour multiplied by your project volume is your real bottleneck. A larger database multiplies it.
What actually increases deals
Four things, in order of effect.
Relevance judged against your products, not your industry. Filtering for "commercial buildings over €10 million" is category filtering — it returns hundreds of projects, most of which do not need your specific system. Real relevance requires the system to know your portfolio. Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets, which is why two manufacturers looking at the same school can correctly receive different scores.
Earlier detection. A project found at published tender is usually a project already lost on specification. Projects detected at planning and design stage — from permits, planning applications, developer announcements, trade press and local news — are the ones where the outcome is still open.
A named decision-maker per project. Not a firm. The individual handling this project, with reachable details, confirmed as relevant to your product category. Without that, every project is still a research task.
Removal of the work after qualification. A qualified project still needs outreach drafted, a follow-up scheduled and a CRM record updated. If that stays with the rep, one step out of six has been solved.
The uncomfortable arithmetic
Fewer, better projects beat more projects. That is counterintuitive when the pipeline looks thin, so it is worth making concrete.
A rep working 60 projects at a 15% specification rate produces nine specifications. The same rep working 40 well-chosen projects at a 30% rate produces twelve — with less time spent and better follow-up on each.
Exclusive project sales insights, directly to your inbox
Subscribe to our weekly newsletter.
The lever is not volume. It is the share of worked projects that were worth working, and that is a qualification problem.
What to do instead of buying more data
Measure your coverage first. Take one market you know well, list every relevant project your team was aware of last year, and compare against an external feed for the same definition. If the delta is small, you do not have a data problem. If it is large, you have one — but see the next point.
Then measure your throughput. Of the projects you did see, what share reached a named decision-maker? What share reached specification? If those numbers are low, more input will not help.
Fix in that order. Coverage without throughput produces a bigger list nobody works. Throughput without coverage produces excellent work on a fraction of the market. Most manufacturers need both, and the throughput fix has to come first or the coverage improvement is wasted.
The last figure is the relevant one here — it improved because fewer, better-chosen projects were worked, not because more were.
Frequently asked questions
Does a bigger construction project database improve sales? Rarely on its own. Access to data is usually not the constraint; the constraint is the rep hours required to turn a project record into a conversation with someone who can specify your product.
What should you look at before buying project data? How many projects your reps already carry, at which project stage first contact happens, and how long it takes to get from a record to a named decision-maker.
Why do project database subscriptions fail to deliver? Because raw records create qualification work rather than removing it, so usage concentrates in a few power users and reps return to their known accounts.
Is it better to work fewer projects? Usually yes. A smaller number of well-qualified projects with disciplined follow-up outperforms a larger number worked superficially.
Ready to fix throughput before volume?
Find out how Building Radar's revenue engineering solution delivers qualified projects with named contacts instead of a larger database.
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.
Schedule an initial consultation