# Runninghill Brand Voice

> Professional, collaborative, and results-oriented with a focus on long-term partnership and technical mastery.

## Positioning
Runninghill is a software development partner that provides custom digital solutions, technical consultation, and team augmentation for businesses looking to scale. They position themselves as an integrated extension of a client's team rather than a detached third-party vendor.

## Voice principles
*   **Collaborative:** Uses language that emphasizes partnership, integration, and shared vision.
*   **Ambitious:** Employs strong verbs like "transform," "elevate," and "scale" to signal growth and high-impact results.
*   **Technically Confident:** Speaks with authority about stacks and methodologies without becoming overly academic.
*   **Reliable:** Focuses on lasting relationships and meeting expectations through "vetted" and "skilled" expertise.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | High-level, aspirational, and focused on "vision" and "transformation." |
| Service Descriptions | Action-oriented and benefit-driven, explaining the "how" behind the "what." |
| Technical Stack | Competent and versatile, highlighting a broad "arsenal" of tools. |
| Blog/Thought Leadership | Insightful and generous, emphasizing the value of sharing knowledge. |
| Careers/Contact | Direct and welcoming, inviting professional engagement. |

## Lexicon
- **Use:** Transform, elevate, scale, partner, vision, lasting relationships, comprehensive, versatile, well-versed, integrated, roadmap, pathway.
- **Avoid:** Outsourcing (use "team augmentation" or "partner" instead), basic, cheap, quick-fix, temporary.

## Messaging do's and don'ts
*   **Do:** Emphasize that developers "feel like they are sitting right next to your team."
*   **Do:** Focus on the "long-term value" rather than just completing a sprint.
*   **Do:** Mention the synergy between aesthetics and robust backend functionality.
*   **Don't:** Position the service as a hands-off, "black box" development process.
*   **Don't:** Use overly passive language; keep the focus on "building," "architecting," and "maintaining."

## Evidence
*   "We establish lasting client relationships."
*   "You need developers who feel like they are sitting right next to your team."
*   "Bringing Your Vision to Life / Transforming Your Digital Presence."
*   "Meeting a sprint goal is expected. Designing software that keeps pace with future requirements is rare."
*   "Our skilled backend developers wield a vast arsenal of languages."