Skip to content
All case studies
Revenue teamWorkflow Automation2 min read

“Poor leads” wasn’t useful enough feedback

Sales knew why prospects were rejected. Marketing needed those reasons connected to campaign records, not left in notes and conversations.

HubSpot Workflows · Lifecycle Sync · Marketing Reporting

38% → 89% usable sales feedback coverage

3 Campaign Changes Triggered · 4 Hours/Week Manual Compilation Removed · 10-Week Feedback Loop Rebuild

The feedback loop I connected

“Poor lead” was too broad to guide a campaign change. Sales outcome categories and selected HubSpot fields connected rejection reasons with acquisition records, while missing feedback remained visible for follow-up.

Lead-quality discussions relied on anecdotes.

HubSpot contained acquisition activity and sales outcomes, yet much of the feedback stayed in notes, spreadsheets and conversations. Marketing heard that quality was weak without a dependable view of which sources were responsible or what sales meant by a poor lead.

Make the feedback specific, current and usable

Marketing and sales agreed lifecycle stages and a small set of outcome reasons that could change targeting, copy or budget. Only fields needed for those decisions entered the synchronization.

Timestamps and sampled journeys checked that a campaign record belonged to the right sales outcome. Missing feedback stayed unresolved until reviewed, rather than being counted as neutral or positive demand.

Make sales feedback specific enough to change a campaign.

A small set of outcome reasons distinguished poor fit, timing and a useful opportunity. Campaign context and checked updates connected those reasons to acquisition decisions.

Make sales feedback specific enough to change a campaign.
Outcome categoryDecision it can informInterpretation check
Company or role fitAudience and exclusion prioritiesIs the agreed fit definition applied consistently?
No active need or timingOffer, nurture and progressionWas the inquiry premature rather than inherently poor?
Budget or commercial mismatchProposition and qualificationDoes the evidence describe a recurring pattern?
Unreachable or incompleteFollow-up and data qualityCould response process or missing information explain it?
Missing feedbackCoverage repair and investigationDo not treat an empty value as a neutral outcome

A missing response was not a positive outcome. Incomplete feedback remained visible until someone resolved it.

Check that campaign and sales updates match

Detailed reason codes can reduce accuracy when sellers struggle to distinguish similar options. A small actionable set with room for notes was more maintainable than requiring every nuance to become a picklist value.

Sales feedback also reflects response, capacity and individual qualification judgment. It deserved a place in acquisition decisions without becoming an infallible score, so record checks and interpretation remained part of the weekly review.

Ten weeks of usable feedback

After ten weeks, usable sales feedback coverage rose from 38% to 89%. Three campaign changes followed from the new evidence, and manual compilation required four fewer hours per week.

The ten-week result is stronger feedback coverage, four fewer hours of compilation per week and three campaign changes informed by the data. It does not yet establish that those changes improved acquisition cost or customer value; that requires the next downstream performance review.

Feedback had to arrive as an actionable CRM outcome. Visible missing values prevented silence from being mistaken for rejection, while traceable updates gave marketing something it could actually use.

CRM feedback-loop implementation

I can help you turn sales outcomes into usable campaign feedback.