# Elastic Brand Voice Guidelines

## Communication Style
*   **Tone and Personality:** The Elastic voice is **authoritative, precise, and action-oriented.** It reflects the personality of a technical leader—confident in its capabilities but grounded in practical application. The tone is professional and enterprise-ready, avoiding fluff in favor of clarity.
*   **Stylistic Elements:**
    *   **Action-First:** Sentences frequently begin with imperative verbs (e.g., "Collect," "Monitor," "Build," "Detect").
    *   **Conciseness:** Copy is stripped of unnecessary modifiers. The focus is on the "how" and the "result."
    *   **Technical Clarity:** Complex concepts are distilled into high-impact, functional descriptions.
*   **Vocabulary Preferences:** Use industry-standard terminology (e.g., "observability," "embeddings," "remediation," "telemetry") balanced with outcome-focused verbs like "accelerate," "optimize," "centralize," and "scale."

## Content Patterns
*   **Common Themes:** Search AI, data-driven insights, security, observability, and scalability. The brand consistently positions itself as the backbone for modern, AI-integrated infrastructure.
*   **Structural Approach:** 
    *   **Feature-Benefit Pairing:** Each product or feature is introduced with a clear functional purpose followed by the business outcome (e.g., "Zero operational load so that you can build faster").
    *   **Categorical Organization:** Content is structured logically by solution (Search, Observability, Security), making it easy for technical users to navigate to their specific pain point.
*   **Call-to-Action (CTA) Styles:** CTAs are direct, functional, and low-friction. They typically use a verb-noun structure: "Start free trial," "Download," or "Access report."

## Audience Interaction
*   **Relationship Style:** The brand acts as a **knowledgeable partner** to developers, architects, and IT decision-makers. It respects the user's intelligence by focusing on technical utility rather than marketing hyperbole.
*   **Formality:** Professional, neutral, and objective. It avoids overly casual slang or overly rigid corporate jargon, opting instead for the language of technical practitioners.
*   **Engagement:** Engagement is driven by providing immediate value—whether through a free trial, a technical whitepaper, or a feature explanation. The brand does not "sell" to the user; it "enables" the user.

## Guidelines & Examples

### Do's and Don'ts
*   **Do** prioritize speed and efficiency in your writing. Use short, punchy sentences.
*   **Do** focus on the technical outcome. Always explain *why* a feature matters to the user’s workflow.
*   **Don't** use vague marketing adjectives like "revolutionary" or "game-changing." Let the product’s capabilities speak for themselves.
*   **Don't** be overly wordy. If a sentence can be cut by 20% without losing meaning, cut it.

### On-Brand Examples
*   **Instead of:** "We have created a way for you to make your logs easier to manage."
*   **Use:** "Centralize and analyze logs to detect, investigate, and remediate incidents."
*   **Instead of:** "Our new tool is great for making your cloud experience better."
*   **Use:** "Zero operational load so that you can build faster."

### Content Types
*   **Product Descriptions:** Brief, benefit-driven summaries that highlight specific technical capabilities.
*   **Analyst Reports/Validation:** Leveraging third-party recognition (e.g., "Forrester Wave Leader") to establish authority.
*   **Technical Navigation:** Clear, categorized menus that allow users to find solutions based on their specific infrastructure needs.