Build a lead list in Claude and import it into Vertiqa

Research and CRM entry are usually two separate chores. With Vertiqa connected, they can be one conversation: build the list in Claude, review it, and have the same chat create the accounts in Vertiqa.

This works with whatever you used to build the list — a Claude Cowork research task, a web search, a prospecting connector, or a spreadsheet you paste into the chat. Vertiqa only cares about the finished list.

Step 1 — Get the list into a reviewable shape

Before anything is written to Vertiqa, ask for the list as a table. It is far easier to spot a wrong address or a duplicate here than after import.

Build me a list of 20 IT services and consulting firms in the Atlanta metro
with 20-200 employees. For each one give me: company name, website, street
address, city, state, postal code, industry, and employee count. Show it as a
table. Do not put anything into Vertiqa yet.

These are the fields a Vertiqa account can take:

Field	Notes
Name	Required
Website, phone, email	Primary channels
Address, city, state, postal code, country	Filed on the account
Industry	Free text if you have no industry list
Type	commercial, residential, or household only
Status	active, inactive, or churned
Annual revenue, employee count	Optional firmographics

Type is not a lifecycle label. "Prospect", "customer", and "partner" are rejected — a business you are prospecting is commercial. Track lifecycle with the deal's pipeline stage or a tag instead.

Step 2 — Check for duplicates first

The connection creates accounts one at a time and does not de-duplicate them for you. Make the check explicit:

Before creating anything, search Vertiqa's accounts for each company name in
that list and tell me which ones already exist. Do not create anything yet.

Step 3 — Import a batch and read it back

Start with a handful rather than the whole list, so a wrong mapping costs you five records instead of fifty.

Import or add the first 5 companies from that list as accounts in Vertiqa. Set
type to commercial and owner to me, and fill in website, address, industry, and
employee count. Show me the exact records you are about to create, then wait for
my confirmation.

After it runs, ask for the result as a table with the new record links so you can open one and confirm the fields landed where you expected. Then repeat for the rest of the list.

Step 4 — Keep the provenance

An imported account with no story attached is a mystery to whoever picks it up next. Add the source in the same pass:

On each account you just created, add a note recording where it came from: this
research list, the date, and the firmographics you used. Add a tag "Q3
prospecting" as well.

Add the people, too, when your research turned up names:

Create a contact on each of those accounts with the name, job title, and email
from the list. Show me the contacts before you create them.

Step 5 — Turn them into deals, if you want them worked

Accounts on their own do not appear in a pipeline. To open deals against them:

List my lead pipelines and their stages, then create an opportunity in the first
stage for each of the five accounts, named "<Company> — Q3 outreach". Show me the
list before you create it.

One thing to fix afterwards: a deal created through the connection links to a contact, not to an account. Open the deals in Vertiqa and set the account, or create the contacts against the account first and attach those contacts to the deals.

When to use Vertiqa's CSV import instead

Reach for the CRM Import Center rather than the chat when:

• The list runs to dozens or hundreds of rows.
• You are migrating out of another CRM and have an export file.
• You want column mapping, a preview with blocked-row warnings, and duplicate-safe import in one pass.
• You need to bring accounts, contacts, and notes across together.

The chat is the better tool for a small, freshly researched list where the research and the judgement calls are happening in the same conversation.

Before you import anything

• Only import contact details you have a legitimate basis to hold and use. Records created this way are real CRM records subject to the same privacy obligations as any other.
• Verify addresses and websites in the review step. A confident-looking research table can still be wrong, and a wrong record is harder to remove than to catch.
• Keep the create step behind an explicit confirmation rather than on always-allow.

Related

• What the Vertiqa connection can do
• Import CRM data
• Accounts
• Account, contact, or location?
• Fix common Vertiqa connection problems