Money & Business May 18, 2026

Fest Marketing Spend Cap Worksheet - What Micro-Studios Can Afford Before October 2026 Next Fest

2026 fest marketing spend cap worksheet for micro-studios—runway months, category caps, wishlist targets, and stop rules before October 2026 Next Fest.

By GamineAI Team

Fest Marketing Spend Cap Worksheet - What Micro-Studios Can Afford Before October 2026 Next Fest

You have four months of runway and a $8,000 trailer quote. October 2026 Next Fest is not a lottery ticket—it is a cash event with store art, demo stability, and optional paid amplification stacked on top of survival burn.

This Money & Business worksheet caps fest marketing spend (paid and quasi-paid) against cash months remaining, evidence and cert costs you already committed, and a wishlist target you can defend to yourself—not to imaginary investor slides.

Pair with regional pricing second pass, UTM source tagging, and store icon readability—money and discovery fail together when only one side is disciplined.

Who this is for and what you get

Audience You will be able to…
Solo dev paying rent from savings Set a hard fest cap without guilt-spending
Two-person team with part-time contractor Separate must-ship from nice trailer line items
Lead answering publisher questions Show a one-page cap tied to runway, not vibes

Time: ~90 minutes first worksheet; 20 minutes monthly refresh until fest freeze.
Prerequisites: Rough monthly burn (salary + tools + contractors), bank balance or advance schedule, Steam page live or dated.

Why this matters now (May 2026)

  1. Q3 2026 compressionPartner intake windows steal evenings; marketing spend competes with evidence labor, not just art.
  2. Fest quote season — Editors and motion studios book October slots in May–June; unsigned quotes become sunk cost pressure.
  3. Post-evidence-stack clarity — Teams that adopted BUILD_RECEIPT discipline now see ops cost; marketing must fit the same honesty.
  4. Global pricing realityRegional pricing fixes conversion; blasting ads at a broken price sheet burns cap faster.
  5. Publisher diligenceQ3 diligence packets ask how fest spend maps to measurable wishlist goals.

Direct answer: Fill fest-spend-cap-2026.md with runway months, category caps, and stop rules before you sign any fest-adjacent invoice.

Definitions (what counts as fest marketing spend)

Counts toward cap Usually excluded (track separately)
Paid social / search Core salary and rent
Trailer and motion contractors Engine and middleware subscriptions you need anyway
Influencer keys + paid posts Cert evidence labor (partner packets)
Store art contractors beyond internal time PC build hardware you already owned
Fest booth fees if applicable Savings you refuse to touch (emergency only)
PR wire or list services Legal/accounting retainers

Quasi-paid: Your time has opportunity cost, but this worksheet tracks cash out the door so caps stay auditable.

Step 1 — Runway floor (non-negotiable)

cash_on_hand_usd =
monthly_burn_usd =   # rent + food + tools + contractors + tax set-aside
runway_months = cash_on_hand / monthly_burn
Runway months Fest marketing cap rule (default)
< 3 $0 paid marketing; organic + owned channels only
3–5 5% of cash on hand OR one line item ≤ $500, whichever is lower
6–9 10% of cash on hand, max $3,000 without written exception
10+ 15% of cash on hand, still require wishlist math below

Emergency rule: If runway drops below 3 months after signing a quote, trigger stop rule (Step 5)—cancel or defer non-refundable work only if contract allows; never hide runway shrink from co-founders.

Document in fest-spend-cap-2026.md with date stamp.

Step 2 — Evidence and ops reservation (subtract first)

Fest marketing competes with shipping costs. Reserve these before marketing cap:

Line Typical micro-studio range Notes
Notarization / platform fees $0–$400 Mac builds if applicable
Contractor QA week $0–$2,500 Fest demo stability
Store art pass (internal time valued $0 cash) $0–$1,500 If outsourcing icon fixes
Legal review (AI disclosure, privacy) $0–$1,200 Pairs with AI disclosure challenge
Travel to event (if any) $0–$3,000 Often zero for digital-only

Reserved_subtotal subtracts from cash available for marketing:

marketing_pool = cash_on_hand - (monthly_burn * 2) - reserved_subtotal

The two-month burn hold is survival buffer—not negotiable on first worksheet pass.

Step 3 — Wishlist target and implied cost ceiling

