THE QUESTION THIS NOTE ANSWERS

When should an MSP discover a prospect's technical debt?

Before the agreement, while both parties can understand the work, price onboarding and remediation responsibly, change scope, or decide the relationship is not a fit.

What we read / what we never read

Public-domain evidence and customer-approved, read-only tenant evidence have different boundaries. No message bodies, files, chats, documents or prompts. Public availability is not blanket legal clearance; confirm scope and obtain qualified advice.

Read the evidence, its limitations and the next question to confirm. This article brief is not an assessment result.
When should an MSP discover a prospect's technical debt?

Before the agreement, while both parties can understand the work, price onboarding and remediation responsibly, change scope, or decide the relationship is not a fit.

The expensive version of discovery begins after the agreement.

The MSP wins the account, starts onboarding, and then discovers unsupported equipment, old servers, weak identity practices, application sprawl, missing documentation, sharing problems, licensing surprises, backup gaps, and years of deferred work.

Now the MSP has two bad choices: absorb remediation that was never priced, or begin the new relationship with an invoice the client never expected.

Price the work you can actually see

Public evidence can reveal questions about external posture, complexity, technology footprint, and possible technical debt. It cannot prove the internal condition. An authorized cloud review can add supported identity, application, permission, licensing, sharing, and managed-device context. It still carries coverage and source limits.

The point is not to label a difficult environment a bad client. It is to ask what it will actually take to bring the environment to a standard the MSP is willing and able to manage.

Discovery protects both sides

Better evidence gives the MSP a chance to price onboarding and remediation responsibly. It gives the prospect a chance to understand the work before signing the wrong agreement. And it gives both parties a chance to change scope, sequence the work, or decide the relationship is not a fit.

Do not buy the client's technical debt just to win its revenue.