A Proposal Isn’t a Technology Strategy

By Dave Curley, Founding Partner, Lithan Advisory Group

A company decides it has outgrown its IT provider. Leadership asks around, meets four MSPs, and collects four proposals. Someone builds a comparison spreadsheet. Within a few weeks, the field is down to two.

It feels like a disciplined process. It isn’t, because the most important decision got skipped: what does the business need this relationship to accomplish?

When leadership leaves that question unanswered, the proposals answer it instead. Each provider fills the gap with its own assumptions about what the company needs. Leadership selects a provider and inherits the strategy embedded in its proposal, often without realizing a strategic choice was made. They picked the best-written document.

“Leadership selects a provider and inherits the strategy embedded in its proposal, often without realizing a strategic choice was made.”

That isn’t the provider’s fault. A good MSP can assess the environment, identify risks, and recommend sensible improvements, and that expertise should inform spending and priorities. But leadership still has to decide whether the next dollar supports expansion, reduces a particular operating risk, or waits because another business need deserves the money first. Those are strategic decisions.

Those unresolved choices show up throughout the comparison process.

A longer service list looks like a better answer. It only is if the services match the problem. More coverage can close a real gap. It can also duplicate tools the company already pays for. The list can’t establish value until the business knows what it needs covered and why.

Two monthly fees look comparable. One may include incident response while the other prices response separately. One assumes your team handles employee onboarding; the other assigns that work to the provider. Until responsibilities are clear, leadership is comparing prices for different work.

“Proactive” and “strategic” carry too much weight. When a proposal promises strategic guidance, the business should know which decisions that guidance is meant to help leadership make and how the recommendations will be evaluated. Without that agreement, the quarterly meeting becomes a status update with a better title.

A new provider inherits unresolved business decisions. The next MSP may fix real service failures. It still needs direction on priorities the company never settled. If leadership expects the provider to resolve those disagreements through its service model, the next relationship develops familiar problems under a different contract. Changing the provider does not break the cycle. Defining the strategy does.

The cost usually shows up as overlapping tools and projects that consume budget without advancing the priorities leadership cares about, plus management time spent revisiting decisions that never had a clear basis for approval.

Picture a CFO who wants predictable spending and an operations leader who needs room to expand into a new market. Both have a point. A provider can explain the technical options and their consequences. It cannot decide how the company should balance financial predictability against the flexibility to grow. No comparison spreadsheet resolves that disagreement either.

Someone has to make a business decision, informed by technical reality, before the company can fairly judge any proposal.

That is the work behind Strategy Before Services. Before providers are asked to propose solutions, leadership needs an agreed brief: what technology must accomplish, the constraints that should govern investment, and who decides when priorities collide. Technical expertise should inform that brief, including challenging assumptions that don’t hold up. The business retains ownership of the decisions.

Two providers can then recommend different solutions while responding to the same requirements, which makes the comparison worth something. The good ones will challenge the brief. A capable MSP may spot a dependency leadership overlooked or explain why the proposed timing creates unnecessary risk, and how a provider pushes back tells you more about its judgment than its service list does.

Leadership owns the direction, but turning it into a usable brief takes investigation, technical judgment and the discipline to settle competing priorities. It doesn’t have to do that alone. Independent advice helps because it isn’t tied to selling the technology services that follow. The MSP’s expertise stays essential, and its recommendations can be measured against requirements the business already owns.

Lithan Advisory Group does that work with leadership, and our partners have seen the MSP relationship from both sides of the contract. Dave Curley spent more than 15 years leading sales across MSP, SaaS and cybersecurity, so he knows how provider proposals get built. Greg Datz brings nearly 30 years of technology leadership: he founded and exited a managed IT and cybersecurity services firm, served as CTO of a cybersecurity services provider, and led enterprise-scale modernization programs. We have sold MSP services and we have run them. We help leadership set the strategy and define what providers are being asked to accomplish. We don’t sell, implement or take referral fees on the technology services that answer it.

So look at what you plan to hand the candidates. Does it explain what the business needs to accomplish and which decisions are already made? Or does it leave each provider to guess what matters? If you don’t have a brief, that’s your first finding.

If you’re preparing for an MSP renewal, considering a provider change, or questioning whether your current technology investments support the business, start with a free 30-minute Strategy Before Services: GRID Technology Decision Review. It examines how your business makes technology decisions today, before another proposal sets the direction.

Book your GRID review

Dave Curley is a Founding Partner of Lithan Advisory Group, where he helps leadership teams decide what technology must accomplish before any provider is asked to deliver it. He has spent more than 15 years in B2B sales leadership across managed services, SaaS and cybersecurity, so he knows how a technology proposal gets built from the provider’s side of the table. He is based in Westchester County, NY.