The Leonidas Promise: What Sets Our IT Services Apart

The Leonidas Promise is the short version of how we think IT services should work. It's not a slogan — it's the operating principle that determines how we hire, how we structure SLAs, and how we choose which engagements to take. The promise has three parts: we answer the call, we tell the truth, and we own the outcome. Everything else flows from those.

We Answer the Call

Responsiveness is the foundation of any service business. For an IT services provider, the difference between a 15-minute response and a 4-hour response on a critical issue is often the difference between a recoverable problem and a costly disruption. Our operating standard is that critical-priority tickets get human acknowledgment within 15 minutes, business hours or after. Lower-priority tickets follow SLA windows that vary by service tier but are tracked and reported transparently.

What that requires operationally is bench depth — enough engineers across multiple time zones and on-call rotations that someone is always available to triage. We've built that capability deliberately. It's not free, but it's the single most-valued attribute clients cite when they describe what differentiates Leonidas from previous providers.

We Tell the Truth

The second part of the promise is harder to operationalize than the first. Telling the truth in IT services means recommending the right solution even when it's smaller (and less profitable for us) than the alternative. It means saying "you don't need that" when a client asks about an over-engineered solution that wouldn't actually solve their problem. It means acknowledging when something went wrong on our end, instead of obscuring it. It means being clear about what's working and what's not in a client's environment, even when the news is uncomfortable.

This is the part of the practice that has the longest payoff. Truth-telling builds trust slowly, but it compounds. Most of our longest-tenured clients started with a single moment where they got an honest answer to a question they were expecting to be sold something on. That trust is the foundation everything else is built on.

We Own the Outcome

The third part is about taking real responsibility for whether the business problem gets solved, not just whether a ticket gets closed. A "fixed" ticket where the user is still struggling is not an outcome — it's a metric distortion. We measure outcomes against what the business needed, not against ticket-system fields. That shows up in practice as:

• End-to-end ownership — if your problem touches your ISP, your software vendor, and your hardware vendor, we manage all three coordinations until it's resolved
• Documented closure — every significant incident gets a written summary of what happened, what we did, and what's being changed to prevent recurrence
• Quarterly business reviews — not pitch decks, but real reviews of what's working, what's not, and what should change
• Willingness to fire ourselves — when an account isn't a good fit anymore, we say so and help with the transition rather than holding on for the revenue

Why These Three

You could draft a longer list of values, and many MSPs do — pages of bullet points that sound great in marketing copy but don't actually drive decisions. Three principles are easier to operationalize and easier to hold ourselves to. Every quarter we ask whether we're meeting all three; the gap between aspiration and execution is what we work on. If you'd like to see what that looks like in a working engagement, a free assessment is the simplest way to start. The conversation will tell you a lot about whether the promise translates into how we actually behave.