Ground them in people, organizations, and projects

Ungrounded signals create activity without progress. Everyone agrees something "might be big," but no one knows who owns the conversation, what proof applies, or what should happen this week.

Grounding connects a rumor to people, organizations, and context so the next move is obvious.

That usually means naming:

• a person: the clearest contact tied to the change
• an organization: the owner, developer, agency, or collaborator involved
• a relationship owner inside the firm who should stay close to the signal
• a market and project type so the signal can be compared to direction
• a possible timeline: even a rough window beats "someday"
• a relevant proof point or gap the firm would need to compete
• a next action specific enough to schedule

Compare vague versus grounded:

"Hospital exploring expansion" is vague.

"Former client Dana now leads ambulatory planning at Bayview Health. They are evaluating outpatient growth in Pinellas over the next 12 months. We have two relevant clinic projects. Alex knows their owner’s rep. Next action: ask Alex for context before outreach."

That is grounded.

Grounding does not require perfect information. It requires enough specificity that someone else in the firm could pick up the signal two months later and still understand why it mattered.

This is where pre-RFP notes, relationship maps, and weekly BD rhythm meet. Grounded signals have a place to live before they become formal pursuits.