What are you actually asking for?

What you see vs what the work actually is

Clients usually describe the visible result: "I want a VTuber model," "make it game-ready," "just swap the head," "I already have a base." Creators hear the hidden requirements: rig type, poly budget, export format, source handoff, commercial license, origin chain, and whether the mesh was built for that target at all.

This cluster exists to slow that down before money or time gets wasted. Think of it like a machined part: the finished part is what you see; the blueprint, tolerances, and process are what make it actually work.

Self-check before you message an artist

Write answers down — vague DMs become expensive guesswork.

• Target: Where must this work? OBS, VRChat, Unity, Blender renders, resin print, Booth resale?
• Movement: Static image, posed sculpt, tracked avatar, or full animation set?
• Files: Final export only, or editable source the next person can actually use?
• Rights: Personal, commercial, streaming, merch, resale — spelled out, not "full rights."
• Origin: Custom from scratch, or built from VRoid, Daz, game assets, marketplace parts, or generators (see Academy for AI workflow)?

Common traps (read these before you assume a cheap edit)

• The three-click illusion. A tutorial can swap a head in three clicks on one model type. A real commission may need UVs, textures, hair, shape keys, and rig integration — days of work, not minutes.
• Pretty is not animation-ready. A beautiful static sculpt may have no usable rig, wrong topology, or no body under the clothes.
• "Optimized" can mean hollow. Hidden geometry is often deleted on purpose. An outfit swap may require rebuilding parts that were never modeled.
• A base is not "almost done." VRoid, Daz, and marketplace bases still need license checks, retargeting, and often major rebuilds for your target. See having a base.
• Frankenstein models fight back on edit. Stitched parts can look fine until a simple change exposes a mess. See your model is a Frankenstein.
• "Small edit" is not a scope word. The same request can be a material swap or a multi-day rebuild — name the systems, not the adjective. See small edits are not always small.
• AI in the brief. Generators and licenses change fast — not a customer path step. Name tool, tier, and use in writing; see Academy AI workflow pack.
• References are not a brief. Mood boards help direction. They do not replace deliverables, platform targets, file list, or rights in writing.