LeadRecoverly Feature and Finding Dictionary
This page describes implemented plan limits, feature gates, approval requirements, and important reversal limits. It does not claim features or outcomes that are not present in the code.
Plan limits and feature access
| Plan | Included limits | Implemented access |
|---|---|---|
| Free | Sample scan; 1 portal; 1 seat; 500 contacts; 250 companies; 250 deals | Read-only |
| Clean | $49 monthly or $490 annually; 2 portals; 2 seats; 10,000 contacts; 5,000 companies; 5,000 deals | Cleanup, duplicate intelligence, standardization, import preflight, CSV export, approved writes |
| Recover | $149 monthly or $1,490 annually; 5 portals; 5 seats; 50,000 contacts; 25,000 companies; 25,000 deals | Clean plus recovery engine, routing rules, monitoring, scheduled reports, score history |
| Optimize | $299 monthly or $2,990 annually; 10 portals; 10 seats; 150,000 contacts; 75,000 companies; 75,000 deals | Recover plus executive reporting, team scorecards, advanced patterns, custom rules, higher limits |
Finding and workflow dictionary
| Finding or workflow | Record type | Availability | Approval model | Important limitation |
|---|---|---|---|---|
| Duplicate contacts and companies | Contact or company | Clean scan and higher | Review first; merge requires paid access, Edit Mode, editor role, write scope, and MERGE confirmation | A merge may not be perfectly reversible |
| Data standardization | Contact, company, or deal property | Clean and higher | Preview; plan/risk batch limit; Edit Mode; editor role; write scope; APPLY confirmation | Only approved recipe/property combinations |
| Import preflight | CSV rows and fields | Clean and higher | Validation only; no HubSpot write | Passing checks does not prove factual accuracy |
| Routing recommendations | Contact, company, or deal | Recover and higher | Rule preview; saved rules require editor role; ownership write remains separately approved | Rules require maintained owner IDs and business logic |
| Scheduled monitoring | Portal-level scan results | Recover and higher | Configured cadence and thresholds; service session required | Depends on completed scans and available access |
| CRM health score | Current scan findings | All plans, within plan scan limits | Explainable deductions across five weighted areas | Not a validated revenue forecast |
Action reversibility
Action history stores old and new values and supports reversals where the underlying action and current HubSpot state allow it. Merges, deleted data, changed associations, and later edits by HubSpot users or external systems may not be perfectly reversible.
How this dictionary stays accurate
Plan names, limits, prices, and feature gates are generated from the shared product configuration used by the application. Public documentation should be changed only when that canonical configuration or the corresponding server behavior changes. This prevents a marketing page from promising access that the server does not grant and makes discrepancies detectable during release validation.
Related documentation
Implementation details and review guidance
How to read availability
A minimum plan means that the server feature gate recognizes the feature at that tier and above. It does not bypass portal limits, seat limits, workspace roles, Edit Mode, HubSpot scopes, typed confirmation, batch limits, or record-level validation. Those controls remain cumulative.
Read-only and write workflows
Scanning, previews, exports, and file validation can be available without changing HubSpot. Write workflows are intentionally separate. Where implemented, the server resolves current entitlement, verifies role and scope, validates the submitted object and property, applies idempotency or operation checks, and logs the result.
Meaning of reversibility
Reversibility means LeadRecoverly has enough stored before-state and supported API behavior to attempt a reversal. It is not a promise that every external effect can be undone. Merges, deletions, association changes, workflow enrollment, notifications, and later edits by people or integrations may create consequences outside the original action.
Enterprise and future features
The Enterprise row describes the existing configuration limits in the shared plan source. It should not be read as a promise of custom services, certifications, support levels, or features that are not separately documented and contractually agreed.