AI sales list building: a controlled Leadbase workflow

Your ideal customer profile should become a list your sales team can use. With Leadbase, describe the companies you want to reach, research the criteria that matter to your offer and add the relevant people, work emails and direct numbers in the same workspace.

Build your list around your own market definition

Leadbase connects discovery, qualification and enrichment. Custom research fields help answer the business questions standard database filters miss. Sources and summaries stay beside each result, so your team can understand why an account belongs without repeating the research.

Work in the app, ask the built-in assistant or connect your AI client through MCP. Share the resulting Sheet or export reviewed contacts into your existing outreach process.

Build your first target list, or explore your market with the Leadbase team. The steps below show how to make the results useful and reviewable before scaling.

What a trustworthy list-building workflow must prove

A persuasive summary is weak evidence. A reviewable workflow produces a chain that another person can inspect:

This order matters. A large candidate set is not proof of quality. A reachable email is not proof of buyer fit. A confident AI answer is not proof that its source establishes the criterion. Each layer should make the next commercial decision safer without pretending to eliminate judgment.

Define the commercial decision before the search

Most ICP descriptions combine facts, assumptions, and aspirations in one paragraph. An agent cannot reliably tell them apart. Before opening a database, write down the decision the list must support.

For one segment, answer five questions:

1. Which problem must the account plausibly have? Name the operating condition your offer addresses, not just an industry label.
2. What makes the account relevant now? This may be a visible initiative, hiring pattern, technology change, expansion, or another observable event. If timing does not matter, say so.
3. Which role owns or feels the problem? Separate the likely business owner from an influencer, user, or procurement contact.
4. What disqualifies an account? Geography, business model, company structure, incompatible technology, or an existing commercial relationship may be grounds for exclusion.
5. What evidence is acceptable? Specify whether a company website, job posting, public registry, press release, or another source can support the decision.

The result should be testable. “European manufacturers that need automation” is not. “Manufacturing companies with operations in Germany, a visible maintenance or production leadership function, and current evidence of a plant-modernization initiative” is. The second version still needs research, but a reviewer can explain why a record passed or failed.

Turn the ICP into a field contract

A field contract defines what the research may write, what evidence it must retain, and what happens when the answer is unclear. It prevents a confident paragraph from masquerading as structured data.

Keep observations and decisions in separate columns. “The careers page lists three maintenance roles” is an observation. “This account has urgent buying intent” is an inference the source does not establish. Store the prior value when existing data changes so a reviewer can see whether the workflow found new evidence, corrected a field, or merely reformatted it.

The contract also assigns ownership. Sales operations can own identity and routing rules, a segment owner can approve qualification criteria, and an account owner can make the final activation decision. “The AI decided” is not an accountable workflow.

Build the list in six controlled stages

Consider an illustrative campaign for a software company selling maintenance planning to industrial businesses. The team wants German operating companies with a relevant production footprint and a plausible maintenance owner. This is an example of workflow design, not a claim about a real campaign.

1. Discover accounts broadly

Start at company level. Search from the written market description and collect enough context to distinguish an operating company from a holding company, reseller, consultancy, or unrelated business with similar keywords.

Do not request every email or phone number yet. Contact data has little value when the account itself has not passed qualification, and early lookup makes weak candidates unnecessarily expensive to discard.

2. Apply deterministic exclusions

Use ordinary filters for criteria that do not require interpretation: excluded countries, known customers, unsupported company types, or records already owned by another team. Deterministic rules are easier to audit and rerun than research.

Keep the reason for exclusion in a field. Otherwise, the same account may reappear in the next search and consume work again.

3. Research one criterion per field

Investigate narrow questions separately:

• Does the company operate a production site in the target geography?
• Is there current evidence of a maintenance, production, or plant-management function?
• Is there a public initiative that supports the timing hypothesis?

Each result should contain a status, short factual explanation, source, and check date. Avoid one large “research notes” field. When identity, fit, timing, and role are mixed in a paragraph, neither reviewers nor downstream rules can use the result consistently.

4. Calculate a decision state

Translate the completed fields into pass, review, or fail. Reserve pass for records that meet every required criterion. Use review for contradictory sources, ambiguous company structures, or missing evidence that a person can reasonably resolve. Failed records should retain the failed criterion and remain blocked from activation.

A numeric score may sort a queue, but it must not erase hard exclusions. An account with a high total score and one decisive disqualifier is still a failed account.

5. Resolve people and contact fields after qualification

Only now identify relevant people and request the fields needed for the planned channel. Keep role fit separate from contact availability: a reachable address does not make someone the right buyer, and a relevant buyer without a usable contact field should remain incomplete rather than receive guessed data.

