If you deliver audio to clients, the work is not finished when the files leave your drive.

We keep seeing good sonic branding undone at implementation. The mark fires late on mid-range phones, sits at the wrong level against the showreel, replays on every page until the visitor mutes the tab. The client reads that as cheap work, not as a handoff gap.

Two things that changed how we scope:

→ Treat web implementation as a named deliverable in the proposal, not a favour after delivery. Either you do it, or you write the spec whoever builds the site has to follow. → Ship a short implementation note with the files. Where the sound belongs in the visit, target level relative to other site audio, frequency cap, mute behaviour.

It takes an hour, it protects six weeks of work, and it is billable.

Full version here: https://supadark.com/notes/sound-logo-web-implementation