Template P9 · Paid & Lead Generation
Platform Automation Constraint Sheet.
What we feed the machine, now that we no longer drive it. As buying automates, the job migrates from operating campaigns to architecting the inputs, and almost no template library has caught up.
The decision this template protects
What inputs and constraints we give the system, since those are now the levers we actually hold.
Paid & Lead Generation
Main Course Module 4 · Asset and funnel design
Version 1.0 · 19 August 2026
Fill it in your browser →
Download the PDF · 4 pages · 158 KB ↓
The browser version keeps everything on your device. Nothing you type is sent to aFactor.
Before you start, you need
What has to be true first.
- Current campaign configuration.
- Conversion and audience data quality assessment.
- Creative and feed inventory.
What this template will not do for you
Its stated limits.
- It will not tell you how any platform's system works internally. Those are not disclosed and change without notice.
- It has a short half-life. Check the review date before relying on the mechanics described here.
- It does not replace judgment about strategy. Better inputs to the wrong objective produce faster failure.
What is in it
6 sections, and what each one makes you write down.
01
The four inputs you control
- Input
- What it determines
- Current state
- Quality
02
Signal architecture
- Question
- Answer
- Deliberate?
03
Asset supply
- Asset type
- How many live
- Refresh rate
- Enough for the system to test?
04
Data quality
- Data input
- Present
- Accurate
- Fresh
- Consent basis recorded
05
Constraints and guardrails
- Guardrail
- Set?
- Value
- Reviewed
06
What we can no longer see
- What is now opaque in this account
- What we do instead to stay honest about performance
Judgment prompts
Questions the template makes you answer.
- Which lever are you still pulling that the system now overrides?
- If the signal you optimise toward is imperfect, what is the system quietly getting better at finding?
- Are your guardrails deliberate decisions or platform defaults nobody has examined?
- What has become invisible, and does the client know?
The defensible output
What you are left holding.
A documented input architecture across signal, assets, data and constraints, plus an honest statement of what has become unobservable.
Published open. Copy it, adapt it, use it on client work. If you pass it on, keep the attribution line on it.
More from the library
Sixty-five instruments, eighteen published open.
Each one names the decision it protects, states what it will not do, and ends in something you could defend six months later.