AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Budget Recommendation Calculator

skill-fourteenwm-ppc-ai-skills-budget-recommendation-calculator · by fourteenwm

Calculates conservative budget recommendations for Google Ads accounts based on pacing variance, impression share analysis, and performance constraints. Auto-invoke when creating budget recommendations, investigating underspending, or determining optimal budget increases. Enforces 5-10% increase limits and performance safeguards.

No reviews yet
0 installs
30 views
0.0% view→install

Install

$ agentstack add skill-fourteenwm-ppc-ai-skills-budget-recommendation-calculator

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fourteenwm-ppc-ai-skills-budget-recommendation-calculator)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Budget Recommendation Calculator? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Budget Recommendation Calculator Skill

Purpose: Provides standardized methodology for calculating conservative, data-driven budget recommendations that balance pacing targets with performance goals.

Type: Domain knowledge skill (auto-invoked)


Core Principles

Budget Philosophy

  1. Primary Goal: Hit monthly spend targets (pacing within tolerance)
  2. Secondary Goal: Maintain acceptable CPA/ROAS performance
  3. Conservative Approach: 5-10% increases (not aggressive jumps)
  4. Algorithm Safety: Avoid shocking smart bidding algorithms
  5. Performance Guardrails: Never increase if performance is failing

Why Conservative Increases?

  • Smart bidding needs time to adapt (3-7 day ramp-up period)
  • Large budget jumps risk CPA spikes (algorithm overspends during adjustment)
  • Multiple small increases > one large increase (safer, more controllable)
  • Client trust: Predictable, controlled spend changes

Budget Recommendation Decision Tree

Decision Point 1: Should We Increase Budget?

✅ YES - Increase Budget if ALL of the following are true:
  1. Pacing Variance Check:
  • Standard tolerance portfolios: Underspending beyond ±8% monthly tolerance
  • Tight tolerance portfolios: Underspending beyond ±5% monthly tolerance
  • At least 5 days into the month (exclude early-month variance)
  1. Performance Check:
  • CPA is acceptable (within goal or 80% of target)
  • No major quality issues flagged
  1. Impression Share Check:
  • Budget Lost IS >10% (spend potential exists)
  • OR Rank Lost IS >50% + any Budget Lost IS (competitive pressure + budget constraint)
  1. Recent Changes Check:
  • NO budget increase in last 7 days (avoid ramp-up period)
  • NO recent campaign launches in last 7 days
  • NO major targeting changes in last 7 days
❌ NO - Do NOT Increase Budget if ANY of the following are true:
  1. Performance Failure:
  • CPA >20% over goal (need quality fixes first)
  • ROAS 20% week-over-week
  1. Recent Changes:
  • Budget increased within last 7 days (still ramping)
  • New campaigns launched within last 7 days
  • Major targeting/bidding changes within last 7 days
  1. Low Demand:
  • Search IS >80% AND Budget Lost IS 20% variance, performance concerns)
  • 0.5: Standard conservative (use for 10-20% variance)
  • 0.6-0.7: Moderate (use for 5-10% variance, strong performance)
  • 0.8-1.0: Aggressive (use for 30%) and you want to estimate full spend potential

Formula:

Estimated Full Spend Potential = Current Spend ÷ (1 - Budget Lost IS)

Example:

Current MTD Spend: $500
Budget Lost IS: 40% (0.40)

Estimated Full Spend Potential = $500 ÷ (1 - 0.40)
                                = $500 ÷ 0.60
                                = $833 (for current MTD period)

If we're 50% through month:
Projected Monthly Spend Potential = $833 × 2 = $1,666

Current Monthly Budget: $1,000
Spend Potential: $1,666

Gap: $666 (66% increase needed)

APPLY 10% CAP:
Recommended: $1,100 (10% increase)
Note: "Significant untapped spend potential - will require multiple increases"

Use Case: This method is good for understanding total opportunity, but ALWAYS apply 5-10% cap to actual recommendation.


Method 3: Daily Budget Calculation (Tactical)

When to use: When you need to translate monthly budget to daily budget for Google Ads implementation

Formula:

Daily Budget = Monthly Budget ÷ Days in Month

Example: October (31 days)

Recommended Monthly Budget: $1,100
Days in October: 31

Daily Budget = $1,100 ÷ 31 = $35.48/day

Rounded: $35.50/day (Google Ads allows 2 decimal places)

Example: February (28 days)

Recommended Monthly Budget: $1,400
Days in February: 28

Daily Budget = $1,400 ÷ 28 = $50.00/day

IMPORTANT: Google Ads can spend up to 2x daily budget on any single day, but will not exceed monthly total (daily budget × days in month).


Budget Recommendation Output Format

Standard Recommendation Template

================================================================================
BUDGET RECOMMENDATION
================================================================================

CURRENT STATE:
- Current Monthly Budget: $X,XXX
- Current Daily Budget: $XX.XX/day
- MTD Spend (through Day XX): $X,XXX
- Pacing Variance: +X.X% (UNDERSPENDING by X.X%)
- % Through Month: XX.X%
- % Spent: XX.X%

PERFORMANCE CHECK:
- Cost per Conversion: $XX.XX (Goal: $XX.XX) ✅ WITHIN GOAL
- [or ROAS: X.Xx (Goal: X.Xx) ✅ WITHIN GOAL]
- Performance allows for budget increase

