@sellable/install 0.1.177 → 0.1.179

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.177",
3
+ "version": "0.1.179",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {
@@ -220,6 +220,25 @@ reference to avoid long-token copy errors. Account rows are not people leads
220
220
  yet. The confirmation creates the `domainFilterId` that constrains the follow-on
221
221
  `search_prospeo` people search.
222
222
 
223
+ For lookalike seed selection, route by campaign intent. In outbound/sales
224
+ prospecting campaigns, treat "best customer", "top customer", "target domains",
225
+ "approved accounts", "customer domains", and similar wording as target
226
+ account/customer seed asks. Use explicit user-provided target/account/customer
227
+ domains or company names first, then verified past-customer/account evidence from
228
+ research, CRM, or proof. Never substitute the sender's current company/domain or
229
+ employer history as a lookalike seed for outbound unless the user explicitly
230
+ confirms that domain is a target/customer seed or asks for sender-company peers.
231
+ In job-search/application campaigns, lookalike seeds may be existing companies
232
+ from the candidate's current or past employers because those companies define
233
+ the candidate-fit lane. If campaign intent or seed source is ambiguous, ask
234
+ whether the seed should be target/customer domains or current/past employers; if
235
+ YOLO requires moving without a seed, switch to non-lookalike company filters
236
+ instead of inventing a seed. If the user asks for a geography like Germany,
237
+ preserve it in account discovery where supported (`company_location_search` or
238
+ `company_icp.geographic_markets`) and in follow-on people search
239
+ (`person_location_search`); do not drop geography when moving from lookalike
240
+ accounts to people leads.
241
+
223
242
  Prospeo company/account search is useful when the source plan depends on
224
243
  website traffic (`company_website_traffic`), confirmed AI Attributes including
225
244
  `pricing`, `uses_ai`, `has_api`, `has_chrome_extension`, `has_sso`,