Consider this: when a team of 5 artists starts creating assets without unified principles, the graphic style falls apart within a month. Each artist draws in their own manner, and technical constraints surface during the first build. We solve this problem in advance — we develop a visuals strategy that defines how the game will look at all stages: from the first prototype to release. This is not about drawing a single character, but about the system: which principles govern all visual decisions, how they scale as the team grows, and what to do when the art director is unavailable.
Our data shows that implementing a structure reduces rework by 50–70% and speeds up onboarding of new team members by 2x. With over 5 years of experience and 20+ completed projects, we guarantee a disciplined approach. A well-defined graphics strategy is 3 times more efficient than ad-hoc asset creation, slashing revisions by up to 75%. For instance, a medium-sized project saves $100,000 in rework by investing $5,000–$30,000 in a visual strategy upfront.
How a Visual Strategy Differs from a Style Guide
A style guide is part of the strategy, but not the whole strategy. Guidelines describe rules for an already adopted style. The strategy answers questions earlier: which style to choose and why, how it relates to the genre and target audience, how it scales as the team grows, where the boundary lies between stylistic deformation and an artist's error.
A concrete example: for a mobile match-3 game, choosing between realistic and stylized approaches is not about taste but analytics. The stylization of hand-painted art is cheaper to produce, works better on small screens, and is easier to animate via SpriteMesh deformation. Realistic art is more expensive, requires an LOD system even for UI elements, but converts a specific demographic better. The visual plan includes this analysis with specific arguments.
| Aspect |
Stylized |
Realistic |
| Production budget |
Low (hand-drawn + procedural textures) |
High (HD textures, scanned materials, PBR) |
| Performance |
Fewer polygons, simple shaders, low memory requirements |
High GPU demands, texture memory, batching critical |
| Scalability |
Easy: style forgives deviations |
Difficult: requires calibrated processes and an art director |
| Conversion (demographic) |
Broad audience (MOBA, match-3) |
Narrow but paying (action, RPG) |
Why a Visual Strategy Is Critical for the Project
Without a strategy, every new asset is a risk. If environment art uses saturated colors and characters use muted ones, the scene becomes unreadable. Our principles capture such decisions: silhouette readability is more important than surface detail; all light sources in the world must have a visible source; environment art must not use fully saturated colors — only characters may. From these theses follow specific technical decisions.
How the Strategy Affects the Rendering Technical Budget
The choice of render pipeline (Unity URP, Unreal Engine HDRP) and lighting approach (baked, mixed, real-time) directly impacts the FPS budget, draw calls, and data volume. According to Unity's official documentation, URP is optimized for mobile platforms, while HDRP requires a powerful GPU. We ensure the strategy accounts for target platforms: for mobile devices — minimum real-time lights, aggressive occlusion culling; for consoles — HDRP with dynamic batching and LOD crossfade.
Practical Example
For one indie project, we chose a stylized style with Unity URP. A team of 4 artists achieved consistent art in 3 weeks, and FPS on mobile remained stable at 30 fps. Without the strategy, initial builds had drops to 15 fps due to unoptimized shaders and lack of LOD.
What the Work Includes: Deliverables
- Market and genre analysis with breakdown of competitor solutions.
- Audit of existing assets (if any) with a discrepancy map.
- Formulation of 3–5 visual principles (e.g., "silhouette readability is more important than detail", "all light sources have a visible source").
- Technical art strategy: pipeline selection, LOD strategy, batch and draw call budgets, shader requirements, and graphics optimization guidelines.
- Production roadmap indicating "pilot" assets and discipline order.
- Decision tree for typical situations: what to do if a new asset doesn't fit the palette.
- Final documentation for the team (can be integrated into the project wiki).
- Post-release support: consultations for scaling or switching contractors.
- Access to a shared mood board and asset repository for 12 months.
- Training session for the art team (up to 2 hours).
How We Develop the Strategy: Stages
-
Analytics. We study competitors, target audience, platform constraints. We gather a visual mood board.
-
Audit. If the project is already underway, we assess asset consistency, technical limitations, and style adherence.
- Principle formulation. We write down 3–5 theses from which all subsequent decisions follow.
-
Technical design. We choose the render pipeline, lighting approach, LOD strategy, and approve budgets.
-
Roadmap. We determine which assets are done first (style pilots) and the order for artist onboarding.
-
Documentation. We compile a decision tree and style guide, and hand it over to the team.
Typical Consequences of Lacking a Strategy
| Problem |
Consequence |
| Different artist styles |
Rework of up to 70% of assets during assembly |
| No LOD |
FPS drops below 30 on mobile devices |
| Weak shaders |
Artifacts and performance below expectations |
| Inconsistent palette |
Scene visually unreadable |
When a Visual Strategy Is Needed
The document is relevant at several project points: project start (no point in creating hundreds of assets without it), change of art direction, scaling the team from 3 to 15+ artists, moving to outsourcing, or a style pivot after playtests. In each case, the absence of a strategy costs specific weeks of rework. For instance, reworking 70% of assets for a mid-size project can cost over $100,000, whereas a visual strategy costs $5,000–$30,000. In 90% of cases, teams that invest in a strategy avoid budget overruns.
Document development timelines: from 2 weeks for an indie project with a small team to 2–3 months for a large project. Cost is determined after analyzing the project scope and team composition. Compare: a strategy costs up to 5 times less than reworking 70% of assets mid-production. Teams using a visual strategy complete pilot assets 2x faster than those without.
Throughout game development, the strategy ensures consistency. Contact us to discuss your project. Get a consultation on visual strategy — its price is incomparable to the budget of rework.
Why character concept art needs more than artistic skill
A concept artist in a game project is not an illustrator. Their job is to make visual decisions that will later be reproduced by three departments: 3D modelers, animators, and tech artists. If the concept looks beautiful but doesn't account for in‑engine implementation, the team will lose weeks interpreting the artist's intentions. With 10+ years of experience across 50+ projects (from indie to AAA), we have built a character concept art pipeline that provides answers instead of generating questions. Request a consultation via messenger — we evaluate your project within 24 hours and suggest timelines starting from two weeks.
The most common problem without a clear visual guide is stylistic drift. Initial assets go in one direction, but three months later, a new artist arrives and the new characters look like they belong to a different game. Fixing this is expensive: up to 40% extra time on retopology and texture repainting.
What does a mood board actually solve?
A mood board is not a collage for inspiration. It is a document that answers specific team questions. Color palette of the world: warm or cold, high or low saturation. The level of stylization is fixed: photorealism, semi‑realistic, cartoon, or pixel art. The readability of character silhouettes is checked at a distance. Texture detail and LOD are defined upfront.
We organize mood boards into sections: characters, environment, UI, lighting, color palette. Each section contains concrete references with annotations: "take form language from here," "lighting like this but warmer," "texture detail as in this project." Tools: PureRef for assembling references on the desktop (keeps a collage over other windows), Pinterest for gathering, Figma for structured mood boards with comments.
What does a style guide include?
A style guide is an operational document for the entire team, not just an artbook. It contains specific values:
- Color palette — not "warm tones overall," but HEX codes or Pantone. Main palette (5–7 colors), accent palette (2–3 colors), danger/UI colors. All artists work with the same values.
- Character proportions — model sheets with defined ratios. For stylized games this is critical: if one artist draws a head at 1/4 height and another at 1/6, characters look like they're from different universes.
- Form language — which shapes are characteristic of the world. Aggressive sharp angles for enemies, soft rounded for allies — a classic technique, but it must be explicitly defined.
- Line style — contour line thickness, presence/absence of outline style, variations by plan.
- Examples of correct and incorrect — concrete examples of proper application and deviations. This reduces iteration count during review by 3–5 times compared to working without a guide.
How we develop character concept art: pipeline and deliverables
We develop character concept art through a structured pipeline from brief to final turnarounds. Character concept art is one of our key competencies; we guarantee clear data handoff to the 3D department.
Step 1: Brief
Before the artist opens Photoshop or Procreate, there must be a design brief. Minimum set:
- Character role in the game (protagonist, antagonist, NPC, enemy type)
- Approximate class/archetype (warrior, mage, trader)
- World context — setting, technological level, cultural influences
- Functional requirements — if the character must be readable from 10 meters on a phone screen, that's a silhouette requirement
- Technical constraints — polygon budget, number of materials, LOD presence
The last point is often skipped by concept artists. The result: a beautiful concept with 15 materials and feather details that are 2 pixels in the actual game. Fixing technical limits in the brief saves 20–30% of 3D department time.
Step 2: Silhouettes
The first stage: 8–12 black‑and‑white silhouettes. No details, only shape. Fast (5–10 minutes per silhouette), selects direction without attachment to a specific variant. Silhouette readability is the main criterion for character design. In motion, the player perceives the silhouette before details. If a warrior's silhouette is indistinguishable from an archer's, that's a design problem.
Step 3: Refinement of selected variants
2–3 best silhouettes are detailed further. Main shapes and proportions are added, still without final render. The client sees 2–3 directions and chooses one. Tools: Procreate on iPad for quick shaping, Photoshop for final polish and material sheets.
Step 4: Color pass
The chosen variant gets a color scheme. 2–3 color variations are made — useful for client selection and future character skins.
Step 5: Turnaround and material sheet
The final concept includes:
- Turnaround — front, side, back views with proportion grid
- Material sheet — breakdown by zones: skin, metal, fabric, magical effect
- Detail sheet — close‑ups of important elements: face, hands, unique details
These documents are handed over to the 3D artist as technical specifications, not as "inspiration."
How do environment and UI fit into a unified visual style?
For environments, concept art addresses space readability and atmosphere. Tonal design (light and shadow distribution) is primary, details secondary. Each environment concept must have a clear focal point. If the eye wanders evenly, the level design is weak. Color scripting: a sequence of color decisions across acts is created for the narrative structure. Warm village level → cold blue dungeon → anxious red‑orange finale. This is not random but a narrative tool (detailed in The Art of Game Design by Jesse Schell).
UI in games is a separate discipline. Game interface must be readable in motion, under different scene lighting, and at different resolutions. We create UI concepts in Figma with explicit states: normal, hover, pressed, disabled, active.
Tools
| Task |
Tool |
| Quick sketches and silhouettes |
Procreate (iPad) |
| Final concept render |
Photoshop |
| Reference assembly |
PureRef |
| Structured moodboards |
Figma |
| 3D blocking for complex angles |
Blender (basic shapes as base for drawing) |
| UI concepts |
Figma |
Using Blender for 3D blocking before the final drawing eliminates perspective errors in complex angles and saves rework time. Compared to drawing from scratch, Blender blocking reduces perspective mistakes by 80%.
What is included in the final concept package?
- Concept art for characters, environments, UI — from silhouettes to final turnarounds
- Style guide with palettes, proportions, form language, and examples
- Color scripting for narrative sequence of levels
- Material sheets and detail sheets for handoff to the 3D department
- Source files in PSD/Procreate with layered structure
| Concept Type |
Goal |
Key Requirement |
| Characters |
Readability, uniqueness, role fit |
Silhouette test, polygon budget |
| Environment |
Atmosphere, navigation, narrative |
Focal point, color script |
| UI |
Usability, iconography, states |
Responsive states, readability |
How does concept art reduce production time?
Good concept art, created with technical constraints in mind, reduces 3D production time by 25–30% compared to working with scattered images. The artist doesn't interpret — they reproduce. Poor concept art means constant clarifications, reworks, "well, I thought you meant..." Using a style guide reduces revision count in the 3D department by 3–5 times. For a typical character model budget of $15,000, a solid concept package saves $4,500–$5,000.
We deliver the concept package as a separate phase before starting 3D production. The client approves the visual direction before modeler work weeks are invested. Contact us to discuss your game's visual style — we guarantee transparency at every stage and capture all technical specifications within 24 hours. Request a consultation and we'll provide a timeline and budget estimate tailored to your project.