SCOPE & ESTIMATES
How estimates work and example requests
We review the features, responsibilities and existing materials before discussing scope, deliverables, cost and timing. Start with your challenge even if the budget or specification is undecided.
What affects cost and timing
- Features and responsibilities
- Clarify new development versus changes, and whether support starts at design, implementation or testing.
- Condition of existing materials
- Available code, specifications and assets affect the investigation and preparation needed.
- Target environment and integrations
- Review devices, operating systems, Unity or Java versions, databases, AWS and external APIs.
- Deliverables and review
- Agree on project data, review builds, documentation, test coverage and acceptance conditions.
- Assets and revisions
- Clarify supplied images, audio or VFX materials, new production, reviews and the adjustment process.
- Preferred timing and later support
- Discuss release or event dates, review stages, maintenance and further changes.
What we clarify for each service
Game development
Features, screens, stages, supplied assets, platforms, external SDKs and testing scope.
Game effects & VFX
Effect count, duration, style, assets and shaders, Unity integration and performance review conditions.
Technical Artist / Unity support
Reproduction steps, investigation scope, Unity and render pipeline versions, changes or tools, and target devices.
Java, AWS & business systems
Existing specifications and code, business requirements, database and AWS integration, change impact, migration and testing.
AI & workflow automation
Tasks, connected APIs and tools, processing volume, exceptions, approvals and maintenance scope.
Prototypes & interactive content
Hypotheses, interactions, screens, assets, distribution format and event usage conditions.
Examples of focused requests
A focused change to a business system
Start with a needed feature, such as an extra field in a Java input screen.
- Possible scope
- Review existing specifications, implement the agreed change, run related tests and explain the changes.
- What to clarify first
- Impact on screens, databases and validation, plus available code and test environments.
Create or refine one VFX effect
Discuss a single skill impact, UI reward sequence or an improvement to an existing effect.
- Possible scope
- Share references, review a rough version, create or refine the agreed effect and hand over the data.
- What to clarify first
- Style, duration, target environment, supplied assets and responsibility for integration.
A prototype to test an idea
Make the central rules or controls usable so the team can try them and discuss the idea.
- Possible scope
- Define the test objective, prototype key interactions, provide a demo and share findings and open questions.
- What to clarify first
- Who tests what, required features and assets, target devices and the demo date.
Tell us what you would like us to help with.
We review the request and identify the information and scope needed next. Budget choices in the form describe your preferred budget, not a service price list. Choose “Discuss / undecided” if it is not yet set.
Discuss an estimate