Contractor vs Hire Cost Worksheet for Fest Marketing Week - Micro-Studios 2026

Your producer wants a community manager for October Next Fest week. HR math says a part-time hire at $22/hour is cheaper than a $450/day contractor. Then you add payroll tax, onboarding, tool seats, and the fact that fest week needs five days of live posting, not a twelve-week ramp—and the contractor line wins while the spreadsheet still says hire.

May–October 2026 layoff-wave micro-studios staff fest windows with contractors (trailers, social, QA, PR) because full-time headcount feels risky. Without a contractor vs hire worksheet, teams either over-hire into runway cliffs or under-staff fest week and burn founders on Discord at 2 a.m.

This Money & Business worksheet compares fully burdened hire cost vs scoped contractor cost for fest marketing week roles—paired with fest marketing spend cap, not dual-SKU economics or store-metadata checklists.

Non-repetition note: The spend cap worksheet sets how much cash you can spend; this worksheet decides contractor vs employee for fest-week labor inside that cap.

Pair with regional pricing second pass and Q3 partner intake compression—contractor quotes often arrive the same week as diligence asks, and both compete for founder attention.

Why this matters now (May–October 2026)

1. Layoff-wave staffing — Teams replace departed marketing hires with contractors for fest sprints without redoing math.
2. Quote season — Trailer and motion studios price May–June slots; social contractors book October weeks now.
3. Runway honesty — Fest cap fails if hire burden hides in "salary" rows while contractors hit marketing cap.
4. Publisher diligence — Q3 diligence asks who owns fest comms; worksheet shows decision, not vibes.
5. Founder burnout cost — Unscoped "we'll do social ourselves" is a hidden hire of founder hours—worksheet forces explicit rows.

Direct answer: For each fest-week role, fill hire burden column, contractor column, and decision row in contractor-vs-hire-fest-2026.md; file contractor_vs_hire_receipt_v1.json before signing contracts.

Who this is for and what you get

Time: ~75 minutes first worksheet; 15 minutes per new role.
Prerequisites: Fest spend cap draft, rough role list, local burden assumptions documented honestly.

Fest marketing week roles (scope first)

Rule: Compare hire vs contractor per role, not studio-wide. One role may hire; another may contract.

Definitions

This worksheet tracks cash; founder substitute is optional sanity check, not payroll.

Step 1 — Hire burden formula (working dev)

base_hourly_usd =
hours_per_week =
weeks_needed_including_ramp =   # include 2–4 weeks ramp if new hire
gross_wage = base_hourly * hours_per_week * weeks_needed

burden_multiplier = 1.15 to 1.35   # region-dependent; document yours
benefits_usd =                     # health, etc., if applicable
tool_seats_usd =                   # Discord mods tools, schedulers, Adobe
onboarding_hours * founder_shadow_rate =

fully_burdened_hire_usd = (gross_wage * burden_multiplier) + benefits_usd + tool_seats_usd + onboarding_usd

Beginner mistake: Comparing $22/hr hire to $450/day contractor without multiplying hours or burden.

Example hire row (community, part-time)

Step 2 — Contractor formula

contractor_day_rate_usd =
days_in_sow =
platform_fee_pct = 0–20%   # marketplace or agency
travel_usd = 0
revision_rounds_included = 2

contractor_total = (day_rate * days) * (1 + platform_fee) + travel

Example contractor row (same community role)

In this example hire wins on cash if you truly need six weeks part-time—but contractor wins if you need only fest week intensity without ramp risk.

Step 3 — Decision matrix (per role)

Winner rule: Lowest cash that meets SOW quality bar—not lowest hourly rate on paper.

Step 4 — Pair with fest marketing cap

From fest spend cap:

marketing_pool_usd =   # after runway hold and evidence reserve
contractor_subtotal = sum(contractor rows chosen)
remaining_cap = marketing_pool - contractor_subtotal

If contractor choices exceed cap, do not silently move costs to "hire" without burden math—re-scope SOW days.

Step 5 — contractor_vs_hire_receipt_v1.json

