How to send mixes to clients (without the email mess)
You finished the mix at 1am. Now comes the part nobody enjoys: zipping the file, uploading it somewhere, pasting a link into an email, and then waiting for feedback that arrives as a voice note saying "the second chorus feels off." Off where? You spend the next session scrubbing the timeline trying to find the moment they meant.
Delivery is where good work quietly loses time and trust. Here's how to set it up so the song gets to the client, the feedback is specific, and you get paid — without the thread.
Why email, WeTransfer, and Dropbox break down
They were never built for creative review. Each one solves a slice of the job and leaves you to glue the rest together by hand:
- Links expire. A client comes back three weeks later to approve the master and the download is dead — so you re-upload, again.
- Feedback lives somewhere else. Notes land in email, DMs, and texts. There's no single place that says what's still open.
- "The latest version" is a guess. Mix_v3_FINAL_final2.wav is a meme for a reason. Nobody is sure which file is current.
- Getting paid is a separate chase. The invoice goes out on a different day, in a different tool, and slips down the to-do list.
What a professional delivery setup looks like
Four things turn delivery from a chore into a system. You can assemble them yourself, or use a tool that does all four in one place.
1. One private link, not attachments
Send a single link to a page where the client can listen in the browser — no download, no account hoops, no app to install. The link stays live, so the same URL works whether they open it tonight or next month.
2. Feedback pinned to the exact second
The single biggest upgrade you can make: let the client click the waveform and leave a comment at 1:42 instead of describing it in prose. "Vocal too loud here" attached to a timestamp is worth ten paragraphs of "the second part." You stop guessing, and revisions get faster.
3. Version control so "the latest" is unambiguous
Upload a new revision and the client always sees the current one, with a clear note of what changed between takes. No more sending the wrong file or re-explaining which is which.
4. Get paid at the same place you deliver
Tie the invoice to the delivery. The cleanest version: the client can preview the work, but the full master unlocks when the invoice is paid. You stop being the person who has to send three polite reminders, because payment is part of the handoff, not an afterthought.
See how the client portal works
A simple workflow you can copy
- Bounce the mix and upload it once to a private, persistent link.
- Share the link with the client — no sign-up required to listen.
- Ask for timestamped comments instead of a general "thoughts?"
- Make revisions, upload the new version, and add a one-line changelog.
- When the work ships, send the invoice from the same place — or gate the final behind it.
Common mistakes to avoid
- Sending stems and the mix in the same dump — the client gets confused about what to review. Keep the review file separate.
- Letting feedback live in DMs. If it's not in one place, it's not tracked, and something gets missed.
- Delivering the final before the invoice clears. Preview-then-unlock protects you without making you the bad guy.
- Re-uploading on every request. Use a link that doesn't expire so old projects stay reachable.
Delivery isn't the boring part at the end. It's the part of the job the client actually experiences — make it feel as good as the mix sounds.
Levels Flow puts all four pieces in one link: a persistent client portal, timestamped feedback, automatic version control, and invoice-gated delivery. It's the setup we wanted in our own sessions.