> ## Documentation Index
> Fetch the complete documentation index at: https://handbook.polar.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Voice & Tone

> How Polar sounds, in writing

Polar sounds like a founder who's felt the exact pain the product solves. Who's duct-taped billing together at 2am, watched inference costs eat their margin, and wished something like this existed. That experience is the voice.

## Write like a developer

Short sentences. Active voice. No throat-clearing. Get to the point in the first line and stay there. If it can be said in five words, say it in five words.

## Have a point of view

Polar is opinionated. It knows what good billing looks like and isn't shy about it. Wishy-washy language, "we think," "we believe," "it might be" doesn't exist here. State the thing.

## Never sound like fintech

No compliance voice. No "we take security seriously." No "seamless payment experiences." No enthusiasm about money that feels performed. Revenue is the outcome, not the personality.

## Writing principles

**Lead with the thing.** Never bury the point. The first sentence of anything, a headline, a doc section, an error message, an email, should contain the most important information. Everything else supports it.

**Short sentences over long ones.** If a sentence has more than two clauses, break it. Complexity in ideas is fine. Complexity in sentences isn't.

**Active voice, always.** "Polar meters your usage" not "your usage is metered by Polar." The product does things. Write like it does.

**Specificity over generality.** "Bills per token" beats "flexible usage-based pricing." "Ships in an afternoon" beats "quick to implement." Concrete details are more convincing than abstract claims.

**Omit needless words.** Read everything back and cut every word that isn't earning its place. If the sentence works without it, remove it. Then read it again.

**Don't explain what's obvious.** Polar's audience is technical. They don't need "what is an API call" explained. Assuming intelligence is itself a form of respect.

**Humor is dry, never performed.** If there's wit in the writing it comes from precision and understatement, not exclamation points or forced personality. If you have to signal that something is funny, it isn't.

**Consistency in terminology.** Pick the right word for a concept and use it every time. Don't alternate between "usage event" and "consumption event" and "API call" to avoid repetition. Precision means consistency.