Ballet turns that into one workflow. Describe the enrichment rules in plain English, connect Salesforce or HubSpot plus an enrichment source, and the play runs the same way every time.
You can start it from Studio, on a CRM trigger, or by asking Claude (over MCP) to enrich a lead while you are already in a conversation.
What this playbook does
The playbook matches a new lead to your CRM, fills missing company and contact fields from enrichment sources you approve, applies scoring and routing rules, and writes only the fields you allow.
Because the workflow is reviewable code, RevOps can see every step. Because it is exposed over MCP, the same play can be started from Claude when a rep pastes a lead into chat.
What you hand Ballet
When a new lead is created in Salesforce, or when Claude asks to enrich a lead, match it to the right contact and account, pull firmographics from ZoomInfo, apply our ICP score, set the owner from our routing table, and flag any record we cannot match confidently.
Running it from Claude over MCP
Connect Claude (or Cursor) to https://api.ballet.dev/mcp, then ask it to enrich a lead. The client finds this playbook, runs it, and reads the result back into the conversation.
See the MCP setup page at /mcp and the help article on connecting to Ballet's MCP endpoint for client config.
How to use it
- Open the Lead Enrichment playbook in Ballet and connect Salesforce or HubSpot.
- Connect an enrichment source your workspace is allowed to use.
- Describe your scoring and routing rules, then simulate a few leads.
- Publish the playbook and optionally enable a CRM trigger.
- From Claude or Cursor, ask it to run lead enrichment on a record.
