# Clockwork Brand Voice

> Clockwork sounds like a high-performance engineer: precise, urgent, and obsessed with maximizing efficiency.

## Positioning
Clockwork provides software-driven AI fabrics for enterprises and GPU cluster operators. It eliminates communication bottlenecks and infrastructure failures to ensure AI workloads run at peak capacity without stalling.

## Voice principles
*   **Urgent and Assertive:** Uses active verbs and absolute statements to highlight the high stakes of AI downtime.
*   **Technically Precise:** Employs specific industry terminology (TCO, Goodput, ROCm, Link Flaps) to establish authority with infrastructure experts.
*   **Efficiency-Obsessed:** Focuses relentlessly on the elimination of waste, whether it is "wasted GPU cycles" or "costly checkpoint restarts."
*   **Direct and Declarative:** Favors short, punchy sentences that state facts plainly without marketing fluff or flowery adjectives.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Bold and results-oriented. Focuses on immediate performance gains. |
| Technical Features | Analytical and problem-solving. Connects infrastructure issues to business impact. |
| Industry Validation | Authoritative and data-backed. Uses third-party metrics to prove value. |
| Call to Action | Direct and instructional. Encourages the reader to stop wasting resources. |

## Lexicon
- **Use:** Peak cluster utilization, software-driven AI fabric, never stalls, never sit idle, Goodput, fault tolerance, eliminate contention, communication bottleneck, GPU cycles, non-stop AI jobs.
- **Avoid:** "Seamless integration" (use "runs anywhere"), "Revolutionary" (use "software-driven"), "Easy-to-use" (focus on "performance" and "observability" instead).

## Messaging do's and don'ts
*   **Do:** Focus on the financial and temporal cost of failure (e.g., "avoid costly checkpoint restarts").
*   **Do:** Use active verbs like "eliminate," "guarantee," "prevent," and "maximize."
*   **Do:** Frame the network/communication as the primary hurdle to AI scaling, not the compute itself.
*   **Don't:** Use passive language or soft claims; Clockwork "eliminates" issues rather than "helping to reduce" them.
*   **Don't:** Focus on the "AI" as a creative tool; focus on the "AI workload" as a heavy industrial process.
*   **Don't:** Use generic tech jargon when a specific technical term (like "Link Flaps") is more accurate.

## Evidence
*   "AI that never stalls. GPUs that never sit idle."
*   "The Bottleneck in AI is Communication, Not Compute."
*   "Stop wasting GPU cycles. Start scaling smarter."
*   "Avoid costly checkpoint restarts and run nonstop AI jobs."
*   "Identify slow, inefficient or failing workloads."