Steam Regional Pricing Second-Pass Worksheet - Fix Discovery Leaks Before October 2026 Next Fest

You set $19.99 USD once in Steamworks and moved on. Three months later, players in two regions complain the game “costs too much,” wishlist-to-purchase lags in others, and your DLC price-anchor tests never ran because base game rows were never sane.

October 2026 Next Fest sends global traffic to a store page that Steam renders in local currency. This Money & Business worksheet is a second-pass regional review—not legal tax advice, not a demand to race to the bottom—so you fix parity leaks and wallet friction before fest week panic discounts.

Why this matters now (May 2026)

1. Fest traffic is global — Visit spikes surface regional price pain you did not see during US-only playtests.
2. Post-rationalized stacks — One-engine teams have bandwidth to fix business ops in Q2–Q3 2026.
3. DLC and cosmetic lanes — Price anchors fail if base game sends mixed signals.
4. Truth and trust — Store truth audits include “is the price honest for advertised scope?”

Direct answer: Run a 90-minute second pass on Steamworks suggested regional prices, document decisions in release-evidence/05-operations/pricing/regional-second-pass-2026.md, and freeze base price changes four weeks before fest unless data forces a deliberate exception.

Who should run this worksheet

• 1–5 person teams with a live or upcoming Steam page
• Games priced $4.99–$29.99 USD base (worksheet scales mentally outside band)
• Studios that already picked a revenue model

Skip if: not on Steam yet—finish playtest branch first.

Worksheet columns (copy to spreadsheet)

Parity band is qualitative: “within acceptable band,” “intentionally lower,” “intentionally higher (premium positioning).”

First pass vs second pass (what changed in 2026)

First pass optimizes speed. Second pass optimizes global readability when traffic is about to spike. Skipping second pass is how teams discover Brazil pain during Next Fest livestreams.

Currency psychology (plain language)

Players do not convert mentally from your USD anchor. They ask:

• “Is this two lunches or one?”
• “Does this feel fair next to games I already own?”
• “Did the demo promise content worth this tier?”

Your worksheet cannot answer taste—but it removes absurd outliers where Steam’s auto rate lands far from local norms and you never noticed.

Top-15 country starter rows (model)

Even pre-launch, seed your spreadsheet with rows you will almost certainly care about:

1. United States (USD)
2. China (CNY)
3. Germany (EUR)
4. United Kingdom (GBP)
5. Russia (USD or regional policy per Steamworks current rules—verify live UI)
6. Brazil (BRL)
7. Poland (PLN)
8. France (EUR)
9. Canada (CAD)
10. Australia (AUD)
11. Turkey (TRY)
12. Japan (JPY)
13. Argentina (USD/ARS per current Steam display)
14. Mexico (MXN)
15. South Korea (KRW)

Add rows when Steamworks traffic report surprises you post-launch.

Step 1 — Lock USD anchor (15 minutes)

Answer on paper before opening twenty regions:

1. Target buyer: premium indie, budget fest demo, or survival price?
2. Hours of content honest at launch vs demo?
3. Comparable titles you are not competing with (avoid fantasy comps).
4. Refund risk if price feels high for scope—pair with demo patch notes.

Write one sentence anchor rationale in evidence README.

Revenue model alignment (pick one primary story)

Your five revenue models article helps choose structure. Regional second pass should match that story:

Changing model and price same week confuses every signal.

Steamworks UI walkthrough (conceptual)

Screens move; the sequence persists:

1. Open app → Store & Steam → Pricing (or equivalent)
2. View base game package price
3. Open regional pricing matrix
4. Compare recommended vs custom per country
5. Save → note effective date Steam displays
6. Screenshot matrix after save → evidence folder

If UI offers bulk edit, still review top-10 manually—bulk tools miss strategic intent.

Worked example (model numbers, not your game)

Anchor: $17.99 USD — 8–12 hour premium-adjacent indie, fest demo honest.

Do not copy numbers—copy structure.

Communication when you change rows

Players notice price changes. Minimum two-pass patch note if structural change ships live:

• Player impact: “Regional prices adjusted for fairness; USD unchanged.”
• Known issues: none if true
• Support: link FAQ if you maintain one

Silence reads as mistake or greed depending on direction.

Block 5 finance row templates

