Short answer: Build the case on four numbers — addressable project volume you currently cannot see, realistic specification rate by entry stage, average value of your product per project, and rep capacity freed from research and admin. Multiply conservatively, compare against total cost including internal effort, and present the payback as a range rather than a point estimate. Cases built on feature comparisons or vendor ROI calculators do not survive a CFO conversation.
Why most cases fail internally
Three recurring reasons, all avoidable.
The benefit is stated as efficiency. "Reps will save five hours a week" invites the response that they should therefore carry more accounts, not that revenue will rise. Time saved is only a benefit if you can say what it converts into.
The numbers come from the vendor. A supplier's ROI calculator is a sales tool, and everyone in the room knows it. Use your own data, even where it is rough.
The timeline is not stated honestly. Construction sales cycles run six to twenty-four months. A case implying revenue impact in quarter one will be judged a failure in quarter two, regardless of whether the underlying work is going well.
The four numbers
1. Addressable project volume you cannot currently see
The foundation of the case. Take one market you know well, list every relevant project your team was aware of last year, then compare against an external feed for the same definition — same countries, building types, size range, product categories.
The delta is your invisible market. For most manufacturers it is uncomfortably large, and it is the number that reframes the conversation from "a tool" to "we are competing in a fraction of our market."
2. Specification rate, split by entry stage
Your own history. Take the last forty pursued projects, record the project stage at first contact, and calculate the specification rate for early-entry versus late-entry projects.
Most manufacturers find a substantial gap. That gap, applied to the newly visible projects from number 1, is the core of the benefit calculation.
3. Average value of your product per project
Not total project value — the value of your own product. Pull it from order history, segmented by building type, because a hospital and a logistics centre differ by an order of magnitude for most portfolios.
4. Rep capacity currently consumed by research and admin
Sample rather than estimate. Ask three reps to log their week in half-hour blocks for two weeks, categorised into: specifier contact, travel, research and list building, CRM and admin, internal meetings.
The research and admin share is what a project intelligence platform removes. Express it as additional projects each rep can work, not as hours — hours invite the wrong conclusion.
Putting it together
The calculation, deliberately conservative:
Step | Value |
|---|---|
Newly visible relevant projects per year | 400 |
× Realistically pursuable (capacity-limited) | 15% → 60 |
× Specification rate at early entry | 20% → 12 |
× Specification-to-order conversion | 70% → 8.4 |
× Average product value per project | €45,000 |
= Incremental revenue | €378,000 |
Then apply your gross margin, and compare against total annual cost.
Present it as a range. Run the same calculation at a pessimistic specification rate and a realistic one. A case with a floor is far more persuasive than a case with a single confident number.
The costs buyers forget
Internal effort to make it work. Product documentation, target market definition, CRM configuration, training, an internal owner. A cheaper tool requiring a half-time internal owner is not cheaper.
Time to first revenue. Nothing closes for at least two quarters. Budget for that in the case rather than being surprised by it.
The cost of non-adoption. A licence used by 20% of reps costs five times its nominal price per active user. Include an adoption assumption explicitly, and say how you will measure it.
Structuring the proposal
Six sections, two pages:
The gap, in one number. Relevant projects in our market versus projects we saw last year.
What it costs us. That gap multiplied through specification rate and average product value — the revenue currently going to competitors by default.
What changes. Systematic discovery, product-level qualification, decision-maker contacts, automated CRM work. Concrete, not adjectival.
What it costs. Licence plus internal effort plus adoption risk, stated openly.
How we will know. The metrics you will report, with a baseline: projects identified, average project stage at first contact, specification rate, win rate from project found to closed, weekly active users.
Timeline. Leading indicators in one quarter, specification effects in two to three, revenue on the sales cycle.
Section 5 is what distinguishes a case that gets approved from one that gets deferred. Committing to a measurement plan signals that you expect to be held to it.
Useful reference points
External benchmarks strengthen a case when they come with named companies rather than anonymous averages. From Building Radar's reference customers: Sedus attributes €45 million in generated project volume to the platform; Holcim reports a 400% increase in sales meetings; Fröscher measures a 4.1x increase in win rate from project found to closed. On the tender side, teams report roughly 83% faster processing of service specifications.
Use these to argue that the mechanism works elsewhere — not to project your own numbers. A CFO will discount borrowed figures, correctly.
Frequently asked questions
How do you calculate ROI on construction sales software? Estimate the additional projects you would see and could pursue, apply your own specification rate and average product value per project, then compare the resulting gross margin against total cost including internal effort.
What payback period is realistic? Typically twelve to twenty-four months, because revenue arrives on the construction sales cycle. Leading indicators appear within one quarter.
Who should own the business case? Sales leadership, with finance involved early. Cases owned by marketing or IT tend to be evaluated as tooling rather than as revenue investment.
What is the strongest single argument? The gap between projects existing in your market and projects your team knew about. It is verifiable, uncomfortable, and not a claim about software.
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 size your own gap?
Find out how Building Radar's revenue engineering solution shows you how many relevant projects your team is currently not seeing.
Schedule an initial consultation