ReadyCustomer Guide

What makes a qualified customer opportunity

A qualified opportunity is a request that matches a participating business’s defined criteria well enough to be worth routing. It is not a guaranteed sale.

Core qualification signals

ReadyCustomer evaluates requests against the buyer’s stated ICP. Common signals include:

  • Service fit — the requested work matches what the business offers.
  • Geography — the location is inside the business’s service area.
  • Timing — the need is within a usable window (for example, flooring within 60 days).
  • Economic value — budget or expected deal size meets the minimum the business set.
  • Reachability — a valid contact method and consent exist.
  • Request quality — enough detail to assess fit without guesswork.

A score or filter combination can be applied. For the flooring pilot, a request needs valid contact, consent, GTA/Ontario geography, timing within 60 days and a score of at least 70. Budgets below CAD $2,500 are typically disqualified when a budget is supplied.

What a qualified opportunity is not

  • A bulk contact list entry.
  • An impression or click.
  • A guaranteed closed sale.
  • Proof that the person will accept a quote or complete a purchase.

The participating business owns follow-up, quoting, sales and fulfilment. Outcomes vary.

Why the distinction matters

Businesses pay for the opportunity because the qualification step reduces time spent on irrelevant inquiries. The value is in the match quality, not in volume of raw names.

For businesses

Define the criteria that matter

Tell us the service, geography, timing, minimum value and contact requirements that make an opportunity worth your time.

Define my ICP

Frequently asked questions

Does qualification guarantee a sale?

No. Qualification improves the chance the request is relevant. The sale depends on the business’s process and the customer’s decision.

Can rules change by category?

Yes. Pilot rules are refined as real outcomes are observed. Formal policies should be set once there is enough data.

What happens to non-matching requests?

They can be stored but are not routed in the current flooring-focused matching. They remain unmatched.