- Regional sheet: frozen 2026-06-01 through post-fest review
- Overrides active: BRL, PLN (see evidence path)
- Promo scheduled: none until T+30 post-fest
- Runway impact: neutral (no base USD change)

Interaction with attribution experiment

If running 21-day UTM sprint, tag price-change posts separately—surface=steam-community, creative=pricing-faq-2026-05.

Micro-studio timeboxing

Debate is good; document the decision even when founder wins.

Red flags that are NOT fixed by regional cuts

• Demo crashes
• Misleading trailer co-op
• Zero reviews / broken Deck glyphs
• Browser SKU over-promising

Fix ops first; worksheet second.

Step 2 — Steam suggested vs override (30 minutes)

In Steamworks → Pricing:

1. Note recommended regional conversions.
2. For each top-10 traffic country from Steamworks stats (or educated guess if pre-launch), mark accept or override.
3. Never override blindly down everywhere—signals desperation to algorithms and players.

Wallet-friction regions (model guidance)

You are not solving macroeconomics—you are removing obvious leaks.

Step 3 — Parity band rules (15 minutes)

Model bands for micro-studios:

Record reason column—future-you forgets why BRL moved.

Step 4 — Connect to DLC and cosmetics (15 minutes)

If you sell optional content:

• Cosmetic anchors must be % of base per DLC worksheet
• Second pass on base before cosmetic A/B
• Do not run regional base changes same week as cosmetic test—confounds attribution experiment

Step 5 — Fest freeze calendar (15 minutes)

Add to capsule iteration calendar:

Exception process: two-person sign-off + row in operating review Block 5.

Release-evidence export

release-evidence/05-operations/pricing/
  regional-second-pass-2026-05.md
  worksheet-export.csv
  fest-freeze-calendar.md

regional-second-pass-2026-05.md minimum:

# Regional second pass — 2026-05

- USD anchor: $… — rationale: …
- Overrides: BRL …, TRY …
- Frozen from: YYYY-MM-DD
- Next review: post-Next-Fest +30 days

Operating review Block 5 (finance)

Friday sheet:

• “Regional sheet status: frozen / open”
• “Countries flagged for post-fest review: …”

Four consecutive sheets during Q3 show publisher diligence you steer revenue ops.

Qualitative signals (no invented metrics)

Watch patterns, not hero percentages:

Publisher and partner conversations

Publishers in Q3 2026 intake sometimes ask:

• “Who owns pricing decisions?”
• “When did you last review regions?”
• “What is fest freeze policy?”

Your regional-second-pass-2026-05.md answers without a live call. Attach to diligence packets under 05-operations/pricing/.

Discount interaction (do not double-confound)

Weekly discount experiments opinion piece warns about promo fatigue. Regional second pass is not a sale:

Run structural pass before scheduling fest-adjacent sales, or you cannot tell which lever moved conversion.

Wishlist vs purchase (reading Steamworks)

Without inventing metrics, log qualitative bands weekly during May–September:

Soft Brazil + healthy US → row fix, not global sale.

Scope truth gate (mandatory before any cut)

If truth audit fails, do not lower price to compensate for misleading demo. Fix copy and build parity first—price cuts train wrong players to buy.

Sample override rationale snippets (paste into sheet)

BRL: -8% vs suggested — growth market, content hours mid-tier, avoid premium signal.
TRY: accept suggested — volatile; quarterly review scheduled.
EUR: accept suggested — tight parity with USD anchor.

Future-you reads why, not just numbers.

Post-fest review agenda (30 minutes)

Thirty days after October Next Fest:

1. Export regional revenue + units if available
2. Compare to worksheet predictions
3. Mark rows “revisit” or “hold”
4. Schedule cosmetic price anchor only after base stable

Contrarian note

Some teams refuse all regional customization on principle. The 2026 counter-argument is visibility: Steam shows local prices whether you philosophize or not. Documented intentional overrides beat accidental defaults.

Glossary

Extended FAQ

Early Access pricing?

EA can move once with clear patch note policy; freeze harder during public fest demo week.

Multiple SKUs (PC + soundtrack)?

Each SKU gets tab; anchor game first.

Epic/GOG ports?

Duplicate worksheet per store—Steam fest focus does not migrate automatically.

AI cosmetic SKUs?

Disclose generative cosmetics honestly; price as % of base per DLC worksheet.