Avoid fantasy CAC. Use bands:

Fest outcome tier Wishlist adds (8 weeks) Notes
Survival +500 Validates store page not broken
Solid +2,000 Supports two-storefront maintenance
Stretch +8,000 Requires content + traffic; rarely bought with ads alone

Implied spend sanity check:

max_cost_per_wishlist = marketing_pool / target_adds

If max_cost_per_wishlist < $0.50, paid social rarely helps indies at small budgets—fix truth audit and vertical slice demo first.

If > $2.00 and runway ≥ 6 months, small tests may be rational—still cap total.

Step 4 — Category caps (fill the worksheet)

Allocate marketing_pool across categories; total must not exceed pool.

Category Suggested max % of pool Stop if…
Trailer / motion 40% Storyboard not approved by producer
Paid social tests 25% 14 days no wishlist lift vs organic baseline
Influencer / keys 15% No tracked UTM or Steam tag
Store art contractors 10% Palette + icon gates not green
PR / lists 10% No pickup after one cycle
Contingency 10% Hold until week 6 pre-fest

Example (illustrative numbers only):

  • marketing_pool = $4,000
  • Trailer cap = $1,600
  • Paid social cap = $1,000 (four $250 two-week tests)
  • Influencer = $600
  • Store art = $400
  • PR = $400
  • Contingency = $400

Rename categories in your sheet; percents are guardrails, not law.

Step 5 — Stop rules (write before spending)

Trigger Action
Runway < 3 months Pause all paid; organic only
Wishlist 14-day rolling below 50% of plan Freeze paid social; audit store page
Single invoice > 25% of pool without contingency Producer + finance sign-off
Demo crash rate > 2% during fest spike Redirect cap to stability (crash-log challenge)
Publisher asks for unbudgeted co-marketing Trade scope, not silent overrun

Paste stop rules at top of fest-spend-cap-2026.md so they are visible when tired.

Worked scenarios (composite patterns, not named studios)

Use these as sanity anchors—your numbers will differ.

Scenario A — Solo dev, $18k cash, $3.5k burn

Field Value
Runway ~5.1 months
Default cap rule ≤10% cash, max $3k → $1,800 pool before reserves
After 2-month hold + $800 evidence $1,000 marketing_pool
Wishlist tier Survival (+500)
Implied max $/wishlist $2.00 (borderline—organic first)
Trailer cap (40%) $400 (storyboard + capture, not cinematic)

Decision: No paid social until icon gate passes and organic week baseline logged.

Scenario B — Duo, $45k cash, $7k burn

Field Value
Runway ~6.4 months
marketing_pool (after holds + $2k evidence) ~$4,500
Wishlist tier Solid (+2,000)
Implied max $/wishlist $2.25
Paid social Two $300 tests, 14 days each, separate UTMs

Decision: Trailer at $1,800 with locked shot list; contingency untouched until August.

Scenario C — Publisher advance tranche, $12k cash + $30k milestone due post-fest

Field Value
Treat advance Only cleared cash counts until milestone terms met
marketing_pool Compute on $12k unless contract guarantees pre-fest draw
Attach cap sheet To milestone evidence export

Decision: Publisher "marketing expectation" slides must map line-by-line to category caps—uncategorized asks become scope negotiation, not silent debt.

Paid social micro-test design (when pool allows)

Never launch one $2,000 campaign. Run sequential micro-tests:

Week Spend Hypothesis Success signal
1 $0 Organic baseline Wishlists/day in spreadsheet
2 $250 Creative A + landing = store page +20% vs baseline 7-day avg
4 $250 Creative B (hook change) Beat A or stop
6 $250 Region cluster only if pricing pass fixed Lower CPA in target country

Fail fast: If week 2 does not beat baseline, freeze paid through fest—redirect remainder to demo stability or icon/screenshot fixes.

Log in fest-spend-cap-2026.md with Steam tag or UTM per source tagging experiment.

Trailer scope negotiation (inside cap)

When trailer quotes exceed 40% of pool, negotiate deliverables—not just price:

Tier Deliverable Fits small pool when…
A 30–45s key beats, in-engine capture Pool under $1,500
B + titles, SFX, one revision Pool $1,500–$3,000
C Full cinematic, VO, multiple revisions Pool over $3,000 and runway ≥ 9 months

