# Peakflo Brand Voice

> Peakflo sounds like a high-performance, technical partner that prioritizes autonomous execution over simple automation.

## Positioning
Peakflo provides agentic AI workflows for global enterprises to automate and execute complex finance and business operations. It is designed for industries like Logistics, Manufacturing, and F&B that need to eliminate manual bottlenecks in AR, AP, and procurement without changing their existing tech stack.

## Voice principles
*   **Agentic and Autonomous:** Focus on the AI's ability to "execute," "decide," and "act" rather than just "help" or "assist."
*   **Quantifiable:** Uses hard metrics and "before vs. after" narratives to prove operational impact.
*   **Frictionless:** Emphasizes that the software adapts to the user (no manual mapping, no changing platforms) rather than the other way around.
*   **Authoritative:** Uses technical, industry-specific terminology (LLM-as-Judge, AR/AP, supply chain) to signal expertise in complex enterprise environments.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Bold and outcome-oriented. Focuses on "acceleration" and "execution." |
| Feature Descriptions | Technical and capable. Explains the "how" (AI agents, LLMs) with confidence. |
| Success Stories | Narrative and empathetic. Highlights the specific "manual struggles" faced before the solution. |
| Industry Solutions | Consultative. Addresses specific sector pressures like "rising financial pressures" or "complex supply chains." |

## Lexicon
- **Use:** Agentic workflows, execute, autonomous, acceleration, manual bottlenecks, LLM-as-Judge, self-evaluation, "without lifting a finger," seamless integration.
- **Avoid:** Manual mapping, rigid rule-setting, dashboards (when implying manual work), "traditional" automation.

## Messaging do's and don'ts
*   **Do:** Use active verbs that imply the AI is doing the work (e.g., "Peakflo executes," "AI agents browse," "Automate calls").
*   **Do:** Contrast the "Before Peakflo" manual state with the current automated state.
*   **Do:** Highlight that the system "learns" and "optimizes" itself continuously.
*   **Don't:** Suggest that the user needs to do heavy lifting to set up the system (e.g., avoid "map it all out manually").
*   **Don't:** Use vague promises; stick to specific improvements like "decision accuracy" and "process performance."
*   **Don't:** Imply that the team needs to change their tools; emphasize that Peakflo "meets them where they are."

## Evidence
*   "Agentic workflows that automate and execute"
*   "LLM-as-Judge... making each execution smarter than the last"
*   "Before Peakflo, [Company] had to manually..." (Success story pattern)
*   "Peakflo doesn't ask your team to change platforms"
*   "Forget dashboards that require manual input"