← Guides

Qualifying what comes in

The inbound qualification engine

A form with three fields to a verdict with its evidence, before anyone picks up the phone.

By Mike Hurley, founder of WarmUp. We built this for a company's book-a-call form. It is running as a pilot: it reads the CRM and writes nothing back yet.
Version 1.0. Last updated . About 7 minutes.

Motion
Inbound
Channel
Website
Steps
8

The inbound qualification engine: the route

Left to right: the form and the gaps it leaves, the engine, Stage 1 (is the pain there?), Stage 2 (is it big enough?), the verdict. Each stage decides by count: Stage 1 needs two of its three checks to pass, Stage 2 one of its two. An orange arrow is a yes. The two lines underneath carry every no to Not ICP and every unknown to Needs review. Each stage is drawn in full beside its step under "How to build it". Go to the stages in detail

  1. 1The form

    Identity · fill the gaps

  2. 2The engine

    Inbound qualification

  3. 3Stage 1: Is the pain there?

    Three checks

    2 or more of 3?

    • Yes: Two or more passes: on to Stage 2.
    • Unknown: Otherwise: Needs review.
    • No: Two or more fails: Not ICP, nurture.
  4. 4Stage 2: Is it big enough?

    Two checks

    At least 1 of 2?

    • Yes: Either check passes: In ICP, call now.
    • Unknown: Otherwise: Needs review.
    • No: Both fail with confidence: Not ICP, nurture.
  5. 5VerdictIn ICP, call now
    After the account verdict
    CRM write-backOff during the pilot
    • Flow
    • Pass, yes
    • Fail, no
    • Unknown

    An unknown never counts as a pass.

  6. An unknown never counts as a pass.
  • Flow
  • Pass, yes
  • Fail, no
  • Unknown
  • An unknown never counts as a pass.
In:
A name, a company and an email.
The engine:
Researches every submission, runs Stage 1 and Stage 2, and keeps the evidence for each answer. It reads the CRM. During the pilot it writes nothing back.
Out:
A verdict, the evidence behind it, and who to call.

Download the boardOpen it full sizeOne sheet, free to keep and share.

Why it helps

A short form gets filled in. Ask for a name, a company and an email and people book. Ask for a title, a website and a company size and fewer do. The cost of the short form lands on the rep, who opens the call knowing a name and an email address and spends the first ten minutes finding out whether the company is one you can help.

The engine does that finding out before the call. It turns the email into a company, finds the person's title, and runs five checks in two stages. The rep gets one of three answers with the evidence behind each check: call now, take a look first, or not a fit right now. A good account with the wrong person on the form is still flagged as a good account, with a note to reach someone else there.

What I cannot tell you yet is what it does to close rates. It is a pilot. The verdicts are being read by a person beside the calls that follow, and nothing is written to the CRM until the field names are approved.

Why we built it this way

  • Every check has three answers. Pass, fail or unknown, each with the evidence that produced it. A check that can only say yes or no has to guess when the lookup comes back empty, and the guess is invisible later.
  • Finding nothing is not a pass. The definition we started from let "no tool detected" count as a pass. A lookup that finds nothing mostly proves the lookup is thin. We changed it: two independent sources must both come back clean, and one of them must find a sign of the manual process. Clean and silent is unknown.
  • Pain first, size second. Stage 1 asks whether the problem exists at this company. Stage 2 asks whether the company is large enough for it to matter. A big company without the problem is not a lead.
  • Sizing is a soft gate. Revenue and spend are estimates. Stage 2 passes on either check and fails only when both fail with confidence. An estimate alone never parks a lead.
  • There is a third verdict. A free-mail address, a failed lookup or two sources that disagree all go to Needs review. A person taking a short look beats a confident wrong answer.
  • The person is checked after the account. The job title is tested against the buyer personas once the account has its verdict, so a junior person at a strong account does not sink the account.
  • The company profile is bought once. One enrichment feeds three checks. Your own map is read before anything is bought.

