Keep the evidence and offer consistent, but translate the consequence for the person responsible for the outcome. A founder may need speed and growth, a CFO may need control over financial and compliance risk, and a talent leader may need confidence that the change will not create a people problem.
Short answer: An MSP should keep the evidence and offer consistent, then explain the consequence for the person responsible for the outcome. A founder may care about speed and growth. A CFO may care about wasted money, compliance exposure and control. A talent leader may care about ownership and whether a change creates a bad hire. The pitch fails when it answers a question nobody in the room asked.
I learned this by sending the same pitch to two separate people at the same company: a founder and a CFO. The founder replied within the first three hours. The CFO never replied at all.
Same offer. Same words. Different result.
That was the problem.
One finding. Three different questions.
A founder sees a Microsoft 365 finding that former contractor accounts and broad application grants are still present and thinks speed. Close the old access before growth carries yesterday's permissions into the next customer.
A CFO sees the same finding and thinks risk. Which accounts can reach company data? What control will an insurance or finance review ask about? Who owns the cleanup, and what evidence will show that it happened?
A Head of Talent sees it and thinks, “Is this a people problem?” They need to know which guest or former-worker accounts are legitimate, who owns the review and how access can change without turning a routine control into a blame exercise.
None of those reactions is irrational. Each person is listening for the downside they will be blamed for if the decision goes wrong. The evidence did not change, but the person changed the question.
That is the MSP sales conversation SCOUTz is built to support. A customer-approved Microsoft 365 review can show supported identity, guest-account and application evidence without reading mail or files. The MSP keeps one source, one date and one boundary, then explains the consequence to the person who can act on it. The mistake is not lacking a better feature list. It is answering the wrong person's question. It is the same reason a better first sales meeting starts with the lead's question, not the MSP's stack.
Ask what this person gets blamed for
Before I write a line now, I ask one question: what does this person get blamed for if it goes wrong?
For a founder, the answer may be growth stalling. They want to know whether stale access or an over-permissioned app will slow the company down, consume scarce attention or keep the business from taking on the next customer.
For a CFO, the answer may be money wasted or a control failure. They need to understand the financial exposure, the cost of leaving it open, the cost of fixing it and the evidence that will show whether the work changed anything.
For a talent lead, the answer may be a bad handoff or an initiative nobody owns. They need a clear role, a manageable access change and confidence that the recommendation supports the people responsible for making it work.
The condition is still the condition. The source is still the source. The boundary is still the boundary. What changes is the consequence you put next to it and the next choice you offer.
Personalize the question, not the truth
Personalization is often reduced to mentioning the prospect's latest post or congratulating them on a funding round. That is decoration. Useful personalization is a fact about the prospect's environment that the person can verify, followed by the business question that belongs to them.
The same Microsoft 365 finding might produce three responsible openings:
- Founder: “Your tenant still has former contractor accounts and broad app grants. Which access path should we close before the next growth push?”
- CFO: “Your tenant has administrator accounts without enforced MFA. What control do you want documented before the next insurance or finance review?”
- Talent lead: “Your tenant has guest and former-worker accounts without a current owner. Who owns cleanup, and how should the team know what is changing and why?”
The evidence did not become three different findings. The MSP did not make three different promises. The explanation respected the person who has to act on it.
That is the distinction between personalization and spin. Spin changes the claim to make it sound urgent. Personalization keeps the claim honest and changes the question so the right owner can answer it.
The proposal should make the owner visible
If the first conversation goes well, the proposal should carry that same discipline forward. Name the condition, the source and date, the business consequence, the owner and the next decision. Do not hide a role-specific risk inside a generic “security improvement” line.
A founder may approve a short first engagement because it removes a growth blocker. A CFO may approve it because the scope and evidence make the financial exposure legible. A talent lead may approve it because the work has an owner and a change plan. Those are different reasons to say yes to the same responsible work.
The proposal is stronger when those reasons are visible rather than forced into one universal paragraph. The evidence-before-product approach keeps the conversation honest while the owner decides what matters.
Frequently asked questions
Why does the same MSP sales pitch work for one executive and fail for another?
Each person is accountable for a different downside. A founder hears speed and growth, a CFO hears spend and compliance risk, and a talent leader hears hiring and ownership risk. The offer can stay the same while the consequence and proof are made relevant to the person in the room.
What should an MSP say to a CFO during a sales conversation?
Start with the condition that creates financial, compliance or operational exposure, name the source and date, and explain what decision the CFO can make next. Avoid turning a technical finding into a fear claim or a promise of savings.
How can an MSP personalize a sales pitch without changing the truth?
Keep one evidence record and one honest boundary, then change the explanation of why it matters to that role. Personalization should change the question being answered, not the condition being reported.
What question should an MSP ask before writing a proposal?
Ask what this person gets blamed for if the decision goes wrong. The answer identifies the consequence your proposal must address and the owner who needs to agree on the next step.
Does SCOUTz create a different report for every executive?
No. SCOUTz keeps the source, timestamp, finding, limit and next choice connected. The MSP can use the same evidence in role-appropriate language without creating conflicting versions of the truth.
How SCOUTz gets you there
SCOUTz is prospect intelligence for MSPs. It keeps a dated finding, its source, its limit and the next question connected so the MSP can explain one condition to the founder, CFO or operating owner without creating three versions of the truth. The customer-approved Microsoft 365 review can show supported identity, guest-account and application evidence without reading mail or files. The work then moves into the MSP's chosen systems with the business consequence and responsible owner still attached. Point it at a prospect's tenant with consent, identify the question that belongs to the person in the room, and walk in with a reason.