Review work that resembles your product
A portfolio can show strong images without proving fit for your category. Ask for examples that resemble your material, scale, configuration count, and delivery channel. A polished car render does not answer whether the team can handle fabric, packaging, medical equipment, or a large configurable catalog.
Look for evidence of proportion control, material reading, labeling, and repeatable camera rules. Ask what source data the project used and how the team handled incomplete references.
Ask about the working review cycle
A production partner should explain what they need before modeling starts, what each review round checks, and how they record approved decisions. Geometry, materials, camera, and final output should not all be revised in the same unstructured feedback round.
Ask who approves each stage and what happens when the product changes after a render is approved. The answer reveals whether the process can handle normal product development without losing traceability.
Confirm the actual deliverables
Name every required output. That may include still images, source files, web-ready GLB assets, animation, AR-ready files, or a set of product variants. Do not assume that a final image includes an editable scene or that an interactive asset includes every source texture.
If the project includes web 3D, agree the target viewer and validation step. glTF provides a standard delivery format, but the renderer determines support for extensions and presentation choices.
Ask for evidence behind the process
| Question | Useful answer | Unresolved concern |
|---|---|---|
| What source data controls the product? | A reference hierarchy and a way to approve missing details. | Geometry is inferred without identifying the assumptions. |
| How are materials approved? | Representative surfaces under agreed conditions. | One attractive image is treated as proof for every finish. |
| How are revisions recorded? | Named versions, consolidated comments, and stage decisions. | Conflicting feedback has no decision owner. |
| What does interactive delivery include? | Exact formats, target runtime, dependencies, and checks. | A GLB filename is the only technical acceptance condition. |
| What can the client reuse? | Written deliverables and usage terms. | Editable sources or future variants are assumed rather than agreed. |
This is a discussion guide, not a certified vendor score. Apply it to a representative paid trial or a clearly scoped sample when appropriate. Compare providers against the same outputs and acceptance criteria rather than inferring production suitability from unrelated portfolio images.
Check reuse and ownership terms
Ask whether the output is intended for one campaign, a product page, regional variants, marketplaces, or later updates. Match the file organization and naming to that scope. Confirm which assets the team delivers, what can be revised, and how future variants will be handled.
A good service decision comes from a usable process and appropriate deliverables, not from a portfolio image alone.