IMPLEMENTATION GUIDE
Separate fit from intent
Use company enrichment for attributes such as primary industry, employee count, and headquarters. Get engagement signals from your own product, website, or CRM. Keep fit and intent as separate values so a large company with no engagement does not automatically outrank a smaller account requesting a demo.
Make the result explainable
Store the input fields and a short reason with every score. Treat missing headcount as unknown rather than zero. If an account lacks enough evidence, place it in a review queue instead of marking it a poor fit. Revisit rules against qualified opportunities to see whether they match the accounts your team actually wins.
Update the queue after enrichment completes
The initial API response is a queued task. Match the completed task to the lead using the ID stored in your backend, then calculate the score. Verify Loop webhook signatures and make updates idempotent. EnrichLoops supplies the profile; your scoring model and CRM control prioritization.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Company enrichmentExplore the company fields available for your fit model.Common questions
Does EnrichLoops return a built-in lead score?
EnrichLoops returns company fields. Your app or CRM calculates a score using the criteria you define, optionally combined with first-party engagement data.
Does company size indicate buying intent?
Company size describes account fit. It does not establish buying intent. Combine it with signals you collect, such as demo requests or product activity.