Where AI fits in a B2B sales cycle: start at the handoffs

A B2B deal rarely stalls because someone worked too slowly. It stalls in the gaps. A lead sits in an inbox over a weekend. Account notes live in one person's head. The proposal waits for a price check that waits for a call. If you want AI to help your sales team, look at those gaps before you look at the tools.

Map the handoffs first

Draw the cycle as a row of boxes, then mark every place a deal moves from one person, system or day to the next. In an illustrative mid-market distributor, that might be six handoffs: web form to sales assistant, assistant to account executive, executive to pricing, pricing to proposal, proposal to legal, signed deal to onboarding.

Each handoff has the same three costs. Someone has to re-read what came before. Something gets lost. And the customer waits without knowing why. An AI assistant is good at the first, decent at the second, and can help with the third.

Four places it earns its place

Inbound questions come first. A visitor asks something specific about lead times or minimum orders. An assistant that answers from your own published content, and hands over a clean summary when the question needs a person, saves the first reply cycle. We cover how to build one in how to build and measure an AI assistant for your website.

Call preparation is next. Before an account executive speaks to a prospect, an assistant can pull together what the company publishes, what has changed since the last conversation, and what your own CRM already holds. The executive still decides what matters.

Proposals can start from a draft: the structure, the scope language and the closest past examples. A person owns the price and the promises.

Last is the write-up: call notes, next steps and the CRM update. Salespeople skip it more than any other task, and skipping it makes every later handoff expensive.

Where it should stay out

Pricing decisions, contract terms and anything that commits the company. Keep those with people, and make that rule visible to the team. A model that sounds sure of itself is not a reason to let it quote a discount.

Start with a workflow, not an agent

Anthropic's guidance on building effective agents recommends finding the simplest solution possible and adding complexity only when needed. It also separates workflows, where steps are fixed in advance, from agents that decide their own steps. For most sales handoffs a workflow is enough: take the form, check it against the content, draft the reply, send it to a person. Predictable beats clever when a customer is on the other end.

Measure the handoff, not the tool

Pick one handoff and record, before you change anything, how long it takes and how often it goes wrong. For inbound leads that could be the time to first useful reply and the share of leads that needed a second question. After four weeks, compare. If the number did not move, change the design or drop it. A tool that feels helpful and moves nothing is a cost.

One thing to do this week

Ask your sales leader to name the single handoff where deals wait longest, and pull ten recent examples. That sample is the start of a specification, and often shows that the fix is partly process and partly software. If you would like a hand shaping it, see how we approach AI development.