How to build it

  1. Write the checks down before you build anything. One file: each check, its sources, and what counts as pass, fail and unknown. The person who owns the definition of a good customer signs off on this file, not on the workflow.
  2. Fill the identity gaps first. Email to company domain. A free-mail address stops here and goes to Needs review. Name and company to a public profile and a job title. A title already in the CRM wins.

    A book-a-call form

    It asks for a first name, a last name, a company and an email. No title, no website, no company size. Short forms get filled in; the engine finds the rest.

    Identity · fill the gaps

    Email to company domain

    A free-mail address (Gmail, Yahoo) stops here and goes to Needs review.

    Name and company to job title

    Found on the person's public profile. A title already in the CRM wins if there is one.

    Domain to company profile

    Description, headcount, HQ, company page. Bought once and used by three checks.

    Your own map first

    If the company is already classified in your own table, reuse the segment. No cost, one classifier.

    In: A name, a company and an email.
  3. Read your own map before you spend. If the company is already classified, reuse its segment. Otherwise buy one company profile (description, headcount, HQ) and use it for every check that needs it.
  4. Run Stage 1. Three checks, each returning pass, fail or unknown with its evidence. The stage passes on two or more passes, fails on two or more fails, and is unknown otherwise.

    The problem is unsolved

    Is the company still doing by hand the job you sell a fix for?

    Source: A research agent and a technology lookup, two independent sources

    See note A

    Pass
    Both sources find no tool in place, and one finds a sign of the manual process.
    Fail
    Either source finds a tool that already does the job.
    Unknown
    Both clean but no sign of the manual process, or a source errored. Silence is not a pass.

    The right kind of company

    Is it in a segment you sell to?

    Source: Your own map, else a research agent, into one fixed list of segments

    Pass
    One of the segments you sell to.
    Fail
    One of the segments you have ruled out.
    Unknown
    Unclassified, or the evidence is thin.

    Enough people feel it

    Are there three or more people in the roles that live with the problem?

    Source: A count of public profiles by job title at the company

    Pass
    The count is 3 or more.
    Fail
    The count is a number below 3.
    Unknown
    The lookup returned nothing.
    2 or more of 3?
    Yes:Two or more passes: on to Stage 2.
    Unknown:Otherwise: Needs review.
    No:Two or more fails: Not ICP, nurture.
  5. Run Stage 2 only when Stage 1 passes. Revenue from enrichment, or implied by headcount with a range you have written down. Spend as a band with a confidence. A figure a rep confirms on a call replaces the estimate.

    Revenue in range

    Is revenue inside the band you can serve, and is it the right type of business?

    Source: Revenue enrichment, else revenue implied by headcount

    See note B

    Pass
    The right type, and reported revenue or the headcount band sits in range.
    Fail
    The wrong type, or both revenue and headcount sit outside the range.
    Unknown
    No revenue figure and no headcount.

    Spend in range

    Does the company spend enough each year on the thing your product touches?

    Source: A research estimate as a band with a confidence. A figure a rep confirms on a call replaces it.

    Pass
    Above your floor at high or medium confidence, or confirmed by a rep.
    Fail
    Well below the floor at high or medium confidence, or confirmed below it.
    Unknown
    Low confidence, the middle band, or no band at all.

    Sizing confirms the floor. It is not the reason you call.

    Stage 2 passes on either check and fails only when both fail with confidence. An estimate alone never parks a lead.

    At least 1 of 2?
    Yes:Either check passes: In ICP, call now.
    Unknown:Otherwise: Needs review.
    No:Both fail with confidence: Not ICP, nurture.
  6. Decide the verdict by rule. Both stages pass: in ICP. A stage fails with confidence: not ICP. Anything else: needs review. Then check the person's title against your personas.

    Verdict

    In ICP, call now

    Stage 1 and Stage 2 both pass. The rep opens the call with where it hurts, holding the evidence for each check.

    Needs review

    An undecided gate, a free-mail address, a failed lookup, or two sources that disagree. A person takes a short look before any call.

    See note D

    Not ICP, nurture

    Stage 1 or Stage 2 fails with confidence. Look again when a fact changes.

    The person is a separate check

    The job title is tested against your buyer personas after the account verdict. A title that maps to none of them fails. A good account with the wrong person is still worth a call to someone else there.

    CRM write-back

    Off during the pilot

    The verdict, each check's answer, the evidence and the persona are ready to write. Nothing is written until the field names are approved.

    Out: A verdict, the evidence behind it, and who to call.
  7. Keep the write-back off at first. Record the verdict, the five answers, the evidence and the persona in the workflow's own table. Have a person read them beside the real calls for a few weeks. Turn on the CRM write when the answers hold up and the field names are agreed.
  8. Give it a reader. Someone looks at Needs review every morning. Every wrong call becomes a change to the checks file, never a hand edit to one row.

