# Opal Brand Voice

> Technical, authoritative, and decisive, speaking to security engineers as peers through the language of automation and code.

## Positioning
Opal is the programmable access platform and identity control plane for security teams that ship fast. It replaces manual, broken processes with just-in-time access and policy-as-code to eliminate standing risk across SaaS, cloud, and on-prem systems.

## Voice principles
*   **Action-Oriented:** Uses strong, imperative verbs to signal immediate impact.
*   **Technical & Precise:** Employs engineering metaphors (programmable, code, graph, script) to establish credibility with a technical audience.
*   **Direct:** Favors short, punchy sentences that cut through corporate jargon to address the "broken" reality of access management.
*   **Confident:** Positions the product as a definitive solution that "delights" users while "enforcing" security.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Bold and visionary. Focuses on high-level transformation (Stop/Start). |
| Feature Descriptions | Descriptive and functional. Uses technical terminology (JIT, UAR, Python-like). |
| Error States | Playful but brief. Uses industry-specific puns (identity crisis). |
| Call to Action | Direct and urgent. Focuses on seeing the platform or customer proof. |

## Lexicon
- **Use:** Programmable, Enforce, Just-in-Time (JIT), Standing risk, De-risking, Policy-as-code, Control plane, Deeper integrations, Identity intelligence.
- **Avoid:** Manual, Spreadsheets, Rubber-stamping, Patchwork, Static access, Legacy (implied by "broken").

## Messaging do's and don'ts
*   **Do:** Frame security as a programmable problem that can be solved with code and AI.
*   **Do:** Contrast the "old way" (spreadsheets, rubber-stamping) with the "Opal way" (automation, intelligence).
*   **Do:** Use active pairings like "Stop Reviewing. Start Enforcing."
*   **Don't:** Use vague marketing fluff; stay grounded in specific technical outcomes like "revoking the moment it's not needed."
*   **Don't:** Treat AI as a buzzword; describe it as a specific agent (Paladin) with a clear investigative role.
*   **Don't:** Use passive voice when describing access control.

## Evidence
- "Opal is the programmable access platform"
- "Stop rubber-stamping. Start de-risking."
- "Standing access is standing risk."
- "Your access policy, as real code."
- "Ask your access graph anything."
- "Sorry, we're having an identity crisis……" (Error state)