Indie Game Production Planning: A Lightweight System for Assets, Costs, Launch Work and Handoffs

Small game projects usually do not fail because nobody had a giant project-management system.

They fail in smaller, more ordinary ways: the asset list keeps growing, nobody remembers which marketplace purchase belongs to which scene, outsourced work arrives without a clean handoff, launch tasks are left until the end, and planned costs quietly become actual costs without anyone noticing the difference.

A solo developer or small team does not need enterprise process to reduce those problems. It needs a small number of records that answer useful questions quickly.

This guide describes a lightweight production-planning system built around six questions:

1. What does the game actually need?
2. What should be bought, created or commissioned?
3. What will it cost in money and time?
4. What is the current production state?
5. What must happen before launch?
6. What evidence needs to survive after the work is done?

The goal is not to manage every hour. The goal is to make expensive uncertainty visible before it becomes a late-stage problem.

Start with the asset scope, not the shopping cart

Before buying models or commissioning work, create a single asset list.

For each asset, record at least:

• asset name;
• category;
• gameplay or scene role;
• priority;
• source strategy;
• planned cost;
• status.

The source strategy can be deliberately simple:

• Buy — use an existing marketplace asset;
• Create — make it internally;
• Commission — pay for custom production.

That one choice prevents a common planning mistake: treating every missing asset as a modelling task.

A project with 120 required assets may not need 120 custom models. Some assets are cheap to buy, some are worth making because they define the visual identity, and some are better commissioned because the required skill or production time is not available internally.

If you want to test this workflow without building a large tracker first, the free/pay-what-you-want Indie Game 3D Asset Planner Lite covers priority, Buy/Create/Commission decisions, planned vs actual cost and status in one small workbook.

Give hero assets a different budget rule

Not every object deserves equal production effort.

A background crate, a boss weapon, a modular wall kit and the main blacksmith forge may all be 3D assets, but they have different effects on the final game.

A useful priority system is:

• High — defines gameplay, marketing, visual identity or a critical environment;
• Medium — important supporting content;
• Low — replaceable filler, decoration or polish.

Then apply the budget accordingly.

High-priority assets are where custom work, stronger art direction or additional iteration may be justified. Low-priority assets should usually be solved with the cheapest acceptable method.

This helps protect the game from a familiar trap: spending three evenings perfecting a prop the player sees for four seconds while a hero environment remains unfinished.

Track planned cost and actual cost separately

One number called “cost” is not enough.

Keep two fields:

• Planned cost — what you expected before the decision;
• Actual cost — what the project really spent.

The difference teaches you something.

If purchased assets repeatedly cost more than expected because bundles are required, the planning assumption was wrong.

If commissions repeatedly expand beyond the first quote, the scope or revision process may be weak.

If internal production is recorded as zero cost, the money column may look excellent while the schedule quietly collapses. That is why production hours should be tracked separately from cash.

For a larger project, the full Indie Game 3D Asset Planning Kit adds budget and production-time tracking, license records and a reusable commission brief around this basic asset plan.

Do not treat internal production time as free

A solo developer may not pay an invoice to themselves, but their time still has an opportunity cost.

You do not need to invent a perfect hourly value. Start with measurable production time:

• estimated hours;
• actual hours;
• blocked hours if meaningful;
• reason for major variance.

Suppose a marketplace prop costs $15 and a custom internal version takes six hours.

The correct decision is not automatically “make it because making it costs $0.”

The real question is whether those six hours create enough differentiation or reusable value to justify not spending them on gameplay, polish, marketing or another asset.

This is especially important when building large modular environment packs for your own game. Reuse can make internal production extremely valuable—but only when the asset genuinely gets reused.

Separate the production plan from the launch plan

A game can be technically close to complete and still be commercially unprepared.

Launch work has its own dependencies:

• store page;
• capsule / key art;
• trailer;
• screenshots;
• demo status;
• release build QA;
• press materials;
• creator outreach;
• announcements;
• localization;
• accessibility review;
• patch / support plan.

Do not hide these inside a generic “marketing” task.

Create launch milestones and attach actions to them.

For example:

T-90 days

• store page baseline;
• core screenshots;
• first public positioning;
• creator / press target research.

T-30 days

• trailer finalization;
• build confidence check;
• outreach wave;
• launch content schedule.

T-7 days

• release candidate;
• store assets rechecked;
• known issue list;
• launch-day communications ready.

Launch day

• build live;
• store state verified;
• announcement links checked;
• support channel watched.

