Quick answer
Scope the deliverable, not the adjective. Replace "small" with which systems the edit touches: geometry, UVs, textures, rig, weights, blendshapes, shaders, scale, and platform export. A five-minute color tweak and a five-hour hair rebuild can both be described as "small" in a DM.
Wrong assumption
"It is only a color change / only moving the hair / only adding a jacket." That describes the screenshot you want — not the pipeline. Easy when materials are layered and non-destructive. Painful when everything is baked into one texture, the outfit slot never existed, or the rig was never set up for that part to move independently.
Why "small" is vague
Clients usually describe the visible delta: "make the eyes bigger," "change shirt color," "fix the clipping." Artists price the systems delta: which meshes, UV islands, material slots, bones, weight maps, shape keys, and export targets must be opened, changed, and re-tested.
- You see: one area on the character.
- The file may require: mesh edits, new UVs, texture rebakes, weight repaints, blendshape fixes, Unity/VRChat re-upload, and regression tests on every expression you use on stream.
That gap is why two clients can send the same sentence and get wildly different quotes. The request is not wrong — it is incomplete until you name systems and constraints.
How this page fits the cluster
- This page: your edit request is vague — how to describe it so quotes are honest.
- Frankenstein models: why the file fights back when a "small" edit hits stitched parts.
- Having a base: "just edit my base" hides the same problem from the starting file side.
- Source files: export-only handoffs turn small edits into rebuilds.
Describe your edit — copy this into the message
Fill in what you can. Unknowns are OK — say "I don't know" so the artist knows to inspect first.
- What you want different — markup, reference, or plain language ("shorter hair," "new jacket," "less clipping on left shoulder").
- What must still work after — face tracking, hand tracking, all current expressions, VRChat upload rank, game engine import, etc.
- Which parts you think are involved — hair only, outfit only, face mesh, full body, Unity scene, textures only.
- Current files you can send — Blender project, FBX, VRM, Unity package — not only screenshots.
- Contract context — is this a included revision, a paid add-on, or a new commission on an old file?
Systems your edit might touch
Ask yourself (or the artist) which rows apply. More checked rows usually means more time — even if the screenshot change looks tiny.
| System | "Small" can mean | Often deeper than it looks when |
|---|---|---|
| Geometry / mesh | Nudge a vertex, hide a mesh | New silhouette, outfit swap, or missing body under clothes |
| UVs | Recolor an existing island | New parts need unwrap; texel density mismatches across kitbash |
| Textures / materials | Slider on a separate hair material | Hair, skin, and clothes share one baked albedo |
| Rig / bones | Minor constraint tweak | New clothing needs new bones, or two armatures were merged |
| Weights / skinning | Paint one small clipping area | Outfit swap, hair cut, or new mesh at a seam |
| Blendshapes / expressions | Adjust one existing key | Face sculpt change breaks visemes; keys from different pipelines merged |
| Shaders / engine | Swap albedo in Unity | Shader model differs between DCC and target engine |
| Platform export | Re-export same VRM | VRChat rank, PhysBones, scale, or validation rules change after mesh edit |
Same words — different depth
| You said | Often quick when | Often deep work when |
|---|---|---|
| Change hair color | Hair has its own material slot | Hair is baked into skin or body texture |
| Shorten / restyle hair | Modular hair cards with clean UVs | Requires new topology, UVs, and weight repaint |
| Add or swap jacket | Outfit slot and body exist under clothes | New modeling, UVs, textures, weights, clipping tests |
| Fix clipping | Minor weight paint on one seam | Outfit and body need remodel; scales do not match |
| Tweak face / eyes | Blendshapes already exist and transfer | New sculpt, retopo, re-bake, re-rig expressions |
| Swap head or body | Same rig template, planned modular design | Mixed bone naming, weights copied from another base |
| "Make it Unity / VRChat ready" | Already authored and tested for that target | Shader conversion, scale, retarget, optimization, upload validation |
| "Same as reference image" | Reference matches current topology and style | Reference implies redesign, new outfit, or new proportions |
Revision, add-on, or rebuild?
Artists need to classify your request — not to be difficult, but because contracts and quotes attach to deliverable types.
- Included revision: small adjustment within the original scope (e.g. agreed color pass on separated materials) — usually limited count in contract.
- Paid add-on: new work on top of delivery (new outfit piece, new expression set) — should be quoted before work starts.
- Rebuild: file structure makes the "small" edit cheaper to redo from a clean base — honest artists say this up front; see Frankenstein models.
If you are not sure which bucket you are in, say so. Ask for an inspect-first quote: artist opens files, lists systems touched, then prices.
What the artist cannot know until they open the file
- Whether hair, face, and body share one texture
- Whether the body exists under the current outfit
- Export-only vs editable layers, modifiers, and material nodes
- How many third-party parts were stitched together without documentation
- Whether your "small" change breaks expressions, tracking, or platform rank limits
Sending files before arguing about price is not optional for honest scoping — it is the only way to turn your vague request into a real one.
Why artists push back on "small"
- They cannot see how the file is built until they open it.
- Your "small" may require re-export and re-test on every platform you use.
- Revision limits cover agreed deliverables — not unlimited reinterpretation of "small."
- Prior handoffs may be export-only — edits force rebuild, not tweak.
- They have been burned quoting "quick fixes" on files that needed days — scope protects both sides.
What to send with an edit request
- The current files (not only screenshots or a Twitch VOD timestamp)
- Target software and version (Blender, Unity, VRChat SDK, VTube Studio path, etc.)
- Markup or reference for the desired change — and what is out of scope
- Whether the change must survive animation, tracking, and every expression you use live
- Revision count already used in the contract, or acknowledge this is net-new work
What to ask before you pay
- Is this a revision, add-on, or new deliverable?
- Which systems will you touch — mesh, UVs, textures, rig, weights, Unity scene?
- Is re-rig or weight paint in scope for this request?
- Will you test in my target platform, not only the DCC viewport?
- If the file structure forces a rebuild — is that a separate quote line?
- What do you need from me if the edit is bigger than my message implied?
DJP interpretation: I have quoted "just fix the hair" and opened a file where hair, face, and body shared one baked texture — that is a texture rebuild and maybe a new hair mesh, not a small edit. I have also had "change the jacket color" take twenty minutes because the outfit was a separate material on a clean VRoid. Same client language, completely different jobs. Tell me what must still work after the change and send the file; skip the word small.
Scope note: Contract revision limits apply to agreed deliverables — not unlimited reinterpretation of "small." When possible, write edit classes in the original quote (e.g. color-only revision vs mesh change).