The campaign still needs its own privacy and outreach review. Public availability, a business context, and technical reachability do not by themselves make a particular message or channel lawful or appropriate.

6. Activate only accepted records

Make the final transition explicit: an owner accepts the record, chooses the destination, and records the next action. Sending every discovered account directly into a CRM or sequence hides the moment when research became sales activity.

If the CRM is the system of record, define which fields this workflow may hand off and which rep-owned fields it must preserve. A list-building process should not overwrite account notes, lifecycle status, or active-opportunity context.

Build the workflow in Leadbase

1. Describe the market you want. Start with your own ICP in the Lead Database workflow and inspect the matching companies.
2. Keep your qualification criteria beside the accounts. Use typed columns in a shared Sheet for the facts and decisions your team needs.
3. Ask the assistant for a concrete outcome. Name the Sheet, rows, columns and intended result. It works within your access permissions and credit controls. See Assistant basics.
4. Review and continue. Inspect changed cells and sources, use the stop control for ongoing work, and consult Actions and access for execution details.
5. Research the next useful field. Run enrichment on selected rows. Review returned values and keep missing answers visible.
6. Share a list your team can work. Use Sheet sharing, named versions and history to preserve the accepted handoff.

Prefer your own AI client? Connect through MCP and run Leadbase research within your workspace permissions. Chat history lets you return to the conversation; saved research remains in the Sheet.

Write instructions that produce reviewable output

The instruction should mirror the field contract. A compact specification is more useful than a persuasive persona prompt:

Decision: Determine whether this company meets the approved segment criteria.
Required criteria:- Operates a production site in Germany- Has a visible maintenance, production, or plant-management function
Output:- decision: pass | review | fail- production_site: present | absent | unclear- relevant_function: present | absent | unclear- rationale: maximum two factual sentences- sources: URL and date checked for each researched criterion
Rules:- Use "review" when sources conflict or evidence is incomplete.- Do not infer a criterion from industry wording alone.- Do not invent a person, role, source, or timing signal.

Test the instruction on edge cases before scaling it: a parent company with several subsidiaries, a manufacturer with only a sales office in the target market, a stale leadership page, and a company whose relevant role exists but is vacant. These cases expose ambiguity faster than a batch of obvious matches.

Put a measurable review gate before volume

Freeze a labelled sample before expanding the workflow. Include clear matches, clear failures, and borderline cases; a sample containing only top-ranked accounts does not test the difficult decisions.

For every correction, record the reason. Useful error categories include wrong company identity, an inferred criterion without evidence, a stale or irrelevant source, a role attached to the wrong entity, overlooked evidence, a missing required field, and an ignored hard exclusion.

Measure the workflow at field and decision level:

• Evidence coverage: records with acceptable evidence for every required criterion divided by records reviewed
• Decision agreement: records where the reviewer accepts the pass/review/fail state divided by records reviewed
• Correction rate by field: corrected values divided by reviewed values for that field
• Review rate: records routed to a person divided by records researched
• No-result rate: records where requested evidence or a contact could not be found divided by records processed
• Activation acceptance: records approved for the intended campaign divided by records submitted for final review

Do not collapse these into one vanity score. A high review rate can mean the instruction is too cautious, or it can be the correct response to weak public evidence. Inspect examples before moving a threshold. Replies and opportunities can help evaluate the segment and message later, but they do not prove that every underlying field was correct.

Choose the system for the actual bottleneck

Leadbase brings the research behind your pipeline into one workspace: market discovery, custom qualification and contact enrichment. Keep the resulting account context when you share the Sheet or export it to your CRM and engagement tools.

Build your first useful list

Do not start a sales conversation with “How many leads can AI generate?” Start with one segment and an acceptance test. Bring the written ICP, known exclusions, 25 to 50 deliberately mixed accounts, the fields that determine acceptance, permitted source types, and one intended handoff destination.

Before the run, agree on the maximum correction rate for decisive fields, the required evidence coverage, who resolves review cases, and what would make the workflow unsuitable. After the review, compare accepted accounts—not raw row count—with the current method. If the evidence is too weak, the review burden too high, or the handoff does not fit the team, the pilot should say so.

Build your first qualified list with Leadbase or bring one real market brief to our team. Start with a relevant sample, review the accounts and contacts, then expand the workflow that works for your team.

For the narrower operator job of turning one ICP brief into a reviewed account list, use the ICP-to-account implementation Guide and its downloadable translation record. This article remains the canonical discussion of agent instructions, evidence review, and safe pilot governance.

Continue with a practical worksheet

To make the qualification rules concrete, use the B2B ICP template and three worked examples. Then test the decisive fields with the five company research prompts and evidence audit.