A qualified demo passes five tests. A human attended it. It took place on a date that has passed. The account is on your approved list. The attendee holds a title you agreed in advance. The call ended with agreed next steps. Blesso, a done-for-you B2B go-to-market service, counts demos this way, and a buyer can check every test from their own calendar.
Key takeaways
- A demo counts only if it passes all five tests. Four out of five is not a demo.
- Each test closes one specific way a provider can inflate its number.
- Verify the tests from your calendar, your CRM and your sales team's notes, not from the provider's dashboard.
- Agree the approved account list and the ICP titles in writing before the first sequence runs.
- Pair this checklist with a booked-versus-held clause in the contract. The two do different jobs.
Why a demo needs a definition
An outsourced appointment-setting provider is paid, or judged, on a number of demos. If the contract does not define the word, the provider defines it. The usual drift is quiet: a demo that was booked is counted as held, a held call with the wrong person is counted as qualified, and an account you never wanted is counted as pipeline.
The fix is a short checklist agreed before work starts. Blesso publishes its own on its how-we-work page, under the line "counted from your calendar, not our dashboard". This article walks through that checklist as five tests. The booked-versus-held contract article covers the legal wording. This one covers the qualification itself.
The five tests at a glance
| Test | The failure it prevents | Where you verify it |
|---|---|---|
| 1. A human attended | An empty room, a bot, or an auto-accepted invite counted as a demo | Your rep's notes, the call recording, the video tool's participant list |
| 2. The date occurred | A future booking counted as a result | The event date on your calendar |
| 3. The account is approved | Easy accounts outside your market counted as wins | The approved account list, matched to the invitee's domain |
| 4. The attendee matches ICP titles | A call with someone who cannot buy counted as qualified | The attendee's title on LinkedIn or in your CRM |
| 5. Next steps were agreed | A pleasant call that goes nowhere counted as pipeline | Your rep's follow-up email and the CRM next-step field |
Test 1: a human attended
Why it exists. A booking is an invite. An accepted invite is a click. Neither one is a conversation. This test says a real person from the prospect's side joined and spoke with your team.
How you verify it. Ask your rep who joined. If your video tool keeps a participant list or a recording, check it. An invite that shows "accepted" on your calendar proves nothing about attendance. A rep's note such as "Dana joined, 28 minutes, asked about SSO" does.
Common failure. The invitee joins for under a minute, or an assistant accepts and nobody appears. Agree a minimum yourself, for example a named prospect on the call for the real discussion, and write it down.
Test 2: the date occurred
Why it exists. A demo on next Thursday's calendar has not happened. Meetings in the future get cancelled and moved. A count that includes them overstates what you have received.
How you verify it. Filter your calendar to events dated before today. Count only those. Blesso's rule is that a no-show counts against the number: only held meetings count, not bookings.
Test 3: the account is on the approved list
Why it exists. The provider chooses who to contact unless you choose for them. Without a list, the easiest accounts to book fill the number, and they may sit outside the market you want to sell into. The approved list turns "any company that said yes" into "a company you wanted".
How you verify it. Keep the approved account list in a sheet you own. For each demo, take the domain of the invitee's email address and look it up. If the domain is not on the list, the demo does not count, however good the conversation was.
Common failure. The list grows quietly during the engagement. Fix this by treating additions as a change you approve, not an update the provider makes.
Test 4: the attendee matches the agreed ICP titles
Why it exists. A demo with an intern is a conversation with someone who cannot sign. Your ideal customer profile (ICP) names the roles that buy, such as a head of sales or a founder. This test holds the provider to those roles.
How you verify it. Read the attendee's title on their professional profile or in your CRM contact record. Compare it with the title list in your agreement. If your rep reports that the buyer joined later in the call, record that, and decide in advance whether it counts.
Common failure. Titles are vague. "Manager" can mean ten different things. Agree exact titles, or exact title families, in writing, before the first email goes out.
Test 5: next steps were agreed
Why it exists. A demo that ends with "we'll be in touch" has produced no commitment. This test asks for evidence that the prospect agreed to something specific: a second call, a trial, an introduction to a colleague, or a decision date.
How you verify it. Look for the follow-up email your rep sent and the next-step field in your CRM. If both are empty, the call did not produce a next step. This is the one test that depends on your team's own record keeping, so it only works if your reps log what was agreed.
A worked example (made up)
This example is invented to show the arithmetic. It is not a customer result. Say your provider reports 10 demos for the month.
| Step | Demos left | What you found |
|---|---|---|
| Reported by the provider | 10 | The dashboard total |
| After test 1 and 2 | 8 | One no-show, one still scheduled for next week |
| After test 3 | 7 | One invitee's domain is not on the approved list |
| After test 4 | 6 | One attendee is a coordinator, not an agreed title |
| After test 5 | 5 | One call ended with no agreed next step |
Five counted demos, not ten. Nothing in the provider's report was dishonest. The two sides simply used different definitions. Agreeing the five tests first removes that gap.
The sixth rule: the monthly cap
Blesso's published rules add one condition to the five tests: the demo must fall within the monthly cap. The cap is the monthly meeting target, which Blesso sets from your average contract value (ACV), your market and how narrow the list is, and agrees before month one. The cap keeps the target and the count on the same footing. It is part of the agreement, not a test of any single demo.
How to set this up before you sign
- Write the five tests into the agreement as a schedule, so you can update them without rewriting the contract.
- Share the approved account list and agree how additions are approved.
- List the ICP titles, exactly, and say what happens when the title is unclear.
- Name your calendar and CRM as the record of what counts, and say the provider's dashboard is a report, not the count.
- Agree targets before the first sequence runs. Blesso does this before month one.
Blesso counts demos from the customer's calendar and publishes the tests above on its how-we-work page. If you want to see how the five tests would apply to your market, you can book a call.
FAQ
Is a booked demo the same as a qualified demo?
No. A booked demo is an invite that was accepted. A qualified demo is one that was held and passed all five tests: a human attended, the date occurred, the account is approved, the title matches your ICP and next steps were agreed.
Who decides the approved account list?
You do. The provider can propose accounts, but the list is yours, and any addition should need your approval. If the provider can edit the list alone, the account test measures nothing.
What if the buyer joins the demo late?
Decide this before the engagement starts. A reasonable rule is that the demo counts if an agreed title joined for the real discussion, and your rep records that in the notes. Write the rule down so it is not argued case by case.
Can I check demo counts without the provider's dashboard?
Yes. Use your calendar for dates, your approved list for accounts, your CRM for titles and next steps, and your reps' notes for attendance. Blesso's rule is the same: demos are counted from your calendar, not its dashboard.