The Hardest Mile Is Not Doing the Work. It Is Creating the Appetite for It.

Big Idea 02 from MSP to MVP. Why "our clients don't want strategy" is a symptom rather than a verdict, and how fluency changes what clients ask you for.

Every MSP has delivered a project that transformed a client's operation. The work itself, whether the migration, the security program, or the automation, was never the hard part. The hard part came before it: getting the client to want it.

Chapter 2 of MSP to MVP names this precisely. The hardest mile is not doing the work. It is creating the appetite for it. Most of the industry has quietly given up on that mile. Ask around and you will hear the same diagnosis delivered as settled fact: our clients skip QBRs, they have declined the strategy conversation, they just want things to work.

Read that again as a symptom instead of a verdict and it looks different. Every successful client already runs on technology. A client that does not treat technology as a strategic asset is not a client without appetite. It is a client whose appetite nobody has worked to create.

Stop inviting them to your meeting

Before any tool enters the picture, there is a structural problem worth fixing, because it costs nothing and most MSPs have never questioned it. The meeting is always yours.

Consider what a client experiences walking into the provider's meeting. They arrive predisposed to expect a pitch: some tickets reviewed, some things to buy. Senior people opt out entirely and send someone junior to take notes. The provider then reads the empty chair as proof that appetite does not exist.

Flip it. Invite yourself to the client's meeting. In their room, nobody frames the conversation for you, tailors it to you, or expects you to present anything. You are a fly on the wall while they talk about what is actually going on: real problems, in their own words, unfiltered by the vendor frame. That is where appetite comes from. It does not come from a better pitch. It comes from hearing what they would never think to tell their IT provider.

There is a sales truth buried in this that experienced operators eventually learn. The most selling happens when the selling stops. Get a client talking about their business and they will invariably surface their issues, pain points, and wish list. At that point the proposal is mostly feeding back what they told you. Done well, the conversation is the statement of work.

Fluency is not expertise

The reason MSPs default to their own meeting and their own agenda is comfort. The technical domain, with its stack, its abbreviations, and its roadmap slide, is defensible ground. Asking a business question you cannot fully answer is not.

That is exactly the question that changes your category. Picture the conversation: "I don't know what inventory velocity means in your warehouse, but it seems to matter. Walk me through it." No MSP has ever asked that client about inventory velocity, or supply chain exposure, or why their trucks idle for twenty minutes during every ERP update. The first provider to ask is not showing off expertise. They are showing genuine interest in the specifics. People are never reluctant on this topic. Open the subject of their own business and pride does the rest.

That is the crucial distinction the chapter draws. Walking in fluent does not mean walking in as an industry expert. Fluency is knowing the terms, the pressures, and the questions worth asking, enough to hold the conversation in their language. The provider who never crosses that line stays a generalist forever, pitching the same email migration to the law firm, the manufacturer, and the clinic. The provider who crosses it stops being compared to other MSPs at all.

The catch, historically, was cost. That kind of fluency took days of research per client, a luxury reserved for the biggest accounts, if it happened at all.

One URL, five minutes

That is the constraint the chapter's companion tool removes. Drop a client's website address into the Industry Trends Report and about five minutes later you are reading a briefing prepared for that specific client. It covers their industry's overview and the technology trends moving through it, with business impact and compliance implications. It covers the risks rising in that industry and the regulatory landscape, sorted by what actually applies to them. It closes with the practices their better-run peers follow, each with a quick win and a KPI attached. It exports to PPTX, ready for your branding.

Two things make this more than a research shortcut. First, it works in both directions. In a vertical you know well, the report reinforces the trust you have already earned, with pattern knowledge confirmed and current. In a vertical you do not know, it is a structured way to listen. The client may even correct something in it, and the correction is itself engagement. Second, clients do not care that the research was AI-assisted. What registers is that someone showed up prepared, specifically for them. Preparation reads as caring. The tool did not change the sincerity of that, only its cost.

There is a pattern among teams that adopt this. It stops being an occasional move and becomes process. Nobody goes into a sales call or business review without running it first, the way nobody walks in without checking the ticket history. Some run it on prospects before a first conversation. "Let me look at your site and put something together for you" is a first gift, not a pitch.

Why this matters more now, not less

There is an obvious objection. If AI can produce the briefing, the client can produce it themselves. They can, and that is precisely the point. When answers are commoditized, answers stop being the value. Anyone can ask the same question of the same model. What cannot be commoditized is a person who sits with your problem, listens, and steers toward an outcome. That is the partner function. MVP means most valuable partner, not the most automated vendor and not the most silent one. The technology's job is to make the human in the room fluent faster, not to replace the room.

This week

The move is deliberately small. Take the next client meeting already on your calendar. Run one report. Walk in with one industry insight they did not expect their IT provider to know.

If you want the full cycle, export the deck, put your branding on it, and send it ahead of the meeting with a single line: "Put this together for you. Does it match what you're seeing?" The question invites correction, and correction is a conversation.

In parallel, run the zero-tool version. Invite yourself to one client's internal meeting this month instead of inviting them to yours. Listen. Do not present. Ask one business question you genuinely cannot answer, and write down what you learn in the first ten minutes.

The hardest mile gets walked one conversation at a time. The difference now is that you can start every one of them already fluent.

Big Idea 2 of 12, from MSP to MVP: Building Unbreakable Partnerships in the Customer Success Era by Chris Day (Forbes Books, 2026). Previous: You Are a Good MSP. That Is Exactly the Problem. Next: The Loop and the Tie, on why the most durable growth is already inside your client base.