A producer ships a starter kit: sound logo, three length variants, a zip file. The client opens it, likes what they hear, uses the files — and six months later can't explain to a new hire why the notification chime sounds the way it does. Nobody wrote it down.
That gap is where retainer conversations die before they start. Turning a sound pack into a sonic branding retainer depends on the client trusting the producer as a system, not a one-time vendor — and trust needs something to point to besides a folder of WAV files. The starter kit doc is that thing.
Most producers skip it because it feels like the least musical part of the job. It's also the part that decides whether the relationship survives past delivery.
Why the One-Pager Is the Hardest Part of a Starter Kit
Sound design is a skill producers already have. Writing about sound design in a way a marketing manager can defend in a meeting is a different skill, and most producers have never been asked to build it.
The instinct is to describe the work the way it was made: "pitched down a minor third, layered a sub click under the transient, ran it through tape saturation." That's true and it's useless to the client. Nobody in a brand meeting is going to repeat "tape saturation" to justify a sonic choice to their VP.
The doc has one job: give the client language to defend the sound without needing the producer in the room. That reframing — from production notes to defense material — is what separates a starter kit that gets reused for two years from one that gets forgotten by the next campaign.
What Belongs in the Doc (and What Doesn't)
A starter kit doc is short by design. Three sections cover it:
The rationale. One paragraph per sonic decision, written in plain language: what the sound communicates, why that fits the brand, what it should never be confused with.
The variant map. A simple table matching each length variant (full, short, tag) to the format it's built for — app launch, ad pre-roll, notification — so nobody has to guess which file goes where.
The guardrails. Two or three sentences on what would break the identity: wrong pitch, wrong tempo, pairing it with the wrong visual motion. This is the section that prevents a well-meaning junior designer from remixing the sound logo into something unrecognizable six months later.
What doesn't belong: production specs, plugin chains, DAW screenshots, anything that reads like a session log instead of a brand document. That material has a place — a sonic brand guidelines document goes deeper into full systems for larger engagements — but a starter kit doc for a first client stays intentionally thin. One page, not ten.
Writing the Rationale in Brand Language, Not Producer Language
The rationale is the part clients actually read, and it's the part most producers write worst — because it's tempting to prove expertise by using technical vocabulary instead of proving it by making the reasoning legible.
A weak rationale: "The sound logo uses a rising major third to create positive valence, mixed at -14 LUFS for streaming consistency."
A working rationale: "The sound rises — it's built to feel like an opening, not a stamp. That matches a brand that wants to feel like it's inviting people in rather than announcing itself at them. It's mixed to sit comfortably next to music and voice, so it never has to fight for attention."
Both sentences describe the same sonic decision. Only one of them survives being repeated in a client's internal meeting without the producer present. The test for every line in the rationale: would this still make sense if the client read it out loud to someone who's never heard the sound?
A Simple Template You Can Reuse Client to Client
The doc doesn't need to be reinvented each time. A reusable structure keeps the writing fast and keeps every client kit feeling like it came from the same disciplined process — which is itself part of the pitch for retainer work.
One-line summary — what the kit delivers and where it lives (link or folder).
The sound, in one paragraph — what it is and what it's meant to feel like.
Variant map — full / short / tag, mapped to use case.
Guardrails — three sentences on what not to do with it.
Next steps — one line flagging what expands the kit later (new touchpoints, seasonal variants, a rollout across more formats — see how sound logos get rolled out across every touchpoint).
That fifth section does double duty: it closes the doc cleanly and plants the retainer conversation without turning the document into a pitch deck. The client reads a reference; they walk away already primed for what comes next.
A Worked Example
Templates read as abstract until they're filled in. Here's what section two and four might look like for a fictional coffee subscription brand:
The sound, in one paragraph: "The sound logo is a short rising motif built around two notes — it opens rather than announces. It's designed to feel like the moment a bag of beans is opened for the first time: brief, warm, unhurried. It works underneath a voice or a beat drop without competing for space."
Guardrails: "Don't pitch the motif down — a lower register reads as heavier and more corporate than the brand's tone. Don't loop or repeat it inside a single spot; it's built to appear once, not to carry a whole track. Don't pair it with hard-cut visual transitions — it's written to sit under a soft fade."
Notice what's absent: no key signatures, no BPM, no reference to the synth patch used to build it. A client — or a new hire with zero music background — can read both paragraphs and know exactly what the sound is for and what would break it. That's the bar for every line in the doc: could someone with no audio training repeat this back correctly in a meeting?
Formatting and Delivery — PDF, Notion, or Slide?
Format matters less than consistency, but it's not neutral. Three options cover most cases:
A one-page PDF works best when the client will forward it internally — legal, a new hire, an agency partner. It travels cleanly and doesn't require an account to open.
A shared Notion page works well for ongoing clients, especially ones already moving toward retainer, because it can be updated in place as the kit grows instead of being re-sent as a new file each time.
A single slide fits when the doc needs to sit inside a larger brand deck the client already maintains — common with startups building their first full identity.
Whichever format, the file name and the rationale language should stay identical to what ships in the kit. A doc that describes a "warm ascending chime" next to files literally labeled soundlogo_v3_final_FINAL.wav undercuts the professionalism the doc is trying to establish. Name files the way the doc describes them.
Mistakes That Undermine an Otherwise Good Kit
Writing the doc after the client asks for it. Waiting turns a proactive deliverable into a reactive scramble, and the writing quality shows it. The doc gets written during delivery, not after a follow-up email.
Explaining the "how" instead of the "why." Production detail belongs in a private working file, not the client-facing doc. If a line describes a plugin instead of a feeling, cut it.
Skipping the guardrails section. Without stated limits, every internal stakeholder feels free to reinterpret the sound however suits their slide. The guardrails section is what a producer on retainer actually gets paid to enforce later — write it down early so there's something to point back to.
Making it too long. A ten-page brand bible for a first-time client signals overkill, not thoroughness. Save the long-form system for a full sonic brand guidelines document once the relationship justifies it — the starter kit doc stays under one page.
FAQ
Do I need design skills to make this look professional?
No. A clean one-page layout in Notion, Google Docs, or Canva is enough. The writing does the work; the formatting just needs to stay out of the way.
Should I charge separately for the documentation?
Usually not as a line item — bundle it into the starter kit price as part of the deliverable, the same way a designer bundles a style guide into a logo project. It's part of what makes the kit worth the price, not an add-on.
What if the client never reads it?
Write it anyway. The doc's job isn't just persuasion in the moment — it's the reference that surfaces eighteen months later when someone new joins the brand team and asks why the sound is what it is. That's the moment it earns its keep.
How is this different from the rationale mentioned in the starter kit article?
That piece introduced the one-page rationale as part of the starter kit offer. This one is the practical how-to: what goes in it, how to write it, and how to format and deliver it so it holds up months after the files are opened.
