Indie DLC and Cosmetic Price-Anchor Worksheet: Test Price Points Before October Next Fest (2026)

Your Discord poll said $7.99 for the cosmetic pack. Your gut said $4.99. Your spreadsheet said nothing because you never built one. Then October Next Fest traffic arrived, players opened the store page, saw a price that did not match the demo’s vibe, and left without wishlisting.

Pricing is not a morality play. It is experiment design. This Money & Business guide gives micro-studios a price-anchor worksheet you can run in May–September 2026—before fest pressure forces a panic discount.

Who this is for

• Solo devs shipping a first cosmetic or small DLC alongside a festival demo
• Three-person teams arguing about $4.99 vs $7.99 in Discord without data
• Publishers who want evidence before locking milestone revenue assumptions

Not for: AAA live-ops teams running perpetual rotating sales—that is a different operations book.

Why this matters now (May 2026)

Three 2026 pressures make anchor tests urgent this quarter:

1. Visit-to-wishlist conversion — Steam’s discovery stack rewards pages that convert attention into intent. Price mismatch reads as “mobile bait” or “premium pretension” depending on direction.
2. DLC and cosmetic lane saturation — More indies ship optional purchases; players compare your anchor to last week’s roguelite, not to your costs.
3. Post-rationalization stack discipline — Teams that rationalized to one SKU have fewer engineering surfaces but higher margin pressure per SKU—pricing errors hurt faster.

This worksheet does not replace five revenue models that work. It tells you which anchor to test first for optional purchases.

Direct answer (TL;DR)

1. Pick one optional purchase lane (cosmetic or DLC expansion—not both in week one).
2. Set two anchors one step apart (example: $4.99 vs $7.99 US).
3. Run two-week store copy tests holding build constant.
4. Measure wishlist add rate per visit, not revenue yet (pre-launch).
5. Lock anchor in release-evidence/pricing-anchor.md before fest uploads.
6. Pair with regional pricing spreadsheet discipline before global sales.

What a price anchor is (and is not)

Anchor — The first number players see for an optional purchase class. It sets expectations for everything after.

Not an anchor:

• Your internal cost-plus calculation alone
• A competitor’s price from a different genre
• A publisher slide from 2024

Is an anchor:

• The US base price on the store page for the cosmetic/DLC row
• The number in the short description bullet list
• The price shown in the festival demo shop UI if purchases are marketed

Worksheet template (copy to sheets)

Add columns for refund rate post-launch later; pre-launch, conversion is the honest signal.

Two-week A/B discipline (no build changes)

Week A (anchor A copy):

• Store short description bullet lists price and contents explicitly
• Trailer lower-third shows anchor A for 2 seconds
• Demo shop UI (if any) shows anchor A

Week B (anchor B copy):

• Change only price strings and capsule secondary text
• Do not change trailer footage or demo build hash

If conversion moves, price framing moved. If nothing moves, problem is not anchor—it is demo trust or capsule clarity.

Guardrails — do not test these during fest prep

Cosmetic vs DLC expansion lanes

Rule: Expansions need vertical slice honesty. Cosmetics need clarity that stats are not sold.

Regional sanity (one afternoon)

After US anchor locks:

1. Open regional pricing guide
2. Apply purchasing-power sanity bands
3. Pin regional table in same release-evidence/pricing-anchor.md

Do not launch fest with US-only thinking.

Discount interaction policy

Write this paragraph before any sale:

“Fest week: no change to cosmetic anchor. Base game may participate in platform sale per calendar. DLC anchor holds unless conversion data invalidates.”

Pair with weekly vs biweekly patch cadence so live-ops does not fight pricing tests.

release-evidence/pricing-anchor.md skeleton

# Pricing anchor decision
- SKU: cosmetic_pack_v1
- US anchor locked: $4.99
- Test window: 2026-06-02 .. 2026-06-16
- Conversion anchor A: 8.2%
- Conversion anchor B: 6.1%
- Decision rationale: higher conversion + acceptable Discord tone
- Regional table version: 2026-06-18
- Next review: 2026-09-01 (pre-Next-Fest freeze)

Operating review integration

Add Block: Pricing to 30-minute operating review:

• Anchor test running? Y/N
• Conversion delta direction
• Any fest discount request pending

Common mistakes (2026)

1. Testing price during broken demo week
2. Letting founder mood pick $7.99 because art is “worth it”
3. Ignoring negative sentiment on “greedy” anchors without parsing who said it (buyers vs non-buyers)
4. Changing anchor after wishlist spike from unrelated trailer—false attribution
5. Launching mobile SKU with PC anchor copy unchanged
6. Forgetting tax-inclusive display expectations in EU store views

When to use sales vs anchor tests

Anchor tests — pre-launch or pre-DLC announcement windows with organic traffic.

