Home / Blog / Article
LiveOps · Aug 7, 2026
Designing a LiveOps Economy From Scratch: Currencies, Sinks, and Faucets
A game economy that is not deliberately designed will design itself, badly, within about two weeks of soft launch. Players find the fastest path to maximum currency, sinks go unused, and the numbers your monetization model depended on stop meaning anything. Building an economy from scratch is not about picking currency names, it is about mapping every faucet, every sink, and the ratio between them before a single balance value goes into a spreadsheet.
Start With Sinks, Not Faucets
Most first-time economy designs start by listing ways players earn currency, then bolt on spending options afterward. This produces economies that inflate immediately, because faucets were designed for player satisfaction while sinks were designed as an afterthought. We reverse the order: map every sink first, every genuinely desirable thing a player can spend currency on, upgrades, cosmetics, energy refills, roster slots, and only then size the faucets to match. If your sinks cannot plausibly absorb the currency your faucets generate at a realistic play session length, the economy is broken before a single player touches it.
Soft Versus Hard Currency Separation
The split between an earnable soft currency and a premium hard currency exists to protect monetization from inflation, not to create artificial friction. Soft currency should flow generously enough that free players feel real progress; hard currency should be scarce enough that its value is never in question. The failure mode we see most often is a single currency doing both jobs, which forces the design into an uncomfortable choice: make it scarce enough to protect monetization, and free players feel starved, or make it generous enough to satisfy free players, and paying players feel like their purchase bought nothing meaningful.
Faucet Design: Pacing Without Grinding
Every faucet needs an explicit answer to one question: how many minutes of play does it take to earn enough for the cheapest meaningful sink. If that number is under five minutes, the currency feels worthless. If it is over forty-five minutes for a free player, the game feels like a grind built to sell a shortcut, and players notice the difference between pacing and pressure immediately. We tune faucets against a target session length pulled from actual playtesting data, not assumption, then verify the math holds across a full week of expected play, not just a single session.
Sink Variety Prevents Currency Hoarding
A single dominant sink, one upgrade path, one gacha pull, concentrates all spending decisions into one moment and makes the rest of your currency feel purposeless between those moments. We design at least three sink categories running in parallel: a permanent progression sink (upgrades, unlocks), a consumable sink (energy, boosters, retries), and a cosmetic or collection sink that has no gameplay impact but real perceived value. Players who are not ready to spend on progression still have somewhere for currency to go, which keeps the economy feeling alive instead of stalled while they wait to afford the next big purchase.
Modeling Inflation Before Launch
Spreadsheet economy models lie unless they account for player skill growth over time, and skill growth changes faucet output in ways static models miss entirely. A player earning currency per level in week one earns meaningfully more per minute by week four simply from playing better, clearing content faster, hitting fewer failure states that waste time without payout. We build economy models as time-series simulations across a projected four-to-six week player lifecycle, not single-session snapshots, specifically to catch the inflation curve before it reaches live players instead of after the first support tickets arrive.
Instrumenting The Economy For LiveOps Response
An economy design is a hypothesis, not a final answer, and the only way to know if the hypothesis held is to instrument every currency event server-side from day one: every faucet fire, every sink transaction, every balance change, tagged with player segment and session context. Without this instrumentation a LiveOps team is flying blind on economy health until players start complaining in reviews, by which point the fix is a much bigger intervention than a quiet balance patch would have been. We treat currency telemetry as a launch-blocking requirement, not a nice-to-have added after the fact.
A Pre-Launch Economy Checklist
Before an economy goes into soft launch, confirm: every sink was mapped and sized before any faucet was tuned; soft and hard currency have genuinely distinct roles, not just distinct names; faucet pacing was validated against real playtest session data, not designer assumption; at least three parallel sink categories exist so spending is not gated behind one bottleneck; the economy was modeled as a multi-week simulation, not a single-session spreadsheet; and every currency event is instrumented server-side before the first player touches the build. Economies that pass all six generally survive their first month of live data with only minor tuning. Economies that skip the modeling step usually need a full currency rebalance within the first two weeks, which is a far more painful and visible fix.
Keep Reading
More from the blog
Designing LiveOps Events That Do Not Burn Players Out: Cadence, Offers, and Segmentation
Want these insights on your build?
The engineers writing these articles are the ones who would work on your game.