October 6, 2026

A probe says who it runs on, and starts with your back catalogue out

Admin

Turning on a paid enrichment probe used to mean one thing: an outbound lookup for every profile in the workspace. A workspace with fifty thousand profiles, most of them churned years ago, paid for fifty thousand lookups about accounts nobody was going to sell to again — and paid before seeing a single answer.

Every probe now has a Who it runs on section with two controls:

• Include profiles you already have. Off by default on anything that costs money. With it off, the probe runs on profiles that arrive from now on — your history is simply out of scope, and the estimate says so. Turn it on once you have seen what the probe returns and decided the history is worth paying for. Free probes start with it on; there is nothing to protect you from.
• Which profiles. On top of that: everyone, by lifecycle state ("New and Active" is the usual answer), recently signed up within a window you set, or a custom rule using the same builder the rest of the lifecycle uses.

The count under the control is live. Narrow the scope and watch the estimate shrink before you commit to it.

Try a probe on real profiles before you turn it on

Admin

Try it runs a probe on 5, 10 or 25 real profiles and shows every property it produced, the evidence behind each one, the ones it dropped and why, and what the calls actually cost. Each result is headed by the profile and the value that was actually sent — the email, the domain, the store URL the lookup read — so you can check the input before you trust the answer. The profiles are drawn from the scope you have set, so what you see is what the rest of the run will look like.

This existed before, but only for probes you wrote yourself — the four shipped probes, which are the ones most workspaces turn on, could not be tried at all. Now both get it.

Nothing is saved: no properties land, no ledger entry, no state. The calls are real and really charged, which is why it is a button.

Every property a probe produces, with what it holds

Admin

A probe's page used to list its output keys as a row of small grey chips, with the explanation hidden in a tooltip. Nine keys like product_count_band and last_published_at were about to become part of your profile vocabulary — in the scoring picker, the profiles table and every rule — with nothing anywhere saying what they held.

They are now a list: the name, the key, whether the value is meant for scoring, filtering or reference, and a line saying what it actually means.

The on/off switch moved to the probe's page

Admin

The Enrichment list is now a read — name, what it reads, who it runs on, what it costs, and whether it is on. Nothing on that screen spends money.

Turning a probe on is the one irreversible, billable act on the page, and it had been sitting on the screen with the least context: no binding, no scope, no estimate, no sight of what the probe produces. It now lives on the probe's own page, directly above the number it commits you to.

Enrich now works on a profile that has never been looked up

Admin

Enrich now on a profile only re-queued lookups that had already run at least once, so on a profile nobody had looked at — exactly the one you are most likely to be asking about — it quietly did nothing. It now queues the lookup properly, including for probes whose scope would normally exclude that profile: asking about one profile by hand is an override on purpose.