Sales — post-launch retention arcs with mature wishlist base.

Never use a deep sale to discover anchor—you discover sale shoppers, not anchor fit.

Map anchors to your revenue model first

Before opening the worksheet, confirm which lane from five revenue models you are actually running:

If your pitch deck says premium but your store page whispers battle-pass language, fix the model before testing cents.

Ninety-minute anchor sprint (May–September 2026)

Run this once per SKU lane before fest uploads freeze:

Minutes 0–15 — Inventory

• List every place a price appears: store page, press kit, demo UI, Discord pin, trailer lower-third.
• Screenshot current state into release-evidence/pricing-anchor/screenshots/.

Minutes 15–35 — Hypothesis

• Write one sentence: “Players who loved the demo will pay $X because Y.”
• Pick anchors A and B one meaningful step apart—not $4.99 vs $5.99 unless you have huge traffic.

Minutes 35–55 — Instrumentation

• Confirm Steam store traffic reporting access.
• Add a single spreadsheet row per day: visits, wishlists, notes.
• If you run privacy-safe telemetry, do not log prices in client events—keep pricing tests store-side only.

Minutes 55–75 — Copy pack

Draft two short-description variants:

Variant A (lower anchor example):

Optional Cosmetic Pack — three character skins + lobby emote. $4.99. No gameplay stats. Supports continued updates.

Variant B (higher anchor example):

Collector Cosmetic Pack — three skins, emote, nameplate frame. $7.99. Cosmetic only; no pay-to-win.

Minutes 75–90 — Calendar lock

• Schedule week A and week B on the operating review calendar.
• Assign one owner: only they may change price strings mid-test.

Worked example (synthesized pattern, not a named studio)

A three-person roguelite team shipped a festival demo in June 2026. Base game wishlist intent was healthy, but optional-skin interest looked soft. They hypothesized players saw $7.99 as “double the vibe tax” against a $14.99 base game anchor.

Week A ($7.99 copy): visit-to-wishlist 7.8%

Week B ($4.99 copy): visit-to-wishlist 9.4%

They locked $4.99 for the cosmetic pack, kept base price unchanged, and documented the decision before September fest assets exported. Post-launch, the pack sold steadily—not because $4.99 was “correct forever,” but because the test happened before trailer renders baked in the wrong number.

This is a pattern teams report on forums—not a promise your numbers will match.

Bundle and “complete edition” interactions

Anchors get muddy when bundles enter the picture:

1. Complete edition should list explicit contents—never hide the cosmetic in fine print.
2. If base game + DLC bundle exists, test bundle delta separately from cosmetic-only anchor.
3. During fest, avoid launching a new bundle the same week as anchor week B.

For teams on stack rationalization, one bundle SKU is enough; more SKUs multiply anchor mistakes.

Psychology players actually cite (2026 forum patterns)

Players rarely write spreadsheets. They write:

• “Feels like a mobile trap” — often high anchor + vague contents
• “Supporting the devs” — often clear contents + fair anchor
• “Wait for sale” — often prior deep discount memory, not your test

Your worksheet column J (Discord sentiment) should tag quotes:

Do not let NOISE rows veto a conversion win without buyer corroboration.

Expansion DLC: anchor as percentage of base

When the optional purchase is more game, use percentage bands:

Pair with milestone payment checklists if a publisher advance assumes a higher DLC anchor—show the test doc in milestone evidence.

Fest freeze calendar (September 2026)

Violating the freeze to “try one more price” during fest week confounds every metric you care about.

Cross-link to demo and capsule work

Price anchors fail when upstream trust fails. Run these siblings in order:

1. Demo honesty labels
2. Capsule iteration calendar
3. This worksheet
4. Regional pricing pass

Skipping step 1 makes step 3 lie to you.

AI-assisted store copy warning

If you use LLMs to draft store bullets:

• Run human-gated patch-note discipline on price claims
• Disclose generative assist per AI disclosure checklist if copy ships publicly

Models love inventing “30% more content” lines—dangerous next to price anchors.

Post-launch: when to reopen the worksheet

Reopen anchor decisions only when:

• Conversion shifts >20% relative for four consecutive weeks post-launch
• Refund rate on the SKU exceeds your documented band
• You add substantial new contents (not recolors)

Otherwise, stability beats founder anxiety.

Publisher and milestone context

If a publisher milestone pays on revenue:

• Show anchor test methodology in milestone evidence
• Tie milestone payment checklists to locked anchor doc version

Transparency reduces “why is DLC priced lower than pitch deck” fights.

Key takeaways