Require storyboard sign-off before animation. Pair with capsule discipline—trailer hook must match first screenshot, not a different game.

May–October cash timeline (planning view)

Month Finance focus Marketing action
May 2026 Fill cap worksheet; reserve evidence Defer signatures
June Lock category caps; organic baseline Trailer tier A/B scope
July First micro-test if pool allows UTMs live
August Freeze major new contracts Contingency hold
September Fest freeze on pricing Spend contingency only on proof fixes
October Measure wishlists/day; no hero spends Vertical slice execution

Template — fest-spend-cap-2026.md

Copy into release-evidence/05-operations/finance/:

# Fest marketing spend cap — October 2026 Next Fest
Updated: YYYY-MM-DD

## Runway
- cash_on_hand_usd:
- monthly_burn_usd:
- runway_months:
- marketing_pool:

## Reserves (subtracted first)
- two_month_burn_hold:
- evidence_reserved:
- notes:

## Wishlist plan
- tier: Survival | Solid | Stretch
- target_adds_8wk:
- max_cost_per_wishlist:

## Category caps
| category | cap_usd | spent_usd | stop_rule |
|----------|---------|-----------|-----------|
| trailer | | | |
| paid_social | | | |
| influencer | | | |
| store_art | | | |
| pr | | | |
| contingency | | | |

## Stop rules (active)
1.
2.

## Monthly log
| month | pool | spent | wishlist_adds | notes |
|-------|------|-------|---------------|-------|

Co-founder tabletop (45 minutes)

Time Activity
0–10 Read runway aloud; agree cap rule row
10–20 Debate wishlist tier—pick one
20–30 Assign category owners
30–40 Write two stop rules verbatim
40–45 Sign PDF export or commit markdown to repo

No trailer vendor calls until tabletop output exists—prevents emotional signing.

When marketing cap should stay zero

  • Runway under three months without signed bridge funding
  • Demo crash rate unresolved (crash-log challenge not green)
  • Store truth audit failed
  • Partner evidence queue red within 14 days of fest
  • Team unanimous "ship demo" week—marketing pause is feature work

Zero cap is a strategy, not shame.

Step 6 — Monthly refresh ritual (20 minutes)

First Monday each month May–September 2026:

  1. Update cash_on_hand and monthly_burn.
  2. Recompute runway_months and marketing_pool.
  3. Log actual spend vs cap per category.
  4. Compare wishlist adds to UTM experiment notes.
  5. Adjust next month caps—never retroactively justify overruns.

Drop summary into Friday Block 5 ops folder if you already run release evidence rituals.

Beginner quick start (30 minutes)

  1. Open notes app; write cash on hand and monthly burn (round up).
  2. If runway < 6 months, set marketing_pool to zero until Step 2 reserves are funded.
  3. Pick one wishlist tier (Survival / Solid / Stretch).
  4. Write one stop rule you will actually obey.
  5. Delay trailer quotes until cap row exists.

Success check: you can state your fest cap aloud in one sentence without checking Slack.

Pairing with funding and publisher milestones

Document How this worksheet connects
Funding landscape Layer grants and advances before marketing pool
Milestone payment checklists Attach cap sheet to milestone evidence exports
DLC price anchor Revenue assumptions feed runway, not the reverse

If a publisher advance assumes $50k marketing, map their number to categories here—uncategorized "marketing" is where teams go insolvent.

Common mistakes (seven)

  1. Trailer first, cap second — Signature before runway math.
  2. Counting wishlists without UTMs — Cannot learn; cannot stop.
  3. Ignoring evidence reservation — Marketing spends; demo ships broken.
  4. One giant Facebook test — No iteration budget left.
  5. Borrowing from tax set-aside — Runway illusion.
  6. Fest week price changes — Conflicts with regional pricing freeze.
  7. Comparing to AAA launch budgets — Different game; different cap.

Pro tips (six)

  1. Prepay vs milestone contractors — Match milestone checklists cadence.
  2. Trailer tiering — Storyboard-only pass within cap before full motion.
  3. Organic baseline week — Log wishlists with zero spend before paid tests.
  4. Cap public Discord boosts — Community spend is still cash.
  5. Align with evidence cycles — Marketing week alternates with validator week on thin teams.
  6. Save worksheet in release-evidence/05-operations/finance/ beside pricing passes.

