What Is Lex? Meet LeadX's AI Lead-Gen Assistant (2026)

Quick answer: Lex is LeadX's in-app AI assistant. You type a plain-English request like "find dentists in Austin without a website," and Lex plans and launches the matching Scout campaign for you instead of you clicking through niche and city fields manually. It has guardrails that push back on vague requests, supports multiple chats like ChatGPT, and is available on LeadX Pro and Agency plans.

Most lead-gen tools make you learn their interface before they're useful: pick a niche from a dropdown, type a city, set filters, hit run. Lex flips that. You describe what you want in a sentence, and it turns that sentence into a real campaign. This post covers exactly what Lex does, how the natural-language flow works end to end, why it pushes back on vague requests instead of just running them, and who it's actually built for.

What is Lex, exactly?

Lex is a chat-based AI assistant built into LeadX, powered by a leading large language model. It sits alongside Scout (business finder), Builder (site generator), and Outreach (email/SMS sender) as a fourth way to work: instead of operating those tools through forms, you talk to Lex and it operates them for you.

Concretely, Lex can:

• Turn a natural-language request into a Scout campaign. "Find plumbers in Denver with no website" becomes a real, running search with those parameters.
• Handle multi-city and multi-niche requests in one go. Ask for several niches or several cities in a single message and Lex plans a campaign that covers all of them.
• Explain what it's about to do before it does it. Before launching, Lex shows a "Ready to run?" summary card so you can confirm or adjust before any credits are spent.
• Hold multiple separate conversations. Lex uses a multi-chat pane, the same pattern as ChatGPT, so you can keep one thread for a client's niche and another for your own prospecting without them bleeding into each other.

How does natural-language campaign creation actually work?

The flow is the same shape every time, whether the request is simple or compound:

1. You describe the campaign in plain English. For example: "I want no-website roofers in Phoenix and Tucson."
2. Lex parses the request into structured parameters. It extracts the business type (niche), the location(s), and any filters like "no website." Those are the same fields Scout's manual form asks for, just derived from your sentence instead of typed into boxes.
3. Lex checks the request against its guardrails. If the niche or city is missing, too vague, or not a real, searchable business type, Lex asks a clarifying question instead of guessing.
4. Lex shows a "Ready to run?" card. This summarizes exactly what it's about to launch: niche(s), city or cities, and any filters, so nothing runs without a visible confirmation step.
5. You confirm, and the campaign launches. From there it behaves exactly like a campaign you built manually through Scout: same lead scoring, same no-website detection, same export.

For multi-city or multi-niche requests, LeadX handles this internally with pipe-joined values (for example, passing "dentists|orthodontists" as niches and "Austin|San Antonio" as cities), so one Lex conversation can kick off what would otherwise be several separate manual campaigns. If you want to understand what the underlying Scout search is actually doing with those parameters, see how to find local businesses without a website.

Why does Lex push back on vague requests?

This is the part that separates an assistant from a chatbot that just does whatever you say. If you ask Lex something like "find me some leads" or "get me businesses," it will not guess a random niche and city and burn a search on a request that was never going to produce anything useful. Instead, it asks you to specify:

• A real, searchable business type. "Businesses" is not a niche; "auto repair shops" is.
• A real city or region. "Nearby" or "everywhere" doesn't map to a search Scout can run; a named city or metro does.

This guardrail exists because a vague campaign wastes the same lead allowance as a well-targeted one, and a scattered list ("some businesses somewhere") is nearly useless for outreach. Lex is designed to get you to a specific, workable campaign, not just to acknowledge a request. It's the same discipline behind choosing a specific, profitable niche instead of prospecting broadly. Lex just enforces it at the point of search instead of leaving you to figure it out after a bad list comes back.

Who is Lex actually for?

Lex is built for people who already understand what a good campaign looks like but don't want to operate the form every time:

• Freelancers and small agencies running the same kind of search repeatedly (a niche, a metro, "no website") who'd rather describe it once than re-click filters.
• Agencies managing multiple clients, where each client's niche and target cities differ; the multi-chat pane keeps each client's requests and history separate.
• Anyone newer to LeadX who wants to get to a real campaign fast without first learning every field in Scout's manual builder.

It is not a replacement for judgment about which niches are worth pursuing or how to pitch what comes back; it's a faster on-ramp to the same underlying Scout, Builder, and Outreach engine everyone else uses.

What plan do you need for Lex?

Lex, along with Outreach (email and SMS) and CRM integrations, is available on LeadX's Pro plan and above. The free tier and Starter plan give you Builder (site generation) on every no-website lead you find, but the conversational assistant itself is a Pro-and-up feature. If you're evaluating whether Pro is worth it, the honest way to think about it: if you're running the same kind of search often enough that clicking through the manual form feels repetitive, Lex removes that friction.

Lex versus just using Scout manually

Nothing Lex launches is fundamentally different from what Scout can do through its manual form: same lead sourcing from Google Maps, same scoring by rating and review count, same no-website flagging. The difference is entirely in how you get there. Manual Scout is faster if you're doing something highly specific and one-off; Lex is faster if you're describing a campaign in the moment and don't want to translate your own sentence into form fields yourself, or if you're running several similar campaigns back to back and want a running conversation history of what you've already searched.

Frequently asked questions

What is Lex in LeadX?

Lex is LeadX's in-app AI assistant. It takes a plain-English description of the leads you want (a business type and a city, for example) and turns it into a real, running Scout campaign, showing a confirmation summary before anything launches. It's built on a leading large language model and supports multiple simultaneous chat threads.

Does Lex replace Scout?

No. Lex is a different way to operate Scout, not a separate lead source. Every campaign Lex launches uses the same Google Maps sourcing, scoring, and no-website detection that Scout's manual form uses. Lex just derives the search parameters from your sentence instead of you filling in fields.

Why does Lex ask me to be more specific instead of just searching?

Lex has guardrails that require a real business type and a real city before it will launch a campaign. This prevents wasted searches on vague requests like "find me some leads," which would burn your monthly lead allowance on a list too scattered to be useful for outreach.

Can Lex handle more than one city or niche at once?

Yes. You can describe a multi-city or multi-niche request in a single message (for example, several related niches across two cities) and Lex plans a campaign covering all of them rather than requiring one conversation per combination.

Do I need the Pro plan to use Lex?

Yes. Lex, along with Outreach and CRM integrations, is part of LeadX's Pro plan and above. Builder (automatic site generation) is available on every tier, including free, but the conversational assistant itself requires Pro.