How to Brief a Composer for Custom Music (What Actually Speeds Up the Process)
A brief doesn’t need to be long or technical. It needs to answer the questions a composer would otherwise have to ask you before starting — the more of those you answer up front, the fewer round-trips before work actually begins.
The short version
- Describe mood and energy in plain language — “driving but not aggressive” beats a genre label.
- Say where the music ends up: online only, or TV, an app, a campaign. That sets the license, not just the composition.
- One reference track says more than a paragraph of description.
- A rough brief is enough to start — the brief goes to the composer, not into a queue.
What a brief needs, at minimum
Vicate’s brief form asks for four things: your name, your email, reference tracks, and a description of the project. That last field is where most of the useful information lives — here’s what makes it actually useful.
What to include in the project description
- What the music is for. A video, an ad, a game, a brand identity — the context changes everything about tempo, structure and mood.
- Length or rough runtime, if you know it. Even an estimate (“around 90 seconds” or “a 30-second loop”) is more useful than nothing.
- Mood and energy, described however feels natural. “Tense but not scary,” “warm and a little nostalgic,” “driving but not aggressive” — plain language works better than genre labels alone.
- Where it needs to end up. Online only, or does it need to run on TV, in an app, or across a bigger campaign? This affects the licensing scope, not just the composition.
- Timeline. If there’s a deadline, say so early — it’s the single easiest thing to plan around if you mention it up front, and the hardest to fix if it surfaces late.
- Budget range, if you have one. Not required, but it narrows the conversation faster than going back and forth on scope first.
Reference tracks are doing more work than people think
The reference-tracks field isn’t decorative. A track (Vicate’s own catalog or anywhere else) that’s close to the mood you’re after says more in ten seconds of listening than several sentences of description. If you don’t have one, that’s fine — just say what you’re picturing instead.
You don’t need a full brief to start
A short brief is enough. If you only have a rough idea — a project that’s still forming, or a quick question about whether something’s even feasible — sending that as-is is fine too. It’s easier to refine a loose starting point together than to wait until everything is fully defined before reaching out.
What happens after you send it
The brief goes to the composer directly — not a queue, not an auto-generated quote. Expect a personal reply that responds to what you actually described, not a form response.
FAQ
Do I need to know exactly what I want before briefing?
No — a rough description and a reference track or two is a real starting point. Precision helps, but isn’t required to begin.
Is there a minimum project size for custom music or adaptation?
Not specified up front — describe the project and you’ll get a straight answer on whether it’s a fit.
Can I ask a quick question before committing to a full brief?
Yes — a short question is a fine way to start; you don’t need a complete brief just to ask something.
On Vicate Music: the brief goes straight to the composer — describe the project, add a reference track if you have one, and go from there.