A spec demo can make a hiring decision feel safer. Instead of choosing from credits, reels and a meeting, the director hears music against the actual picture. The producer gets an object the team can discuss.
But a pitch can also create false certainty. It may select the composer who guessed the temp most accurately, had an empty weekend or delivered the glossiest mockup. None of those qualities guarantees a clean approval process after picture lock.
I treat a demo as a narrow production test, not an audition for general talent. Before requesting one, I want the team to name the risk it is trying to reduce. If the existing work and a detailed conversation already answer that question, adding a pitch round may only spend time the schedule needs elsewhere.
Define the hiring risk first
“Which composer is best?” is not a useful test question. “Who understands the point of view in this scene?” can be. So can “Can this musical idea survive dialogue and sound design?” or “Does this person turn conflicting notes into a workable next version?”
Those are different tests. The first is about dramatic reading. The second concerns arrangement and space. The third requires an exchange, not just one polished file.
A producer should decide what evidence the pitch needs to provide. Otherwise the director may judge emotion, the picture editor may reward tight sync, and an executive may respond to production value. Everyone votes on a different job while believing they heard the same comparison.
I separate creative fit, working method and delivery confidence. A cue can reveal creative fit. The questions around it reveal method. A realistic discussion of schedule, approvals, stems and final deliverables says more about delivery than an unlimited mockup does.
Use the reel before creating new work
A reel should not be filtered only by genre. One thriller does not prove that another thriller needs the same palette. I listen for transferable problems: restraint under dialogue, a controlled build, an unstable point of view, a transition that changes scale, or a theme that can appear without announcing itself.
Credits matter, but they need context. They do not automatically explain the exact role, the size of the music team or when the composer joined post. A first call can connect the finished work to a process. I want to know what the composer asks for before writing, how early ideas are presented, how revisions are tracked and what happens when the cut moves.
Sometimes that is enough to hire. Avoiding a demo is not avoiding due diligence. It means the available evidence already addresses the actual risk.
Pick one scene with a real question
If the team still needs a pitch, choose a short scene that exposes the central musical problem. The loudest sequence is rarely the only useful one. A dialogue scene where score must change perspective without advertising the twist can reveal more about judgement.
Use a stable picture version with visible timecode. If editorial changes the cut during the test, the comparison becomes muddy. One composer may be responding to a different rhythm rather than solving the problem less effectively.
The brief should explain what the audience knows, what the score must not reveal, why the temp track is there and which part of the direction remains open. It should identify the intended level of finish. A sketch, a developed mockup and a near-master are not comparable deliverables.
The brief should also resist overprescribing the answer. If every hit, instrument and structural turn is fixed, the exercise measures reproduction. It does not show how the composer reads picture.
Do not mistake turnaround for collaboration
A short deadline can be relevant when the production genuinely has no room. Used artificially, it mostly tests who was available when the email arrived.
I pay attention to the response before the music. Did the composer identify an ambiguity? Ask who has final approval? Separate what one reference says about pace from what another says about tone? Those questions are part of the work, not a delay before it.
High mockup quality can be useful when orchestration and scale are central to the decision. It can also hide an unresolved dramatic idea. A leaner demo may state the idea more clearly and leave room for the production to shape it. Give every candidate the same expectation so polish does not become an accidental scoring system.
Compare a small set of things
I would keep the review grid short:
- Does the cue address the dramatic function in the brief?
- Does the idea remain legible with dialogue and effects?
- Can the composer explain choices without treating them as untouchable?
- Does the response to one focused note improve the scene?
- Does the proposed workflow look sustainable through final stems and masters?
Review against the same picture and at matched playback levels. A louder mockup should not win by physics. Keep the temp available for reference, but describe what it does rather than using resemblance as the score.
I would not make the final decision through a blind vote. You are hiring a collaborator, not licensing an anonymous track. Communication, judgement and ownership of the process are relevant evidence.
State what happens to the demo
Before work begins, candidates should know the scene, audience for the pitch, number of requested versions, decision date and intended use of unselected material. If the production expects alternates or stems, that belongs in the request rather than appearing after delivery.
Clarity matters because a spec cue should not quietly become temp for the next composer, a source of ideas for another pitch, or material carried into the final cut without a new agreement. If the team wants to develop one proposal, it should say so and move into a defined working relationship.
Keep the scope proportional. Multiple scenes, several alternates and full deliverables before selection rarely produce a sharper answer. They build a miniature scoring process before the production has chosen who should run it.
A conversation may be the stronger test
A demo can show one musical instinct. It is less effective at showing stamina across revisions, judgement after a recut or the ability to keep approvals organised. A concrete conversation around the scene and post schedule often exposes those qualities faster.
I can describe what I would test first, what I would send for direction approval, what I would hold until the idea is signed off and how I would prepare final deliverables. That is closer to the job than producing several unrelated cues in a vacuum.
Before asking for a spec demo, write down the uncertainty it must resolve. If it is a specific musical question, keep the test short and comparable. If it is about trust, process or availability, use the reel and the meeting. You can hear my work and send the scene, context and post schedule.