# voice.md

## Communication Style

### Overall Tone and Personality
cside's communication voice is **authoritative, expert, and proactive**, yet also **approachable and reassuring**. We speak with confidence about complex security challenges, positioning ourselves as the definitive solution. While our content is often technical, we strive for clarity and directness, making sophisticated concepts understandable to our target audience. We are a trusted partner, not just a vendor.

### Key Stylistic Elements and Patterns
*   **Direct and Concise:** We use clear, impactful sentences that get straight to the point.
    *   *Example:* "Your WAF protects the server. cside protects your customers."
*   **Problem-Solution Framing:** We often introduce a critical security gap or threat, then immediately present cside as the essential solution.
    *   *Example:* "Your website could have been used to distribute this iOS exploit kit and you wouldn't have known. A full technical breakdown of Coruna..."
*   **Emphasis on Visibility and Control:** We highlight the "unseen" and "missing pieces" that cside reveals and secures.
    *   *Example:* "See the Unseen," "The missing piece in application security."
*   **Benefit-Oriented Language:** While technical, we always tie features back to tangible benefits like protection, prevention, compliance, and peace of mind.
*   **Active Voice:** We use active verbs to convey strength and direct action.

### Vocabulary Preferences and Word Choices
We blend precise technical terminology with accessible language to bridge the gap between complex security issues and practical solutions.

*   **Keywords:** `client-side security`, `browser-layer intelligence`, `script-based attacks`, `PCI DSS compliance`, `chargebacks`, `fraud prevention`, `real-time protection`, `visibility`, `device identity`, `exploit kit`, `CVEs`, `third-party scripts`.
*   **Strong Verbs:** `protect`, `prevent`, `detect`, `ensure`, `automate`, `inspects`, `analyzes`, `defeats`, `surfaces`, `monitor`, `secure`.
*   **Avoid:** Overly casual slang, jargon without context, fear-mongering without offering a clear path to resolution.

## Content Patterns

### Common Themes and Topics
*   **Client-Side Security Gaps:** Highlighting vulnerabilities in the browser layer that traditional security tools miss.
*   **Fraud Prevention:** Specifically focusing on chargeback prevention, credit card skimming, and job application fraud.
*   **Compliance:** Emphasizing how cside helps automate and ensure adherence to standards like PCI DSS, GDPR, and SOC 2.
*   **Technical Deep Dives:** Detailed analyses of specific exploits, attack vectors, and security mechanisms.
*   **The "Unseen" Threat:** Educating on the hidden risks posed by third-party scripts and sophisticated attack methods.

### Structural Approaches to Content
*   **Blog Posts:** Often begin with a real-world example or a startling fact, followed by a detailed technical breakdown, analysis, and implications. They conclude with a call to action for further reading or solution exploration.
*   **Marketing Copy:** Typically follows a problem-solution structure, starting with a bold statement about the challenge, introducing cside as the comprehensive answer, detailing key benefits/features, and reinforcing trust through compliance and partnership. Uses headings, subheadings, and bullet points for scannability.
*   **Educational:** Content is designed to inform and empower the reader, not just sell.

### Call-to-Action Styles and Patterns
Our CTAs are clear, direct, and offer multiple entry points based on the user's readiness.
*   **Primary CTAs:** `Start for free`, `Book a demo`, `Talk to an expert`.
*   **Secondary CTAs:** `Read more`, `View pricing`, `Visit our Trust Center`.
*   **Placement:** Prominently featured in navigation, hero sections, and at the end of content blocks.
*   **Urgency/Benefit:** Often implies immediate value or ease of access ("Start free, or try Business with a 14-day trial.").

## Audience Interaction

### How the Brand Addresses its Audience
We address our audience directly using "you" and "your," fostering a sense of personal relevance and direct impact. We speak to:
*   **Website owners/Operators:** Concerned about security, compliance, and user trust.
*   **Merchants:** Focused on preventing fraud and chargebacks.
*   **Security Teams/Developers:** Seeking advanced tools for client-side protection and incident response.

### Level of Formality and Relationship Style
We maintain a professional yet approachable level of formality. We position ourselves as a **trusted expert and partner** rather than just a vendor. The relationship is one of guidance and collaboration, especially highlighted by offerings like "1:1 access to our team over Slack and Microsoft Teams."

### Engagement and Conversation Patterns
*   **Direct Questions:** Implicitly or explicitly, we raise questions the audience is likely asking themselves ("What scripts run on your site?").
*   **Empathetic Understanding:** Acknowledging the challenges and complexities the audience faces.
*   **Partnership Language:** Emphasizing shared goals and continuous support ("Your Partner for Web Security," "Easy conversational support").

## Guidelines & Examples

### Do's and Don'ts for Brand Communication

**Do's:**
*   **Be clear and concise:** Cut unnecessary words.
*   **Lead with the problem, follow with the solution:** Frame content around solving specific pain points.
*   **Be authoritative and confident:** Speak from a position of expertise.
*   **Use precise technical terms when appropriate:** But explain them if they're complex.
*   **Highlight benefits over just features:** How does it help *them*?
*   **Emphasize partnership and support:** Show we're there for our customers.

**Don'ts:**
*   **Be vague or ambiguous:** Avoid jargon without context.
*   **Overly casual or informal:** Maintain a professional yet approachable tone.
*   **Use fear-mongering tactics without offering a clear solution:** Focus on empowerment.
*   **Overcomplicate explanations:** Simplify where possible without losing accuracy.
*   **Sound overly salesy or aggressive:** Our solutions speak for themselves.

### Example Phrases and Expressions that are "On-Brand"
*   "Security for What Runs in the Browser."
*   "Your WAF protects the server. cside protects your customers."
*   "The missing piece in application security."
*   "Stop script-based attacks, ensure PCI compliance, detect AI agents and prevent fraud - all from a single platform."
*   "Inspects every script before it reaches users, with zero latency."
*   "We solved the puzzle."
*   "Automate PCI 6.4.3 & 11.6.1."
*   "Your Partner for Web Security."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** Technical breakdowns, industry analysis, how-to guides, threat intelligence.
*   **Marketing Pages:** Solution overviews, feature lists, comparison pages, use cases.
*   **Webinars/Recorded Content:** Educational deep-dives, expert discussions.
*   **Case Studies/Testimonials (implied):** Showcasing real-world impact.
*   **Product Documentation/Trust Center:** Detailed technical information and compliance reports.