1. Price anchors are hypotheses tested with conversion, not debates.
2. Two anchors, two weeks, build constant.
3. Wishlist conversion per visit is the pre-launch metric.
4. Cosmetic and expansion lanes have different expectation bands.
5. Lock decisions in release-evidence/pricing-anchor.md.
6. Regional pricing is a second pass, not optional.
7. Do not deep-discount during anchor discovery.
8. Fest prep needs locked anchors by September 2026.
9. Pair with revenue model choice and demo honesty.
10. Spreadsheet discipline beats Discord polls.

Decision tree (one screen)

Demo trustworthy? ──no──► Fix demo labels first
        │
       yes
        ▼
Revenue model locked? ──no──► Pick from five models article
        │
       yes
        ▼
Pick ONE optional lane (cosmetic OR expansion)
        ▼
Run anchor A vs B (two weeks, build frozen)
        ▼
Conversion winner + buyer-tagged sentiment OK?
        ├─yes──► Lock US anchor → regional pass → fest freeze
        └─no──► Retest OR fix discovery (not both same week)

Extended worksheet rows (add after row K)

Export the sheet as CSV into release-evidence/pricing-anchor/ so Git history shows when you knew what you knew.

Roles on a three-person team

The marketing lead edits price strings during tests; engineers do not “hotfix” typos that change anchors mid-week.

Steam-specific friction points (2026)

• Short description is the highest-signal price real estate—put anchor and contents there, not buried in the long description only.
• Capsule should not imply currencies you do not sell; mismatched coin art + dollar price confuses mobile-trained players.
• Demo with a greyed-out shop is fine; lying about purchasability is not—label “preview pricing” if checkout is disabled.
• News posts during anchor tests should avoid announcing sales; use development updates instead.
• Curator keys do not replace anchor tests—curator audiences skew kind.

Mobile SKUs without forking your soul

If Google Play Data Safety and Steam diverge:

• Lock US anchor logic once, then map regions per platform tables.
• Do not run simultaneous Steam and mobile anchor tests—traffic quality differs.
• Cosmetic-only on mobile still needs the same contents honesty as PC.

Live-ops cadence vs anchor stability

Teams running weekly vs biweekly patches sometimes want to “bundle” a price change with a content drop. Policy:

Content patch week: no anchor change.
Anchor change week: no new gameplay systems.

Mixing both trains players to associate updates with wallet surprises.

Wishlist plateau false positives

If post-Next-Fest plateau diagnostics say discovery is flat, a higher anchor will not rescue you—it will amplify distrust. Run plateau fixes first, then reopen row A of the worksheet.

Ethics and trust (short)

• Sell cosmetics, not power, unless your entire model is honest about it.
• Show odds if loot boxes exist—this worksheet assumes direct purchase, not gacha.
• If kids can access the game, treat family pricing expectations seriously on mobile.

Seven pro tips from 2026 operating reviews

1. Print the worksheet—founders respect paper.
2. Test anchors only when demo build hash is stable for 14 days.
3. Never argue price in public Discord during week B—take DMs, log tags privately.
4. Keep a “price string diff” text file between variants for audit trails.
5. Screenshot Steam backend analytics weekly; exports vanish in disputes.
6. Tell your publisher the test ended, not just the winner.
7. Schedule the next review before launch crunch eats the calendar.

FAQ

We are free-to-play later. Do anchors matter now?
Yes for wishlist page positioning and positioning against premium competitors.

Can we test three prices?
Not in one two-week window—sequence A vs B only.

What if conversion is equal?
Pick lower anchor for goodwill unless margin requires higher and art supports premium signaling.

Does this apply to itch pay-what-you-want?
Principle yes; metrics differ—use median payment not wishlists.

We have no traffic for A/B.
Fix discovery (capsule iteration calendar) before price tests.

Our publisher picked $9.99 before we tested. Can we push back?
Yes—with this worksheet as evidence. Milestone conversations go better with conversion charts than vibes.

Should the demo include real checkout?
Only if checkout works and refunds are supported; otherwise label preview pricing clearly.

We sell a soundtrack separately. Does that change cosmetic anchors?
Treat soundtrack as its own lane—do not bundle-test cosmetics and audio in one anchor week.

What about regional currency rounding?
After US lock, run the regional pass—rounding errors cause more refund anger than a $1 US difference.

Can we raise anchor post-launch without backlash?
Grandfather existing owners or add contents; silent raises burn trust.

Does Epic or console parity matter?
If you promise parity, document the same anchor logic per platform contract—console cert may require price tier tables earlier.

We only sell on Steam for now. Skip mobile?
Skip mobile tests, not mobile thinking—players compare your anchor to last week’s mobile port anyway.

Close: The worksheet is boring on purpose. Boring pricing decisions survive October traffic; exciting guesses do not. Lock your anchor in May or June, respect the September freeze, and spend October arguing about trailer pacing—not whether $7.99 was a vibe crime against your demo.