Quickstart & reference.

Quickstart

1. Load data. Drop a CSV, TSV or Excel file into the demo — or click Use sample data to try it with 50 real companies.
2. Clean (free). One click fixes casing, whitespace, malformed emails and typo'd titles. Open the Diff view to inspect every change character-by-character.
3. Dedupe (free). Duplicates are matched on normalized email and merged before anything is billed.
4. Enrich. Gaps fill through the provider waterfall; every value carries a source and confidence score. You're only charged on a verified match.
5. Sync. Push to Salesforce, HubSpot, Pipedrive, Dynamics or Zoho — or export a clean CSV.

Shortcut: /demo?run=auto plays the whole flow automatically — useful for sharing.

Preparing your file

Headers are auto-detected with common aliases. Recommended columns:

Field	Accepted headers (examples)	Required
Company	company, account, organization	Yes
Contact	contact, name, full name	Yes
Title	title, job title, role	No
Work email	email, work email, e-mail	Recommended
Phone	phone, mobile, direct dial	No
Employees	employees, headcount, size	No
Industry	industry, vertical, sector	No

CSV and TSV delimiters are auto-detected; Excel files read the first sheet. Up to 50k rows per run on Growth, 250k on Scale.

Credits & billing math

1 credit ≈ $0.01. Cleaning and dedupe never consume credits. A miss never bills.

Action	Credits
Clean a record / merge a duplicate	Free
Find & verify a work email	1
Verify an existing email	0.2
Mobile / direct dial	3
Firmographic record	1
iData AI research field	5

Full plans on the pricing page.

How the waterfall works

Providers are queried in sequence: iData first-party → vendors → iData verification. The first result above the 75% confidence threshold wins and is verified; everything below keeps falling. A single provider typically reaches ~60% email coverage — the waterfall reaches ~96% on the sample set. Watch it animated →

Sync & field mapping

Records upsert by email: existing CRM records update in place, new ones are created, duplicates are never written. Mapping is auto-detected (e.g. work_email → Email, company_hq → Billing City) and editable before the first push.

API Scale plan

Programmatic enrichment for pipelines:

POST /v1/enrich
{"records":[{"company":"Ramp","domain":"ramp.com","contact":"A. Cohen"}],
 "fields":["work_email","phone","employees"],
 "verify":true}

Returns per-field values with source and confidence. Webhooks for async batches. Full reference ships with the Scale rollout.