FindingcurrentRunning agents

Most B2B teams lack the deal volume a self-learning signal model needs

Below a vendor's outcome floor, learn per detector and call it human-tuned.

SymptomA signal or scoring tool promises a model that learns from your outcomes, and you close far fewer deals a year than its model needs.

Signal vendors describe self-learning models, and their own documentation states the outcome volume those models need. Salesforce's Einstein Opportunity Scoring asks for 200 won and 200 lost in two years, and vendors such as MadKudu also set minimum training volumes. The clinical rule of thumb is ten outcomes of the rarer class per model parameter.

Most teams selling large B2B deals close well under that floor, which buys one or two parameters. A per-account propensity model is out, and it answers the wrong question because it ranks accounts by the chance of an opportunity when the question is when and through whom.

Per-detector precision starts wide and stays wide. A detector that fires 20 times and precedes 2 meetings has precision 0.10, with a 95% interval (Wilson) of roughly 3% to 30%. Zero of 20 still allows up to 16%.

If your team is below that floor, priors do the first year's work and a person does the learning, so human-tuned is the honest label.

Targeting confounds the rest because reps work the accounts you scored highest, making every fit signal look predictive. A top fit tier can end up holding a large share of new opportunities simply because that is where the effort went.

Below that floor, a single detector's precision takes a long time to become measurable. Counting replies as a secondary outcome adds labels, at the cost of a proxy that can lie.

Check your setup read-only

Count your closed-won and closed-lost opportunities over the last 24 months. Compare the counts with the vendor's published training floor, such as 200 won and 200 lost. Below the floor, the model isn't learning from your data.

Passes ifYour closed-won and closed-lost counts both meet the vendor's published training floor.

Access needed:crm-read

If it fails: changes to make later (not part of the check)
  1. 01Learn precision per detector, not per account. Report precision with a 95% interval, never a point estimate.
  2. 02Write each detector's prior as pseudo-counts with its source. Let data outweigh the prior only once fires exceed the pseudo-count.
  3. 03Pool detectors into families so a family can learn where a single rare detector can't.
  4. 04Measure conversion only among worked accounts, never with raw opportunity counts. Use meetings per routed card and replies per touch as the measures.
  5. 05Route 2 below-threshold cards a week as a work-anyway slice, marked as exploration.
Applies ifYour CRM or a connected vendor tool scores accounts or signals with a model that learns from your outcomes.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.