May 24, 2025
Conflict Checks Before the First Draft, Not After the Handshake
Running a conflict check after a proposal has already been drafted, sent, and verbally agreed to is a common sequencing error that turns a routine step into an awkward, relationship-damaging conversation.
Why the sequencing matters
A conflict discovered before any commitment is a routine, expected part of professional practice. A conflict discovered after a prospect believes the engagement is essentially settled is a much harder conversation, and it can damage a relationship that took real effort to build, even when the firm handles the disclosure properly.
Where to place the check
As soon as a prospect is identified as a serious candidate for outreach, not after a meeting, not after a verbal agreement, run the conflict check against current and past client relationships in the CRM. This should happen early enough that, if a conflict exists, the firm never sends outreach that later has to be walked back.
What this requires operationally
A conflict check depends on the firm's own client history being accurate, current, and easy to search, a name, an affiliated entity, an industry adjacency. If that internal record is not well maintained, the check itself becomes unreliable regardless of when in the process it happens. Getting the sequencing right matters less if the underlying data it checks against is incomplete.
Handling a conflict that surfaces anyway
Even with an early check, a conflict can surface later as new information comes in, a prospect discloses an affiliated entity the firm did not previously have on record, for example. When that happens, the least damaging response is prompt, direct disclosure to the prospect, explained plainly, rather than delay while the firm decides how to handle it internally. Prospects generally respond better to an early, honest disclosure than to a late one that looks like it was avoided as long as possible.
Keeping the internal conflict-check record itself current
A conflict check is only as good as how recently the underlying client and matter list was updated. A firm that runs checks against a list that is months out of date is effectively running a check that cannot catch anything that changed since the last update. Keeping that internal record close to real-time, even through a simple regular update process, matters as much as running the check at the right point in the outreach sequence.
A short note on how prospects tend to react to early disclosure
A prospect told plainly, early, about a potential conflict and how the firm plans to handle it generally reads the disclosure as a sign of good judgment rather than a red flag, provided the explanation is clear and the firm has an actual plan rather than just an apology. The tone of the disclosure matters as much as the timing.
A short note on the relationship between proposal quality and win rate over time
A single well-crafted proposal rarely explains a meaningful shift in a firm's overall win rate, since any one outcome is influenced by many factors outside the document itself. The more reliable signal comes from tracking a consistent standard, the swap test, the scope-and-assumptions discipline, applied across dozens of proposals over a year, and watching whether the aggregate win rate moves, rather than judging the standard by any single deal.
This longer view also protects a firm from overreacting to a single loss on an otherwise well-built proposal, since some prospects were never winnable on price or fit regardless of how the document was written, and a good process should be judged on its aggregate results, not on any one outcome it could not have controlled.
A final word on what separates a good proposal process from a good proposal
Any individual proposal can be improved with enough time and attention from a skilled writer. What is harder, and more valuable, is a process that reliably produces a good proposal under normal time pressure, for the tenth prospect of the month as well as the first. The tests and checklists described throughout this piece exist for that reason, to make the tenth proposal as sound as the first one, not to make any single document perfect.
Key takeaways
- Run conflict checks as soon as a prospect is identified, before any outreach goes out.
- A conflict found early is routine; one found after a verbal agreement damages the relationship.
- The check is only as reliable as the firm's own CRM data behind it.
- Sequencing this correctly avoids a specific, avoidable, and costly mistake.
Questions, answered
What is the short answer on Conflict Checks Before the First Draft, Not After the Handshake?
Conflict checks are a routine due-diligence step, but treating them as a business-development step rather than an afterthought avoids a specific, costly mistake.
What are the key takeaways?
Run conflict checks as soon as a prospect is identified, before any outreach goes out. A conflict found early is routine; one found after a verbal agreement damages the relationship. The check is only as reliable as the firm's own CRM data behind it. Sequencing this correctly avoids a specific, avoidable, and costly mistake.
How does VIPMarketing approach proposal automation?
VIPMarketing drafts each proposal from what the account is doing and your own library of past proposals, decks and case studies. Your approver signs off before it goes out as Word, PDF or PowerPoint.