Product Updates
DiscoLike v2: Features on Every Plan
DiscoLike v2 includes the core feature set across plans, including tech stack targeting and segmentation. Plans still differ in usage pricing, execution rates, and service.
· updated October 6, 2026
DiscoLike v2 removes feature gates from the core product. A team can use tech stack targeting, customer segmentation, and the integration options without moving to a higher plan just to access those capabilities.
Plan choice still matters for volume, execution rates, and support. Feature access and unlimited usage are different things.
What is included across plans?
The v2 feature set includes company and contact exclusions, company-name-to-domain matching, hierarchy data, growth and vendor data appends, and contact and social linkage.
You can combine those capabilities in one workflow: find a company segment, exclude existing CRM accounts, inspect the technology footprint, and research relevant contacts.
Higher plans provide benefits such as volume pricing, priority support, team training, research assistance, and higher MCP and API execution rates. Check pricing for current terms.
Email verification and email discovery
Email verification is complimentary for contacts supplied by DiscoLike. Verification checks an available email; discovery attempts to find one.
For people found through ContaGen, email discovery is billed at your plan’s per-record rate for each email discovered from first and last name results. Keep that distinction in your cost model when comparing contact workflows.
API, MCP, CLI, and SDK workflows
The release adds CLI and SDK options alongside API and MCP. The CLI supports terminal tasks and scheduled jobs. The official SDK starts with Python.
Use the interface that fits your team: direct API calls for application integration, MCP for agent-driven research, or the CLI for repeatable operational tasks. The underlying account criteria should stay consistent across interfaces.
Salesforce, HubSpot, and Pipedrive integrations
The CRM integrations support pushing saved-query results into the CRM, excluding existing records from new searches, and filling missing domains and emails.
Decide how companies and contacts map to your CRM records before importing a large list. Review a small batch for duplicates and field mappings first.
Put the release to work
A useful first project is to expand one established customer segment while excluding accounts already in your CRM. Validate a sample, discover the relevant contacts, and measure accepted records before scaling.
Start in DiscoLike or review integration options. For the later geographic and subindustry capabilities, see Local B2B Search: Geography, Niches, and AI.
Related posts:
