# Pandium Brand Voice

> Pandium sounds like a pragmatic, engineering-first partner that prioritizes speed and control over marketing fluff.

## Positioning
Pandium is an integration platform for B2B SaaS companies that allows product, engineering, and partnership leaders to build and scale native integration marketplaces. It positions itself as the alternative to "vendor lock-in" by providing code-level access and infrastructure that works with existing developer workflows.

## Voice principles
*   **Efficiency-Focused:** Uses time-based metrics (days not months) to emphasize immediate value and speed to market.
*   **Developer-Centric:** Uses technical terminology (git repositories, auth management, code-level access) to build credibility with engineering teams.
*   **Empowering:** Focuses on what the user "can" do and "owns" rather than just listing platform features.
*   **Direct:** Uses short, punchy imperative sentences that get straight to the business or technical benefit.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | High-impact and results-oriented, focusing on speed and scale. |
| Feature Lists | Practical and benefit-driven, categorized by specific user roles (Product, Engineering, Partnerships). |
| Social Proof | Humble but confident, letting customer results (6x faster, 70% reduction) speak for the brand. |
| Pricing | Transparent and professional, emphasizing predictability and value calculation. |

## Lexicon
- **Use:** Days not months, code-level access, vendor lock-in, first-class, offload, scale, robust, predictable, "say yes".
- **Avoid:** No-code (unless as a contrast), magic, revolutionary, black box, proprietary language.

## Messaging do's and don'ts
*   **Do:** Emphasize that developers can use their own tools and languages.
*   **Do:** Connect technical actions to business outcomes like revenue attribution and cost reduction.
*   **Do:** Use active verbs like "Ship," "Launch," "Own," and "Scale."
*   **Don't:** Use vague buzzwords; stay grounded in the reality of the integration "plumbing."
*   **Don't:** Imply that the platform is a "no learning curve" tool for non-technical users; it is built for devs.
*   **Don't:** Over-promise on ease without mentioning the "code-level" control that engineers value.

## Evidence
*   "Launch integrations in days not months" (Efficiency-focused).
*   "Own Your Integration Code, Skip the Vendor Lock-In" (Empowering/Developer-centric).
*   "Say yes to more integration requests" (Direct/Benefit-driven).
*   "No learning curve for devs" (Role-specific clarity).
*   "We’ll handle the plumbing" (Pragmatic/Direct).