Year-end budget conversations that start with their number, not yours
The scenario:
Every October, MSPs draft proposals for next year's budget cycle based on what they think a client should spend, then find out in January that the client set a number three months earlier nobody asked about. Starting the conversation with their existing budget figure, rather than your proposed one, changes the negotiation from persuasion to fit.
This works because it removes the guessing game from both sides. A proposal built against a number you never confirmed is a guess dressed up as a plan, and clients usually tell the difference even when they do not say so directly. Asking the question early also gives you time to make the case for a bigger number, rather than finding out in January that the ceiling was set months ago without you.
The workflow:
Step 1 - Ask the budget question before you propose anything.
Ask your AI tool of choice to draft one simple question for your next client check-in: what has already been set aside for IT and security next year, before you present anything specific. Most MSPs skip this and guess instead.
-
Step 2 - Build two versions of your proposal, not one.
Once you know the range, ask your AI tool to draft a core proposal that fits inside their stated budget, and a second, slightly larger version framed as what becomes possible with a modest increase. Presenting both keeps the client in control of the final number.
-
Step 3 - Time the follow-up to their fiscal calendar, not yours.
Ask your AI tool to draft a short note confirming next steps, timed to land before whatever internal deadline the client mentioned for finalizing their own budget, instead of your own follow-up schedule.