# mabl Brand Voice Guidelines

This document outlines mabl's communication style, tone, and patterns to ensure consistent and effective brand messaging across all content.

## Communication Style

### Overall Tone and Personality
mabl's voice is **confident, authoritative, and empowering**. We speak as an expert partner, guiding our audience towards innovative solutions. The tone is professional yet approachable, emphasizing a forward-thinking and solution-oriented mindset. We are:
*   **Visionary:** Highlighting the future of software development and quality.
*   **Empathetic:** Acknowledging the challenges faced by engineering teams.
*   **Action-Oriented:** Focusing on tangible outcomes and improvements.
*   **Trustworthy:** Backing claims with evidence and expertise.

### Key Stylistic Elements and Patterns
*   **Benefit-Driven:** Always connect features to clear benefits for the user or their team (e.g., "move faster with confidence," "reduce maintenance without sacrificing coverage or speed").
*   **Problem/Solution Framing:** Often starts by addressing a pain point before presenting mabl as the answer (e.g., "Don’t let code outrun confidence.").
*   **Strong Verbs:** Use active, impactful verbs (e.g., empower, validate, accelerate, investigate, release, adapt, merge).
*   **Clarity and Conciseness:** Avoid jargon where simpler terms suffice, but embrace technical vocabulary appropriate for our audience.
*   **Quantifiable Results:** Incorporate metrics and data, especially in customer stories, to build credibility.
*   **Repetition of Core Concepts:** Reinforce key ideas like "confidence," "speed," "quality," "AI-driven," and "agentic" throughout content.

### Vocabulary Preferences and Word Choices
We use precise, industry-specific terminology that resonates with our technical audience.
*   **Preferred Terms:** AI-driven, agentic, automation, quality engineering, continuous testing, CI/CD, DevOps, Shift Left, end-to-end testing, low-code, machine learning, software quality, validation, customer experiences.
*   **Avoid:** Overly casual slang, overly academic or abstract language without practical application.
*   **Focus on Outcomes:** Words like "faster," "reliable," "efficient," "trust," "empower," "innovative," "seamless," "intelligent."

## Content Patterns

### Common Themes and Topics
*   **The Future of Quality:** Emphasizing AI, agentic development, and intelligent automation.
*   **Developer/QE Empowerment:** How mabl helps teams achieve more with less effort.
*   **Speed and Efficiency:** Accelerating development cycles and reducing maintenance.
*   **Trust and Confidence:** Ensuring software quality and reliable releases.
*   **Modern Development Practices:** Integrating with Agile, DevOps, CI/CD workflows.
*   **Problem-Solving:** Addressing common challenges in testing and quality assurance.
*   **Customer Success:** Showcasing real-world impact and ROI.

### Structural Approaches to Content
*   **Hierarchical Headings:** Clear `H1`, `H2`, `H3` structure for readability and scannability.
*   **Introduction, Problem, Solution, Benefits, Call to Action:** A common flow for marketing copy and blog posts.
*   **Process-Oriented Breakdowns:** Explaining how mabl integrates into or improves a workflow (e.g., "Verification at every stage: Build, Validate, Investigate, Release").
*   **Data-Backed Arguments:** Using statistics, reports (e.g., Gartner), and customer testimonials to support claims.
*   **How-to Guides and Explanations:** For blog content, providing practical advice or defining complex concepts.

### Call-to-Action Styles and Patterns
CTAs are clear, direct, and vary based on the content's purpose:
*   **Direct Engagement:** "Book a Demo," "Try mabl for free."
*   **Informative/Educational:** "Learn More," "Read the full report," "Learn what good validation looks like →."
*   **Story-Driven:** "Read more about [Customer Name]."
*   **Action-Oriented:** Often using verbs that imply progression or deeper understanding.

## Audience Interaction

### How the Brand Addresses its Audience
We address our audience directly using "you" and "your team," positioning mabl as a partner that understands their needs and empowers them. The focus is on the collective success of "engineering teams," "developers," and "QA professionals."

### Level of Formality and Relationship Style
The relationship is **professional and expert-to-expert**. While not overly formal, we maintain a respectful and knowledgeable tone. We aim to be helpful, insightful, and inspiring, fostering a sense of trust and partnership rather than being overtly casual or overly academic.

### Engagement and Conversation Patterns
Engagement is built through:
*   **Addressing Pain Points:** Demonstrating an understanding of the audience's challenges.
*   **Offering Solutions:** Presenting mabl as the clear path to overcoming those challenges.
*   **Providing Value:** Through educational content, practical advice, and success stories.
*   **Empowering Language:** Using phrases that encourage action and highlight potential for improvement.

## Guidelines & Examples

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

**Do's:**
*   **Be Confident:** Speak with authority and conviction about mabl's capabilities.
*   **Be Clear and Concise:** Get straight to the point, especially in headlines and key messages.
*   **Focus on Benefits:** Always link features to tangible outcomes for the user.
*   **Use Technical Language Appropriately:** Speak the language of our audience without unnecessary jargon.
*   **Emphasize "Agentic":** Highlight the unique, intelligent automation aspect of mabl.
*   **Show, Don't Just Tell:** Use customer examples and quantifiable results.

**Don'ts:**
*   **Be Vague or Ambiguous:** Avoid generalizations; be specific about what mabl does and how it helps.
*   **Sound Overly Promotional:** Focus on value and solutions, not just selling.
*   **Be Overly Casual or Informal:** Maintain a professional and expert tone.
*   **Understate Impact:** Don't shy away from highlighting the transformative power of mabl.
*   **Use Buzzwords Without Context:** Ensure technical terms are used accurately and with purpose.

### Example Phrases and Expressions that are "On-Brand"
*   "Empower your team to build and release innovative software faster with AI-driven automation you can trust."
*   "Don’t let code outrun confidence."
*   "mabl agents continuously validate customer experiences across web, mobile, and APIs, so engineering teams can move faster with confidence."
*   "The quality system for agentic development."
*   "Keep validation moving with development so teams get trusted feedback without slowing down the build."
*   "Merge confidently. Release faster."
*   "Our agents keep tests current as software changes, reducing maintenance without sacrificing coverage or speed."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** How-to guides, explanatory articles on technical concepts, industry insights, product updates, customer stories.
*   **Marketing Copy:** Website landing pages, solution overviews, value propositions, benefit-focused descriptions.
*   **Case Studies/Customer Stories:** Detailed accounts of customer success, often with quantifiable results.
*   **Reports/Whitepapers:** Authoritative content like Gartner Magic Quadrant reports.
*   **Webinars/Events:** Educational and interactive content.
*   **Integrations Pages:** Highlighting compatibility and ecosystem fit.