ICP definition
Without Sanka
✗ Tribal knowledge, varies by rep
With Sanka
✓ One shared model — marketing, SDRs, and AEs all align
Prospecting that turns your ICP into actionable lists
Define ICPs, build ranked account lists, and push context into enrichment and outreach — from the UI or the SDK.
Ask anything...
Prospecting
Changes will appear here
Trusted by 1,000+ teams
Overview
Prospecting that turns your ICP into actionable lists
ICP modeling
Set firmographic and behavioral criteria once. Every list you build inherits the same scoring logic.
Ranked account lists
Accounts and contacts are scored and sorted so reps work the highest-fit opportunities first.
SDK and API access
Build lists from code with sanka-sdk. Query contacts, apply ICP filters, and trigger downstream workflows in one call.
Workflow
Why teams run prospecting inside the Sales OS
- 01Install the pluginAdd the Sanka plugin to Claude or Codex. One file, no config.
- 02Describe your ideal customerTell the AI who you sell to. It creates your ICP filter and builds a ranked list automatically.
- 03Start sellingAsk for the next best lead, trigger outreach, or enrich a contact — all in natural language.
- 04Shared ICP ownershipMarketing and sales co-own the ICP model. Changes go through review before they affect live lists.
- 05List change historyEvery add, remove, and re-score is logged. Trace why a contact entered or left a list.
Compare
Why teams run prospecting inside the Sales OS
| Workflow | Without Sanka | With Sanka |
|---|---|---|
| ICP definition | ✗ Tribal knowledge, varies by rep | ✓ One shared model — marketing, SDRs, and AEs all align |
| List building | ✗ Manual CSV exports that go stale | ✓ Live lists synced to CRM and pipeline data in real time |
| Scoring & routing | ✗ Separate tools, separate data sources | ✓ Scoring, routing, and outreach share one prioritization source |
| Enrichment handoff | ✗ Copy-paste between tools | ✓ One-click push to enrichment — data flows back automatically |
| AI & API access | ✗ No programmatic access to lists | ✓ AI agents and scripts access the same list context as humans |
| Audit trail | ✗ None | ✓ Every list change logged with reason |
List building
Without Sanka
✗ Manual CSV exports that go stale
With Sanka
✓ Live lists synced to CRM and pipeline data in real time
Scoring & routing
Without Sanka
✗ Separate tools, separate data sources
With Sanka
✓ Scoring, routing, and outreach share one prioritization source
Enrichment handoff
Without Sanka
✗ Copy-paste between tools
With Sanka
✓ One-click push to enrichment — data flows back automatically
AI & API access
Without Sanka
✗ No programmatic access to lists
With Sanka
✓ AI agents and scripts access the same list context as humans
Audit trail
Without Sanka
✗ None
With Sanka
✓ Every list change logged with reason
Customer quotes
Don't take our word for it.
We want inventory, sales management, tax, and accounting to connect smoothly while keeping operating cost and time low.
At first, we managed everything in Excel. Human error was a constant problem, and our inventory value did not match at fiscal close.
By implementing Sanka, we expect to connect reel racks with shop-floor inventory data so we can calculate requirements based on accurate stock.
FAQ
Frequently asked questions
Can I build and manage lists entirely through the API?
Yes. Every list operation available in the UI is also available via sanka-sdk. You can create ICP filters, query matching contacts, and trigger workflows programmatically.
How does prospecting connect to scoring and enrichment?
ICP scores from the prospecting module feed directly into lead scoring rules and routing workflows. When you push a contact to enrichment, the enriched data flows back to the same record — no manual sync.
Do lists stay fresh as CRM data changes?
Lists are live views, not static exports. When contact data updates in CRM, list membership and scores recalculate automatically based on your ICP criteria.
Can this work with HubSpot or Salesforce?
Yes. Sanka does not need to replace your CRM. It can start from CRM data and extend it into governed operational workflows.