# Contact enrichment software: credits and CRM field controls

Compare contact enrichment credits and CRM field controls before choosing a workflow.

Canonical page: https://quillwell.com/guides/contact-enrichment-software/
Updated 2026-10-31
Publisher: Quillwell Guides (https://quillwell.com/guides/about/). Editorial standards: https://quillwell.com/guides/editorial/

## The short answer

- Price the result you need: [FullEnrich](https://fullenrich.com/pricing) assigns different credit costs to work email and mobile phone results.
- Count uncertain results in your budget: [FullEnrich](https://help.fullenrich.com/en/articles/9736469-how-do-credits-work) charges for catch-all and probably-valid work emails, while no-result lookups are uncharged.
- If you need to protect existing CRM values, start with a workflow that lets you set field rules and test those rules on a small list.
- Export what you need before leaving. [FullEnrich](https://help.fullenrich.com/en/articles/9736469-how-do-credits-work) ends remaining subscription credits at cycle end after cancellation and deletes enriched contacts after three months.

## Compare the result and the handoff

Choose the workflow around the record you already have and the output you need to keep. A result can consume a credit before anyone decides whether it belongs in the CRM.

We compare documentation from FullEnrich, Findymail, Hunter and HubSpot. FullEnrich uses a waterfall; Findymail describes both prospecting and a separate managed CRM service. Hunter documents a HubSpot sync, while HubSpot provides a property-history recovery process.

Documented billing and CRM decisions

| Vendor or workflow | Billing unit | Limit that matters | Control or export |
| --- | --- | --- | --- |
| FullEnrich | Credits per result or enrichment type | Catch-all and probably-valid work emails are charged; no-result lookups are uncharged. | HubSpot list beta offers per-field fill-empty or overwrite rules. |
| Findymail | Usage limits on prospecting plans; separate credit plans | Credit-plan finder successes and verifier requests have different rules. | Datacare advertises field rules with preview and rollback. |
| Hunter | Billing terms not covered here | Only the lead owner can manually sync that lead. | Record-level finding fills an empty email; existing leads need an explicit sync. |
| HubSpot | Enrichment billing not covered here | Contact property history retains up to 45 revisions. | Export property history and use record IDs to import earlier values. |

Source: [FullEnrich: pricing](https://fullenrich.com/pricing), [FullEnrich: credits](https://help.fullenrich.com/en/articles/9736469-how-do-credits-work), [Findymail: Prospecting and reseller plans](https://www.findymail.com/pricing/), [Findymail: API usage](https://app.findymail.com/docs/), [FullEnrich: CRM lists](https://help.fullenrich.com/en/articles/15819147-enrich-your-hubspot-contact-lists-using-fullenrich), [Findymail: Datacare](https://www.findymail.com/crm-enrichment/), [Hunter: HubSpot sync and ownership](https://help.hunter.io/en/articles/1885573-hubspot-integration), [HubSpot: property history](https://knowledge.hubspot.com/properties/export-property-history)

The table describes different jobs. A list run can add missing fields to selected records; ongoing maintenance also needs a way to detect changes and review updates. Decide which job matters before comparing allowances.

## Calculate credits for the results you receive

Budget for each requested field and for results that need review. A paid result and an address ready to use are separate decisions.

[FullEnrich pricing](https://fullenrich.com/pricing) assigns one credit to work email enrichment, ten to a mobile phone lookup and 0.25 to standalone profile or company enrichment. [FullEnrich credit rules](https://help.fullenrich.com/en/articles/9736469-how-do-credits-work) include probably-valid and catch-all work emails among charged results; a no-result lookup is uncharged. Custom pricing can differ.

For example, under FullEnrich’s documented rules, a work email returned as catch-all plus a returned mobile phone would use eleven credits. Keep the email verdict with the record so someone can decide how to handle it. The [email verification guide](https://quillwell.com/guides/email-verification-software/) explains why an uncertain verdict needs a separate decision.

[Findymail pricing](https://www.findymail.com/pricing/) separates usage-based prospecting subscriptions from reseller credit plans. [Findymail API documentation](https://app.findymail.com/docs/) says credit plans charge for finder successes, while each verifier request costs one verifier credit regardless of result. Individual, Team and Scale share usage limits, so the credit rules do not reveal each plan’s absolute allowance.

Quote the workload in the unit the plan actually uses. Record requested fields and result status alongside account usage for the same list. A charge on an uncertain result can be legitimate under the stated rules, but the record still needs a decision before use.

## Choose what can change in the CRM

Set the rule for each field before running enrichment. Filling a blank and replacing an existing value solve different problems, and a single CRM can contain both.

[FullEnrich’s HubSpot list-enrichment beta](https://help.fullenrich.com/en/articles/15819147-enrich-your-hubspot-contact-lists-using-fullenrich) offers fill-empty or overwrite rules per field for manual runs of up to 5,000 contacts. It excludes scheduling or previews. It also excludes re-verification and job-change detection. A periodic cleanup therefore needs additional work outside that documented list workflow.

[FullEnrich’s integration setup](https://help.fullenrich.com/en/articles/12035296-getting-started-with-hubspot-integration) requires admin access in both accounts and flags uncertain matches for review. Its [app beta guide](https://help.fullenrich.com/en/articles/16235002-setup-guide-for-fullenrich-s-hubspot-application-beta) carries a not-yet-available banner even though other FullEnrich guides describe integration and list enrichment. The app guide describes a preview for pushing already enriched contacts; that is a different workflow from list enrichment.

[Hunter’s HubSpot integration guide](https://help.hunter.io/en/articles/1885573-hubspot-integration) says only a lead owner can manually sync their lead, including from shared lists. Existing leads need an explicit sync after connecting. Hunter’s record-level finding fills an empty email; that rule should not be assumed for every mapped sync field.

[Findymail Datacare](https://www.findymail.com/crm-enrichment/) advertises continuous CRM maintenance with field-level no-override defaults. It also advertises preview and rollback. Its field rules are configurable, so inspect the actual setting for each property. Test a deliberately populated field alongside an empty one before using a larger segment.

## Keep a recovery copy before you cancel

Treat remaining credits, exported records and CRM history as separate assets. Save a usable copy while the account and its export controls are available.

[FullEnrich’s credit guide](https://help.fullenrich.com/en/articles/9736469-how-do-credits-work) says monthly credits normally roll over for three months and yearly credits for twelve. After cancellation, remaining subscription credits expire at the end of the billing cycle. The same guide says enriched contacts are deleted after three months, qualifying its broader statement that data is not deleted.

[FullEnrich’s contact guide](https://help.fullenrich.com/en/articles/12785389-how-to-enrich-contacts-in-fullenrich-a-step-by-step-guide) describes exporting results or pushing them to HubSpot. Its [app beta guide](https://help.fullenrich.com/en/articles/16235002-setup-guide-for-fullenrich-s-hubspot-application-beta) says HubSpot values remain after disconnect. Confirm the available route first, then reconcile the exported records with the destination before relying on that handoff.

A [HubSpot user on Reddit](https://www.reddit.com/r/hubspot/comments/1njxjyw/hubspot_enrichment_input_incorrect_information/) reported unwanted changes after enriching records. The author’s setup and the cause are unverified, but the report makes a useful recovery question: can you identify the earlier value and restore the correct record?

[HubSpot property-history export](https://knowledge.hubspot.com/properties/export-property-history) can include current and prior values alongside timestamps and update source. Contact history retains up to 45 revisions, and exports use UTC timestamps. HubSpot’s recovery process imports earlier values using record IDs; finite history is no substitute for a separate backup.

Save a pre-run export with record IDs and the properties you intend to change. After the run, compare it with the new values and keep the audit record somewhere your team can access after cancellation. Test a restore on a controlled record before the exit date.

## Run a field and credit worksheet

Use the same controlled records for each candidate and record the outcome for every row. The worksheet turns an attractive demo into a decision about your own workflow.