planning-marketing-budget

Use when the user needs to derive a marketing budget from revenue targets, plan headcount for a 1-3 person team, decide what to build vs. buy vs. automate, or allocate spend across channels with ROI expectations. Use when budget is based on gut feel rather than revenue math, or resource allocation feels arbitrary.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "planning-marketing-budget" with this command: npx skills add amogha-dalvi/marketing_gtm/amogha-dalvi-marketing-gtm-planning-marketing-budget

Marketing Budget & Resource Allocation

Overview

At $1M-5M ARR you are resource-constrained by definition. This skill turns revenue targets into a precise resource plan -- how much to spend, where to spend it, who does the work, and what tools to buy. Every downstream execution skill draws its resource envelope from this one.

When to Use

  • Marketing budget is set by gut feel or arbitrary percentage rather than revenue-backward math
  • No clear headcount plan exists (unclear when to hire marketer #2 or #3)
  • Tool stack is growing without ROI justification or quarterly audits
  • Channel spend is spread too thin across 6+ channels with no clear winner
  • Founder time on marketing is untracked and unoptimized
  • Preparing for a new fiscal year, funding round, or growth target change
  • AI tools have changed the resource equation but team has not recalibrated

Don't use when: You have a validated revenue-backward budget model less than one quarter old with monthly review cadence already in place.

Quick Reference

PhaseDurationOutput
Revenue-backward budget modelDay 1Budget derived from revenue targets
Headcount planningDay 2Hiring roadmap with timing triggers
Build vs. buy vs. automateDay 3Decision matrix per marketing function
Tool & tech stack budgetingDay 4Tiered tool list with cost justification
Channel ROI estimation & phasingDay 5Channel allocation, quarterly sequencing
Monthly budget review processOngoingReview framework with decision rules

Core Deliverables

  • Revenue-Backward Budget Model -- Total budget from pipeline targets, allocated by category
  • Headcount Plan -- Hiring triggers, role profiles, outsource-vs-hire decisions
  • Build/Buy/Automate Matrix -- Strategic value x frequency x AI-automatable scoring
  • Tech Stack Budget -- Tier 1/2/3 tool selections with cost and alternatives
  • Channel ROI Model -- Spend, time-to-result, pipeline-per-dollar per channel
  • Monthly Review Template -- Agenda, decision rules, reallocation triggers

Common Mistakes

  • Allocating budget by gut feel instead of working backward from revenue targets
  • Spreading budget across 6+ channels (master 1-2 before adding a third)
  • Hiring ahead of playbook (prove it with freelancers and AI first)
  • Buying Tier 3 tools at $2M ARR when a spreadsheet works fine
  • Treating founder time as free without tracking opportunity cost
  • Locking into annual contracts before a channel is proven
  • Setting budget once a year without monthly reviews

Integration

Feeds into: running-content-engine, optimizing-geo-visibility, creating-sales-enablement, executing-launch-playbook, reducing-cac, accelerating-pipeline, managing-marketing-ops

Refresh: Full budget rebuild annually. Monthly review with channel ROI assessment. Headcount and tech stack audit quarterly. Build/buy/automate reassessment every 6 months.

See workflow.md for phase-by-phase execution, revenue math templates, headcount decision matrices, build/buy/automate scoring frameworks, tech stack tier guides, and channel ROI benchmarks.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

reducing-cac

No summary provided by upstream source.

Repository SourceNeeds Review
General

running-content-engine

No summary provided by upstream source.

Repository SourceNeeds Review
General

growing-nrr

No summary provided by upstream source.

Repository SourceNeeds Review
General

accelerating-pipeline

No summary provided by upstream source.

Repository SourceNeeds Review