Key points
A portfolio is a baseline. It shows what the studio has done, but it does not confirm they can execute your specific style and technical requirements.
A paid test is not a free sample. It is a structured evaluation with a real brief, real deliverables, and fair compensation for the studio’s time.
Scope the test tightly. One or two assets is enough to learn what you need. A large test brief is expensive to evaluate and rarely more informative than a small one.
Quality is only one signal. Brief reading, communication, iteration speed, and how the studio handles ambiguity matter just as much.
The brief you write for the test is the real test. Vague test briefs produce inconclusive results and are a waste of both sides’ time.
How to Run a Paid Art Test — And What to Look for in the Results
A portfolio review is where most studio evaluations start. You look at the work, check the style range, see whether the technical execution is where you need it, and form a working impression. It is a necessary step. It is not a sufficient one. Portfolios show finished work. They do not show how a studio reads a brief, handles unclear direction, manages a feedback round, or performs under a real production timeline. A studio’s portfolio may represent its best work across five years. It does not tell you what you will receive on your project, with your art direction, in your production window. That is what a paid art test is for. Most studios understand the idea of a test project. Fewer know how to structure one that actually surfaces useful information. A test brief that is too vague produces results that tell you nothing. A test scope that is too large wastes both sides’ time and money. A test where you only look at the final asset and ignore how it was produced misses most of what the test is actually measuring. This post walks through when to require a paid test, how to write a brief that makes it useful, and how to read the results accurately.When a Paid Test Is Worth Running
Not every outsourcing engagement needs a paid test. If you have worked with a studio before, have reviewed their work on projects similar to yours, and are confident in the brief, a test adds friction without much value. A paid test makes sense when one or more of the following is true.The portfolio is strong but not directly comparable
A studio may have excellent work that does not closely match your specific style direction. Strong technical execution in one visual style does not guarantee the same result in another. If the closest portfolio reference is adjacent to your requirement rather than a direct match, a test removes the uncertainty.The scope or complexity is high
For larger or longer engagements, the cost of getting the wrong partner is significant. A brief paid test is cheap compared to several months of rework or a production restart. The higher the stakes, the more a small upfront investment in validation pays off.The art direction is unusual or demanding
Some projects have very specific stylistic rules, unusual technical constraints, or demanding quality bars. These are harder to evaluate from a general portfolio. A test scoped to your actual requirements tells you quickly whether the studio can navigate that specificity.Communication has felt unclear
If early conversations with the studio have been vague, slow, or difficult to navigate, a test is a low-risk way to check whether that pattern continues under production conditions. Sometimes studios communicate differently once there is a clear brief and a real deliverable in play. Sometimes the pattern holds.Paid test, not free sample
A paid test is a professional evaluation, not a request for free work. Studios that are asked to produce assets without compensation are being asked to absorb cost and risk before the relationship has been established. Fair payment signals that you take the process seriously. It also increases the likelihood that the studio’s best people work on it.How to Write a Test Brief That Actually Tests Something
The quality of a paid test depends almost entirely on the quality of the brief. A vague test brief produces vague results. You cannot evaluate a studio’s ability to read direction if you did not give it any. A good test brief is identical in structure to the brief you would use for actual production. It includes style references, technical specifications, delivery requirements, and a clear description of what the asset needs to do. The only difference is the scope: one or two assets, not a full batch. Here is what a useful test brief should contain.| ELEMENT | WHAT TO INCLUDE |
|---|---|
| Asset scope | One or two assets. Representative of your style and technical requirements, not a full batch. |
| Style references | Mood board, approved comparisons, and at least one example of what is explicitly out of scope. |
| Technical specs | Polygon budget, texture resolution, LOD requirements (3D), or resolution and export format (2D). |
| Rig or animation notes | If relevant: blendshape targets, skeleton requirements, or animation constraints. |
| Engine and platform | What engine will the asset run in? Any platform-specific constraints? |
| Delivery format | File naming, folder structure, and file format expectations. |
| Evaluation criteria | Let the studio know you will assess brief reading, communication, and iteration alongside quality. |
| Timeline | Give a realistic deadline. A test that is rushed to the point of failure tells you little. |
A note on references
References are not decoration. They are the clearest signal a brief can send about visual intent. Include a tight mood board with approved comparisons. More importantly, include at least one example of what you do not want. Studios that rely entirely on positive references and never define exclusions often end up with technically competent work that drifts in the wrong direction.A note on the timeline
Give the studio a realistic deadline. A test that is rushed to the point of failure tells you nothing useful about the studio’s actual capability. It tells you that the timeline was unreasonable. If you want to learn how a studio performs under pressure, create a moderately tight timeline, not an impossible one.What to Look for in the Results
The final asset is the obvious thing to evaluate. It is not the only thing. A paid test is a compressed version of a full production collaboration. The signals it produces go well beyond visual quality. Here is how to read them accurately.Does the asset reflect the brief?
Start with the obvious: did the studio deliver what was asked? Not a variation on what was asked, not a more detailed version of their default style, but a direct response to your references, technical specs, and direction. If the asset looks good but does not match the brief, that is important information. It means the studio has strong output but inconsistent brief-reading. That gap compounds over a long production.How did the studio communicate during the process?
A studio that went silent until delivery tells you one thing. A studio that flagged a brief ambiguity in the first two days and asked a specific, useful question tells you another. Neither silence nor excessive questioning is ideal. You are looking for proactive, proportionate communication: a studio that surfaces real uncertainty without inventing problems that are not there.Did they send a work-in-progress pass?
Sharing a rough pass early, before the asset is finished, is a production habit that prevents large rework. It allows the client to flag directional issues while course-correction is still cheap. If a studio delivers only a finished asset with no intermediate check-in, ask yourself whether that pattern will hold throughout a longer production. It likely will.How did they handle feedback?
Give a feedback round as part of the test. Ask for a revision on something specific. Watch what happens. Did the studio confirm their understanding of the note before acting on it? Did they implement it accurately? Did they raise a question if something was unclear? A studio that quietly implements bad feedback and produces the wrong thing again is a studio whose revision cycles will be expensive.How did the final delivery arrive?
File naming, folder structure, export formats, and documentation tell you about the studio’s production hygiene. A clean, well-organised delivery is a production multiplier. A delivery that requires re-labeling, re-exporting, or follow-up questions before it can enter your pipeline is a form of hidden cost that accumulates across every milestone.What the test results are actually telling you
A paid test that produces a good-looking asset with poor communication, no intermediate pass, and messy delivery is a test that passed visually and failed operationally. Both halves matter. Operational reliability is what makes quality consistent across a full production. Visual output alone does not.How to Evaluate the Results Fairly
Evaluation should happen against the brief, not against an ideal that was never communicated. If the test brief was vague or incomplete, a disappointing result may reflect the brief quality rather than the studio’s capability. Before drawing conclusions, ask whether the brief gave the studio a realistic chance to succeed.Compare against stated criteria
Go back to the evaluation criteria you included in the brief. Was the asset at the right technical spec? Did the style match the references? Was the brief read accurately? Were delivery requirements met? Comparing against stated criteria keeps the evaluation honest and gives you something to discuss with the studio if you decide to give feedback.Give structured feedback even if you do not proceed
A studio that invested time and effort in a paid test deserves clear, specific feedback if you decide not to move forward. Vague rejection after a paid test is a poor professional practice and damages future goodwill in the industry. Be specific about what was strong and what did not meet the requirement. This costs you thirty minutes and is the right thing to do.Do not make the decision on a single test
If the test produced a borderline result — good in some areas, weaker in others — consider whether a brief conversation with the studio would clarify anything. Sometimes a test result that looks like a capability gap is actually a brief interpretation issue that a short call resolves. Do not invest in a full production on the back of a borderline test, but do not dismiss a strong overall candidate because of one unclear data point either.Running a Test With Saigon Dragon Studios
At SDS, a paid test is structured as a genuine production sample. We use the same brief, review, and delivery process we would use in full production. The test becomes the first calibration point for style matching, technical fit, communication cadence, and feedback workflow. We treat feedback on test work seriously. If a test does not meet the requirement, we want to understand why, whether that means refining our interpretation of the brief, adjusting the style approach, or flagging a technical gap and solving it before production begins. If you are evaluating an outsourcing partner for an upcoming project, get in touch with your project details. We can walk you through how a test round would work for your asset type and art direction.Not always. If you have worked with the studio before or their portfolio closely matches your requirements, a test adds time without much value. A paid test makes the most sense when the art direction is unusual, the scope is large, the portfolio is adjacent rather than directly comparable, or when early communication has raised questions. Use your judgment about where the uncertainty actually lies.
Costs vary based on asset type, complexity, and studio rates. A useful test should cover one or two representative assets, not a full batch. Expect to pay market rates for the work, a test is not a discount sample. The relevant question is not the test cost alone, but what it costs if you skip the test and discover a fundamental mismatch three months into production.
Your test brief should include: the asset type and scope, style references and exclusions, technical specifications (polygon budget, texture resolution, LOD requirements or 2D export specs), delivery format and file naming requirements, the engine and platform the asset will run in, and a clear timeline. Include evaluation criteria so the studio understands you are assessing more than visual quality. A test brief that mirrors your actual production brief will produce more informative results.
Evaluate against the brief, not against an ideal that was never communicated. Check whether the asset matches your style references and technical specs, whether the studio communicated clearly during the process, whether they sent a work-in-progress pass before the final delivery, how they handled feedback, and whether the delivery was clean and production-ready. A strong result across all of those areas is a reliable foundation for moving into full production.
Yes, and you should. A studio that invested time in a paid test deserves specific feedback if you decide not to move forward. Explain what was strong and what did not meet the requirement. This is good professional practice and costs very little. It also keeps the door open for future collaboration if the gap was addressable and the relationship was otherwise positive.
