Questions Clients Ask Before Starting

When someone reaches out about licensing music or building a custom sound pack, the first conversation usually follows a familiar shape. They are not asking about pricing tiers or download limits. They want to know whether the audio will actually work in their project, and what happens if it does not.

The most common question is about usage rights. Clients want a plain answer: can this track be used in a YouTube video, a podcast episode, a short film that might go to a festival, or a game that could ship commercially? The answer matters because a vague license creates risk, and risk stops a project before it starts.

The second question is about stems. Many editors and producers do not want a single mixed file. They want the dry vocal, the bass line, the percussion, and the room tone as separate layers so they can balance the audio against dialogue or sound effects. Knowing which stems are available before a purchase saves a lot of back-and-forth.

The third question is about revisions. A client might love the direction of a custom sound design but need the impact to hit a frame earlier, or the ambience to sit lower under a voiceover. It helps to know upfront how many revision rounds are included and what counts as a revision rather than a new direction.

There is also the practical question of delivery format. Some clients work in Pro Tools, others in DaVinci Resolve or Unity. Asking about sample rate, bit depth, and file naming conventions before exporting saves everyone time. A pack delivered as 48 kHz WAV files with clear names like "whoosh_impact_01.wav" is far easier to drop into a session than a folder of vaguely labeled MP3s.

Finally, clients ask about turnaround. A podcast editor on a weekly schedule needs a different timeline than a game studio planning a release six months out. Being honest about capacity and deadlines at the start prevents frustration later. The goal is to match the right sound to the right project without surprises.