The report announces that leads are cheaper. The person answering them asks whether anyone has changed the form, because several enquiries now arrive without the information needed for a useful reply.
Both observations can be accurate. They are describing different parts of the process.
Here is an invented review, with no client performance figures, showing the annotations I would want beside an encouraging acquisition headline.
Headline: Cost per lead has fallen.
Annotation: What does “lead” mean here? A recorded form event, a distinct request, an enquiry within the service's scope or a conversation accepted by the receiving team? Give the event its actual name before allowing the cost attached to it to imply more.
If the definition changed, describe that change next to the comparison. A shorter form might make submission easier while postponing a question the business still needs answered. That can be a worthwhile trade. It should be an understood trade, rather than an accidental reporting improvement.
Headline: The account generated more enquiries.
Annotation: How many distinct requests do those events represent? Someone who submits again after hearing nothing may not be a second opportunity. They may be the first opportunity becoming concerned.
The practical investigation is small. Check how the event is recorded, how duplicate requests are recognised and what the customer sees after submitting. Use authorised records and keep personal information out of the presentation. The team needs the pattern, not an unnecessary copy of somebody's private message.
Headline: Lead quality needs improving.
Annotation: Who assessed it, using which definition, after how much time? A suitable request sent to the wrong inbox is not necessarily an acquisition problem. A request missing a crucial detail may point to the page or form. An enquiry outside the service area may point to the promise, targeting or both.
Read the first reply the team would send. If it begins by asking which service the customer selected on the page, something useful may have been lost in the handover. If it asks for a photograph the form never mentioned, consider explaining that requirement earlier.
Headline: The latest campaign has not produced sales.
Annotation: Is the observation window long enough for the ordinary sales process? Recent requests may still be awaiting visits, quotations or a considered decision. That does not excuse a slow response. It does mean the report should distinguish unfinished evidence from an established failure.
Google's offline-conversion guidance describes connecting later outcomes to ad interactions. The measurement arrangement still needs agreed definitions, appropriate data handling and a check that the recorded outcome means what the business thinks it means.
For anyone considering groas's business offering, I would bring those definitions into the initial outcome discussion. A target cannot resolve an ambiguity that the team has never named.
The next review should contain an action someone can own: repair the notification, explain a required detail, investigate unsuitable enquiries or wait for a defined group to mature. “Improve lead quality” is a concern. It becomes work only when we describe the problem more precisely.
A slightly less triumphant headline is fine. I would rather know which conversations became useful than admire a bloody cheap event that nobody can explain.
A thought worth keeping?
