@sellable/mcp 0.1.77 → 0.1.78
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -926,6 +926,9 @@ Required behavior:
|
|
|
926
926
|
economic capacity, competitor/vendor exclusion, and active current-role status
|
|
927
927
|
as table-stakes buyer-quality gates; include geography/market whenever budget,
|
|
928
928
|
channel adoption, language, compliance, or delivery assumptions depend on it
|
|
929
|
+
- customize the concrete thresholds for those gates to the client's offer,
|
|
930
|
+
market, price point, delivery model, and competitor landscape; the invariant
|
|
931
|
+
is that every passing lead should be worth the user's time if they reply
|
|
929
932
|
- do not turn "shown interest", post engagement, Signals source, recent posting,
|
|
930
933
|
provider source, or first-send priority into a production filter; those are
|
|
931
934
|
discovery or messaging context, not proof the lead is qualified
|
|
@@ -10,6 +10,12 @@ to buying." A lead who may reply but cannot buy, lacks budget, sits at the wrong
|
|
|
10
10
|
account type, is a vendor/competitor, or is on the wrong side of a marketplace
|
|
11
11
|
is not a good lead.
|
|
12
12
|
|
|
13
|
+
The exact qualification gates are client- and offer-specific, but the standard
|
|
14
|
+
does not change: anyone we reach out to, and anyone who replies, should be worth
|
|
15
|
+
the user's time to talk to. Use the client's price point, buyer, channel,
|
|
16
|
+
delivery constraints, market, and competitor landscape to define the concrete
|
|
17
|
+
gates for that campaign.
|
|
18
|
+
|
|
13
19
|
Source interest is not qualification. A lead who engaged with a post, appeared
|
|
14
20
|
in a Signals search, recently posted on LinkedIn, or "showed interest" in the
|
|
15
21
|
topic has only supplied discovery context. That context can justify the source
|
|
@@ -75,6 +81,13 @@ Confirmed production filters should fail closed on buyer quality. The default
|
|
|
75
81
|
confirmed filter set must explicitly include each table-stakes gate below, or
|
|
76
82
|
`lead-filter.md` must state why a gate is irrelevant for this campaign:
|
|
77
83
|
|
|
84
|
+
Customize the concrete threshold for each gate to the client and offer. For
|
|
85
|
+
example, "has money" might mean enterprise headcount for one client, funded
|
|
86
|
+
seed-stage team for another, multi-location practice size for another, or
|
|
87
|
+
existing tool spend for another. Do not hard-code Sellable's exact budget,
|
|
88
|
+
geography, or title rules into unrelated campaigns; hard-code the principle that
|
|
89
|
+
passing leads must be worth the customer's time.
|
|
90
|
+
|
|
78
91
|
- right role / function: the person owns or directly influences the buyer
|
|
79
92
|
problem; wrong-function leads fail even when they match the source topic
|
|
80
93
|
- right seniority / authority: the person can approve, pilot, champion, or
|