Skip to content

rampstackco/claude-skills / skills/paid-media-strategy

paid-media-strategy

Verified

A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media strategy, ad budget allocation, channel selection, paid media plan, audit my Google Ads, audit my Meta Ads, scale paid media, kill underperforming campaign, paid media hypothesis, ad spend strategy, attribution reality, performance marketing strategy. Also triggers when a team is asking how to scale paid media, or whether to add a new channel, or how to reallocate spend across channels.

references/budget-allocation-templates.md

View on GitHub
# Budget allocation templates

Four split patterns plus pacing guidance. Pick the template closest to your situation and adapt.

The splits operate at the same time: brand vs performance, baseline vs test, primary vs secondary channel, daily vs lifetime.

---

## Template 1: Growth-mode allocation

For brands actively scaling with a working unit economic model.

| Bucket | Share | Notes |
|---|---|---|
| Prospecting | 70% | New audience reach. Largest share because growth comes from new demand. |
| Retargeting | 20% | Engaged-but-not-converted users. Small audience, high CTR, low CAC. |
| Test | 10% | Systematic tests of new audiences, channels, or creative concepts. |

Plus brand-vs-performance: 25% brand, 75% performance for B2C. 50-50 for B2B with longer cycles.

Plus channel: 60-70% to one primary channel that has proven its CAC, 25% to a secondary, 5-15% to scale-out experiments.

---

## Template 2: Steady-state allocation

For brands holding scale rather than aggressively pushing it.

| Bucket | Share | Notes |
|---|---|---|
| Prospecting | 50% | Lower share because steady-state needs less new demand. |
| Retargeting | 30% | Higher share because the existing pipeline is the main flow. |
| Test | 20% | Higher share than growth-mode; steady-state is when systematic testing pays off. |

Plus brand-vs-performance: 40% brand, 60% performance. The brand share is higher than growth-mode because steady-state is about defending position.

---

## Template 3: Brand-heavy allocation

For categories where brand investment compounds (premium consumer, B2B with long consideration, regulated industries).

| Bucket | Share | Notes |
|---|---|---|
| Brand | 60% | Awareness, reach, video at scale. Long-term demand pipeline. |
| Performance | 40% | Search and retargeting on the demand the brand creates. |

Within performance, 60% prospecting and 40% retargeting is typical. Test budget comes out of the brand share.

---

## Template 4: Performance-heavy allocation

For DTC and direct-response B2C where the unit economics are tight and brand effects are slow to compound.

| Bucket | Share | Notes |
|---|---|---|
| Brand | 20% | Minimum viable awareness investment. Mostly content and organic. |
| Performance | 80% | Direct-response paid; CAC is the binding metric. |

Within performance, growth-mode splits apply: 70% prospecting, 20% retargeting, 10% test.

---

## Pacing patterns

Budgets that run flat through the month miss the demand peaks and overspend during the troughs. Three pacing patterns to layer onto the daily template.

**Front-load testing weeks.** When launching a new creative concept or a new audience, front-load 60% of the test budget in the first 7 to 10 days. The platform learning phase needs concentrated signal; spreading too thin means slower convergence.

**Back-load seasonality.** For categories with a seasonal peak (holiday, end-of-quarter, category-specific moments), shift 30 to 50% of monthly budget into the peak two-week window. Flat budgets through Q4 leave money on the table.

**Front-load for launch.** For new campaigns with no historical data, front-load creative testing in week one. Accept lower efficiency in week one in exchange for picking the winning creative quickly. By week three the winning concept should be running at scale.

**Steady for evergreen.** For mature campaigns hitting consistent CAC at scale, run flat daily. The platform's learning is stable; introducing pacing variance creates noise that reduces optimization quality.

---

## Daily vs lifetime budgets

**Daily budget.** Use for ongoing campaigns where you want a stable spend floor. The platform charges up to your daily cap regardless of opportunity, which is what you want for predictable production work.

**Lifetime budget.** Use for finite tests where the platform should pace itself across a defined window. Lifetime budgets prevent runaway spend during testing; the platform optimizes pacing so the test ends on the planned date with the planned spend.

Mistakes. Using daily for tests (the test runs forever or stops abruptly when budget is paused). Using lifetime for evergreen campaigns (the platform front-loads or back-loads in ways you do not want).

---

## Channel split mistakes

The most common channel-budget mistake is the equal split. Spreading $100K across four channels at $25K each produces four underperforming campaigns; one campaign at $80K plus three at $7K each produces one strong learning signal and three quick reads on whether the others are worth scaling.

The principle. One channel does the heavy lifting (60 to 70% of budget). Others scale supplementally. Resist the temptation to be balanced. Balanced budgets across unproven channels is the most expensive way to learn nothing.

The exception. After two channels are proven independently, splitting toward equal is fine because each channel has its own efficient scale. Before that point, concentrate.

---

## Reallocation triggers

Three signals that the current split needs to shift.

1. **Primary channel CAC drifted up by 25% over two weeks.** The audience is saturating or competition increased. Shift some budget to the secondary channel and drop the primary's daily.
2. **Test budget produced a new winner.** A test channel or audience is hitting CAC equal to or better than baseline. Promote it to baseline at 15% of total budget; the previous baseline holds 55 to 60%.
3. **Frequency exceeded threshold across the prospecting audience.** The audience saw the creative more than the cap. Either rotate creative or expand the audience; if both are constrained, pull back budget.

Reallocation cadence: monthly review minimum. Weekly during high-spend periods or active scale-up.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall