Help Center

Everything you need to get the most out of the estimator - from quick setup and real use cases to scope planning, deadlines, budgeting, import/export, and data handling.

This tool is designed to help you turn rough ideas into structured, realistic production estimates. Whether you are estimating a single task, planning a full feature, comparing delivery scenarios, or checking whether a deadline is realistic, the estimator helps you understand the true impact of scope before work begins.

It works for freelancers, leads, producers, outsourcing teams, game teams, creative departments, and anyone who needs a clearer way to estimate work, time, cost, and staffing.

FAQ

What is this estimator and what does it actually do?

This estimator helps you break work into tasks, define how many units of each task need to be delivered, assign the roles involved, and calculate the total effort required to complete the project.
Instead of relying on rough guesses, it gives you a structured model of production effort. You can see how work is distributed across specialists, how much time the project may take, how team size affects delivery, how much the work may cost, and which roles are most likely to become bottlenecks.
In simple terms, it helps answer questions like:

How big is this project really?
How many people do we need?
Can we hit this deadline?
What will this scope cost?
Which discipline is overloaded?
What happens if we change the scope, budget, or team size?

Who is this tool for?

This tool is useful for a wide range of users and workflows.
It works especially well for:

freelancers preparing estimates or quotes
art directors and leads planning creative scope
producers balancing team capacity and deadlines
outsourcing vendors preparing structured bids
agencies translating deliverables into time and cost
game teams planning features, LiveOps, and content production
digital teams planning interface, assets, and implementation work
stakeholders who need a clearer view of effort before approval

You do not need to be a technical user to get value from it. You can start with a simple task list and refine the estimate step by step.

How do I start using the estimator if I have never used a tool like this before?

The easiest way to start is to think about the work in five simple steps.
Step 1 - Add your tasks

Start by listing the major pieces of work that need to be delivered.
These can be screens, features, assets, content sets, environments, characters, UI flows, event components, or any other meaningful production units.

Examples:

Main screen
Shop
Season Pass feature
Tutorial
Main heroes
Backgrounds
Event flow
Reward system
Promo banners

Do not worry about being perfect at first. Start with a practical breakdown.
Step 2 - Set the quantity

For each task, define how many units need to be created.

Examples:

1 main screen
6 backgrounds
3 main heroes
8 promo banners
5 popups
12 reward icons

This is where the tool becomes powerful: instead of manually multiplying everything in your head, you let the estimator scale effort by quantity.
Step 3 - Add the required roles

Now add the roles involved in delivering the work.

Examples:

UI/UX
2D Art
3D Art
Animator
Concept Art
Technical Artist
FX
Game Designer
Developer
QA

You can use the default roles or rename them to fit your own workflow.
Step 4 - Assign hours by role

For each task, enter how many hours each role needs per one unit of that task.

For example:

One background may require 8 hours of 2D Art, 1 hour of Animation, and 0.5 hours of QA
One main hero may require 16 hours of 2D Art, 10 hours of Animation, and 1 hour of QA
One feature may require hours from UI/UX, Game Design, Development, QA, and Art

This transforms the estimator from a simple list into a real production model.
Step 5 - Review the results

Once the tasks, quantities, and hours are in place, the estimator calculates:

total hours across the whole project
hours per role
hours per person
estimated duration
cost, if rates are added
delivery pressure against a deadline
where more people may be needed

This is where you start seeing the real size of the project.

What kinds of tasks should I add?

Add tasks that represent meaningful chunks of production work.
Good tasks are things like:

Main screen
Shop
Player profile
Tutorial
Season Pass feature
LiveOps event
Main heroes
Secondary heroes
Backgrounds
HUD / in-game interface
Reward system
Loading screens
Promo banners
Offer screens
Special event flow

Avoid breaking work into tiny micro-actions too early.
This tool works best when each task represents a production unit large enough to be understood and estimated clearly.

For example, instead of splitting a simple screen into 20 tiny technical actions, it is often better to estimate it as one task with hours distributed across the relevant roles.

How detailed should my estimate be?

Start at the level that helps you make decisions.
If you only need a rough quote, a higher-level estimate is enough.
If you are planning production more seriously, make the structure more detailed.
A good rule:

use fewer, bigger tasks for early planning
use more detailed tasks for production planning and handoff
For example:

Early-stage estimate

Main screen
Shop
Event flow
Characters
Backgrounds

More detailed production estimate

Main screen
Shop
Player profile
Tutorial
Reward popups
Offer screens
Main heroes
Secondary heroes
Background pack
HUD update
Event flow
QA test pass
Both are valid.

The right level of detail depends on the decision you are trying to make.

Can I use this tool for just one task or one features?

Yes.
You do not need a full project to use it.

The estimator also works well for a single task or feature — especially when it is complex enough to involve multiple roles. In that case, you can break it into smaller subtasks and estimate the effort more accurately across the full workflow.
You can combine multiple tasks, quantities, roles, and settings into one complete estimate.

This is useful for:

game features
event flows
content drops
LiveOps content
art production packages
UI updates
marketing deliverables
internal development scope
multi-discipline production planning

Can I use this tool outside game production?

Yes. Once tasks and hours are in place, you can define how many people are available for each role. The tool then shows how much work is assigned per person.

This helps answer:

can the current team handle this scope?
which role is overloaded?
where should we add support?
do we need outsourcing?
is the team balanced?

This is very useful for:

producers
leads
outsourcing coordinators
studio managers
anyone planning team capacity

How do quantities help?

Quantity is one of the most important parts of the tool.

Instead of estimating every repeated item from scratch, you estimate the effort for one unit and let the tool scale it.
Examples:

8 promo banners
12 reward icons
6 backgrounds
3 main heroes
5 popups
20 offer variations

This makes estimates faster, more consistent, and easier to reuse.

It is especially powerful for recurring content production or pipeline-based work.

Why assign hours by role instead of just entering one total number?

Because real production is not done by one generic person.
Different roles carry different parts of the work:

UI/UX may define structure and flow
2D Art may create the visuals
Animator may bring assets to life
TA may handle integration and setup
Developer may implement the logic
QA may validate the result

When you assign hours by role, you get much more useful answers:

who is overloaded
which department carries the most effort
how to size the team
where time really goes
what changes if one role is limited

This is what makes the tool useful for actual planning instead of just rough math.

What roles can I add?

You can add any roles that match your workflow.

Common examples:

UI/UX
2D Art
3D Art
Animator
Concept Art
Technical Artist
FX / VFX
Game Designer
Developer
QA
Producer
Copywriter
Motion Designer
Marketing Designer

You are not locked into a fixed structure.
You can rename roles, add your own, and tailor the setup to your team.

How do I decide how many hours to assign to a role?

Use your best production judgment based on your team, quality bar, and pipeline.

A few good ways to estimate:

use your past project experience
use historical averages from previous tasks
start with a rough benchmark and refine later
estimate one typical unit, then multiply by quantity
ask specialists to validate hours for their discipline

The tool is not trying to magically invent the right number for you.
It gives structure to your assumptions and helps you understand their consequences.

You can always revise the hours later.

Can I compare different versions of the same project?

You can duplicate an estimate and compare different planning scenarios.

Examples:

MVP version vs full version
3 characters vs 8 characters
fewer screens vs a full interface rollout
one event vs a seasonal content package
internal team vs outsourced support
higher polish vs shorter timeline

This turns the tool into a planning sandbox, not just a static calculator.

Can I estimate team size and staffing needs?

Yes. Once tasks and hours are in place, you can define how many people are available for each role. The tool then shows how much work is assigned per person.

This helps answer:

can the current team handle this scope?
which role is overloaded?
where should we add support?
do we need outsourcing?
is the team balanced?

This is very useful for:

producers
leads
outsourcing coordinators
studio managers
anyone planning team capacity

Can I estimate delivery time?

Yes. The estimator uses:

hours per day
workdays per week
people per role

to calculate the expected duration of the work.

