You cannot meaningfully qualify demand that has not declared itself.

Before a prospect responds, a connector mostly has hypotheses. A hiring change, a new contract, a past borrowing event, a technology migration, or a public expansion can make one account more reasonable to contact than another. None of those signals proves what the buyer needs today.

Signals are selection tools

A signal is useful when it helps narrow a market into a more relevant conversation list. It can improve timing and make the opening message specific. The mistake is treating the signal as a diagnosis: “this happened, therefore they need this product.” Businesses rarely work that neatly.

A company with a cash-flow signal might need working capital, longer supplier terms, invoice finance, a conventional loan, an equity solution, or no outside capital at all. The signal gives permission to ask a better question. It does not supply the answer.

Stage one: discover the live situation

Demand discovery is the work of finding and opening conversations with people who may have an active problem. It includes selecting a market, choosing evidence-based triggers, writing a relevant message, and giving the recipient a low-friction way to indicate whether the situation exists.

The goal of the first interaction is not to collect every qualification field. It is to establish whether there is enough real intent to continue. A short response such as “we are considering this in the next quarter” is not qualified yet, but it is new evidence that no database could provide.

Stage two: qualify against a mandate

Once someone raises a hand, the questions become specific. What are they trying to do? Why now? What scale, timing, and constraints apply? Who is involved in the decision? The exact fields must come from the provider’s appetite, not from a universal lead-generation checklist.

In the current SB Everyday funding route, discovery looks for businesses that may have a capital requirement. Only after a reply do amount, use of funds, timing, business context, and willingness to continue become relevant. The funding partner then conducts its own documentation and underwriting. A different niche would demand a different qualification map, even though the two-stage logic stays intact.

Outreach creates the opportunity to learn. Qualification turns what was learned into a decision about the handoff.

Why combining the stages creates poor outreach

If discovery and qualification are collapsed into one step, the first message often becomes a form disguised as an email. It asks for revenue, budget, timing, authority, documentation, and a meeting before the recipient has decided the conversation is relevant. Response falls, and the connector learns nothing.

The opposite failure is passing every positive reply immediately. That protects response volume but transfers all uncertainty to the partner. The healthier approach is sequential: earn the reply with relevance, then earn the introduction with qualification.

A simple operating funnel

  1. Mandate: define the provider’s exact appetite and exclusions.
  2. Market: identify accounts where the mandate could plausibly matter.
  3. Signal: choose evidence that improves whom to contact or when.
  4. Conversation: ask whether a live situation exists.
  5. Qualification: test the stated situation against the mandate.
  6. Introduction: transfer context when both sides agree to proceed.

This separation also makes performance easier to diagnose. If few people respond, the market, signal, message, or channel may be wrong. If many respond but few qualify, the signal may indicate curiosity rather than the right demand—or the mandate may be narrower than the campaign assumed. Those are different problems and should not be blended into one metric.

Begin with curiosity, end with precision

Good demand discovery is open enough to let the buyer correct your assumption. Good qualification is precise enough to protect both parties from an irrelevant handoff. The connector needs both disciplines, in that order.

Written by Souvik Bera, Founder of SB Everyday.

Next note: Context should travel