The playbook
Cost Per Lead Analysis: Template and Field Guide
This cost per lead analysis template turns a broad task into a record another person can use. It captures spend, raw leads, valid leads, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| spend | Record the spend associated with this campaign or conversion record. Use a stable reference so later updates can be matched. |
| raw leads | Record the raw leads associated with this campaign or conversion record. Keep the value specific enough for another owner to interpret. |
| valid leads | Record the valid leads associated with this campaign or conversion record. Keep the value specific enough for another owner to interpret. |
| qualified leads | Record the qualified leads associated with this campaign or conversion record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with spend. Use the same reference throughout the record so notes are not attached to the wrong item. Then define which inquiries count as valid leads. This establishes the information required before the worksheet becomes a request for action.
Next, divide relevant spend by leads from the same reporting basis. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as optimizing for raw form submissions that contain spam or poor fit, rather than a broad instruction to “improve performance.”
Finally, compare qualified and unqualified lead costs separately. Put use valid and qualified lead definitions alongside the raw count in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Optimizing for raw form submissions that contain spam or poor fit |
| Action | Use valid and qualified lead definitions alongside the raw count |
| First check | Define which inquiries count as valid leads |
| Follow-up check | Compare qualified and unqualified lead costs separately |
| Outcome to define | cost per qualified lead |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If raw leads changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep cost per qualified lead connected to the item so the team can later assess whether the action was useful.
Review offer eligibility and fulfillment capacity alongside campaign response. Demand that the business cannot serve is not a useful acquisition result. Update messages and routing when availability or service boundaries change.
Skip the manual steps. Let AgentixFLO run this for every client.
Start now