New exports
- Mixhaus
- The desktop app watches export folders and captures new versions in the background.
- Typical alternative
- The engineer exports, names, uploads, and sends each file manually.
From mix export to client approval and final delivery
Mixhaus is a mix approval workflow for client projects. It captures exports, sends selected versions for review, collects feedback, records approval or changes requested, and supports final delivery from the same project.
Updated
Who it is built for
Engineers and studios who need formal approval before delivering masters, stems, or final packages.
Give every client project a clear next action and a recorded decision history.
How the workflow compares.
Each step from the first bounce to the approved master, with Mixhaus beside the way it is usually done.
| Workflow step | Mixhaus | Typical alternative |
|---|---|---|
| New exports | The desktop app watches export folders and captures new versions in the background. | The engineer exports, names, uploads, and sends each file manually. |
| Client review | The client opens a review room without an account, with the exact versions selected by the engineer. | Review often happens across file links, email, text messages, or a generic player. |
| Feedback | Written and timestamped notes stay attached to the version the client heard. | Feedback can arrive separately from the audio, making version context ambiguous. |
| Approval | The client approves or requests changes against a specific version. | Sign off is often inferred from a message, reaction, silence, or download. |
| Delivery | Approved files and deliverables are sent from the same project with a retained record. | Final delivery commonly moves to a separate transfer link or archive folder. |
Client review
- Mixhaus
- The client opens a review room without an account, with the exact versions selected by the engineer.
- Typical alternative
- Review often happens across file links, email, text messages, or a generic player.
Feedback
- Mixhaus
- Written and timestamped notes stay attached to the version the client heard.
- Typical alternative
- Feedback can arrive separately from the audio, making version context ambiguous.
Approval
- Mixhaus
- The client approves or requests changes against a specific version.
- Typical alternative
- Sign off is often inferred from a message, reaction, silence, or download.
Delivery
- Mixhaus
- Approved files and deliverables are sent from the same project with a retained record.
- Typical alternative
- Final delivery commonly moves to a separate transfer link or archive folder.
Where it fits, and where it stops.
Where Mixhaus is strongest
- The latest version shared with the client is explicit.
- Approval and requested changes are separate from casual comments.
- The final delivery package can be tracked against what was approved.
Where the workflow stops
- Mixhaus is not a DAW, live remote recording tool, or replacement for long term archiving.
- Client sharing is deliberate: captured exports stay private until an engineer sends them for review.
- Spatial audio review uses files supplied by the producer or engineer; Mixhaus does not create or certify a Dolby Atmos master.
Frequently asked questions
Something else on your mind? Email contact@mixhaus.app.
What is a mix approval workflow?
A mix approval workflow is the process of sending a mix for review, collecting feedback, making revisions, receiving a formal decision, and delivering final files.
Can Mixhaus show who approved a version?
Mixhaus records approval and request changes decisions against the project and version so the studio has a clearer history than scattered messages.
Can final files be delivered through Mixhaus?
Yes. After approval, Mixhaus can support final delivery from the same project, including a record of what was sent and downloaded.
Keep reading
Start your first project.
Create your account, install the desktop app, and send your next mix for review from one client project.