The playbook
Cost Per Lead Analysis: Review Process
A useful cost per lead analysis review ends with a supported decision for each item examined. Define the evidence required before opening the report: spend, raw leads, valid leads, qualified leads. These fields give reviewers a shared basis for agreeing what is working, what needs attention, and who should act.
Put the task in context
An illustrative $900 spend producing 30 submissions gives a raw cost per lead of $30. If only 15 are valid and suitable, cost per qualified lead is $60. Keep the qualification definition visible and do not present these numbers as a benchmark.
Set the review boundary
Choose the records or journeys that matter to the current question. Include a normal case, a recently changed case, and an exception where available. This is a diagnostic sample, not a claim that every item has been checked. Record how the sample was selected and what would justify expanding it.
Use explicit review criteria
| Criterion | Review question |
|---|---|
| Define which inquiries count as valid leads | Is the supporting spend current and traceable? |
| Divide relevant spend by leads from the same reporting basis | Does raw leads support the decision being made? |
| Compare qualified and unqualified lead costs separately | Can the next owner verify qualified leads? |
Inspect the evidence before assigning a result
For each item, compare the intended behavior with the observed behavior. Pay particular attention to optimizing for raw form submissions that contain spam or poor fit. If it appears, record where it occurs and which assumption it contradicts. Distinguish a verified defect from an unanswered question and from a preference about how the work should look.
Where the evidence supports the known correction, use valid and qualified lead definitions alongside the raw count. Give that action to an accountable owner with a description of the expected result. If you cannot yet identify the cause, assign a diagnostic action rather than prescribing a speculative repair.
Record a decision that can be acted on
| Decision | When to use it |
|---|---|
| Keep | The current state serves the intended task and the evidence is adequate. |
| Revise | A specific gap is confirmed and the proposed action addresses it. |
| Investigate | Important information is missing or conflicting. |
| Retire or combine | The item has no distinct useful purpose in the current scope. |
Verify corrections and expand selectively
Recheck the affected campaign or conversion record after the owner completes the action. Then inspect other items sharing the relevant cause. A shared template, process rule, or data source may justify expanding the review. Similar wording or appearance alone is a weaker reason.
Turn the review into a decision summary
Summarize the affected scope, confirmed findings, actions, and open questions. Connect the findings to cost per qualified lead using the same definition as the baseline. A good summary lets the responsible person decide what happens next without reading every working note.
Check the destination and the resulting business record before increasing spend. A campaign can send relevant traffic to a form that fails, routes incorrectly, or records duplicates. Fixing that path may change the interpretation of campaign performance.
Skip the manual steps. Let AgentixFLO run this for every client.
Start now