The problem with HubSpot's default pipeline data
Every revenue leader using HubSpot faces the same problem: the pipeline looks clean on Monday morning before the review, and by Tuesday it's already stale.
The reason is simple. Reps update what gets checked. Stage, close date, and amount get updated before pipeline reviews because managers ask about them. Everything else — the competitor that came up on a call, the champion who has gone quiet, the budget that might shift next quarter — gets skipped because nobody is asking about it in a structured way.
The result is a CRM that reflects rep optimism, not deal reality. Stage is a lagging indicator. By the time a deal moves to "Negotiation" on paper, you may have already lost the real decision.
The core problem: HubSpot tracks what happened (emails sent, calls logged, stage changed). It does not track what reps heard — the qualitative intelligence from every customer conversation that actually determines whether a deal closes.
What are field signals in sales?
Field signals are the qualitative observations reps make during customer interactions that don't fit neatly into a CRM field. They include:
- Competitor mentions — a prospect comparing you to a competitor, or a competitor entering the deal late
- Budget signals — budget confirmed, budget questioned, or a freeze announced
- Champion engagement — an internal advocate becoming more or less active
- Urgency signals — a deadline that appeared, or pressure to close from the prospect's side
- Objections — a specific concern or blocker raised by the prospect
- Risk signals — anything that could jeopardize the deal (key contact left, reorganization, procurement delay)
These signals are what experienced sales managers ask about in deal reviews. The problem is that by the time they ask, the information has been filtered through the rep's memory and optimism.
Why HubSpot doesn't capture this by default
HubSpot's activity feed captures structured data well — emails, calls, meetings, stage changes. It does not have a native mechanism for capturing the content of what reps hear on those calls in a structured, queryable way.
Some teams try to solve this with:
- Deal properties — required fields at stage gates (MEDDIC-style). Works for structured qualification but not for signals that emerge mid-cycle without a clean answer.
- Notes — reps log free-text notes. Useful, but unstructured and not aggregatable across deals or segments.
- Slack messages — the most common solution. Intel lives in Slack threads that nobody reads after 48 hours.
None of these give managers a real-time, aggregated view of what the field is seeing across all deals.
The 6 signal types that matter most
How to capture field signals directly in HubSpot
The key constraint is friction. If capturing a signal requires reps to leave HubSpot, open a separate tool, or fill in more than a few fields, adoption drops to near zero within two weeks.
The most effective approach is a native HubSpot CRM card that appears directly in the Deal and Contact sidebar. Reps log a signal in under 20 seconds without leaving HubSpot:
- Select a signal type (competitor, urgency, budget, etc.)
- Rate intensity from 1 (low) to 5 (critical)
- Add one line of context ("Prospect mentioned Salesforce as their current shortlist")
That's it. The signal is logged, timestamped, and attributed to the rep — without any context switching.
How AI turns signals into deal priority scores
Individual signals are useful. Aggregated signals across an entire pipeline are where the real intelligence emerges.
When multiple reps log signals on the same deal, or when a deal accumulates high-intensity signals across multiple types, that pattern is a stronger indicator of deal health than any single data point. This is what the Hive Score captures.
The Hive Score is a deal priority score from 0 to 99 calculated from:
- Signal volume — how many signals have been logged on this deal
- Average intensity — weighted average of signal intensity across all signals
- Rep coverage — how many different reps have flagged the same deal
A deal with a Hive Score of 85 has multiple reps logging high-intensity signals. That is a deal that needs attention — or a deal that is about to close. Either way, it surfaces automatically without a manager having to dig through the pipeline.
What managers can see once signals are flowing
With field signals aggregated, managers get visibility they have never had before:
- Heatmap by segment — which industries or segments are generating the most signal activity
- Real-time alerts — when two or more reps flag the same deal within 48 hours, a Colmena Alert fires automatically
- Rep workload view — which reps are active and which have gone quiet
- AI rep matcher — for any segment, surfaces the rep with the most relevant signal history and current capacity
The result: forecasts based on field reality
When your pipeline review is based on Hive Scores and signal patterns rather than stage and close date alone, the conversation changes. Instead of "the rep thinks this closes next month," the question becomes "what signals has the field logged on this deal, and what do they tell us about actual momentum?"
That shift — from rep-reported status to field-observed signals — is where forecast accuracy improves.
Want to try this in your HubSpot portal? Colmena is a native HubSpot CRM card that installs in under 5 minutes. No code, no custom fields, no configuration. Install free on HubSpot →