Most commercial teams in construction have a version of the same list: projects someone has heard about, copied from a planning register, a news story or a subscription service. The list is usually long, and that is usually treated as a good sign.

It often is not. A list of projects tells you what is happening in the market. It does not tell you what any of it means for your business, and those are different questions.

The same project, four different answers

Take a new owner buying a group of hotels and announcing plans to reposition them. That is one project, and anyone can read the announcement. What it is worth depends entirely on who is reading.

  • For an architect, the interesting moment may be now, before a design team is appointed.
  • For a building services engineer, it may come a little later, once someone is shaping the design.
  • For a joinery supplier, the announcement is early warning; the real opening may come when a specification starts to form.
  • For a facilities management provider, the relevant decision might be a year or more away.

Each of those firms is looking at the same facts and should reach a different conclusion about whether to act, when, and with whom. One project has become four opportunities, and for plenty of other firms it is no opportunity at all.

What turns a project into an opportunity

We find it useful to treat an opportunity as the meeting point of four things:

  • A requirement. The specific service, trade or product the project is likely to need. A project is rarely one requirement; it is many, arriving at different times.
  • Your capability. Whether you can credibly deliver that requirement, in that sector, at that scale, in that place.
  • Timing. Whether the moment to act is still ahead of you. A perfect-fit requirement that has already been appointed is not an opportunity.
  • Commercial fit. Whether you want it: your strategy, your capacity, your route to the people making the decision.

Remove any one of the four and what is left is information. It may be interesting. It is not something your team should spend a week on.

Why long lists disappoint

A project list does the first part of the job—finding things—and leaves the remaining judgement to whoever reads it. For every entry, somebody has to work out what might be needed, whether the firm could do it, whether there is still time and whether it is worth pursuing.

That judgement is the expensive part. It depends on experience, and it tends to live in the heads of a few senior people who have the least time to give it. So the list gets skimmed, the obvious names get followed up, and the opportunities that would have suited the firm best are as likely to be missed as found.

A bigger list makes this worse. The few entries that fit are harder to see, and the work of sorting grows with every new row.

What to ask for instead

If the unit of value is the opportunity and not the project, the useful questions change. Whatever you use to find work—a person, a subscription, a piece of software—it is fair to ask:

  • Does it know enough about our business to tell a relevant project from a merely large one?
  • Does it say what we might be needed for, and when that decision is likely to be made?
  • Does it explain why it thinks so, in a way we can check?
  • Does it show us fewer things, with more confidence, or simply more things?

None of this replaces the relationships and judgement that win work. It decides where that scarce attention goes. A short list of opportunities that fit, with the reasoning attached, is worth more than a long list of projects that exist.