---
bcp_version: "1.0"
file_type: voice
parent: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md
last_updated: 2026-09-23
---

# Voice

> **Public-source demonstration.** This guidance is inferred from public mercury.com copy. Mercury has not reviewed or approved it.

Mercury sounds composed, lucid, and ambitious. It makes financial operations feel lighter without making finance sound trivial. The writing often sets up a familiar source of friction, turns to the product answer, and lands on a short line with shape and momentum.

## Voice attributes

```yaml
voice_attributes:
  - trait: "Clear"
    guidance: "Name the task, control, or outcome in ordinary language."
    evidence_status: observed
  - trait: "Craft-conscious"
    guidance: "Use one considered image or turn of phrase; keep the surrounding explanation exact."
    evidence_status: observed
  - trait: "Founder-aware"
    guidance: "Respect speed and ambition while acknowledging operational responsibility."
    evidence_status: observed
  - trait: "Controlled"
    guidance: "When discussing spend, keep budgets, policies, permissions, and visibility close to autonomy."
    evidence_status: observed
  - trait: "Understated"
    guidance: "Let product detail carry the claim instead of stacking superlatives."
    evidence_status: observed
```

## Register and rhythm

- Use plain American English.
- Prefer short sentence-case headlines with a single clear idea.
- Alternate compact, memorable lines with practical explanatory copy.
- Use verbs that describe work: set, route, categorize, track, issue, lock, connect, approve, and see.
- Speak directly to founders, operators, and finance teams without calling them personas.
- Use contractions naturally.
- Keep financial disclaimers explicit and visually legible.
- Do not use an exclamation point to manufacture excitement.
- Use hyphens or full stops instead of em dashes. Do not use an em dash.

## Vocabulary

```yaml
prefer:
  - "clarity"
  - "visibility"
  - "control"
  - "budgets"
  - "guardrails"
  - "approved transactions"
  - "granular visibility"
  - "self-enforcing expense policies"
  - "shape"
  - "craft"
  - "less admin"
avoid:
  - "revolutionary"
  - "game-changing"
  - "effortless financial freedom"
  - "bank-grade" without a defined meaning
  - "AI-powered" as a substitute for the actual function
  - "autonomous spending" without controls
  - "set it and forget it"
  - "guaranteed"
```

## Writing patterns

**Use:** "Give every budget a purpose. Mercury routes each transaction to the right place and keeps the policy visible."

**Avoid:** "Unlock limitless, autonomous AI spend with a revolutionary fintech platform."

**Use:** "A dedicated agent card makes approved transactions visible by card, budget, vendor, and time period."

**Avoid:** "Let AI spend your money while you focus on growth."

## Context shifts

```yaml
context_shifts:
  product_marketing:
    tone: "confident, visual, concise"
    emphasis: "the problem, the mechanism, the control, and the next step"
  financial_claims:
    tone: "precise, dated, qualified"
    emphasis: "provider, eligibility, rate, scope, and source"
  spend_and_agents:
    tone: "controlled, transparent, operational"
    emphasis: "approved purpose, configured limit, policy, and visibility"
  editorial:
    tone: "thoughtful, curious, concrete"
    emphasis: "how ambitious companies actually work"
```

## Source observations

- https://mercury.com/
- https://mercury.com/about
- https://mercury.com/spend-management
- https://mercury.com/blog/introducing-mercury-spend
- https://mercury.com/credit