Qualification
What counts as a qualified meeting
Qualified means the definition you write down before work starts. Not a generic lead score. Built for B2B software and services companies.
Qualification rules
Four steps. AI-assisted research and outreach, with human qualification review. Unknown or unverifiable criteria fail closed.
01
Agree the customer and the rules
Write down the ideal customer, the qualification criteria, and how the list is sourced: your target account list, or one built from your ideal customer profile. That agreement comes before any work.
02
Approve the list, then start
You approve the list. Outreach starts only after that approval, and it follows your written authorization and applicable law.
03
Book the meeting and hand it off
Meetings are booked only when they meet the written criteria, then handed off with the details your representatives need.
04
Invoice what was held
You are invoiced monthly at $500 for each qualified meeting that was actually held. A no-show is not a held meeting and is not billed. Your contract sets the attendance evidence and minimum duration that show the meeting was actually held. It cannot turn a no-show into a held meeting.
How the account list is chosen
Bring your target account list, or give us your ideal customer profile and we'll build the list. Either way, you approve the list before anyone is contacted.
You choose the accounts
The target account list is yours. It is shared only after a signed agreement, from storage you control, restricted to our business account. No attachments and no public links. If the file includes contacts, you confirm in writing that they may be used and that opt-outs are removed. List data is deleted when the engagement ends.
Built from your ideal customer profile
We research the list from sources whose terms permit the use, agreed in writing before anyone is contacted. You approve the list before anyone is contacted.
Illustrative only
A hypothetical rubric
A hypothetical for a software seller. It is not a client engagement, and title alone does not prove authority, budget, or intent.
| Requirement | Evidence needed | Disqualifier | Verified or unknown | Decision |
|---|---|---|---|---|
| Relevant buyer role | Named role that evaluates the software | No connection to the product decision | Checked before handoff | Fail closed if unknown |
| Agreed company profile | Size, sector, or stack named in the contract | Outside that profile | Checked before handoff | Fail closed if unknown |
| Stated reason to discuss the product | A concrete topic, not a generic introduction | No stated topic | Checked before handoff | Fail closed if unknown |
An unknown required fact does not get the benefit of the doubt. Use the blank worksheet to draft your own rows.