A new client every week. Each one needs a place to listen, leave precise notes, and download the final files. Stop running half of that in Drive, half in WhatsApp, half in "@1:23 the snare" voice memos.
Four phases. Repeat per project. No setup drag.
Six features that make rotating-client work tractable.
Send an invite from your dashboard. The artist gets a localized email (DE or EN, separately configurable), picks a password, and lands in their own portal.
v1, v2, v3, v7… all kept in history. The artist plays whichever they want; you can pin one as the current reference. Free plan: 3 versions total. Pro and Studio: unlimited.
Time-coded to the playhead. Replies nest under the parent comment, so a back-and-forth about "the snare at 1:23" doesn't become a flat list of disconnected notes.
The killer feature. Your client clicks v1 → v2 while the track is playing. No pause, no buffer reload, the playhead stays exactly where it is. They actually hear the difference.
A dedicated section for handing over final files: masters, instrumental versions, alt mixes. Each delivery is tied to the production, not floating in an inbox.
Both producer and artist can edit the lyrics on the same production. Every save is broadcast live — the other side sees the new text without reloading. Last-write-wins, so coordinate, but you stop emailing .docx files back and forth.
A built-in lyric helper (rhymes, synonyms, associations, metaphors) and an AI-generation detector, both rate-limited per plan. Free: 5 AI calls per day. Pro: 20. Studio: 100.
When your artist opens the player, every version of a track — v1, v2, v3 — is decoded into memory up front through the browser's Web Audio API. Each version sits on its own gain node, all of them wired to the same output.
Switching to another version is a single call: gain.setValueAtTime(0, ctx.currentTime) on the old version, gain.setValueAtTime(1, ctx.currentTime) on the new one. No HTML5 <audio> swap, no load(), no seek. The playhead position is preserved exactly. There is no audible gap.
Most browser-based players take a different route — one HTML5 audio element per version, which pauses and re-buffers on every switch. The Web Audio approach is what makes the playhead-preserving cross-fade possible.
Audio-collaboration and feedback tools we surveyed. The right-hand column summarises the field — if even one tool we looked at has the feature, we still mark it as "some". Retrieval date: 14 May 2026.
| Feature | CuePort | Other tools |
|---|---|---|
| Timeline-anchored comments | ✓ | ✓ |
| Threaded replies | ✓ | rare |
| Gapless mid-playback version A/B | ✓ | limited |
| Sessions calendar | ✓ | — |
| Permanent artist account | ✓ | magic link |
| Deliveries (masters + stems) | ✓ | ✓ |
| Reaper integration (sync script) | ✓ | — |
| Native German UI | ✓ | — |
| Free plan | ✓ | some |
Comparison summarises publicly available info from the pricing and help pages of each tool, retrieved 14 May 2026. "Limited" gapless A/B means competitors describe their version-switching as conditional, submenu-based, or do not document the underlying mechanism. We update this table when those sources change.
Free plan covers a small client list. Pro 6,99 € / month unlocks unlimited versions and 50 GB storage.