IMPRESSION SHARE ANALYSIS:
- Search Impression Share: XX%
- Budget Lost IS: XX% (spend potential exists)
- Rank Lost IS: XX% (competitive pressure)
- Diagnosis: Budget constraint is primary limiter

RECOMMENDATION:
✅ Increase Monthly Budget: $X,XXX → $X,XXX (+X.X%)
✅ New Daily Budget: $XX.XX/day

Rationale:
- Pacing variance (+X.X%) exceeds ±8% tolerance
- Budget Lost IS (XX%) indicates spend potential
- CPA performance acceptable (within goal)
- Conservative X.X% increase to move toward pacing target

Expected Outcome:
- Reduce pacing variance from +X.X% to ~+X.X% (closer to ±8% range)
- Maintain acceptable CPA performance
- Algorithm will ramp up over 3-5 days

Next Steps:
1. Implement budget increase in Google Ads
2. Monitor daily for 5-7 days during ramp-up period
3. Re-evaluate pacing after ramp-up period
4. Consider additional increase if still underspending after 7 days

Confidence Level: High
================================================================================

Alternative: Do NOT Increase Budget Template

================================================================================
BUDGET RECOMMENDATION
================================================================================

CURRENT STATE:
- Current Monthly Budget: $X,XXX
- MTD Spend (through Day XX): $X,XXX
- Pacing Variance: +X.X% (UNDERSPENDING by X.X%)

PERFORMANCE CHECK:
- Cost per Conversion: $XX.XX (Goal: $XX.XX) ❌ OVER GOAL (+XX%)
- [or ROAS: X.Xx (Goal: X.Xx) ❌ BELOW GOAL]
- Performance does NOT allow for budget increase

RECOMMENDATION:
❌ Do NOT Increase Budget

Rationale:
- CPA is XX% over goal (quality issues present)
- Increasing budget would worsen CPA (more spend on inefficient traffic)
- Need quality improvements first (ad relevance, landing page, keywords)

Alternative Actions:
1. Improve ad relevance (align ad copy with keywords)
2. Optimize landing pages (speed, mobile experience, relevance)
3. Refine keyword quality (pause low-performing keywords)
4. Re-evaluate budget after quality improvements stabilize

Expected Timeline:
- Quality improvements: 2-3 weeks to stabilize
- Re-evaluate budget after CPA returns to goal range
- Budget increase only if CPA acceptable AND still underspending

Confidence Level: High
================================================================================

Special Cases & Edge Cases

Case 1: Ramp-Up Period (Recent Budget Increase)

Pattern:

  • Budget increased within last 7 days
  • Currently underspending vs. new budget
  • Impression share metrics not stabilized

Recommendation:

❌ Do NOT Increase Budget (ramp-up period)

Rationale:
- Budget increased X days ago (recent change)
- Smart bidding algorithm needs 3-7 days to adjust
- Current underspending is expected during ramp-up

Action: Monitor for 3-5 more days
Timeline: Re-evaluate on [Date] (7 days after increase)

Case 2: Low Demand (High Search IS, Low Budget Lost IS)

Pattern:

  • Search IS >80%
  • Budget Lost IS 80% of shared budget)
  • Other campaigns starved (15%)
  • Need to catch up quickly

Recommendation:

⚠️ End-of-Month Catch-Up (aggressive but necessary)

Current Pacing: +XX% underspending
Days Remaining: X days

Option 1: Conservative Approach
- Increase budget +5-10% (standard)
- Accept that we won't fully catch up this month
- Focus on preventing next month's underspending

Option 2: Aggressive Catch-Up (if performance allows)
- Calculate daily deficit: $(Monthly Budget - MTD Spend) ÷ Days Remaining
- Temporary daily budget increase
- Return to normal after month-end

Recommended: Option 1 (conservative)
- Avoid algorithm shock from large temporary increase
- Better to start next month correctly than force current month

Integration with Other Skills

Prerequisite Skills:

  1. impression-share-diagnostics — Determines if budget is the constraint
  2. A pacing data source — Google Sheet, spreadsheet, or direct API query for MTD spend vs. target

Workflow:

1. impression-share-diagnostics → Diagnoses root cause (budget constraint?)
2. Check pacing variance against your portfolio's tolerance
3. THIS SKILL → Calculates budget recommendation (how much to increase?)
4. Verify current budget data before writing changes

Quality Checks Before Recommending

Pre-Flight Checklist:

✅ Pacing variance exceeds your portfolio's tolerance (typically ±5% to ±10%) ✅ At least 5 days into month (not early-month variance) ✅ CPA within goal or 10% OR Rank Lost IS >50% (constraint exists) ✅ No budget increase in last 7 days (not in ramp-up) ✅ Increase is 5-10% (conservative range) ✅ Daily budget calculation is correct (monthly ÷ days in month)

If ANY check fails:

  • Do NOT recommend budget increase
  • Explain which check failed and why
  • Provide alternative recommendation

Related Skills in This Repo

  • [impression-share-diagnostics](../impression-share-diagnostics/) — Root cause diagnosis before recommendation
  • [mutation-safety](../mutation-safety/) — Two-step approval protocol for writing budget changes to live accounts
  • [gaql-query-patterns](../gaql-query-patterns/) — GAQL templates for pulling budget and spend data

Built by Kurt Henninger. More free skills: github.com/fourteenwm/ppc-ai-skills

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.