Decision brief

When a new lead arrives, do not begin with an AI product pitch. Confirm the desired business result, map one workflow, quantify the current burden, identify systems and sensitive data, define authority and exceptions, and name the person who owns the result. Offer a bounded evaluation first. If the workflow is suitable, propose a small showcase with approved sample data and measurable acceptance criteria before any live implementation.

Ask
Outcome, workflow, volume, systems, current effort, errors, data sensitivity, approvals, exceptions, and owner.
Offer
A free fit evaluation and, when practical, one contained five-business-day workflow showcase.
Avoid
No guaranteed savings, broad transformation promise, live-system access, or sensitive-data transfer during initial qualification.

An owner submits a request saying the team needs an AI agent for customer follow-up. Instead of recommending a platform immediately, CSLM asks where inquiries arrive, how staff decide who should receive them, which details are missing, what promises require approval, and how many requests are handled each week. The first useful opportunity may be a completeness check and review queue—not an autonomous sales agent.

Move routine work forward. Route exceptions to people.

Before and after

Before

  • The lead receives a generic AI-services pitch.
  • Tool selection happens before the workflow and data are understood.
  • The prospect is encouraged to send files, credentials, or customer records too early.
  • A free conversation becomes an undefined promise to build everything.

After a controlled improvement

  • The lead receives a prompt acknowledgment and a short set of relevant questions.
  • One workflow, business outcome, owner, and baseline are documented.
  • Sensitive data and credentials stay out of initial intake.
  • The evaluation ends with a clear no-fit, prerequisites, showcase, or implementation recommendation.

The first questions to ask a new lead

01

What outcome matters?

Ask what should become faster, more accurate, less expensive, or easier to control—and why it matters now.

02

Where does the workflow start and end?

Identify the trigger, final output, responsible owner, and every system or person the work crosses.

03

How often does it happen?

Record weekly or monthly volume, peaks, backlog, average handling time, and how long customers or staff wait.

04

Where is effort or quality lost?

Ask about repeated entry, searching, handoffs, corrections, missed follow-up, duplicate work, and common exceptions.

05

Which systems hold the source of truth?

List the CRM, inbox, forms, spreadsheets, accounting tools, calendars, document stores, and existing integrations—without requesting credentials.

06

What information is sensitive?

Identify personal, payment, health, employment, legal, credential, or confidential business data and exclude it from the first sample unless a later approved design requires it.

07

What may the workflow do?

Separate reading, classifying, drafting, recommending, updating, sending, approving, and deleting. Name every action that requires a person.

08

What would make the evaluation successful?

Agree on a baseline, sample, measurement method, acceptance threshold, stop condition, and decision owner.

Tools and process components

  • Lead acknowledgment template
  • Ten-minute qualification checklist
  • Current-state workflow map
  • Baseline and exception sample
  • Data and permission boundary
  • Showcase acceptance criteria
  • Implementation decision summary

Match the next step to the evidence

Not every inquiry should become an implementation project. The first offer should reduce uncertainty and protect both parties.

Lead conditionOfferDeliverableBoundary
Problem is still broadFree fit evaluationOne workflow hypothesis, missing information, risks, and recommended next stepNo implementation promise
Prerequisites are missingReadiness recommendationProcess, data, ownership, or integration work to complete firstMay recommend ordinary automation or no AI
One workflow is testableContained five-business-day showcaseWorkflow map, bounded prototype or demonstration, observations, and measurement planUses approved sample or redacted data; no autonomous live commitments
Showcase meets acceptance criteriaPaid implementation scopeResponsibilities, integrations, controls, milestones, support, and pricing for approvalStarts only after scope and access are explicitly approved

Choose the next page for the workflow you want to improve.

These links continue the specific operating examples above. They do not assume that every workflow needs AI.

Measure the workflow, not the demonstration.

MetricHow to measure itUseful signal
Response timeTime from lead arrival to human acknowledgmentShows whether genuine inquiries are being handled consistently
Qualification completenessRequired discovery fields answered before solution designReduces premature proposals and repeated follow-up
Baseline burdenCurrent volume, handling time, corrections, delays, and exceptionsCreates a comparison point for a showcase
Showcase decisionNo-fit, prerequisites, proceed, revise, or stop with written reasonsPrevents an experiment from becoming an open-ended project

Safeguards to keep

  • Do not ask a new lead to email passwords, API keys, payment data, health data, or complete customer records.
  • Do not promise a percentage of savings before observing a representative workflow and documenting the calculation.
  • Do not imply that the free evaluation guarantees a showcase or production implementation.
  • Do not let a prototype send messages, approve transactions, change customer records, or make commitments without explicit scope and human authorization.

AI consulting lead intake FAQ

What should the first reply to an AI-consulting lead say?

Acknowledge the request, state that the first step is understanding one workflow and business outcome, ask only the essential qualification questions, and tell the lead not to send credentials or sensitive records.

What is included in CSLM's free evaluation?

CSLM reviews the stated workflow, current tools, burden, data boundary, authority, and measurement opportunity. The result is a fit decision and recommended next step. A contained five-business-day showcase is offered only when the workflow is practical and its boundaries can be agreed.

When should pricing be discussed?

Ask early whether there is an approved budget or decision process, but provide implementation pricing only after the workflow, responsibilities, controls, integrations, and acceptance criteria are sufficiently defined.

Related practical guides

A good first lead conversation makes the problem smaller and the decision clearer. Ask enough to map one workflow, then offer only the next step the evidence supports.