Design Approaches
Not all game design
help is the same.
There are plenty of ways to get progression work done. Some are faster, some are cheaper, some come with more confidence than the situation warrants. This page tries to lay out the differences honestly, so you can decide what actually fits your project.
Back to HomeWhy It Matters
The stakes of a poorly shaped loop
When a developer asks for help with idle game progression, they're generally dealing with one of a few specific problems: the early game loses players too quickly, the mid-game stalls, the economy inflates in ways that weren't anticipated, or the offline progress system doesn't feel meaningful. These are solvable problems — but the quality of the solution depends heavily on how the work gets done.
Generic approaches to game design help tend to produce generic results. Template-based progression systems look fine until the game has enough content to reveal where the template doesn't fit. Quick freelance passes catch obvious issues but often miss the ones that only become visible after you've sat with a game for a while. This page looks at those differences in a straightforward way.
Side by Side
Two approaches compared
This isn't a dismissal of how other designers work — it's an honest accounting of what tends to happen with different approaches and what each one costs in practice.
Aspect
Generic / Template Approach
Slowburn Approach
How work starts
A standard template or spec sheet is applied to your game's numbers
We read the game, ask questions, and understand the specific problem before proposing anything
Scope definition
Often broad and flexible — can expand as the engagement goes on
Defined clearly before work begins; changes discussed openly if they come up
Deliverable quality
Variable — often depends on how well the template fits the specific game
Documented, reasoned, and ready to hand to a developer or act on directly
Communication
Updates when milestones are hit; surprises possible at handover
Issues flagged as they arise; no surprises at the end
Pricing clarity
Hourly or scope-dependent; final cost can shift
Fixed per service; you know the cost before committing
Long-term usefulness
Works until the game grows beyond what the template anticipated
Designed with extensibility in mind, with reasoning that makes future decisions easier
What Sets Us Apart
The things that make a real difference
These aren't the flashiest selling points. They're the things that actually show up in the quality of the work.
Idle-specific expertise
We work specifically in idle and incremental games. The genre has its own vocabulary, its own failure modes, and its own player expectations. A generalist game designer can do competent work here, but someone who knows the terrain saves time and avoids common mistakes.
Reasoning included
We don't just hand over numbers. Every recommendation comes with an explanation of why the approach was chosen, what tradeoffs it involves, and what to watch for. That context is what lets you make informed decisions later when the game changes.
Fixed pricing by service
Hourly billing creates a misaligned incentive where slow work costs the client more. Our services are priced per engagement so you know what you're spending before the work starts, and we have reason to work efficiently.
We decline poor fits
If a project isn't suited to what we do, or if our schedule doesn't allow us to handle it properly, we say so rather than taking it on anyway. This is a simple policy that makes the engagements we do accept go better.
Effectiveness
What tends to happen with each approach
These patterns come from what we've seen in the idle game space — not controlled experiments, but the fairly consistent picture that emerges when you pay attention to where things go wrong.
DIY Balancing
Developers who balance their own progressions often do well on intuition early, then hit a wall when the system gets complex enough that intuition stops being reliable. The problems that emerge are usually fixable, but by then they're often embedded in a lot of content.
Common outcome:
A good early game that loses players somewhere in the second tier of content, usually because a curve wasn't modelled properly.
Quick Freelance Pass
A fast freelance review catches obvious issues and gives the developer something to react to. The limitation is depth — a couple of hours with a game produces surface-level notes, and the kind of systemic issues that only reveal themselves over longer play don't always show up.
Common outcome:
Visible problems fixed, latent problems undiscovered. Can be a good fit for well-developed games that just need a final check.
Slowburn Engagement
Because we define scope carefully and work at a measured pace, the output tends to address both visible and structural issues. The reasoning included in deliverables means problems that come up later are easier to diagnose and fix without another external engagement.
Common outcome:
A progression system the developer understands well enough to maintain and extend themselves, with fewer surprises after launch.
Cost & Value
Thinking about the investment
Our services run from $250 to $580. That's a meaningful amount of money for an indie developer, so it's worth thinking clearly about what you're getting and when it makes sense.
What the cost buys you
The direct output is a documented, reasoned design artefact — a loop design, an implemented system, or a set of pacing notes. The less visible benefit is the time and difficulty it saves when your game doesn't need the kind of post-launch patches that come from progression problems discovered by players.
A single round of significant player-facing balance changes — the kind that need to be communicated, that break existing save data, or that shift the feel of the game — is expensive in ways that are hard to price exactly. The design work that prevents them is easier to price and tends to cost less.
When it probably doesn't make sense
If your game is a very early prototype that hasn't found its core loop yet, spending $250 on Loop Design may be premature — the design might change too much before it's needed. And if your game is already shipping and performing fine, a Balance Pass is probably not a priority.
When it makes more sense
Games that have a solid concept but haven't yet built out their progression, or that are approaching a public release with an economy that hasn't been properly reviewed, are the situations where a focused external engagement tends to earn its cost fairly clearly.
The Experience
What working with us actually looks like
Compared to a less structured engagement, the process here is deliberately simple and predictable.
A less structured approach
Initial call or brief; scope defined loosely
Work in progress; occasional updates on milestones
Handover of deliverable — quality and format variable
Possible follow-up questions if deliverable is unclear
Invoice; possible scope discussion about additional work
Working with Slowburn
You describe the project; we identify the right service and confirm scope before anything starts
Work progresses at a measured pace; you hear from us if anything needs clarification or turns up a relevant issue
Deliverable is clean, documented, and explained — not a draft requiring interpretation
You have the context to act on it without needing further explanation
Fixed cost; no surprises on the invoice
Long-Term Results
How results look over time
The difference between approaches isn't always visible immediately. A template-based progression system and a carefully designed one may behave similarly at launch. The divergence tends to appear as the game grows.
Template-based systems over time
Work fine while the game stays within the template's assumptions
New content layers can be harder to fit without disrupting existing balance
The original reasoning is often opaque, making it harder to make principled changes
Slowburn-designed systems over time
Designed with extension in mind, so new content layers have a clear model to follow
Documented reasoning lets developers make informed changes without starting over
Player-facing issues that do come up are easier to diagnose and address
Common Misconceptions
A few things worth clearing up
Some ideas about idle game design services come up often enough that they're worth addressing directly.
"I can just balance it myself with a spreadsheet."
Often true for simple games. The point where DIY balancing becomes unreliable is when the game has multiple interacting currencies, several upgrade tiers, and offline progress — at that point, the variables are numerous enough that eyeballing the curves stops being sufficient. A spreadsheet is still useful; the question is whether it's being used to model the system correctly.
"Idle game design is just copying what worked in other games."
Reference games are useful for understanding patterns, but applying their numbers directly to a different project is a common source of problems. A curve that works in a game with ten upgrade tiers and one currency behaves very differently in a game with four tiers and three. The design work is in adapting the patterns to the specific project, not just importing them.
"External designers don't understand my game as well as I do."
True, at first. This is why we start by reading the game and asking questions rather than jumping straight to recommendations. The developer's knowledge of their game is genuinely valuable — it's not something to work around, it's something to build from. The combination tends to produce better results than either side working alone.
"I should wait until the game is more developed to think about progression."
There's some truth here — a very early prototype isn't ready for a full loop design. But waiting too long creates its own problem: progression assumptions get embedded in content and are harder to revise. The right time is usually when the core mechanic is settled but the progression layers haven't been fully built yet.
Why Choose This
The short version
If you want someone who will give your game the time it needs, communicate clearly, and hand over something you can actually use — this is probably a good fit. If you need something turned around in 48 hours, it's probably not.
Idle-specific expertise — not a generalist applying generic principles
Defined scope and fixed pricing before any work begins
Documented reasoning that makes future decisions easier, not harder
Honest communication — including when something won't work
Design built for long-term extensibility, not just current content
Paced work that doesn't rush the decisions that need time
Seen enough to be curious?
If Slowburn's approach sounds like what your project needs, we'd be glad to hear about it. Drop us a message — no commitment, no pressure, just a conversation about whether this is a good fit.
Get in Touch