Funnel Stage Variants
Shared quality bar: ../references/output-standard.md. All numbers cited here live in ../references/thresholds.md.
The point of this skill is continuity. A retargeting ad that argues a different
case than the cold ad the viewer already saw restarts the sale instead of
closing it.
Use this skill when
An angle has evidence behind it in one audience and the account wants it
running across cold, warm and retargeting placements. Also use it when the
three stages are already live and each says something unrelated to the others.
The angle must already be proven or explicitly labelled unproven. Not for
inventing or choosing an angle, and not for a first draft of feed copy, which
is paid-social-primary-text-ad-creative. Not for the opening seconds of a
video, which is video-hook-lines-ad-creative. Not for Google search assets tied
to a keyword set, which is search-headline-set-ad-creative.
Required input
- The winning angle as one sentence, and the copy exactly as it runs today.
- The evidence it won on: window as dates, spend,
conversions or link clicks,
and the control it beat.
- Audience definitions for each stage, including what the retargeting pool
actually did to enter it.
- The offer at each stage, if it differs, and who approved the difference.
- Any claim used in the current copy, with its source.
Analysis workflow
- Check whether the angle is genuinely proven. Test the supporting read
against
test.volume_floor, test.min_runtime and test.material_gap
before rewriting anything. A win inside test.material_gap is a tie.
- Extract the invariant: the promise, the mechanism and the proof. These are
what must survive all three stages unchanged in substance.
- Write the cold variant. Assume no prior contact, so the problem is named
before the product and the proof carries more weight.
- Write the warm variant. The problem is assumed known, so the space goes to
the mechanism and to the objection that stops people at this stage.
- Write the retargeting variant, and hold the line that makes this skill worth
running. Stage is the one changed element under
test.one_change_rule, so
four things stay byte-identical across all three: the angle sentence, the
main claim in the exact words it runs in today, the single proof, and the
conversion action with the destination behind it. Change the opening, the
emphasis and the reference to what the viewer already did. Change any of the
four and the account can no longer tell a stage effect from an angle effect,
because two things moved between the cells it is comparing; the retargeting
ad will win, as retargeting ads do, and nobody will know whether the stage or
the new argument did it. The offer is the one people move without noticing:
a discount added at retargeting is a second changed element, not a stage
adaptation.
- Diff the three variants line by line and produce an explicit changed and
unchanged list. Anything in the changed list that touches the promise or the
proof is a defect, not a stage adaptation.
- Check message match at every stage with
match.promise_pairs and
match.above_fold_rule, because stages often point at different pages.
- Apply
claims.evidence_rule, claims.superlative_rule and
claims.restricted_topics to all three variants and mark unsourced factual
lines [claim: needs source].
Decision rules
- The supporting result sits inside
test.material_gap or under
test.volume_floor: the angle is not proven. Write the variants if asked,
label the whole set test at low confidence, and say the extension is a
bet.
- Retargeting variant changes the promise, the proof or the angle sentence:
rewrite. Stage changes emphasis and the reference to prior action, never
the argument.
- The offer differs between stages: this is a second changed element under
test.one_change_rule and the set stops being a stage test. Either hold one
offer across the three, or run the offer change as its own test against a
named control and say the stage question has been given up for this round.
Decision investigate on which of the two questions the account actually
wants answered.
- No stage reaches
test.volume_floor on its own conversions inside
test.min_runtime: the three cannot be compared on conversions at all. Read
them on test.click_floor, state in the output that the answer is
click-side only, and cap the whole set at low under the shared scale.
- Cost per acquisition between two stages differing by less than
money.relevance_floor: no stage won. Report a tie and leave the budget
where it is; a rate difference that does not move cost per acquisition is not
a reason to shift spend between temperatures.
- Retargeting pool sitting under
delivery.ranking_floor of the campaign's
spend: it may have run, but its share is too thin to compare against the cold
and warm stages. monitor, and say the comparison between stages is
unavailable until the pool gets a comparable share of delivery. Where the pool
is under delivery.never_delivered_floor as well, it did not run at all and
the finding is allocation rather than the copy.
- Retargeting pool defined by page view alone with no stated action: label
investigate, because the copy cannot reference something unknown.
- A stage points at a page missing the ad's main claim above the fold:
investigate the page, and hold that stage's variant.
- Fewer than
coverage.angles_per_ad_set live angles once these variants ship:
say so, because a losing week will not be readable. Three stage variants of
one argument are one angle under coverage.angle_distinctness, not three,
and an account that counts them as three has just talked itself into a
coverage pass it did not earn.
- Any line this skill produced that carries
[claim: needs source] is
approval_needed, whatever else its verdict says, and the marker is never
stripped to make the set look finished. A marked line is not shippable copy:
it waits for the named source, or it is rewritten without the claim.
Output format
No verdict line. Three copy blocks, one per stage, each with its audience,
offer, evidence label and decision label. Then two lists side by side: what
changed between stages and what stayed identical. Then a one-line statement of
the strength of the original result in its own numbers. Then the four elements
held identical across the three stages, listed literally, so a reader can check
them rather than trust them. Then What this could not see, Missing data,
Approval gates.
This skill writes copy rather than reading a test or a time series, so it issues
no high confidence label of its own. The confidence it does state is inherited
from the original result being extended, read on the shared scale in full, and it
never rises above what that result carried. Nothing about writing three variants
makes the evidence behind the angle stronger.
Practical example
Illustrative and fictional. Advertiser "Halden". Angle: "you are paying twice
for the same lead". The cold ad is reported at 1.9% link CTR against a control
at 1.7%, over 9 days, 41 purchases across the ad set.
Strength of the original result: 1.9% against 1.7% is about 12% relative,
inside test.material_gap, and 9 days is short of test.min_runtime. The angle
is not proven and the claim that it won is refused as a tie. Variants are still
written, all labelled test at low confidence, and the extension is a bet.
Cold:
Two of your lead sources are selling you the same person. You are paying twice
for the same lead. Halden matches inbound records across sources before they
reach your CRM. Book an audit.
Warm:
You know about the duplicates. Here is where they start: two sources, one
person, two invoices. You are paying twice for the same lead. Halden matches
inbound records across sources before they reach your CRM. Book an audit.
Retargeting:
You opened the duplicate check and left it. Nothing has changed since. You are
paying twice for the same lead. Halden matches inbound records across sources
before they reach your CRM. Book an audit.
Held identical: the angle sentence; the claim "You are paying twice for the same
lead" word for word; the single proof; the conversion action and its
destination. Changed: the opening line and the reference to prior action only.
One offer across all three, deliberately, so the account reads the stage rather
than a discount.
Declined:
- "You already know this works for teams like yours", in the retargeting draft.
No case evidence was supplied, so it is not written. Its slot goes to the
abandoned check, an observed action rather than a claim.
- "Cuts duplicate spend by a third"
[claim: needs source]. This was the single
proof, so all three ship without a proof line and the set is weaker for it.
Any variant carrying it is approval_needed and none goes live with it.
Guardrails
- Never call an angle proven on a result inside
test.material_gap.
- Never let the promise or the proof drift between stages.
- Never reference a prior action the retargeting definition does not contain.
- Never invent a case study, a customer or a saving figure.
- Do not change audiences, budgets or ad status in the account.
- Report every line declined at every stage, with the reason.
1---2name: funnel-stage-variants-ad-creative3description: Takes one angle that is already proven and rewrites it three ways, for cold prospecting, warm audiences and retargeting, naming what changes between stages and what must stay identical. Use when the input is an existing winner being extended across audience temperatures. Not for writing an untested angle from scratch, which is paid-social-primary-text-ad-creative.4---56# Funnel Stage Variants78Shared quality bar: `../references/output-standard.md`. All numbers cited here live in `../references/thresholds.md`.9The point of this skill is continuity. A retargeting ad that argues a different10case than the cold ad the viewer already saw restarts the sale instead of11closing it.1213## Use this skill when1415An angle has evidence behind it in one audience and the account wants it16running across cold, warm and retargeting placements. Also use it when the17three stages are already live and each says something unrelated to the others.18The angle must already be proven or explicitly labelled unproven. Not for19inventing or choosing an angle, and not for a first draft of feed copy, which20is paid-social-primary-text-ad-creative. Not for the opening seconds of a21video, which is video-hook-lines-ad-creative. Not for Google search assets tied22to a keyword set, which is search-headline-set-ad-creative.2324## Required input2526- The winning angle as one sentence, and the copy exactly as it runs today.27- The evidence it won on: window as dates, spend, `conversions` or link clicks,28 and the control it beat.29- Audience definitions for each stage, including what the retargeting pool30 actually did to enter it.31- The offer at each stage, if it differs, and who approved the difference.32- Any claim used in the current copy, with its source.3334## Analysis workflow35361. Check whether the angle is genuinely proven. Test the supporting read37 against `test.volume_floor`, `test.min_runtime` and `test.material_gap`38 before rewriting anything. A win inside `test.material_gap` is a tie.392. Extract the invariant: the promise, the mechanism and the proof. These are40 what must survive all three stages unchanged in substance.413. Write the cold variant. Assume no prior contact, so the problem is named42 before the product and the proof carries more weight.434. Write the warm variant. The problem is assumed known, so the space goes to44 the mechanism and to the objection that stops people at this stage.455. Write the retargeting variant, and hold the line that makes this skill worth46 running. Stage is the one changed element under `test.one_change_rule`, so47 four things stay byte-identical across all three: the angle sentence, the48 main claim in the exact words it runs in today, the single proof, and the49 conversion action with the destination behind it. Change the opening, the50 emphasis and the reference to what the viewer already did. Change any of the51 four and the account can no longer tell a stage effect from an angle effect,52 because two things moved between the cells it is comparing; the retargeting53 ad will win, as retargeting ads do, and nobody will know whether the stage or54 the new argument did it. The offer is the one people move without noticing:55 a discount added at retargeting is a second changed element, not a stage56 adaptation.576. Diff the three variants line by line and produce an explicit changed and58 unchanged list. Anything in the changed list that touches the promise or the59 proof is a defect, not a stage adaptation.607. Check message match at every stage with `match.promise_pairs` and61 `match.above_fold_rule`, because stages often point at different pages.628. Apply `claims.evidence_rule`, `claims.superlative_rule` and63 `claims.restricted_topics` to all three variants and mark unsourced factual64 lines `[claim: needs source]`.6566## Decision rules6768- The supporting result sits inside `test.material_gap` or under69 `test.volume_floor`: the angle is not proven. Write the variants if asked,70 label the whole set `test` at `low` confidence, and say the extension is a71 bet.72- Retargeting variant changes the promise, the proof or the angle sentence:73 `rewrite`. Stage changes emphasis and the reference to prior action, never74 the argument.75- The offer differs between stages: this is a second changed element under76 `test.one_change_rule` and the set stops being a stage test. Either hold one77 offer across the three, or run the offer change as its own test against a78 named control and say the stage question has been given up for this round.79 Decision `investigate` on which of the two questions the account actually80 wants answered.81- No stage reaches `test.volume_floor` on its own conversions inside82 `test.min_runtime`: the three cannot be compared on conversions at all. Read83 them on `test.click_floor`, state in the output that the answer is84 click-side only, and cap the whole set at `low` under the shared scale.85- Cost per acquisition between two stages differing by less than86 `money.relevance_floor`: no stage won. Report a tie and leave the budget87 where it is; a rate difference that does not move cost per acquisition is not88 a reason to shift spend between temperatures.89- Retargeting pool sitting under `delivery.ranking_floor` of the campaign's90 spend: it may have run, but its share is too thin to compare against the cold91 and warm stages. `monitor`, and say the comparison between stages is92 unavailable until the pool gets a comparable share of delivery. Where the pool93 is under `delivery.never_delivered_floor` as well, it did not run at all and94 the finding is allocation rather than the copy.95- Retargeting pool defined by page view alone with no stated action: label96 `investigate`, because the copy cannot reference something unknown.97- A stage points at a page missing the ad's main claim above the fold:98 `investigate` the page, and hold that stage's variant.99- Fewer than `coverage.angles_per_ad_set` live angles once these variants ship:100 say so, because a losing week will not be readable. Three stage variants of101 one argument are one angle under `coverage.angle_distinctness`, not three,102 and an account that counts them as three has just talked itself into a103 coverage pass it did not earn.104- Any line this skill produced that carries `[claim: needs source]` is105 `approval_needed`, whatever else its verdict says, and the marker is never106 stripped to make the set look finished. A marked line is not shippable copy:107 it waits for the named source, or it is rewritten without the claim.108109## Output format110111No verdict line. Three copy blocks, one per stage, each with its audience,112offer, evidence label and decision label. Then two lists side by side: what113changed between stages and what stayed identical. Then a one-line statement of114the strength of the original result in its own numbers. Then the four elements115held identical across the three stages, listed literally, so a reader can check116them rather than trust them. Then `What this could not see`, `Missing data`,117`Approval gates`.118119This skill writes copy rather than reading a test or a time series, so it issues120no `high` confidence label of its own. The confidence it does state is inherited121from the original result being extended, read on the shared scale in full, and it122never rises above what that result carried. Nothing about writing three variants123makes the evidence behind the angle stronger.124125## Practical example126127Illustrative and fictional. Advertiser "Halden". Angle: "you are paying twice128for the same lead". The cold ad is reported at 1.9% link CTR against a control129at 1.7%, over 9 days, 41 purchases across the ad set.130131Strength of the original result: 1.9% against 1.7% is about 12% relative,132inside `test.material_gap`, and 9 days is short of `test.min_runtime`. The angle133is not proven and the claim that it won is refused as a tie. Variants are still134written, all labelled `test` at `low` confidence, and the extension is a bet.135136Cold:137138> Two of your lead sources are selling you the same person. You are paying twice139> for the same lead. Halden matches inbound records across sources before they140> reach your CRM. Book an audit.141142Warm:143144> You know about the duplicates. Here is where they start: two sources, one145> person, two invoices. You are paying twice for the same lead. Halden matches146> inbound records across sources before they reach your CRM. Book an audit.147148Retargeting:149150> You opened the duplicate check and left it. Nothing has changed since. You are151> paying twice for the same lead. Halden matches inbound records across sources152> before they reach your CRM. Book an audit.153154Held identical: the angle sentence; the claim "You are paying twice for the same155lead" word for word; the single proof; the conversion action and its156destination. Changed: the opening line and the reference to prior action only.157One offer across all three, deliberately, so the account reads the stage rather158than a discount.159160Declined:161162- "You already know this works for teams like yours", in the retargeting draft.163 No case evidence was supplied, so it is not written. Its slot goes to the164 abandoned check, an observed action rather than a claim.165- "Cuts duplicate spend by a third" `[claim: needs source]`. This was the single166 proof, so all three ship without a proof line and the set is weaker for it.167 Any variant carrying it is `approval_needed` and none goes live with it.168169## Guardrails170171- Never call an angle proven on a result inside `test.material_gap`.172- Never let the promise or the proof drift between stages.173- Never reference a prior action the retargeting definition does not contain.174- Never invent a case study, a customer or a saving figure.175- Do not change audiences, budgets or ad status in the account.176- Report every line declined at every stage, with the reason.