The proposal is written before you open a blank document. Everything that makes a proposal specific — the client's environment, their timeline, their compliance exposure, the reason they're switching providers right now — comes from the discovery call. If the call produces vague notes, the proposal produces vague language. If the call produces structured, specific information, the proposal nearly writes itself.
Most MSP discovery call advice focuses on which questions to ask. That's part of it. But the more important question is: what information are you actually trying to capture, and how does it map to the sections of a winning proposal? Those are the questions this guide answers.
What a Discovery Call Is Actually For
Qualification is part of a discovery call, but it's not the primary purpose. You're not just asking whether the prospect has budget and decision-making authority. You're building the evidentiary foundation for a proposal that will make the client feel understood before they've asked a single follow-up question.
A well-run discovery call produces four categories of information:
- Environment facts — what they have today
- Business context and pain — why they're looking for an MSP right now
- Compliance and risk exposure — what's keeping them up at night
- Decision structure — who signs, who influences, what the timeline is
A proposal that draws on all four reads like it was written for this client. A proposal that only has environment facts reads like a quote. The difference in close rate is significant.
The Four Information Categories — and the Questions That Unlock Them
Category 1: Environment Facts
These are the technical facts that define scope. You need them to write the services section and the pricing. Without them, you're estimating instead of scoping.
Questions to ask:
- How many users are in your organization? Are they all in one location, or spread across multiple offices or remote?
- What devices are you managing — desktops, laptops, mobile? Roughly how many of each?
- Do you have on-premises servers, or are you primarily cloud-based?
- What are your primary line-of-business applications? (Ask specifically about industry verticals — clinical software, practice management systems, ERP platforms.)
- How old is your current hardware? When was it last refreshed?
- Who provides your internet connectivity, and do you have redundancy?
What you're capturing: The exact inputs for your scope section and pricing model — user count, device count, infrastructure type, application dependencies.
What to write down: Specific numbers, not ranges. "About 45 users across two offices — 30 in the main location, 15 remote" is usable. "Around 40-50 people" needs a follow-up.
Category 2: Business Context and Pain
This is where most discovery calls stay too shallow. The technical situation is only half the story. The business context — why they're looking now, what broke down with their current provider, what's changing — is what makes the executive summary of a proposal specific enough to close.
Questions to ask:
- What's driving the decision to look for an MSP right now? (Listen for the real trigger — a breach, a departing IT person, a compliance deadline, a failed project.)
- What's been the biggest frustration with your current IT setup or provider?
- If you think about the last six months, what IT-related issue had the biggest business impact?
- Where does IT create friction for your team right now? What are people complaining about?
- What does "good" look like in 12 months if we get this right?
What you're capturing: The executive summary of your proposal. The first paragraph of a winning proposal names the client's situation in their own language — their specific pain, their specific trigger, their specific outcome. You can only write that paragraph if you asked these questions and wrote the answers down.
What to write down: Direct quotes when you can get them. If someone says "We got hit with ransomware in January and haven't fully recovered," that sentence belongs in the proposal.
Category 3: Compliance and Risk Exposure
For any client in healthcare, finance, legal, education, or government, the compliance dimension of the discovery call determines whether you win or lose. Generic compliance language in a proposal disqualifies you with regulated clients. Specific, accurate compliance language signals that you've done this before.
Questions to ask:
- Are you subject to any industry regulations — HIPAA, PCI DSS, SOC 2, FINRA, CMMC?
- Have you had a HIPAA risk analysis completed? When was the last one? (Healthcare clients.)
- Do you have cyber liability insurance? What coverage requirements did the policy include?
- Have you experienced any security incidents in the past two years — ransomware, data breaches, phishing losses?
- Do you have any compliance deadlines coming up — audits, renewals, vendor assessments?
What you're capturing: The compliance premium tier, the specific regulatory language to use in your proposal, and the urgency signal that tells you whether compliance is a nice-to-have or a now-or-never priority.
What to write down: The specific regulation by name. Which certifications they have or lack. Any known deadlines. Whether a previous incident is creating urgency.
Category 4: Decision Structure
Proposals get approved by people you haven't met. The decision structure questions help you write for the right audience and navigate the process after you send.
Questions to ask:
- Who will be involved in evaluating and approving this decision?
- Is this a decision you'll make on your own, or will it involve your CFO, CEO, or board?
- What does your decision timeline look like? Is there a date you'd need to be in place by?
- Have you evaluated other MSPs? What's your process for comparing options?
- What's most important to you in making this choice — price, responsiveness, security depth, something else?
What you're capturing: How to pitch the proposal (business outcomes for the executive, technical specifics for the IT manager), who else might read it, and what the client's evaluation criteria actually are.
What to write down: Names and titles of other decision-makers. The stated priority (price vs. reliability vs. security). The deadline, if there is one.
The Note-Taking System That Feeds Your Proposal
Taking useful notes during a discovery call is a skill distinct from asking good questions. The goal isn't a transcript — it's structured information you can use in fifteen minutes when it's time to write.
A simple system that works: label your notes in real time with the section they belong to.
- [EXEC] — Notes for the executive summary (pain, trigger, desired outcome)
- [SCOPE] — Environment facts, user/device counts, application dependencies
- [COMPLIANCE] — Regulations mentioned, incidents disclosed, deadlines stated
- [PRICE] — Signals about budget sensitivity, competitive pricing context
- [CLOSE] — Decision-maker names, timeline, evaluation criteria
At the end of a 45-minute discovery call, you should have 8–12 labeled notes, not two pages of linear text. Those labels map directly to proposal sections.
Four Discovery Call Mistakes That Produce Weak Proposals
Asking too many closed questions early. "Do you have endpoint protection?" produces a yes or no. "What's your current security stack look like, and what gaps keep you up at night?" produces usable proposal content. Lead with open questions for the first half of the call.
Chasing technical rabbit holes. It's easy to spend 20 minutes on network topology when the CFO doesn't care about topology — they care about compliance and uptime. Reserve the technical detail for the scope confirmation, not the discovery.
Not asking why now. The timing of a prospect's search is almost always a signal you should name in the proposal. A contract expiring in 60 days, a breach last quarter, an IT person who just resigned — these are urgency drivers that make an executive summary specific and make the decision feel more immediate.
Not confirming numbers before ending the call. User count, device count, and location count are the minimum facts needed to write a scoped proposal. If you leave the call without confirming these, you'll send an estimate when you should be sending a proposal. Always end with: "Before we wrap up, can I confirm: [X] users, [Y] locations, [Z] servers?"
From Notes to Proposal
A discovery call that produces structured, labeled notes can feed a complete, client-specific proposal in minutes rather than hours. The executive summary comes from your [EXEC] notes — written in the client's own language. The scope comes from your [SCOPE] notes — specific enough to include exclusions. The compliance section uses the exact regulation you noted, not generic language. The pricing reflects the environment facts you confirmed at the end of the call.
The quality of your proposal is a direct function of the quality of your discovery. Better questions, better notes, better proposals — and a shorter gap between the discovery call and the proposal landing in the prospect's inbox.
ScopeMSP is built for exactly this workflow. Paste your discovery call notes — labeled or unlabeled — select the service type and the client's vertical, and get a structured, scoped, priced proposal in under 60 seconds. The note categories described in this guide map directly to what the system needs to produce a proposal that reads like you spent four hours writing it.