AI Sales Automation · Practical guide · AI for sales prospecting

How to use AI in sales: build a faster prospecting workflow

The goal of using AI in sales is not to send more messages. It is to find prospects who fit the offer, prepare a clear reason to contact each one, and learn from the results faster. AI can organize service information, suggest target criteria, and draft sales messages. A person still decides who to contact, what to say, what outreach volume to use, and what to change next.

Published: August 27, 2026Updated: August 27, 20269 min read

Key takeaways

  • AI can turn service information into initial target criteria and draft sales messages.
  • A person reviews who to contact, what to say, what outreach volume to use, and when to run it.
  • The user can watch execution and pause, resume, skip, or add an instruction when needed.
  • Use each prospect's progress to improve the first stage where the numbers fall.

Written by

Kachilu Research

Product research and editorial team

Reviewed by

Tatsuro Matsuzaki

CTO at Kachilu

Has more than 1,000 LinkedIn followers and practical expertise in LinkedIn recruiting and sales outreach.

Use AI throughout the sales prospecting workflow—not just for one-off prompts

Writing a sales message with AI is only one step. A useful workflow connects service analysis, prospect selection, research, messaging, execution, and measurement. AI can prepare the repetitive work, while a person confirms who to contact, what can be claimed, what outreach volume to use, and when to stop.

Sales stageAI can prepareA person reviews
Service setupSummarize the service and likely customer problem from the URL.Decide the value the service can deliver and the exclusions.
Prospect searchSuggest roles, industries, regions, and search terms.Decide whether a prospect is likely to have the problem.
Message draftingDraft first DMs and follow-ups.Review and edit the facts, wording, and request.
ExecutionCarry out repeated work in the configured order.Set volume, timing, and stop conditions.
ReviewRecord progress for each prospect and the count at each stage.Decide which stage to improve.

Start with service information and define the next step

Start with information that explains what the service does, which problem it solves, and who is likely to have that problem. Then define one next step for an interested prospect, such as reading a use case, visiting the product page, or booking a conversation. If the input is vague, the target suggestions and messages will be vague too.

  1. 1.Confirm the problem the service solves in language a buyer would recognize.
  2. 2.Name the role that feels the problem and the role that can act on it.
  3. 3.Define evidence of fit, such as company stage, market, recent activity, or a relevant initiative.
  4. 4.Choose one low-friction next step for an interested prospect.
  5. 5.Write exclusions before building a list, not after messages have been sent.

Kachilu uses the service URL to summarize the offer and prepare initial target criteria. A CTA URL is optional and defines where an interested prospect should go next. After task creation, the dashboard lets the user review and change the reusable templates behind first DMs and follow-ups, the volume for each step, and the days and times for recurring runs. These settings can be adjusted to company policy instead of being left entirely to AI.

Let AI narrow the list, then verify why each prospect is worth contacting

AI can turn the service hypothesis into roles, industries, business needs, regions, tools, post topics, and search terms. Treat those suggestions as a research plan, not a finished lead list. A person still needs to confirm that the role can feel the problem, the company fits the offer, and the available context gives a real reason to make contact.

Review AI-generated message templates before they guide outreach

A useful sales template defines what the message must accomplish at each stage. The connection note explains the reason to connect. The first DM identifies a relevant problem and opens a conversation. A follow-up responds to the state of the conversation instead of repeating the same pitch.

  • Check that every claim can be verified from the service or the prospect's public context.
  • Remove generic praise and invented familiarity.
  • Keep one purpose per message and make the next step optional until interest is clear.
  • Review the reusable template because it will guide later prospect-specific wording.
  • Use the recipient's language and context without pretending to know more than the evidence shows.

Kachilu generates reusable templates for first DMs and follow-ups. After task creation, the user can review, edit, regenerate, and save those templates. The final wording is adapted at runtime using the prospect's available information, conversation context, and language.

Keep execution visible and step in when needed

The biggest operational gap appears after the message templates and workflow settings are reviewed. If execution happens in a black box, the seller cannot see which prospect is active, which step was completed, or when a login, reply, or unexpected page requires judgment. In Kachilu, the user can follow the current task in Kachilu Browser and pause, skip, or resume the workflow when attention is needed.

SituationSystem behaviorHuman action
Normal repeated stepContinue through the configured relationship-first flow.Monitor progress without approving every click.
Context has changedKeep the current state visible.Pause, skip, or add an instruction.
Login or identity checkStop at the step that needs a person.Complete the check, verify the page, and resume.
Prospect should be removed from the workflowPreserve the prospect and action history.Exclude the prospect or stop the task.

Fix the first weak stage, then test again

A prospecting workflow becomes useful when it explains where the process slows down. Record the number of qualified prospects, relevant engagements, connections or follows, DMs, replies, and CTA-stage actions with stable definitions. Then change the first weak stage rather than asking AI to rewrite everything.

  1. 1.If too few prospects qualify, tighten or replace the target hypothesis.
  2. 2.If contact is weak, review the channel, context, and reason for reaching out.
  3. 3.If replies are weak, inspect relevance, claim, tone, and the first question.
  4. 4.If conversations stall, revise the next step rather than increasing message volume.
  5. 5.Run the next small cohort with one major change so the result can be read.

Review these settings before using AI for sales outreach

  • The service, target problem, audience, exclusions, and next step are written down.
  • AI suggestions are treated as hypotheses until a person checks the evidence.
  • Reusable message templates have an owner who reviews claims, tone, and relevance.
  • Volume, schedules, stop conditions, and exceptions are explicit.
  • Each prospect's stage and completed actions are visible.
  • The team changes one major variable at a time and records the next decision.

This design lets AI remove preparation and coordination work without removing sales judgment. Kachilu connects the steps for LinkedIn prospecting—from the service URL and target hypothesis to visible browser execution and stage data—so a small team can run the loop without rebuilding it in separate tools.

FAQ

Frequently asked questions

What can AI do in sales prospecting?

AI can summarize an offer, suggest target roles and search terms, organize prospect context, draft message templates, and record workflow activity. A person should still approve the audience, claims, volume, exceptions, and interpretation of results.

Can AI fully automate outbound sales?

AI can automate repeated preparation and execution steps, but a reliable outbound process still needs human decisions about the offer, target fit, message claims, operating limits, replies, and exceptions. Full automation is not a substitute for those decisions.

What information should I give an AI sales tool first?

Start with the service page, the target customer's problem, evidence of fit, exclusions, and one next step for an interested prospect. Kachilu requires a service URL and accepts an optional CTA URL for that destination.

How do I stop AI-written sales messages from sounding generic?

Define one purpose for each stage, use only verified prospect context, remove generic praise, and review the reusable template for claims, tone, relevance, and the next request before it guides individual messages.

More Kachilu insights

Kachilu

Connect AI preparation, visible execution, and insights for the next sales test

Use Kachilu's 14-day free trial to review message templates and workflow settings, then follow each prospect's progress in one workflow.

Start a 14-day free trial