This is much more realistic than simply dividing total hours by a single number, because it respects how work is distributed across roles.

In practice, project duration is often driven by the slowest or most overloaded role, not by the total hours alone.

That is why this tool helps reveal the real bottleneck.

How do deadlines work?

You can enter a target deadline in calendar days.

Once a deadline is set, the estimator compares the planned work against your current staffing setup and shows whether the team can realistically hit that date.

If the deadline is too aggressive, the tool highlights where more people may be needed.

This is useful for:

launch planning
milestone reviews
sprint discussions
executive planning
stakeholder conversations
risk assessment before approval

Instead of saying “this feels tight,” you can show exactly which role is overloaded.

What does the deadline warning actually mean?

It means the current team setup is not strong enough to complete the planned scope by the selected date.

The tool shows which roles are likely to block delivery and, in some cases, how many more people might be needed to meet the deadline.

This helps you make practical decisions:

reduce scope
extend the deadline
add people
outsource part of the work
lower the quality bar
split the delivery into phases

That makes the tool useful not only for estimating, but also for decision-making.

Can I estimate cost and budget?

Yes. If you enable cost mode and enter hourly rates for each role, the estimator calculates the total production cost across the project.

This is useful for:

internal budget planning
client estimates
comparing scope options
outsourcing decisions
understanding cost impact of production complexity

Because cost is tied to roles, it is much more informative than assigning one flat project number.

You can see not only what the whole project costs, but also which disciplines drive the budget.

What kinds of rates should I use?

You can use:

your internal hourly rates
freelancer averages
vendor rates
blended rates
simplified demo rates

The best choice depends on what you are trying to learn.

If you want:

a budget forecast → use realistic team or vendor rates
a quote → use commercial rates
an internal scope discussion → use simplified internal benchmarks
a demo → use clean sample rates

The tool does not force one pricing model.
It just helps structure the one you already use.

Can I use it for freelancer quotes or agency proposals?

Yes, very effectively.

The tool helps translate deliverables into:

scope
effort
time
budget

This makes quotes more transparent and defendable.

It is especially useful for:

freelancers
boutique studios
outsourcing vendors
agencies
art and production leads preparing estimates for approval

It also makes revisions easier, because you can update the scope and immediately see how the numbers change.

Can I save and reuse estimates?

The tool supports CSV and JSON import/export, which makes it easy to save your work and use it again later.

This is useful for:

backups
templates
sharing with teammates
moving data between sessions or devices
duplicating setups for scenario comparison
keeping a library of standard estimate models

If you often estimate similar kinds of work, this becomes very valuable over time.

What is CSV export useful for?

CSV is useful when you want a simple, spreadsheet-friendly format.

It works well for:

quick editing
spreadsheet workflows
copying data into other tools
simple reviews
fast task and role adjustments outside the estimator

CSV is best when you mainly care about the task list, quantities, and role hours in a flat, readable format.

It is practical and lightweight.

What is JSON export useful for?

JSON is useful when you want to preserve the full structure of the estimate.

That includes:

roles
tasks
quantities
role hours
people per role
rates
settings
deadline-related setup

JSON is better when you want to restore the full estimate later without losing structure.

It is especially useful for:

saving full project states
creating reusable templates
scenario comparison
sharing complete estimator setups
keeping a faithful backup of the whole model

When should I use CSV and when should I use JSON?

Use CSV when you want:

a quick export
spreadsheet editing
simpler sharing
readable task tables
lightweight manipulation of estimate rows

Use JSON when you want:

a complete project backup
full restore of the estimator setup
reusable templates
long-term storage of structured estimate data
scenario duplication with full settings included

A simple way to think about it:

CSV = task table

JSON = full project state

Is my data uploaded somewhere?

The tool is designed to be privacy-friendly and lightweight.

During normal use, project data stays in your browser, and you remain in control of what you save or export.

That means:

you work locally in the browser
you choose what to export
you decide what to share
sensitive scope, staffing, or budget assumptions do not need a heavy cloud workflow to be usable