One row

  1. Form: Dana, a work email, a 400-person machinery maker
  2. Domain found, title Director of Procurement
  3. Stage 1: 3 of 3
  4. Stage 2: 1 of 2
  5. In ICP, call today

Where we chose to be strict

Four judgment calls. Each belongs to whoever owns the definition of a good customer.

AA pass needs evidence
Finding no tool is not enough. Two clean sources plus one sign of the manual process pass. Clean and silent is unknown. (Design rule.)
BSize can pass on headcount
When no revenue figure exists, a revenue-per-employee range decides. Write the range down so everyone uses the same one. (Design rule.)
CSizing is a soft gate
It fails only when both sizing checks fail with confidence. Estimates are often wrong, and a wrong estimate should not cost you a real buyer. (Design rule.)
DA third outcome
Most scoring gives two answers. Needs review catches free-mail, failed lookups and sources that disagree. A person looking beats a confident wrong answer. (Design rule.)

Copy this

The checks file and the verdict rules

The shape of the file, with the thresholds taken out. Put your segments, your role titles and your ranges where the placeholders are.

# checks.yaml: every check answers pass | fail | unknown and keeps its evidence
stage_1:   # is the pain there?   pass on 2+ passes, fail on 2+ fails, otherwise unknown
  - check:   problem_unsolved
    sources: [research agent, technology lookup]        # two, independent
    pass:    both find no tool in place AND one finds a sign of the manual process
    fail:    either finds a tool that already does the job
    unknown: both clean but no sign of the manual process, or a source errored
  - check:   right_kind_of_company
    sources: [your own map, else a research agent]      # into one fixed list of segments
    pass:    a segment you sell to
    fail:    a segment you have ruled out
    unknown: unclassified, or thin evidence
  - check:   enough_people_feel_it
    sources: [count of public profiles by job title]    # your list of role titles
    pass:    3 or more
    fail:    a number below 3
    unknown: the lookup returned nothing
stage_2:   # is it big enough?   soft gate: pass on either, fail only when both fail with confidence
  - check:   revenue_in_range
    sources: [revenue enrichment, else headcount x your revenue-per-employee range]
    pass:    the right type of business AND revenue or the headcount band in range
    fail:    the wrong type, or both revenue and headcount outside the range
    unknown: no revenue figure and no headcount
  - check:   spend_in_range
    sources: [research estimate as a band with a confidence, replaced by a rep-confirmed figure]
    pass:    above your floor at high or medium confidence, or confirmed
    fail:    well below the floor at high or medium confidence, or confirmed below
    unknown: low confidence, the middle band, or no band
verdict:
  in_icp:        stage_1 passes and stage_2 passes
  not_icp:       stage_1 fails, or stage_2 fails
  needs_review:  anything else, and always for a free-mail address, a failed lookup, or sources that disagree
person:      title -> one of your personas, checked after the account verdict; no match = fail
write_back:  off until the field names are approved

The same guide as plain Markdown, for an agent or a notes app: /library/inbound-qualification-engine.md

This guide is the build. What we run when the signal fires, with the first line of the call, what waits for your yes and what you keep, is a signal play with its own page. See the signal play: A request from your website

Words we use

Check:
One question asked of a company or a person, with three possible answers: pass, fail or unknown. Every check keeps the evidence behind its answer.
Unknown:
The answer a check gives when it cannot tell. An unknown is never counted as a pass. It waits for a person or for a missing fact.
Verdict:
What a workflow decides after its checks, with the reasons. A person can always see why.
The map:
One table of companies, keyed on domain, with a status, a segment, a tier and a reason for each. Nothing is deleted from it. A status changes when a fact does.

Want your form qualified before the call?

We build it in your tools and run it with your team.

30 minutes to scope it. Engagements are contracted through WarmUp, Inc.