{
  "schema": "contractor_vs_hire_receipt_v1",
  "fest_window": "2026-10-next-fest",
  "marketing_pool_usd": 3200,
  "roles": [
    {
      "role": "community_social",
      "decision": "contractor",
      "hire_burden_usd": 2496,
      "contractor_usd": 3150,
      "rationale": "only 7 intensive days; no 6-week ramp"
    },
    {
      "role": "trailer_edit",
      "decision": "contractor",
      "hire_burden_usd": null,
      "contractor_usd": 4800,
      "rationale": "specialist SOW"
    }
  ],
  "total_contractor_usd": 7950,
  "cap_compliant": false,
  "action": "defer PR row; reduce trailer days"
}

Pass: cap_compliant: true OR written exception with runway months ≥ 6 documented.

Beginner path — 75-minute worksheet

1. 10 min — Copy template contractor-vs-hire-fest-2026.md.
2. 15 min — List fest-week roles only.
3. 20 min — Fill hire burden for roles where hire is plausible.
4. 20 min — Collect contractor quotes or market day rates.
5. 10 min — Decision matrix + receipt JSON.

Success check: You can explain why community is contractor but QA is hire—or vice versa—in one sentence each.

When hire beats contractor

When contractor beats hire

Hidden costs table

Founder substitute row (optional)

founder_hours_fest_week =
shadow_rate_usd = 0   # cash worksheet uses 0; note hours in doc
founder_opportunity_cost = hours * shadow_rate

If founder substitute > contractor quote, pay contractor—founder hours belong on BUILD_RECEIPT engineering rows, not invisible marketing.

SOW clauses that protect micro-studios

Snippet-friendly answers

Is a $450/day contractor expensive?
Compare total SOW to fully burdened hire for the same calendar window—not hourly sticker price.

Can I hire for fest week only?
Legally varies by region—worksheet is economic comparison; consult payroll rules locally.

Does this replace fest marketing cap?
No—cap first, then contractor vs hire inside cap.

Common mistakes (seven)

1. Ignoring ramp weeks on hire side.
2. Ignoring platform fees on contractor side.
3. Founder hours unpriced as "free."
4. Trailer quote outside cap without deferral plan.
5. One decision for all roles.
6. No receipt before signing.
7. Confusing with dual-SKU revenue math.

Pro tips (six)

1. Get two quotes per contractor role.
2. Book trailer in May–June for October—worksheet includes deposit timing.
3. Pair with UTM experiment so contractor posts are measurable.
4. Log decisions in BUILD_RECEIPT row.
5. Re-run if runway drops below cap stop rules.
6. Defer PR before deferring QA if demo stability weak—Wednesday smoke first.

Gates M1–M5 (publish discipline)

Treat these as binary before you sign fest-week contracts.

Working dev check: grep your evidence folder for contractor_vs_hire_receipt_v1 and confirm cap_compliant matches fest cap stop rules.

Spreadsheet skeleton (contractor-vs-hire-fest-2026.md)

Copy this structure into your ops doc or sheet tab.

# Contractor vs Hire — Fest Marketing Week 2026
fest_window: 2026-10-next-fest
marketing_pool_usd: (from fest cap)
runway_months: (from fest cap)
date_filled:

## Role: community_social
fest_days_needed: 7
hire: base_hourly, hours_week, weeks_incl_ramp, burden_mult, tools, onboarding_h → fully_burdened_hire_usd
contractor: day_rate, days, platform_fee_pct → contractor_total_usd
decision: hire | contractor | founder_DIY
rationale: (one sentence)

## Role: trailer_edit
(repeat)

## Totals
sum_chosen_contractor_usd:
sum_chosen_hire_usd:
remaining_cap:
cap_compliant: yes | no
deferrals: (list)

Beginner tip: One tab per role beats one mega-table—you will re-run trailer row in June when quotes update without touching QA.

Three studio scenarios (illustrative math only)

Numbers below are patterns, not benchmarks. Replace with your quotes.

Scenario A — Solo founder, $3,200 marketing pool, runway 7 months

Lesson: Founder DIY is not free—if 35h blocks vertical slice demo work, contractor community may be cheaper on schedule risk.

Scenario B — Two-person team, $4,800 pool, runway 5 months

Action: Cut trailer to 4 days OR defer PR; re-run receipt before sign.

Scenario C — Post-layoff three-person, $6,000 pool, runway 9 months

Action: Hire path wins community if post-fest comms continue; otherwise switch community to 7-day contractor and save ~$800.

Fest week staffing calendar (T-7 through T+3)

