← All skills
  • Marketing
  • v1.0.0
  • influencers

Forecast pipeline from creator spend

Use this skill when creator budget needs a defensible forecast — "what will €10K of creator spend produce," "build the pipeline model for the creator channel," "what ARR can we commit to from this program." A five-input model (budget, cost per qualified click, click→opportunity rate, win rate, ACV) with a worked example and the sensitivity insight that decides where tuning effort goes.

SKILL.md

Use when the creator channel needs a forward number leadership can hold you to. Produces a pipeline forecast from five inputs — all observable, none hand-waved.

The five inputs

  1. budget (B) — the quarter's spend
  2. cost per qualified click (C) — from your own campaign history; network baseline ~€2.30–2.40
  3. click → opportunity rate (O) — planning band 3–6% for a well-defined ICP audience
  4. opportunity → close rate (W) — your actual sales win rate, from the CRM
  5. ACV — real average contract value, from the CRM

Qualified click means tracked AND ≥30 seconds on-site — the behavioral definition is what makes the whole model honest.

The model

qualified clicks = B ÷ C → opportunities = clicks × O → deals = opportunities × W → new ARR = deals × ACV → return = ARR ÷ B

Worked example at €10,000: 4,167 clicks → 167 opportunities (4%) → 33 deals (20% win) → €200K ARR at €6K ACV → 20× gross return. Run the conservative case too: at 3% and 15% the same budget returns €67.5K (6.75×). Present both — the range is the forecast.

Where the leverage is

The opportunity rate dominates. Doubling it from 3% to 6% doubles pipeline; a ±30% swing in effective CPC moves the model by roughly a third. So tuning effort goes to audience-ICP fit and post quality (what moves O) before rate negotiations (what moves C). Sanity-check the downstream half against reality: click→SQL composites run ~3.4% in network data — a model implying far more should be challenged.

What good looks like

A great forecast shows the formula, sources every input (own history where it exists, network baselines labeled as baselines where it doesn't), and presents a base and conservative case. A mediocre one multiplies best-case everything into a single big number. The overlooked failure: forecasting from CPL with a mushy lead definition — qualified-click-based models survive CFO scrutiny because the unit is behavioral, not declared.

MUST source W and ACV from the actual CRM, never from aspiration. MUST present a conservative case alongside the base. NEVER present a single-point forecast.

Files

1 file ship with this skill. They are installed beside the SKILL.md.

NOTICE1.4 KB
Forecast pipeline from creator spend
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/thomas-marcelle/forecast-creator-pipeline
at https://github.com/swan-gtm/gtm-skills/commit/5d786aad0c7b2ca59b1abf1f601f9407ca261996. Written by Thomas Marcelle (https://linkedin.com/in/thomas-marcelle).
The skill is shared under the MIT License below; this notice must stay with any copy.

MIT License

Copyright (c) 2026 Swan

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.