# TestBox Brand Voice

> Direct, provocative, and technical, focusing on the "real" over the "fake."

## Positioning
TestBox is GTM infrastructure that generates realistic, interconnected data to power live demos and buyer sandboxes. It is built for B2B software teams who need to move beyond static click-throughs and "dummy data" to prove product value through actual functionality.

## Voice principles
*   **Provocative:** Challenges the status quo of "faking it" with blunt, punchy observations about the current state of sales demos.
*   **Technical & Grounded:** Uses engineering-adjacent language (infrastructure, data model, orchestration) to signal depth and reliability.
*   **Outcome-Oriented:** Focuses on the end goal of winning trust and closing deals rather than just the features of the tool.
*   **Concise:** Uses short, declarative sentences that get straight to the point without fluff or corporate jargon.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Bold and challenging. Uses high-contrast statements to highlight the "fake vs. real" dichotomy. |
| Product Features | Action-oriented and mechanical. Uses verbs like "Map," "Generate," "Orchestrate," and "Guide." |
| Customer Testimonials | Relatable and empathetic. Focuses on the pain of manual demo prep and the relief of automation. |
| FAQ / Technical | Authoritative and clear. Provides direct answers about lift, integration, and proprietary tech like the Product Graph. |

## Lexicon
- **Use:** GTM Infrastructure, Product Graph, realistic data, interconnected, orchestrate, buyer intent signals, technical validation, "stop faking it," foundational layer.
- **Avoid:** Click-through, screenshots, dummy data, vaporware, "talking your way to trust," Houdini (as a positive).

## Messaging do's and don'ts
*   **Do:** Use active verbs to describe what the AI agents do (simulate, guide, create).
*   **Do:** Call out the specific embarrassments of bad demos (old dates, "pretend this is zero").
*   **Do:** Frame the product as a "foundation" or "infrastructure" rather than just a "tool."
*   **Don't:** Use flowery marketing adjectives; keep the prose lean and functional.
*   **Don't:** Focus on the UI/visuals; focus on the data and the "actual product" experience.
*   **Don't:** Hedge with phrases like "we help you" or "easy to use." State what the platform does.

## Evidence
- "Stop faking it. Win with your actual product."
- "You're doing Houdini in the background."
- "Everyone claims 'AI-powered.' But you can't explain an agent. People have to drive it."
- "You don't need a better demo tool. You need infrastructure."
- "Scale technical validation, not environment maintenance."