Map who covers which surface so contractor SOWs align with Steam event timing.

Contractor SOW tip: Specify T-7 through T+3 dates in writing so day counts match reality—not "fest week" vagueness.

Burden multiplier reference (document yours)

Honesty rule: If you do not know burden, use 1.25 temporarily and mark estimate: true in receipt—better than comparing fantasy $22/hr to $450/day.

Proof table (before signatures)

File screenshots or PDF quotes in the same evidence folder as release evidence taxonomy recommends.

Pairing with dual-SKU and storefront economics

Dual-SKU economics answers which storefront lanes you maintain; this worksheet answers who executes fest-week labor for the Steam lane.

Do not merge spreadsheets—link cells or copy marketing_pool_usd once.

Working dev path — receipt validation script sketch

Optional sanity check after filling JSON:

import json

def validate_receipt(path: str, marketing_pool: float) -> None:
    data = json.load(open(path, encoding="utf-8"))
    assert data["schema"] == "contractor_vs_hire_receipt_v1"
    total = sum(r["contractor_usd"] or 0 for r in data["roles"] if r["decision"] == "contractor")
    assert total == data["total_contractor_usd"]
    compliant = total <= marketing_pool
    assert data["cap_compliant"] == compliant, "cap_compliant mismatch"
    print("OK", total, "of", marketing_pool)

Run when quotes change mid-summer—October invoices should not surprise cap math.

Agency retainer vs day-rate contractor

Retainers that bleed past fest window belong in monthly burn, not fest-week rows—unless you explicitly scope fest deliverables inside retainer SOW.

Playtest and comms contractor overlap

Playtest isolation playbook separates Playtest surfaces from fest_public. Community contractors must know which links they may post—add a surface column to your worksheet:

Mis-posted Playtest URLs create support load that shows up in refund dashboard tags—not in contractor invoice.

Tax and legal notes (non-advice)

This article is economic comparison, not legal counsel.

When in doubt, pay for one hour of accountant time—often cheaper than one wrong hire.

Month-one adoption ladder

Key takeaways

• Fest marketing week staffing needs scoped per role comparison.
• Fully burdened hire includes taxes, benefits, tools, ramp.
• Contractor total is days × rate + fees—not day rate alone.
• Pair with fest marketing spend cap before signing.
• contractor_vs_hire_receipt_v1.json documents decisions.
• Contractor often wins short bursts; hire wins long ramps.
• Founder time is not free—optional shadow row.
• Trailer/motion almost always contractor SOW.
• cap_compliant false requires deferral plan—not hope.
• Not dual-SKU economics or metadata checklists.
• May–October 2026 contractor surge needs written math.
• SOW deliverables and revision caps matter.
• Re-run worksheet if fest date or runway shifts.
• BUILD_RECEIPT row ties spend to build_label.
• Two quotes beat one urgent yes.

FAQ

Intern instead of hire?
Same worksheet—use stipend + founder management hours in burden column.

Agency retainer?
Model as contractor with monthly SOW; watch cap bleed across months.

Offshore contractors?
Include timezone, FX, and payment fee rows; specify English handoff hours in SOW.

Can I use this for year-round marketing hire?
Yes—extend weeks_including_ramp beyond fest window; contractor column stays burst-only unless you scope longer SOW.

What if trailer quote exceeds entire marketing pool?
Defer trailer, shorten SOW days, or revisit fest cap runway floor—do not hide overrun in hire rows.

Does part-time hire avoid benefits?
Region-dependent; burden column still applies—never compare gross wage to contractor day rate.

How do I track contractor posts?
Pair with 21-day UTM experiment; SOW should require tagged links.

What about voice actor or composer contractors?
Same formulas—specialist SOW; usually contractor lane unless you employ audio staff year-round.

Publisher asked for fest marketing plan—what do I send?
One-page cap excerpt + this receipt JSON + Q3 diligence demo packet cross-reference—not raw quotes.

Founder spouse doing social for free?
Optional shadow row for honesty; cash worksheet stays $0 with note founder_family: true.

Conclusion

Fest week is a sprint, not a headcount plan—unless the math says otherwise.

Run burden math. Scope contractor SOWs. Pair with fest cap. File the receipt. Then sign.

Next reads: Fest marketing spend cap, Dual-SKU economics, BUILD_RECEIPT pipeline.