Snippet-friendly answers

How much should a micro-studio spend on October 2026 Next Fest marketing?
Default: no more than 5–15% of cash on hand depending on runway months, after reserving two months burn and evidence costs—often $0–$4,000 total paid.

What if the trailer is "essential"?
Essential is not unlimited; cap trailer at 40% of marketing_pool or defer scope until pool grows.

Do Steam ads guarantee wishlists?
No; fix store truth and demo stability before raising paid caps.

Key takeaways

  • Fest marketing spend is cash out the door, not hours hoped away.
  • Compute runway months first; under three months means $0 paid by default.
  • Subtract two months burn and evidence reserves before marketing_pool.
  • Tie spend to a wishlist tier and implied cost-per-add sanity band.
  • Use category caps (trailer, paid social, influencers, art, PR, contingency).
  • Write stop rules before signing quotes—not after overrun.
  • Refresh monthly; pair with UTM discipline and regional pricing.
  • Store art and demo quality are conversion levers—cheaper than ads when broken.
  • Publisher advances need this worksheet mapped to their numbers, not vibes.
  • October 2026 Next Fest is a business event—cap it like one.
  • Monthly refresh beats a heroic one-time budget panic in September.

Grants, platform funds, and marketing pool

Platform grants and regional arts funds often label money "marketing." Treat grant lines as restricted buckets:

Source Worksheet treatment
Unrestricted revenue Counts in cash_on_hand
Marketing-only grant Separate sub-pool; cannot steal from payroll
Recoupable advance Map to milestone checklist dates

If grant terms require matching spend, compute match as part of category cap—not "free money" on top of an imaginary pool. Document grant ID beside each invoice in monthly log.

See funding landscape for how grants stack with advances—this worksheet is the spend governor, not the fundraising guide.

Tax and bookkeeping notes (not advice)

  • Export bank CSV monthly into finance/fest-2026/
  • Tag invoices with category column matching worksheet
  • Separate contractor vs software vs ads for year-end reporting
  • Keys and gifted assets may have imputed value—ask your accountant once, not fest week

The goal is audit trail, not perfect GAAP on day one.

Linking caps to operating reviews

Teams running four-Friday operating reviews add one row:

Block Question
Finance (5 min) Are we inside fest cap this month?
Marketing (5 min) Which UTM won last micro-test?
Ship (5 min) Does demo stability justify next spend?

If finance block is skipped three weeks, caps drift—calendar the tabletop.

FAQ

Is organic-only a failure mode?
No. Many micro-studios with runway under six months should run organic + owned channels only; cap worksheet enforces that.

Where do Steam keys for influencers fit?
Keys are not cash until you value them for tax or opportunity; track under influencer cap with UTM tags, not "free."

Should we include console cert costs in marketing_pool?
No—cert is reserved_subtotal (Step 2), not marketing.

What about Kickstarter marketing spend?
Different lifecycle; if KS funds fest, re-run worksheet with KS net after fees as cash_on_hand and stricter contingency.

We already signed an oversized trailer contract—now what?
Document overrun against stop rules; cut other categories to zero; accelerate wishlist measurement; do not hide runway shrink. Renegotiate deliverables (shorter cut) before asking for more funding.

Can we increase cap if wishlists spike organically?
Yes—only by recomputing runway after the spike, not by borrowing from payroll. Organic success means you may reallocate contingency, not abandon the worksheet.

How does this interact with publisher diligence?
Attach the cap sheet to diligence exports so partners see spend discipline alongside demo evidence—reduces "spray and pray" concerns.

Conclusion

October 2026 Next Fest rewards teams that ship a readable store page and stable demo—not the team that burned runway on a trailer no one watched.

Fill the cap worksheet in May while quotes are still negotiable. When September pressure arrives, you will spend from a plan—not from panic.

Save fest-spend-cap-2026.md next to your pricing and UTM notes. Your future self during fest week will not have time to invent finance discipline from scratch.

If a vendor pressures you to "lock October slot today," send the cap sheet—not excuses. Professionals respect teams that know their number. Revisit the worksheet after every major invoice; fest discipline is a monthly habit, not a one-time spreadsheet. Print the stop rules and tape them beside your monitor for fest season.