# voice.md

## Communication Style

### Overall Tone and Personality
Wagon's brand voice is **enthusiastic, confident, and helpful**, blended with a touch of **humility and gratitude**. It's primarily **solution-oriented**, acknowledging complex technical challenges with empathy before presenting clear, modern approaches. The personality is that of a knowledgeable, supportive peer or expert who is genuinely excited about empowering users and teams through data.

### Key Stylistic Elements and Patterns
*   **Direct and Engaging:** Addresses the audience directly using "you" and "your."
*   **Problem-Solution Focus:** Often frames content by identifying a common pain point ("It’s difficult to analyze...", "It’s a huge headache.") and then offering a clear, effective solution.
*   **Concise and Punchy:** Uses short, impactful sentences and phrases for emphasis ("Dead end.", "Modern ETL + modern SQL tools = win!").
*   **Technical but Accessible:** Integrates industry-specific terms (SQL, ETL, Redshift) naturally, assuming a technically savvy audience while ensuring the core message remains clear.
*   **Enthusiastic Exclamations:** Occasional use of exclamations to convey excitement and encouragement ("Gogogo!", "win!").
*   **Contractions:** Frequently uses contractions (e.g., "We’re," "it’s," "they’re") to maintain a friendly, less formal tone.
*   **Playful Technical Nods:** Incorporates subtle, humorous technical references (e.g., `INSERT INTO "Box" VALUES ('Wagon');`).

### Vocabulary Preferences and Word Choices
*   **Positive & Empowering:** "excited," "thrilled," "empowers," "unites," "better," "together," "proud," "humbled," "easy," "win."
*   **Problem-Solving:** "difficult," "cumbersome," "hard," "headache" (for problems) contrasted with "better approach," "easier," "help," "solve," "modern" (for solutions).
*   **Collaborative:** "together," "partner," "shared mission," "teams."
*   **Industry-Specific:** Leverages terms like "data analytics," "insights," "enterprise platform," "cloud data stores," "APIs," "ETL," "SQL" where appropriate.

## Content Patterns

### Common Themes and Topics
*   **Data Integration & Analytics:** The core theme revolves around making data accessible, analyzable, and actionable for teams.
*   **Solving Complex Technical Challenges:** Addressing the difficulties of working with disparate data sources, deploying applications, or choosing development languages.
*   **Collaboration & Team Empowerment:** Emphasizing how technology can unite teams and foster shared knowledge.
*   **Company Updates & Partnerships:** Announcements regarding product evolution, acquisitions, or strategic collaborations.

### Structural Approaches to Content
*   **Narrative Arc (Problem-Solution):** Begins by setting up a relatable challenge, explores common (often flawed) approaches, and then introduces a superior solution or partnership.
*   **Announcement Format:** For major news, a direct and clear statement, followed by context, expressions of gratitude, and practical next steps (e.g., FAQs, links to more info).
*   **Technical Deep Dives:** Provides insights into engineering decisions, processes, or best practices, often stemming from internal experience.
*   **Resource-Rich:** Includes internal and external links for further reading, related blog posts, partner sites, and community discussions.

### Call-to-Action Styles and Patterns
*   **Informational/Guidance:** Direct prompts to read more ("Please read our [transition FAQ]," "read Box CEO Aaron Levie’s [blog post]").
*   **Direct Product Interaction:** Encourages immediate engagement with the product or features ("give them a go," "open these queries right in the app").
*   **Exploratory:** Invites users to explore related resources or catalogs ("check out the current [catalog]").
*   **Community & Support:** Links to email and social media for continued interaction.

## Audience Interaction

### How the Brand Addresses its Audience
The brand addresses its audience as intelligent, technically proficient individuals who face real-world data challenges. It positions itself as a trusted guide and partner, speaking directly to their needs and aspirations.

### Level of Formality and Relationship Style
The relationship is **professional yet friendly and approachable**. It's less formal than an academic paper but more structured than a casual chat. The brand aims to be seen as a helpful expert, a collaborative partner, and a grateful supporter of its community.

### Engagement and Conversation Patterns
*   **Empathetic Acknowledgment:** Recognizes and validates user pain points and frustrations.
*   **Shared Vision:** Articulates a common goal or mission with the audience ("shared mission to make answering questions with data easy").
*   **Gratitude:** Expresses sincere thanks for support, feedback, and engagement.
*   **Openness:** Links to external discussions (e.g., Quora) and partner solutions, fostering a broader ecosystem view rather than solely promoting its own product.

## Guidelines & Examples

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

**DO'S:**
*   **Be enthusiastic and positive:** Convey genuine excitement about solutions and progress.
*   **Acknowledge challenges first:** Frame content by addressing a problem before presenting the solution.
*   **Use contractions:** Maintain a friendly, approachable tone.
*   **Be direct and clear:** Get straight to the point, especially in announcements.
*   **Integrate technical terms naturally:** Speak the language of the audience without being overly academic.
*   **Express gratitude and humility:** Thank users, partners, and supporters.
*   **Encourage further exploration:** Provide links to related content, FAQs, or partner sites.

**DON'TS:**
*   **Be overly formal or stiff:** Avoid jargon where simpler language suffices, but don't shy away from necessary technical terms.
*   **Sound dismissive of user problems:** Always show empathy for the challenges users face.
*   **Be vague or ambiguous:** Provide clear solutions and next steps.
*   **Over-promise or exaggerate:** Maintain a tone of confident realism.

### Example Phrases and Expressions that are "On-Brand"
*   "We’re excited to share that..."
*   "It’s a huge headache."
*   "The better approach is to..."
*   "Modern ETL + modern SQL tools = win!"
*   "We’re humbled by the support from our users..."
*   "Gogogo!"
*   "To understand your customers, you have to..."
*   "We’re proud of what we’ve accomplished."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** For company news, technical deep dives, problem-solution guides, and thought leadership.
*   **Marketing Landing Pages:** Concise, benefit-driven content often mirroring blog announcements.
*   **FAQs:** Detailed answers to common questions, especially for product transitions.
*   **Partnership Announcements:** Highlighting collaborations and integrated solutions.