Seven-day challenge variant (optional)

Teams wanting habit, not one sitting:

Fits inside four Friday operating adoption month.

Anti-patterns

1. Global -30% because Discord said so
2. Changing price daily during fest
3. Ignoring suggested prices without documenting why
4. DLC priced before base second pass
5. No freeze calendar—panic Tuesday discounts

FAQ

Is this tax/VAT advice?

No—Steam handles many display taxes; consult professionals for corporate tax.

Free demo with paid game?

Demo free; second pass applies to paid SKU and optional purchases.

Publisher sets MSRP?

Worksheet still documents your Steamworks rows and rationale for milestone evidence.

Bundles?

Run separate tab in spreadsheet; base second pass first.

Ninety-minute sprint schedule

Season pass and future SKU rows (planning only)

If revenue mix includes future season pass, add ghost rows in spreadsheet:

Ghost rows prevent fest-week panic “let’s launch season pass discounted.”

Legal and platform policy reminder

Steam has partner rules on pricing practices that change. This worksheet is operational, not legal compliance. When unsure, read current Steamworks partner documentation before save.

Printable gate before fest upload

• [ ] USD anchor sentence in evidence
• [ ] Top 10 regions reviewed
• [ ] Overrides have reason column
• [ ] DLC/cosmetic % aligned
• [ ] Fest freeze in calendar
• [ ] Block 5 updated
• [ ] No concurrent global sale planned
• [ ] Truth audit green or explicitly deferred with risk note

After worksheet — what not to do in September

• Do not slash USD because streamer asked
• Do not add paid DLC same day as base cut
• Do not change regions daily during fest
• Do not argue pricing in reviews—fix scope or document FAQ

Regional FAQ for store page (optional blurb)

If players repeatedly ask “why price differs by country,” add short FAQ on store or forum pin:

Steam shows prices in local currency. We set regional prices using Steam’s recommended bands and occasional overrides for purchasing power. USD base price funds ongoing development. Questions: support@…

Honest FAQ reduces bad-faith review bombing about regions you do not control entirely.

Coupling with playtest and fest branches

Playtest branch testers should see near-final price rows before public fest—surprise price day-one erodes trust. Passworded testers can give qualitative “feels expensive/cheap” feedback per country if you know their locale.

AI-assisted pricing research (assistive only)

LLMs can summarize forum threads about pricing—human signs off overrides per prompt registry discipline. Never auto-apply model-suggested global cuts to Steamworks.

Spreadsheet hygiene

• One tab base-game
• One tab dlc-cosmetic
• Version filename pricing-worksheet-v3-2026-05.xlsx
• Commit CSV export to repo monthly

Lost spreadsheets recreate panic.

Success looks like (qualitative)

Final checklist sentence for operating review

“Regional second pass complete; USD anchor unchanged; fest freeze active; evidence at 05-operations/pricing/.”

Copy-paste every Friday during Q3 if pricing is in scope.

Exchange-rate drift between passes

Steam suggested prices move when platform updates bands. Your freeze means no edits, not “never think about currency again.” Calendar a post-fest re-pass even if no emergency—quarterly cadence matches capsule iteration rhythm.

Wishlist psychology vs purchase psychology

High wishlists in a country with weak purchase may be price, language, or payment friction—worksheet only solves price leg. If override does not help after six weeks post-launch, escalate to localization or demo scope review before second cut.

Team roles

Solo founders wear all four hats—still write names in README as “owner: you.”

One-page worksheet PDF (optional)

Export spreadsheet to PDF for publisher packets that dislike live links. PDF date must match git commit date of CSV export—stale PDFs worse than no PDF. Keep the CSV as source of truth; PDF is a snapshot for email attachments only.

Related links

• Revenue mix without overcommitting
• Milestone payment checklists
• Post-Next-Fest plateau
• Truth audit challenge

Close: October 2026 Next Fest players see your game in their currency—not your USD spreadsheet cell. A second-pass regional worksheet in May beats a panic global sale in September. Freeze with intent, document overrides, and revisit after fest with real conversion rows—not forum anecdotes. Put the spreadsheet in release-evidence/ so pricing decisions are receipts, not memory—and so your future publisher email can point to a folder instead of a heated Discord thread. Run the pass once, honestly, before you ask the algorithm to fix a pricing story you never wrote down in May.