Morning Ledger: Brand Voice Framework (Draft v1)

Voice at a glance

Morning Ledger treats coffee as a small daily ritual worth doing well. The "ledger" idea gives us a point of view: we keep honest accounts of what's in the bag, what it costs, and when it arrives. We sound like a dependable friend who happens to know a lot about coffee.

Position on the spectrums

• Formal ←–––●–→ Casual: leans casual, but tidy
• Simple ←●––––––→ Complex: plain language, with no jargon unless we explain it
• Serious ←––●––→ Playful: dry and warm, not zany
• Reserved ←–––●–→ Expressive: calm enthusiasm, saved for the coffee itself

Personality traits

Tone by channel

Website

Tone: clear, calm, and specific. This is where the ledger idea shows most.

• Lead with facts: roast date, origin, price, delivery cadence.
• Short sentences. Headlines state the benefit plainly.
• Make subscription terms (pause, skip, cancel) easy to find, in plain words.
• Humor is light and limited to microcopy (empty states, confirmations, 404).

Examples

• Hero: "Good coffee, on the calendar."
• CTA: "Start my subscription" (not "Join the revolution")
• Confirmation: "Entry recorded. Your first bag ships Tuesday."
• 404: "This page isn't on the books."

Email

Tone: personal, useful, and brief. It's like a note from someone who knows your routine.

• Transactional (orders, shipping, billing): the most straightforward. Information first, with a small touch of warmth.
• Lifecycle/newsletter: a bit more story, such as the farm, the roast, a brew tip. One idea per email.
• Problem or apology: own it quickly, with no spin, and say what we're doing. No jokes.
• Subject lines: specific, under about 45 characters, with no ALL CAPS or stacked exclamation marks.

Examples

• Subject: "Your October bag ships Tuesday"
• Subject: "A small price change, explained"
• Apology: "Your bag was late, and that's on us. We've refunded the shipping and sent a replacement."

Social

Tone: the most playful and conversational, though still dry rather than loud.

• Observational humor about mornings, routines and the first cup.
• Short captions. Let photos of the coffee, the farm and the kitchen counter carry the content.
• Reply like a person, using first names and real answers. Handle complaints publicly with empathy, then move to DMs for details.
• Emoji sparingly (☕ at most). Hashtags minimal.

Examples

• "Monday, itemized: 1 alarm, 2 snoozes, 1 very good cup."
• "Roasted yesterday. In your kitchen by Friday. That's the whole trick."
• Reply to a complaint: "That's not the experience we want you to have, Sam. Sending you a DM now."

Phrases and patterns to avoid

Hype and empty superlatives

• "Best coffee ever" / "world-class" / "game-changing" / "life-changing"
• "Revolutionize your mornings"
• "Premium quality" / "artisanal" without proof

Vague virtue claims

• "Ethically sourced" / "sustainable" / "ethically-made" with no specifics. Give numbers or leave it out.

Fake urgency and pressure

• "Don't miss out!" / "Last chance!" / "Act now!"
• "You'll regret it" or any guilt-based opt-out copy ("No, I don't like great coffee")

Coffee clichés and caffeine-addict tropes

• "But first, coffee" / "Rise and grind" / "Brew-tiful" / "Bean there, done that" / "Espresso yourself"
• "I can't function without my coffee" / "Fuel for your hustle"

Pretentious tasting language

• "Nuanced," "terroir-driven," "elevated," "curated" (unless explained simply)
• Unexplained jargon: "washed process," "cupping score" (explain it or skip it)

Subscription-industry dark patterns in copy

• Hiding cancellation ("Contact us to cancel")
• "Free trial" without stating when billing starts

Tone-deaf filler

• "We're so excited to announce…" / "Thrilled to…"
• "Hey coffee lover!" / "Hi there, friend!"
• "Oops!" for serious errors like billing mistakes

Mechanics: no ALL CAPS shouting, no more than one exclamation mark per piece, and avoid puns in subject lines.

Sample rewrites

Voice test

Before publishing, ask:

1. Could a competitor say this word for word? If so, make it more specific.
2. Is there a real number, date, or detail? Add one.
3. Would we say it out loud to a customer at the counter?
4. Is anything pushing the reader instead of informing them?

Next steps

The skill's workflow keeps the source of truth in docs/brand-guidelines.md, and I haven't written any files yet. Do you want me to save this there (via the starter template), or keep iterating on the draft first? Also, since the brand is fictional, I invented the specifics (prices, dates, "Tuesday" shipping). Swap in whatever you want to treat as canon.