This makes the tool especially attractive for users who want a simple workflow without feeling that they must push planning data into a bigger system first.

Is the tool secure?

Project data stays in the browser during use, and you stay in control of what gets saved or exported.

This is a more responsible way to explain the tool than making exaggerated claims like “fully secure” or “guaranteed safe.”

For many users, especially those working with internal scope, staffing, or budget assumptions, this local-browser approach feels simpler and more comfortable.

Why is local browser data handling useful?

Because many estimates contain sensitive planning information.

Examples:

internal staffing assumptions
vendor budgets
scope before approval
unannounced feature plans
pricing comparisons
early production forecasts

A browser-local workflow reduces friction and gives users more control over what they keep, export, or share.

That is often enough for early planning, internal collaboration, and personal use.

Can I use the tool as a communication tool, not just an estimating tool?

This is one of the most underrated benefits.

A good estimate is not only a number. It is a structured explanation of what the work includes.

The estimator helps teams align around:

what is in scope
what roles are involved
where the effort goes
what drives timeline
what drives cost
where the risks are

This makes it useful in conversations between:

art and production
design and development
leads and stakeholders
internal teams and clients
freelancers and buyers
vendors and partners

It helps replace vague assumptions with visible structure.

What if my estimate is incomplete or uncertain?

That is completely normal.

One of the strengths of the tool is that you do not need a perfect plan to begin. You can start with a rough model and improve it over time.

A practical approach:

add the major tasks
set rough quantities
add the main roles
enter early hours estimates
review the totals
refine the weak points later

This makes the tool useful in:

pre-production
early scoping
proposal stage work
evolving project definitions
moving targets where the exact scope is not final yet

You do not need perfect certainty to get useful insight.

What are some real-world scenarios where this tool is especially useful?

Here are some of the strongest use cases, from simple to advanced.

Scenario 1 — Quick freelance quote

A client asks for:

one main screen
one shop screen
three promo banners

You use the tool to:

add tasks
assign quantity
estimate UI, Art, and Dev hours
add rates
generate a structured quote

Scenario 2 — Art package estimate

You need to estimate:

6 backgrounds
3 main heroes
5 secondary heroes
12 reward icons

You assign 2D Art, Animation, QA, maybe TA, and immediately see total effort across the art pipeline.

Scenario 3 — Feature estimate

You are planning:

Season Pass feature
reward flow
UI updates
implementation
QA

The estimator helps you map design, UI, art, development, and QA effort into one coherent production estimate.

Scenario 4 — LiveOps planning

You want to estimate one event plus recurring offers and banners.

The tool helps model both:

the one-time feature setup
the repeating content units

This is especially strong for content-heavy pipelines.

Scenario 5 — Deadline stress test

Stakeholders ask if the team can deliver in 20 calendar days.

You set the deadline and see:

current duration
overloaded roles
whether the team is on track
where more people may be needed

Scenario 6 — Scenario comparison

You duplicate the estimate and compare:

current scope vs simplified scope
current team vs bigger team
lower budget vs lower polish
internal production vs partial outsourcing

This helps you make decisions before committing.

What is the main value of this tool ?

This tool makes the process:

visible
structured
repeatable
easier to review
easier to share
easier to refine
more realistic in terms of production impact

It turns estimation from guesswork into a clearer decision-making process.

Final takeaway

You can use this estimator at many levels:

as a quick task calculator
as a freelancer quote builder
as a project scoping tool
as a team planning tool
as a deadline risk checker
as a budget estimator
as a reusable content pipeline model
as a scenario comparison sandbox
as a communication tool for aligning teams and stakeholders

The simplest way to think about it is this:

Start with tasks. Add quantity. Add roles. Assign hours. Adjust team and deadline. Review the real impact.

That is where the estimator becomes powerful.

Still need help?

If you haven't found the quick answers you need regarding your bookings or estimates, our team is ready to assist. For direct technical help or specific account inquiries, please email us at contact@projectestimator.tech.

Our production support specialists typically respond within 24 hours.