# TenTwentyFour Brand Voice

> A pragmatic, engineering-led voice that prioritizes technical reliability and transparency over marketing jargon.

## Positioning
TenTwentyFour is a Luxembourg-based software engineering firm that provides custom development, systems operations, and managed hosting. They serve businesses requiring high-reliability infrastructure and bespoke applications built on Free/Libre Open Source Software.

## Voice principles
*   **Methodical:** Focuses on the "how" of the process (testing, configuration, integration) to prove reliability.
*   **Transparent:** Uses plain language to explain technical choices and invites the client to verify work (e.g., "see for yourself").
*   **Pragmatic:** Emphasizes functional outcomes like "less bugs" and "lower total cost of ownership" rather than abstract innovation.
*   **Community-Minded:** References open-source values and a "geeks at heart" culture without being unprofessional.

## Tone by context
| Context | Tone |
|---|---|
| Service Descriptions | Technical and reassuring. Focuses on stability and "keeping IT up." |
| "Know-How" Sections | Educational and authoritative. Explains the bridge between operations and development. |
| Portfolio/Products | Descriptive and utility-focused. Highlights the specific problem the software solved. |
| About/Culture | Enthusiastic but grounded. Uses terms like "strive" and "passionate" alongside legal and technical credentials. |

## Lexicon
- **Use:** Proven, thoroughly tested, guarantees, nominal, bridge the gap, based on your story, Free/Libre Open Source, digital era, bespoke.
- **Avoid:** Cutting-edge, revolutionary, disruption, world-class, synergy (or other non-technical corporate buzzwords).

## Messaging do's and don'ts
*   **Do:** Mention specific methodologies like Test Driven Development (TDD) or Continuous Integration (CI) to build trust.
*   **Do:** Frame software development as a collaborative narrative (e.g., "software based on your story").
*   **Do:** Use "we" to take ownership of the monitoring and maintenance process.
*   **Don't:** Make vague promises; always link a feature to a concrete benefit (e.g., "tests first" leads to "less bugs").
*   **Don't:** Hide the technical complexity; explain the "why" behind containers or configuration management.

## Evidence
*   "We write tests first which guarantees that the software we develop... [is] proven to be working."
*   "Our monitoring solution allows us to catch anything... before it's too late."
*   "We create software based on your story."
*   "You don't have to take our word on that, you can see for yourself!"
*   "Geeks at heart, we not only work in Information Technology, we're passionate about it!"