How to Brief a Freelancer So You Actually Get What You Want

You hired a freelancer. You described what you wanted. You got back something that looks nothing like what you had in mind. Sound familiar?

The problem is almost never the freelancer. It is the brief. A vague brief is an invitation for the freelancer to guess — and they will guess wrong. A good brief eliminates guesswork and gets you what you actually want on the first delivery.

This is the exact framework we use when hiring on Fiverr, Upwork, and for direct commissions. It works for logos, websites, video editing, game assets, writing, and everything in between.

Most people write briefs like they are texting a friend: "I need a logo, something modern and clean, maybe blue." That is not a brief. That is a vibe.

Here is why vague briefs lead to bad results:

• "Modern" means something different to every designer. Your modern is minimalist Swiss. Their modern is gradient mesh with 3D elements.
• "Clean" tells them what to avoid (clutter) but not what to include.
• "Maybe blue" — so blue or not blue? Now they are guessing your preference instead of executing your vision.

A freelancer can only deliver what you describe. The more specific you are, the closer the first draft will be to what you want.

Every good brief answers these seven questions. Copy this structure for any project type.

Include: target audience, primary action you want visitors to take (sign up, buy, contact), competitor sites you like or dislike, content/copy (do not make them write it), responsive requirements, and any integrations (forms, payments, analytics).

The biggest mistake: sending a freelancer to "build a website" without providing the actual text content. They are designers or developers, not copywriters. Have your copy ready or hire a writer first.

Include: raw footage (organized and labeled), reference videos showing the style/pace you want, music preference or tracks, where captions/text should appear, export format and resolution, and platform (YouTube has different specs than TikTok or Instagram).

Pro tip: timestamp your raw footage. "Use clip from 2:34-3:10 for the intro" saves the editor hours of scrubbing through your files.

Include: art style references (screenshots from games with similar aesthetics), technical specs (resolution, file format, animation frames if applicable), how the asset will be used in-game, color palette, and any existing assets it needs to match.

For character designs: provide a character sheet or detailed description including body type, clothing, accessories, expressions needed, and multiple angles if required.

Include: topic and angle, target audience and their knowledge level, tone (casual, professional, technical), word count range, SEO keywords if relevant, examples of writing you like, outline or key points to cover, and any sources or data to reference.

Never say "write me a blog post about X." Say "write a 1,500-word guide for small business owners who have never used email marketing, covering tool selection, list building, and first campaign setup. Tone: conversational but credible. Include actionable steps, not theory."

Even with a perfect brief, the first draft might not be exactly right. Here is how to give revision feedback that actually helps:

• Be specific: "The header font feels too playful — can we try something more geometric like Montserrat?" beats "I do not like the font."
• Use visual markup: Screenshot the deliverable and annotate it. Circle what needs changing. Tools like Markup Hero or even your phone's screenshot editor work fine.
• Separate must-haves from nice-to-haves: "The logo must work on dark backgrounds (critical). It would be nice if we could try a version without the tagline (optional)."
• Do not redesign via text: If your feedback is longer than the original brief, something went wrong. Schedule a quick call instead.