Outcomes Over Products & Where Your IT Partner Fits In

Introduction

During an internal content strategy session, our Executive Vice President, Mitch Martinez, said something that stopped us.

"The services we provide are the 'how', but the ‘why’ is always based on the customer’s desired outcomes. Too many IT vendors skip their customers ‘why’ entirely."  

Like many IT solutions providers, we’ve spent years perfecting our technical narratives, but that's not what our clients care about first. And frankly, it's not what makes us different.

What Your IT Buyers Actually Ask About First

Here's what we've learned after 25 years serving healthcare systems and government agencies across New York State: technical specifications are never the first conversation.

Before anyone discusses speeds and feeds, they want to know three things:

1. Can you keep our data secure?

In healthcare, this isn't theoretical. Patient records, research data, and operational systems all require cybersecurity implementations that meet compliance requirements. Government clients face similar pressures.

"When confidential information crosses the internet, encryption isn't optional. You need comprehensive security at the source all the way to the destination. No gaps, no exceptions."  

That's not marketing language. That's mission critical servicing.

2. What happens when things go wrong?

Every IT leader has lived through the 2 AM call. Server failure. Network outage. Ransomware attack. The question isn't if something will go wrong, but when, and what happens next.

The organizations we work with need to know that there’s a backup that can be turned on in a moment's notice and running as if nothing ever happened. Whether you're running cloud infrastructure, on-premise systems, or a hybrid environment, business continuity isn't a feature; it's a fundamental requirement.

3. Do you understand our actual requirements?

This is where most vendor relationships break down. Too many IT providers are product-pushers in consulting clothing.

Real partnership means understanding that a healthcare system evaluating new infrastructure isn't just buying servers. CIO’s are ensuring that radiologists can access imaging studies, labs can process results, and clinicians can document care without disruption. Government agencies aren't just upgrading networks, they're maintaining public services that communities depend on.

Product-pushers sell someone else’s solution; partners use products to build the bespoke outcomes you require.

‍

Why This Matters for Your Next IT Decision

When we engage with a new client, we're not asking "what do you want to buy?" We're asking "what do you need to accomplish?" The products and services we recommend flow from that understanding, not the other way around.

This is what we mean by outcome-focused delivery. We begin with your requirements and work backward to the solution. Security requirements? Address them first. Business continuity needs? Build them into the architecture from the start. Regulatory compliance? Make it foundational, not an afterthought.

‍

The Questions You Should Be Asking

If you're evaluating IT partners right now, here's what to ask before you review a single spec sheet:

• How do you approach data security?
• What's your methodology for ensuring business continuity?
• Can you walk me through how you've translated requirements into outcomes for similar organizations?
• What happens at 2 AM when something goes wrong?

The vendors who can answer these questions substantively are the ones worth having longer conversations with.

The ones who jump straight to product sheets? Keep looking.

‍

What We Got Wrong (And Right)

Looking at Derive, we’ve been understating what makes us a strong partner. Yes, we have deep partnerships across Microsoft, Cisco, Dell, and dozens of other leading vendors. Yes, we have the technical certifications and contract vehicles that matter for this kind of work.

But those are table stakes.

What isn’t is that we rebuilt NYC's Office of Emergency Management command center after 9/11. We supported citywide technology recovery during Hurricane Sandy. We understand the difference between uptime as a percentage and uptime as a mission-critical requirement when patient care or public safety is on the line.

That's the story we should have been telling all along.

‍

Your Outcomes, Our Methodology

We're not suggesting that technical specifications don't matter. Of course they do. Capacity planning, performance optimization, and infrastructure design are all critical to successful implementations.

But they're the how, not the why.

The right conversation starts with your requirements. Everything else follows.