# Pinecone Brand Voice

> Technical, high-performance, and authoritative, focusing on speed and effortless scale.

## Positioning
Pinecone is a fully managed vector database designed for developers and organizations building AI agents and semantic search. It positions itself as the infrastructure layer that provides "knowledge" and "memory" to AI at any scale.

## Voice principles
*   **Performance-Obsessed:** Uses specific technical metrics (p99, 100ms, 1B vectors) to prove reliability rather than using vague adjectives.
*   **Direct and Functional:** Employs short, punchy sentences that prioritize utility and speed of understanding.
*   **Automated and Effortless:** Emphasizes that the system handles the complexity (no tuning, fully managed, rebalancing) so the user doesn't have to.
*   **Scale-Confident:** Uses language that suggests infinite growth (at any scale, billion-vector, scale effortlessly) to reassure enterprise users.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Visionary and outcome-oriented, focusing on what the user can "give" their AI. |
| Technical Specs | Precise and data-driven, using industry-standard latency and throughput terms. |
| Developer Onboarding | Action-oriented and command-based, focusing on terminal-ready instructions. |
| Enterprise/Pricing | Professional and compliant, emphasizing security standards and SLAs. |

## Lexicon
- **Use:** Knowledge, memory, scale, fully managed, vector throughput, p99 latency, effortless, isolated, semantic search, rebalancing.
- **Avoid:** "Easy" (use "effortless" or "no tuning required"), "Fast" (use specific latency metrics like "<100ms"), "Database" in isolation (prefer "Vector database").

## Messaging do's and don'ts
*   **Do:** Use active verbs like "Give," "Start," "Run," and "Monitor."
*   **Do:** Connect technical features directly to business value (e.g., "Lower costs," "Meet compliance").
*   **Do:** Mention specific integrations and standards (Claude, SOC 2, HIPAA).
*   **Don't:** Use flowery or metaphorical language; keep the focus on the data and the infrastructure.
*   **Don't:** Imply that the user needs to manage the backend; always reinforce that it is "fully managed."
*   **Don't:** Use "if" statements regarding scale; assume the user will scale (e.g., "at any scale").

## Evidence
*   "Give agents knowledge" (Outcome-oriented hero copy).
*   "Acknowledged in under 100ms, searchable within seconds" (Precision-based evidence).
*   "No tuning required" and "Index continuously rebalancing" (Effortless/Automated).
*   "Isolated memory for every agent, at any scale" (Scale-confident positioning).
*   "Start free, scale effortlessly" (Direct, action-oriented pricing).