Voice

The Prelude voice is the personality of a highly skilled security engineer who is also a trusted advisor.

We speak with the authority of someone who has seen the “offensive” side of security and knows exactly what it takes to defend it. We don’t use hype or “FUD” (Fear, Uncertainty, and Doubt); we use data and logic.

Voice Traits

Confident, but not Arrogant: We know our research is industry-leading, but we remain approachable. We speak in certainties because our platform provides them.

Scientifically Precise: We avoid vague marketing buzzwords like “unbreakable” or “military-grade.” Instead, we use specific technical terms (e.g., agentless visibility, configuration drift, adversary emulation) to build credibility.

Direct & Economical: Security professionals are busy. We get to the point quickly, using fewer words to deliver more impact.

Action-Oriented: We don’t just surface problems; we focus on the “prelude” to the solution. Our voice always points toward remediation and clarity.

Tone by Context

Default

Most marketing, product descriptions, and high-level dashboards.

The default tone is balanced and authoritative. We use active verbs and “Certainty” language.

Example: “Know with certainty that your EDR is configured correctly across every endpoint.”

Avoid: “We think our platform might help you understand your tools better.”

Errors and Support

Empty states, 404s, failed tests, and documentation.

The tone shifts to Direct and Helpful. We strip away all fluff to focus on the fix. We take responsibility for technical errors and provide a clear path forward for security gaps.

Example: “Validation failed. The host was unreachable via the specified integration. Check your API permissions and retry.”

Avoid: “Oops! Something went wrong on our end. Please try again later.” (Too casual/vague).

Success and Celebration

Completed migrations, 100% coverage milestones, and “Protected” states.

The tone is Empowering and Calm. We celebrate “Peace of Mind” rather than throwing a party. It’s a professional nod of approval for a job well done.

Example: “Environment Secured. All controls are performing as expected against known adversary tactics.”

Avoid: “You’re a rockstar! You just crushed those threats!” (Too informal for the high-stakes nature of the work).

Voice in Action

Scenario	Generic Security Voice	Prelude Brand Voice
New Threat	”Warning: New vulnerability discovered in the wild."	"CVE-2024-3094 detected. 12 of 84 endpoints running affected versions. Remediation available.”
Product Value	”Our software secures your enterprise."	"Know with certainty that your security controls perform against real-world adversary tactics.”
Data Report	”System scan complete. Issues found."	"Validation complete: 96.4% control coverage across 3 frameworks. 14 gaps identified.”

Writing Style Rules

• Perspective: Speak as “We” (Prelude, the trusted advisor) to the user’s “You” (the security professional).
• Terminology: Use precise security terms (adversary emulation, configuration drift, control validation) over generic alternatives.
• Formatting: Favor short paragraphs and bullet points. Security professionals scan before they read.
• Numbers: Use specific data points and percentages to reinforce certainty.

The “One-Question” Test

When writing for Prelude, always ask: “Does this sentence help the user feel more certain about their security posture?” If the answer is “maybe” or “no,” the copy needs to be more direct.