A studio of one to three people can't compete on salary, benefits, job security or brand. It can compete on clarity — on being the place where a good contractor knows exactly what's being asked, gets an answer within a day, and gets paid on time.
That's not a soft advantage. Most freelance artists and audio people have been burned by vague briefs, silent clients and shifting scope. Being unusually clear is a real differentiator, and it's mostly a matter of writing four or five documents you should have written anyway.
The studio brief
One page, kept current, sent to anyone you're talking to about work. It answers what a stranger needs to know before they decide whether you're worth their time:
- What the studio makes, in one sentence.
- What's shipped, with links. This is the credibility paragraph — a released game, however small, changes the conversation entirely.
- Size and structure, stated honestly. "One full-time person plus contractors" is fine. Pretending to be bigger than you are gets found out in the first call and costs you more than the honesty would have.
- How you work — tools, timezone, how fast you respond, what a typical engagement looks like.
- How you pay. Rate range or budget range, schedule, method.
That last point is the one small studios avoid and shouldn't. Naming a range up front filters out the mismatches before either side spends an hour, and it signals that you've done this before.
The role one-pager
Written per engagement, not per hire. Even for a two-week illustration job, this prevents most of what goes wrong:
- The deliverable, enumerated. Not "some UI art" — "18 icons, one app icon, three screenshot backgrounds," with dimensions and formats.
- The style reference. Links or images, plus a sentence about what you like in each. "Like this, but calmer" is a real instruction; "modern and clean" is not.
- Revision rounds included. Say the number. Two is normal. Unstated revisions are the most common source of freelance resentment in this industry.
- Timeline with a real deadline and what it's tied to.
- Rights and delivery. Who owns the work, whether they can show it in a portfolio (say yes — it costs you nothing and it's worth real money to them), and that you need editable sources, not just exports.
The portfolio clause is free goodwill
Contractors care a lot about whether they can show the work. Granting it explicitly, in writing, before they ask, costs a studio essentially nothing and makes you noticeably more attractive than the clients who leave it ambiguous.
Paid tests, small and real
Portfolios show what someone can do. They don't show whether they can do your thing, or how they handle feedback, or whether they reply to email. A small paid test answers all three.
The rules that keep this fair: it must be small — a few hours, not a few days. It must be paid at the real rate. And it must not be work you actually ship unless you're paying full price for it. Unpaid "tests" that produce usable assets are a well-known scam pattern, and good freelancers will decline on principle, which means the ones who accept are the ones you didn't want.
What you're evaluating is only partly the artefact. How they asked clarifying questions, whether they hit the deadline they named, how they responded to one round of notes — those predict the engagement better than the output does.
The first-week pack
Onboarding at a tiny studio is not an HR process. It's a folder you send on day one so nobody has to ask you five questions they'll be slightly embarrassed to ask.
- Access. Repo, asset storage, task board, chat. All of it, on day one, before they need it.
- The asset spec. Naming convention, formats, dimensions, where things go. If you have an asset pipeline document, this is where it earns its keep.
- The game, playable. A build, on their device. Astonishingly often skipped. Someone making art for a puzzle game should have played the puzzle game.
- A short style and tone note. What the game feels like, what it isn't, three examples of things that are wrong for it.
- The communication contract. Where to ask questions, how fast you'll answer, when you're unavailable. Say your actual response time, not an aspirational one.
That pack takes an afternoon to build the first time and about ten minutes to reuse forever. It's the difference between a contractor's first week being productive and their first week being a series of blocked half-days.
Where to actually find people
For a small studio, in rough order of how well it works:
- Local community groups and jams. You've watched them work. That's worth more than any portfolio. In Greater Philadelphia this means the local game meetups and playtest nights.
- Game jam teams. People who finished a jam project shipped something under pressure — the single most predictive signal available.
- Referrals from contractors you've used. Good freelancers know other good freelancers, and they don't refer people who'll embarrass them.
- University programs. For juniors, with the caveat that you're taking on mentoring cost. Be honest with yourself about whether you have time for that.
- Freelance marketplaces. They work, but the filtering burden is entirely yours and the median is low. Use a paid test.
The two things that lose good people
Slow replies. A contractor blocked on a question is a contractor billing you for waiting, or worse, moving to another client's work and coming back cold. Answer within a day, even if the answer is "I'll get you a proper response Thursday."
Late payment. Freelancers talk to each other. A studio that pays on the day it said it would gets first call on people's time; a studio that doesn't gets a polite decline the next time and never learns why.
Neither of these costs money to fix. Both of them are what "we're small but we're good to work with" actually means in practice — and for a studio that can't compete on anything else, it's the whole pitch.