@sellable/mcp 0.1.87 → 0.1.89
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
|
@@ -611,6 +611,18 @@ Use customer-facing question wording:
|
|
|
611
611
|
- proof emphasis: `Which proof point would most increase this buyer's confidence in {{company}}?`
|
|
612
612
|
- lead source: `How should we get the people for this campaign?`
|
|
613
613
|
|
|
614
|
+
Do not offer quantified reply-rate, meeting-rate, pipeline, revenue, or ROI
|
|
615
|
+
claims as setup proof options unless the user supplied verified benchmark data
|
|
616
|
+
for this exact workspace/sender. If such claims appear in research, label them
|
|
617
|
+
as unavailable/unsupported and use founder/operator credibility, product
|
|
618
|
+
capability, or verified customer proof instead.
|
|
619
|
+
This is a hard guardrail for both option labels and option descriptions: never
|
|
620
|
+
write setup proof option text with numeric outcome language such as `25% reply`,
|
|
621
|
+
`25%-reply`, `reply-rate`, `meeting-rate`, `pipeline`, `revenue`, or `ROI`
|
|
622
|
+
unless that exact benchmark is verified for this workspace/sender. If a profile
|
|
623
|
+
or case study contains that language, strip the number and convert the option to
|
|
624
|
+
non-quantified founder/operator credibility or product capability.
|
|
625
|
+
|
|
614
626
|
Ask the lead-source question as the last question in the first strategy
|
|
615
627
|
batch, after buyer, offer/ask, and proof/safety are understood. Frame supplied
|
|
616
628
|
lists as optional, not required. The three visible options are exactly:
|