Questions that come up before the first call.
Scope, confidentiality, time zones and how we plug into your build. Commercial terms are agreed per project and quoted against your milestone dates.
How does a project start?
Send us the brief and whatever reference you can share — concept, existing assets, a build, a mood board. We sign an NDA before we receive anything sensitive, then come back with a scoped plan: deliverables, milestones, team shape and a named lead per workstream.
Do you sign NDAs?
Yes — before we receive reference material, not after. Most of our work sits under NDA, which is why only a minority of the case studies on this site carry client names.
Which engines and platforms do you work in?
Unreal Engine and Unity, across PC, console and mobile. Art is authored against your material and shader setup rather than a generic pipeline, so assets arrive ready to integrate.
How do you handle time zones?
We are GMT+8, which overlaps European mornings and US Pacific evenings. English-speaking producers work your hours, and milestone reviews are scheduled inside your working day rather than ours.
How does review and reporting work?
Inside your own tools: your branch, your review software, your naming conventions. Work arrives in milestone drops with source handover, and risks are raised while they are still fixable rather than at integration.
What do you need from us to quote?
Four things: what the asset or feature has to do, your poly and texture budgets, the engine and target platform, and the date it has to be in the build. With those we scope to milestones instead of guessing at a lump sum.
Can you work inside our engine and repository?
That is the default, not an extra. We work in your folder structure, follow your LOD and collision rules and report through your review process — so handover costs you integration time, not a translation layer.
Anything not covered here — pricing, minimum scope, revision rounds, IP terms — we agree per project. Ask us directly and you will get a straight answer.
Confidentiality
Work we cannot show you is most of our work.
- We sign an NDA before we receive reference material, not after.
- Client names appear only where permission has been given in writing. Every other case study describes scope and process without identifying the title.
- Reference material, source files and builds stay inside the engagement.
- Access is limited to the named team working on your project.
Engagement models
Three ways to work with us.
1 · Asset packages
A defined list of assets — a character set, a creature batch, a modular kit — scoped to a fixed list and delivered in milestone drops with source handover. Suits a stable art brief where you need throughput without adding headcount.
2 · Milestone packages
One discipline across a milestone: all environment art, all combat animation, the cinematics pass. Runs on your milestone dates and inside your review process. Suits scopes that are still moving and teams that need a partner who can re-plan with them.
3 · Embedded pod
A cross-discipline team — art, design and engineering — working as part of your production, in your branch and your tools, reporting weekly against your dates. Suits full-cycle co-development or getting a vertical slice into a publisher build.
Scope and commercial terms are agreed per project against your milestone dates. Nothing on this page is a fixed rate card.
Capacity
A named team, not anonymous capacity.
- Every workstream has a named lead who stays with the project from kickoff to final drop.
- English-speaking producers work your hours. We are GMT+8, which overlaps European mornings and US Pacific evenings.
- The team assigned at kickoff is the team that ships the milestone — no silent swap of artists halfway through.
- Capacity changes are planned at milestone boundaries, so reviews and build cadence stay predictable.