Reference file

Discovery red flags

discovery-red-flags.md

Discovery Red Flags: A Worked Example

These are disqualifiers from one operator's experience. Use them as a reference for building your own discovery checklist.

Hard disqualifiers — downgrade to Pass if confirmed

Each entry follows the skill's required structure: observed fact, why it disqualifies, and what it sounds like.

Founder-led despite company size

Observed fact: Single decision-maker with no delegation structure. Why it disqualifies: Decision authority remains concentrated with the founder, and the organization lacks the delegated cross-functional structure required for this type of diagnostic work. What it sounds like: "I handle most of the marketing and sales strategy myself."

Wants execution, not diagnosis

Observed fact: The ask is to run programs, not to examine the system. Why it disqualifies: The status quo is not being questioned. They want more capacity within their current approach, not a different approach. What it sounds like: "We just need someone to manage our demand gen."

No executive sponsor

Observed fact: The person on the call cannot authorize or name who can. Why it disqualifies: Without a sponsor, there is no one with standing to challenge the status quo and commit resources to change. What it sounds like: "I would need to run this by my boss."

Infrastructure less mature than it appeared

Observed fact: CRM is a database, not an operating system. Why it disqualifies: The system being diagnosed does not exist yet. This is a creation problem, not a status quo disruption. What it sounds like: "We use the CRM but most of the team tracks deals in spreadsheets."

Creation problem, not diagnosis

Observed fact: Building from scratch rather than repairing. Why it disqualifies: The status quo is absence, not friction. There is nothing to diagnose. What it sounds like: "We have never really had a formal demand gen program."

Cultural fit failure

Observed fact: Blame orientation or pattern of discarding outside help. Why it disqualifies: The organization is not willing to examine its own system honestly. Recommendations will not survive internal politics. What it sounds like: "Our last consultant didn't work out either."

Committee without a champion

Observed fact: No one owns the initiative. Why it disqualifies: Consensus-seeking without a driver means the status quo wins by default. Change requires someone willing to push. What it sounds like: "We all need to agree before we can move forward."

Business too small for system friction

Observed fact: No meaningful cross-functional handoffs. Why it disqualifies: The system friction this operator diagnoses cannot exist at this scale. The status quo may be suboptimal, but it is a people problem, not a system problem.

Watch / validate — probe before verdict

Budget without timeline

Probe: "What would need to happen for this to become a priority in the next 90 days?" Status quo framing: The status quo is tolerable enough that there is no forcing function. If vague: Watch. If they name a specific event: Continue.

Narrow scope disguised as interest

Probe: "Is this the only area where you are seeing friction, or is this part of a broader pattern?" Status quo framing: A narrow ask may mean the status quo is under pressure in one area (doorway to broader work) or may mean they want a tactical fix within the existing system (not a diagnostic engagement).

Building your own disqualifier list

Review your stalled deals. For each one, ask: what was the relationship between this prospect and their status quo? Were they genuinely dissatisfied, or were they exploring without real pressure to change?

The deals that stall most often are the ones where the status quo was tolerable. The disqualifier is not a characteristic of the company. It is a condition associated with the status quo winning.