The entry point problem

You find out at tender stage.
The shortlist was made months earlier.

In construction, the decision about who gets the work rarely happens at the procurement stage. It happens earlier, at the relationship stage, when the developer is still planning and the project hasn't been announced. By the time an RFQ or brief goes out, there's often a preferred team already in mind.

When the shortlist actually forms vs when most BD teams find out
Signal stage
Development Application lodged
Publicly recorded with council. Months before the project goes to market. A Development Application (DA) is the formal request for planning approval. It's the first signal you can trace. It also gives you the most time to build a relationship.
IR monitors here
Signal stage
Land acquired / transferred
A developer buying land signals a project is coming. The question is when, and who is already in conversation with them.
IR monitors here
Window, open
Developer builds preferred contractor list
Relationships are being formed. The shortlist isn't official, but it's forming. This is the window that matters, and it closes before the brief goes out.
Your BD team gets the alert here
Too late
Tender / RFQ released publicly
Most BD teams find out here. The preferred contractor list is already months old. You're pricing against people who were already in the room.
Most BD teams enter here
What late entry costs you

None of this is visible until it shows up in your win rate. By then, the pattern has been running for months.

Arriving too late to the relationship
You know the developer. But the project was in planning for six months before you found out. By the time you called, their team was already assembled.
BD that reacts to what's public
Your BD team finds its work from what's already out there: tender portals, news and referrals. That puts you at the same entry point as everyone else.
Pipeline that depends on referrals you can't scale
Referrals work. But they're not predictable and they can't be scaled. The businesses with consistent pipelines have a systematic way of finding projects early, not a better network.
Detect · Enrich · Alert

Three steps from signal to
conversation.

We're a Revenue Operations Studio: we build and run the revenue system for you. We set up signal-monitoring systems to match your ICP: project type, region, size and the kind of developer. When a signal fires, it's enriched with contact data for the decision-maker and routed to your BD team, inside the Verified Buying Window™, before the shortlist closes.

01 · Detect
Monitor the signals
We watch, nonstop, for plans sent to council, DA lodgements, land transfers and council approvals. Then we filter them to suit your ICP.
Region, project type, and value threshold defined
Planning portals, land title registries, council databases monitored
Signals scored by timing and fit before surfacing
Duplicate and irrelevant signals filtered automatically
02 · Enrich
Match the decision-maker
For each signal that fits, we add contact details for the person who matters. That might be the developer, the project manager, the owner or the architect. It depends on how your BD team sells.
Developer entity matched to key contacts
Verified email and LinkedIn profile appended
Project manager or principal architect identified where relevant
Company size, prior projects, and relationship history noted

Every alert is timed to land inside the Verified Buying Window™. That's the time between spotting the signal and the shortlist being set. Inside it, a relationship can still decide who wins. After that window closes, the same outreach produces a fraction of the result.

An honest assessment

This is not the right fit for every
‍construction business.

Signal monitoring only makes commercial sense when the underlying numbers support it. One additional project win needs to cover the cost of the programme. We check that before proposing anything.

Strong fit
✓
Commercial, industrial, or civil contractor where developer and project manager relationships determine the shortlist
✓
Active BD team that can move quickly on a lead, signals are time-sensitive and the window narrows as the project progresses
✓
Project values where one additional win covers the full cost of the programme
✓
Currently spending estimating hours on tenders with a low win rate
✓
Actively growing into new regions, project types, or client relationships beyond existing referral base
Poor fit, we will say so
✕
Residential volume builders where decisions are driven by price and specification, not pre-existing relationships
✕
Teams without BD capacity to follow up, signal monitoring without a follow-up motion produces nothing
✕
Businesses with a full pipeline and no growth target, if you're at capacity, this adds noise, not value
✕
Project values where the per-signal economics can't be justified against the cost of the programme
✕
Teams wanting a one-off list of leads, signals require a continuous monitoring cadence to produce consistent output
✕
Businesses that work predominantly on government infrastructure contracts, mandatory public procurement rules apply above certain thresholds and the relationship-based shortlisting model does not apply in the same way
Objections we hear, and the honest answers
Objection "We already get plenty of leads through referrals and tender portals."
Referrals and tender portals work. But you can't predict referrals or grow them on demand. And tender portals put you at the same starting line as every other contractor. If your current pipeline covers your capacity targets, this probably isn't the right time. If you're trying to grow beyond what referrals produce, entering at the signal stage is how you do it without adding headcount to BD.
Objection "Our BD team already monitors planning portals manually."
Manual monitoring catches some signals. It misses most. Planning portals, land title registries, and council databases each require separate checking. Doing it well is a full-time job. You'd need to check every region, filter by ICP and find contact details before the window shuts. Most BD teams do it occasionally. Continuous monitoring means catching every signal, not the ones that surfaced on a day someone had time to check.
Objection "We're not sure if our project value justifies the investment."
That's the right question, and we'll answer it before we propose anything. The test is simple: does one additional project win, at your average contract value, cover the full cost of the programme? If it does, the economics work. If it doesn't, we'll tell you that at the scoping stage and save both of us the time.
In Practice

We've had a team of six, probably over the last three years, Googling their little hearts out, and we haven't been able to find the leads you have.

Carissa Dewar
General Manager, business to business client
FAQs

Frequently Asked Questions

Short answers to what comes up most in a first conversation.

  • Where does the signal data actually come from?

    From public planning and property records, monitored continuously and filtered to your ICP. That means planning applications, DA lodgements, land transfers, and council approvals across the regions and project types you work in. Every signal is scored for timing and fit before it surfaces, so duplicates and irrelevant filings never reach your team.

  • Do we need to replace our CRM to use this?

    No. We work with the CRM you already have, including HubSpot and Salesforce, and there is no migration. Alerts are logged against the right record automatically, so your BD team stops doing manual entry. The one prerequisite is a CRM with at least 1,000 active records and an ICP you can define.

  • Who contacts the developer, you or our BD team?

    Your BD team does. We send a checked alert. It has the project details, the decision-maker's contact details and the story behind the signal. Your people take it from there. The introduction stays yours, which matters in a market where the relationship decides the shortlist.

  • What is the Verified Buying Window?

    It is the period between a signal being detected and the shortlist forming. Inside the Verified Buying Window™ a relationship can still change who wins the project. Once it closes, the same outreach produces a fraction of the result, which is why alerts are timed rather than batched.

  • What do you need from us to get started?

    Three things: your ICP criteria, access to your CRM, and BD capacity to follow up. ICP criteria means region, project type, and a value threshold. Of the three, BD time matters most. Watching for signals gets you nothing if nobody follows up.