PN

Signal inbox

Collect raw signals before jumping to solutions. Identify meaningful patterns across the organization.

Sources & filters

Mission · Pipeline quality
Confidence · All
Verification · All
signalemployee
Human confirmed

Sales reports high demo volume but declining SQL quality; many prospects cite ‘researching options’ with no urgency.

Directly challenges activity-first demand strategy

Evidence · 3Similar · 7Confidence · 86%
Owner · Jordan Lee·confirmed·Sales call notes·mission·Jul 17, 2026·Human confirmed
signalcustomer
Human confirmed

Five recent enterprise prospects asked for case studies and security proof before agreeing to a second call.

Supports trust-signal hypothesis for pipeline quality

Evidence · 5Similar · 4Confidence · 91%
Owner · Priya Nair·confirmed·Customer conversations·mission·Jul 16, 2026·Human confirmed
signalanalytics
AI inferred

GA4 shows paid landing pages with 4.1% form rate but only 12% of those become SQLs.

May indicate offer or messaging mismatch

Evidence · 2Similar · 3Confidence · 74%
Owner · System·pending review·GA4 · Analytics agent·mission·Jul 18, 2026·AI inferred
signalcompetitor
Human confirmed

Two competitors relaunched sites leading with customer outcomes and third-party validation, not feature grids.

External pattern aligning with trust hypothesis

Evidence · 2Similar · 1Confidence · 80%
Owner · Lena Park·confirmed·Market research·public·Jul 14, 2026·Human confirmed
signalcustomer
Human confirmed

Ticket themes: unclear setup expectations and surprise about implementation effort.

Primary retention mission signal

Evidence · 12Similar · 2Confidence · 88%
Owner · Priya Nair·confirmed·Support tickets·mission·Jul 15, 2026·Human confirmed

Signal intelligence

AI suggestion
Emerging themes

Trust proof gaps · Activity without intent · Paid quality mismatch

Contradictions

Demo volume rising while SQL quality declines

Unusual observations

Heatmap dwell on FAQ contradicts feature-first page design

Frequently repeated

Enterprise asks for security proof before second call (5×)

Challenges assumptions

Signals challenge “more demos = more pipeline”