# Wisdmlabs Brand Voice

> Professional, outcome-oriented, and technically authoritative with a focus on measurable performance.

## Positioning
Wisdmlabs is a high-end WordPress and WooCommerce agency that provides custom-tailored technical solutions for growth-focused global businesses. They specialize in complex ecosystems like LearnDash and high-impact plugins, moving beyond surface-level design to solve deep-seated performance and workflow issues.

## Voice principles
*   **Performance-Driven:** Focuses heavily on speed, growth, and measurable metrics rather than just aesthetics.
*   **Authoritative:** Establishes credibility through longevity (14+ years), ratings, and status as WordPress Core Contributors.
*   **Solution-Oriented:** Uses active verbs to describe solving specific technical pain points like "lag," "rigidity," or "flat engagement."
*   **Direct:** Uses concise, punchy headers and bulleted results to communicate value quickly.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Sophisticated and confident. Uses aspirational but grounded language. |
| Case Studies | Analytical and problem-solving. Contrasts "before" frustrations with "after" successes. |
| Service Pages | Functional and specific. Lists exact technical capabilities and engagement models. |
| Product/Plugin Copy | Benefit-focused. Explains exactly what the tool allows the user to do (e.g., "Let customers request quotes"). |

## Lexicon
- **Use:** Beautifully crafted, exceptional, custom tailored, high-impact, measurable outcomes, growth-focused, effortless, dependable, driving change.
- **Avoid:** Not evident from captured copy (though the brand avoids fluff and generic "cheap" marketing jargon).

## Messaging do's and don'ts
*   **Do:** Lead with data and social proof (ratings, years of experience, specific percentage gains).
*   **Do:** Use "Real" as a qualifier (Real Users, Real Traffic, Real Growth).
*   **Do:** Frame technical work as an "enabler" rather than just a service.
*   **Don't:** Use overly flowery language without backing it up with a technical benefit.
*   **Don't:** Focus solely on how a site looks; always mention how it performs or scales.
*   **Don't:** Use passive voice when describing improvements (use "Unlocked," "Removed," "Rebuilding").

## Evidence
*   "Website Experiences Beautifully Crafted."
*   "Our Bar Is Simple: Websites Should Feel Effortless For Users, And Stay Dependable For Teams."
*   "Fixing What Speed Tests Miss: Rebuilding Performance For Real Users"
*   "4x User Engagement, +65% Visibility"
*   "Custom tailored tech solutions scaling from robust infrastructures"