# Momentic Brand Voice

> Confident, pragmatic, and highly focused on engineering velocity and reliability.

## Positioning
Momentic is an automated, AI-powered testing platform built for engineering teams. It allows developers to write end-to-end tests in plain English, eliminating flaky tests and scaling coverage effortlessly so teams can ship faster with confidence.

## Voice principles
- **Action-oriented:** Starts with strong, imperative verbs to emphasize speed and productivity (e.g., "Ship fast", "Scale coverage", "Validate any assertion").
- **Pragmatic:** Focuses directly on solving real engineering pain points like test flakiness, constant maintenance, and false positives.
- **Data-backed:** Relies heavily on concrete metrics and customer outcomes to prove value (e.g., "80% coverage in 3 days", "85% reduction in production incidents").
- **Accessible but technical:** Speaks to engineers using industry terms (DOM, end-to-end, regressions) while emphasizing simplicity (plain English, natural language).

## Tone by context
| Context | Tone |
|---|---|
| Marketing hero | Bold, direct, and focused on speed and confidence. |
| Feature descriptions | Explanatory, benefit-driven, and technical but clear. |
| Case studies | Metric-heavy, objective, and impact-focused. |
| Footer/Taglines | Punchy and memorable (e.g., "Ship faster. Test smarter."). |

## Lexicon
- **Use:** plain English, natural language, intent-based, end-to-end coverage, regressions, false positives, ship faster, reliable, zero maintenance, AI-powered.
- **Avoid:** complex scripting, manual QA (when referring to the product's workflow), vague promises without metrics.

## Messaging do's and don'ts
**Do:**
- Highlight speed, reliability, and engineering hours reclaimed.
- Use exact numbers and percentages to demonstrate impact.
- Frame AI as a practical tool that empowers engineers and acts as a teammate.
- Emphasize the shift from exact code structure to user intent.

**Don't:**
- Overcomplicate the testing process in the copy.
- Focus on the AI technology without tying it to a concrete engineering benefit.
- Use passive voice for core actions or product capabilities.

## Evidence
- "Ship fast with AI testing"
- "Write tests in plain English"
- "No flakes, zero maintenance"
- "By tracking user intent instead of exact DOM structure..."
- "A test engineer that evolves with your product"
- "Focus only on real regressions"
- "85% reduction in production incidents"
- "Ship faster. Test smarter."