The Indie Game Launch & Marketing Planner is designed around this kind of milestone, content, outreach, budget and launch-QA workflow.

Keep “sent” separate from “successful”

This matters in production and marketing.

An email being sent is not the same as a reply.

A directory form being submitted is not the same as a live listing.

A build being uploaded is not the same as the store approving it.

A contractor sending a ZIP is not the same as the deliverable being accepted.

Use states that reflect reality.

For outreach, a small sequence might be:

Researching → Ready → Sent → Replied → Positive / Declined → Live

For outsourced production:

Planned → In Progress → Submitted → Rework / Accepted → Closed

The exact labels are less important than refusing to call an intermediate action a finished result.

Keep asset licenses and receipts connected to the project

Third-party assets can save enormous amounts of time, but the useful record is not merely “we bought this.”

Keep enough information to recover the evidence later:

• exact product name;
• marketplace / vendor;
• seller;
• original URL;
• order or receipt reference;
• saved receipt location;
• license name / official reference;
• project usage;
• modification reference;
• unresolved questions;
• last manual review date when needed.

Do not copy passwords, card data or account credentials into the tracker.

The production record should point to evidence, not become a credential vault.

If you only document occasional purchases, the free Game Asset Purchase & License Record Checklist is enough. For a larger library, the Indie Game Asset License & Source Tracker keeps multi-asset records, project usage, receipt indexing and review status together.

Treat outsourced handoff as part of production

Commissioned work is not finished when a preview looks good.

A final handoff may need:

• accepted deliverable identity;
• final runtime/export files;
• source files if required by the agreement;
• dependencies;
• naming / folder clarity;
• third-party material references;
• revision state;
• known defects;
• invoice status;
• backup location.

One of the simplest useful rules is:

Do not close the task only because a ZIP arrived.

Close it when another person could understand what was delivered, what was accepted, where the files live and what questions remain open.

The free Outsourced Game Asset Handoff Checklist covers a single final delivery. The full outsourcing tracker is more useful when several contractors, projects or milestones are active at the same time.

Build a small weekly review instead of constantly managing the tracker

A planning system becomes annoying when every action requires administrative work.

For a solo developer, one weekly review is usually more useful than constant updates.

A practical review can take 15–30 minutes:

Asset scope

• What new assets were added?
• Did any high-priority asset remain blocked?
• Did Buy/Create/Commission decisions change?

Cost and time

• Which items exceeded the plan?
• Did production time move enough to threaten a milestone?

Launch

• What milestone is next?
• Which launch dependency is still missing?

External work

• Is any contractor waiting on feedback?
• Is a handoff incomplete?

Records

• Are new purchases linked to receipts / source records?
• Is anything marked “Needs review” before release?

Then close the workbook and build the game.

Use dashboards for exceptions, not decoration

A dashboard is useful only when it helps decide what needs attention.

Useful signals include:

• high-priority assets not started;
• planned vs actual cost variance;
• hours over plan;
• deliverables waiting for acceptance;
• licenses needing review;
• launch milestones at risk;
• outreach follow-ups due.

A dashboard full of attractive charts that do not change decisions is just another screen to maintain.

A lightweight production stack can stay modular

You do not need one giant spreadsheet containing every part of studio life.

A modular setup is often easier:

• asset production plan;
• launch plan;
• license/source tracker;
• outsourcing tracker;
• QA / release systems;
• marketplace seller operations if you also sell assets.

Use only the systems your current project needs.

For developers who want the production and launch sides together, the Indie Game Production Planning Bundle combines the 3D asset planning and launch/marketing workbooks.

For a broader small-studio workflow, the Indie Studio Operations Bundle adds marketplace seller operations, software-cost tracking, asset-license records and outsourced-deliverable tracking around the production bundle.

The real goal is fewer expensive surprises

Production planning does not make an indie game successful by itself.

It cannot guarantee sales, funding, wishlists, a release date or marketplace approval.

What it can do is reduce avoidable uncertainty.

A useful system lets you answer, quickly:

• What are we building?
• Why is this asset important?
• Who is making it?
• What did we expect it to cost?
• What did it actually cost?
• What is blocking the next milestone?
• What launch work is still missing?
• Can we prove where our third-party assets came from?
• Is outsourced work actually accepted and archived?

If those answers are easy to find, the planning system is doing enough.

Useful next steps: start with the free Indie Game 3D Asset Planner Lite, use the free game-development tools hub for browser utilities, or browse the full Knit of Shadows itch.io storefront for focused production and QA systems.