Monday, before. The sales manager is asked which channels produced last quarter's revenue. He opens the system and finds two hundred records with no source field populated.
He reconstructs it from memory and from what salespeople recall. The answer is confident, plausible and largely wrong, and the marketing budget for the next quarter is set from it.
Tuesday, after. The same question, answered from records that captured the landing page, the referring source and what the enquirer actually asked about, on every enquiry.
Monday before: the enquiry arrives with no context
A name, an email address and a message box. Nothing records which page the person was on, what search brought them, or what they were actually looking at before they decided to make contact.
Tuesday after: the enquiry arrives with its history
Landing page, referrer, the pages viewed and the question asked, attached to the record before anybody touches it.
Wednesday before: the salesperson asks how they heard
Mid call, awkwardly, and records whatever the customer says, which is frequently the most recent thing they remember rather than what actually worked.
Wednesday after: the salesperson confirms rather than establishes
The record already says. The conversation adds nuance instead of starting from nothing, which is a better use of the call.
Thursday before: the report is a guess
Channel performance assembled from partial records and recollection, presented with a confidence the underlying data does not support.
Thursday after: the report is arithmetic
Enquiries, qualified opportunities and closed revenue by source, calculated rather than estimated, and defensible in a budget meeting.
Friday before: the budget follows the loudest channel
Spend allocated to whatever generated visible activity, because nothing distinguishes activity from revenue in the available data.
Friday after: the budget follows the revenue
Including the quiet channel that produced few enquiries and closed most of them, which was previously invisible and underfunded.
What the long sales cycle needs
Source held against the record through months of activity, since a deal closing in the third quarter was created by something in the first.
What the multiple touch problem needs
Recognition that most buyers arrive through several channels, and a consistent rule for how credit is assigned rather than an argument each quarter.
What the offline conversations need
A way to attach the source when a deal arrives through a referral or an event, so those channels appear in the same report.
What the technical setup needs
Which is the ground in attribution and tracking setup questions.
What the qualification adds
Source is more useful alongside budget and size, which is the approach in qualifying by budget without being pushy.
What the sales team needs to believe it
Attribution that contradicts a salesperson's experience is ignored rather than acted on. Showing the underlying records behind each number, rather than a summary, is what makes the report something the team uses instead of disputes.
Capture the source at the first contact
An assistant that records the landing page, the referring source and the question asked, writes it into the record with the qualifying detail and keeps it attached through to close turns a budget conversation from recollection into arithmetic. The detail sales needs is set out in capturing the detail sales actually needs and the intake in qualifying inbound leads without a long form. See pricing, run the numbers on the chatbot ROI calculator, and the sector view sits under b2b.