# Greptile Brand Voice Guidelines

This document outlines Greptile's communication style, tone, and patterns to ensure consistency and clarity across all brand content.

## Communication Style

### Overall Tone and Personality
Greptile's voice is **authoritative, confident, intelligent, and pragmatic**. We speak directly to highly technical professionals, valuing precision, innovation, and efficiency. Our tone is forward-thinking and sometimes provocative, but always grounded in deep technical insight and practical solutions. We aim to be seen as an indispensable partner for engineering excellence.

### Key Stylistic Elements and Patterns
*   **Direct & Concise:** We get straight to the point, avoiding jargon where unnecessary and fluff entirely. Our communication respects the time of our technically astute audience.
*   **Technical Depth:** We don't shy away from complex engineering concepts. Instead, we embrace them, explaining intricacies clearly and confidently.
*   **Data-Driven & Evidential:** Claims are backed by metrics, specific examples, and logical reasoning. We show, don't just tell.
*   **Benefit-Oriented:** Even when diving into technical details, we consistently tie back to tangible benefits for developers, engineering teams, and the overall software development lifecycle.
*   **Strong Headlines:** Our titles and headings are often declarative, question-based, or problem-solution oriented, designed to immediately engage a technical audience.
*   **Emphasis on "Agentic" and "Autonomous":** These terms are central to our product and are highlighted to convey advanced, self-sufficient capabilities.

### Vocabulary Preferences and Word Choices
*   **Technical Jargon:** We use industry-standard terms confidently: `codebase`, `PRs`, `LLMs`, `agents`, `sandbox`, `kernel level`, `semantic search`, `graph index`, `eval harness`, `dependencies`, `introspection builtins`, `validation layer`.
*   **Action-Oriented Verbs:** `catch`, `review`, `test`, `adapt`, `enforce`, `learn`, `integrate`, `autonomously`, `validate`, `resolve`, `outperform`.
*   **Benefit-Driven Adjectives:** `comprehensive`, `advanced`, `efficient`, `accurate`, `independent`, `autonomous`, `smart`, `seamless`, `critical`, `game-changing`.
*   **Confident Language:** We use strong, unambiguous language to convey conviction and leadership.

## Content Patterns

### Common Themes and Topics
*   **AI Code Review Evolution:** Discussing the state, challenges, and future of AI in code review.
*   **Agentic AI in Development:** Deep dives into how agentic AI solves complex software engineering problems.
*   **Technical Deep Dives:** Explanations of underlying technology, engineering challenges, and solutions.
*   **Product Updates & Features:** Announcements of new releases, capabilities, and pricing.
*   **Company Vision & Milestones:** Sharing our mission, culture, funding rounds, and brand evolution.
*   **Performance Benchmarks:** Demonstrating our effectiveness with data and comparisons.
*   **Security & Enterprise Readiness:** Addressing concerns for large-scale and sensitive deployments.

### Structural Approaches to Content
*   **Problem-Solution:** Frequently frames content by identifying a common developer pain point and positioning Greptile as the definitive solution.
*   **Numbered Lists/Steps:** Used for explaining processes, workflows, or key features (e.g., "How it works").
*   **Categorization:** Blog posts are clearly categorized (e.g., Engineering, Product, Announcement, Featured) for easy navigation.
*   **Testimonials & Case Studies:** Integrate social proof prominently to build trust and demonstrate real-world impact.
*   **Direct Announcements:** For major product launches, funding rounds, or significant company news.

### Call-to-Action Styles and Patterns
*   **Direct & Clear:** Our CTAs are unambiguous and action-oriented: `Start now`, `Contact Sales`, `Learn more`, `Get early access`, `View examples`, `Schedule a demo`.
*   **Benefit-Driven:** CTAs often imply a positive outcome or improvement for the user (e.g., `Start now` to elevate your code review process).
*   **Multiple Entry Points:** CTAs are strategically placed throughout content, offering various opportunities for engagement.

## Audience Interaction

### How the Brand Addresses its Audience
We directly address engineers, developers, CTOs, and engineering managers. We assume a shared understanding of technical challenges and present ourselves as a trusted expert and essential partner in their success.

### Level of Formality and Relationship Style
Our tone is professional and authoritative, yet accessible to a technical audience. It's not overly formal, but it maintains a serious, expert demeanor. The relationship is one of a solution provider to a discerning, highly skilled professional. We aim to be respected for our technical prowess and the value we deliver.

### Engagement and Conversation Patterns
We engage by providing valuable insights, solving complex problems, and demonstrating our capabilities. We encourage exploration and deeper understanding through phrases like `See more examples`, `Learn more`, and `Set your rules`. Testimonials serve as direct affirmations of user appreciation and success.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication
*   **DO:** Use precise, technical language where appropriate.
*   **DO:** Back all claims with data, specific examples, or logical, engineering-driven reasoning.
*   **DO:** Focus on tangible, measurable benefits for developers and engineering teams.
*   **DO:** Maintain a confident, authoritative, and forward-thinking tone.
*   **DO:** Be direct, concise, and efficient in your communication.
*   **DO:** Emphasize "independence," "autonomy," and "agentic" capabilities.
*   **DON'T:** Use overly casual, informal, or "bro-y" language that might undermine our authority.
*   **DON'T:** Make vague claims without supporting evidence or over-promise.
*   **DON'T:** Over-simplify complex technical concepts to the point of inaccuracy or condescension.
*   **DON'T:** Sound apologetic, hesitant, or uncertain.
*   **DON'T:** Rely on hype without substance.

### Example Phrases and Expressions that are "On-Brand"
*   "AI agents that review and test pull requests with full context of the codebase."
*   "Greptile outperforms them all by a mile. Honestly the only AI reviewer that doesn't annoy the s**t out of me." (Quoting a customer, but reflects our desired impact)
*   "It punches far above its weight class."
*   "Autonomously Test Every PR."
*   "The Central Validation Layer."
*   "Catches issues that human reviewers easily miss and giving senior-level suggestions to boot."
*   "We tested NVIDIA Nemotron 3 Super 120B on real PRs using our internal eval harness."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** Engineering deep dives, product announcements, industry commentary, company culture insights.
*   **Marketing Landing Pages:** Problem/solution narratives, feature highlights, testimonials, "how it works" explanations.
*   **Case Studies/Customer Stories:** Detailed accounts of how Greptile solves real-world problems for customers.
*   **Benchmarks/Performance Metrics:** Data-driven comparisons and proof of efficacy.
*   **Documentation:** Comprehensive guides and technical references.
*   **FAQs:** Addressing common questions about product, pricing, and security.