# The AIDA model in B2B sales: four stages for the rep, four questions for the manager

https://salesbond.app/blog/aida-model-in-b2b-sales/
Published: 2026-11-07 · Updated: 2026-11-14

The AIDA model is a four-stage model of how a buyer moves toward a purchase: Attention, Interest, Desire, Action. In B2B sales it works as a structure for an email, a call and a proposal: catch the buyer with the first line, show that you understand their problem, prove the value, and ask for one specific next step. It also works, less obviously, as a set of questions a sales manager asks about a stalled deal. Did we ever get their attention? Did they ever say the problem out loud? Did we prove anything? Did we ask for a step?

Most writing on AIDA treats it as an advertising model, which is fair, since it was built for persuading many people at once. In a sales team the same four letters describe one rep, one buyer and one deal in the CRM, and they help a manager see where that deal went quiet.

## What the AIDA model is, and where it came from

AIDA stands for Attention, Interest, Desire and Action, a sequence that takes a buyer from first noticing something to acting on it ( [Close, sales glossary: AIDA](https://close.com/sales/glossary/aida)). Attention is the moment they notice you at all. Interest is when they start to care, because what you said touches something they already think about. Desire is when they want the thing, beyond understanding it. Action is the step they take: a purchase, a sign-up, a demo request ( [DealHub, What is AIDA?](https://dealhub.io/glossary/aida/)).

The origin is older than most sales methods. The American marketer Elias St. Elmo Lewis began coining the phrasing around 1898, and it was revised and promoted in the 1920s by Edward Strong, author of *The Psychology of Selling and Advertising* (1925) ( [EBSCO Research Starters: AIDA model](https://www.ebsco.com/research-starters/marketing/aida-model/)). One detail from the same source matters here. Lewis at first focused on the direct interaction in which a seller converts a potential buyer during a sales call, and only later broadened it to the whole process of finding buyers at any scale. So the sales use goes back to where the model began.

### AIDA in marketing vs AIDA in sales

In marketing, the four stages are usually four kinds of material. DealHub’s example is a content team that maps blogs to Interest and testimonials to Desire so the pieces do not overlap ( [DealHub](https://dealhub.io/glossary/aida/)). One message goes out to many people, and nobody writes back to tell you which stage they are in. You infer it from clicks.

In sales the stages are four things one person says to another, and the other person answers. That changes two things. First, each stage is a sentence or a question. Attention is the first line of the email or the first twenty seconds of the call. Interest is the buyer’s problem in the buyer’s words, usually pulled out by a question rather than stated by you. Desire is proof that the problem is worth solving and that you can solve it: a case, a calculation, a demo of one thing. Action is one concrete next step with a date.

Second because the buyer answers, you find out which stage you are actually in. A buyer who replies “not relevant” never left Attention. A buyer who took the meeting and then went quiet was interested and never got to Desire.

### Variations: AIDAS and AIDAR

The four letters have been renamed and extended more than once. Attention is sometimes called Awareness, and Desire is sometimes called Decision. Some marketers add an R for Retention, a fifth stage for keeping the customer engaged and earning referrals; others add an S for Satisfaction, meaning the buyer should be pleased with the decision after the purchase ( [EBSCO](https://www.ebsco.com/research-starters/marketing/aida-model/)). DealHub calls the Retention version AIDAR and also mentions variants that add Search and Share for online behavior ( [DealHub](https://dealhub.io/glossary/aida/)).

For a B2B team the fifth letter is the useful one, because it’s plain form stops at the signature. What happens after it is a separate piece of work for whoever owns the account.

## An AIDA model example: a B2B sales email

The simplest way to use AIDA in a sales email is to give each stage one line and refuse to let any line do two jobs. Here is a hypothetical example: a rep selling invoice automation to a finance lead.

> **Subject:** approvals in your month-end close
>
> Saw your team posted for a second AP clerk last month. (Attention)
>
> Usually that means invoice approvals are sitting with managers longer than the close can afford. Is that what is happening? (Interest)
>
> A finance team about your size moved approvals out of email and cut the wait to a day; happy to show you the before and after in ten minutes. (Desire)
>
> Would Thursday at 11 or Friday at 2 work for a short call? (Action)

![The four-line example sales email as a card with Attention, Interest, Desire and Action labels in the margin, and three removed elements crossed out](https://salesbond.app/wp-content/uploads/2026/11/aida-model-in-b2b-sales-3.png)

The finance team in the Desire line is invented for this article, and so is the result. In a real email that line only works if the rep can name the customer on the call and show the before and after. If you do not have that proof, write the Desire line as what you will show on the call.

The common failure is Desire before Interest. The second line turns into a paragraph about the product, and the buyer, who has not yet agreed that they have a problem, reads a feature list from a stranger.

The second failure is a soft Action line: “let me know if this is of interest.” It gives the buyer nothing to say yes to. AIDA ends in a step, and in B2B that step is a time on a calendar.

An email also can’t find out whether the Interest line is true. That is the job of the the call. If the buyer replies with their own version of the problem, you have your Interest stage for free, in their words. Save it, because it goes into the call, the proposal and the CRM note. We have a separate, longer [guide to cold email for a B2B team](https://salesbond.app/blog/cold-email-guide-b2b-sales-team/) that covers sequences, reply handling and logging; this article is only about the skeleton.

## AIDA on a sales call

On a call, the stages have different lengths. Attention is short, Interest is long, Desire is one thing, and Action happens before you hang up.

Attention on a call is the first sentence after “hi”. The buyer decides in those seconds whether this is a call they stay on. The sentence that works is the same one that worked in the email: something you noticed about them. “I saw you are hiring a second AP clerk” gives the buyer a reason to stay on the line; “I’m calling from a company that helps finance teams” gives them a reason to leave.

Interest is the bulk of the call, and it is made of questions. This is the part the marketing versions of AIDA skip, because an ad cannot ask. A rep can. What does the approval queue look like at close? Who waits on whom? What happens when an invoice is late? The buyer describes the problem and the rep writes it down. If you run discovery calls on a fixed set of questions, our piece on the [discovery call for a small team](https://salesbond.app/blog/discovery-call-small-team-pipedrive/) has six that cover this stage, and [SPIN selling](https://salesbond.app/blog/spin-selling-pipedrive/) is a whole method for it. AIDA puts Interest before Desire, and SPIN supplies the questions to ask during Interest.

Desire on a call is one thing, chosen from what the buyer just said. Not a tour of teh product. If they said the close slips because approvals sit with two managers, show how an approval moves between two managers and nothing else. The urge to show everything is a step back to marketing AIDA, where you don’t know which stage the buyer is in, so you cover all of them.

Action is the next step agreed on the call, with a date, and written into the CRM as an activity before the next call starts. A rep who ends with “I’ll send some information” has not reached Action. A rep who ends with “Thursday 11, you, me and your controller, I’ll bring the before and after” has. Our [sales call script that writes back to the CRM](https://salesbond.app/blog/sales-call-script-pipedrive/) is built on that idea: every line of the call leaves one record.

## AIDA in a proposal

A proposal is where AIDA gets ignored most often, because the document template was designed by someone who was not on the call. Page one is the vendor logo and a paragraph about the company. Page two is the feature list. Pricing is on page six. The next step is nowhere.

Read it as AIDA and the fix is obvious. Take an imaginary buyer, Northwind. Attention is the title, and the title names the buyer’s problem: “Cutting approval wait at Northwind from four days to one” gets opened and forwarded, while “Proposal for Northwind Ltd” gets filed. Interest is the first section, the buyer’s problem restated in the words they used on the call. This is where the discovery notes earn their keep. A buyer who reads their own sentence back on page one keeps reading, because the rest of the document is clearly about them.

Desire is the proof section: the calculation, the reference, the one screenshot that matches what they said. DealHub describes this stage in sales as case studies, demos or success metrics that connect to the buyer’s goals, with rational proof alongside the emotional pull ( [DealHub](https://dealhub.io/glossary/aida/)). Features the buyer never asked about stay out of this section. They dilute the proof.

Action is the last page, and it is a dated step. Skip “we look forward to working with you”. Name the meeting, the date and who should be in it. Then put the same date into the CRM as the next activity, because a proposal sent without a scheduled follow-up has nothing to pull it forward when the buyer gets busy. We wrote about what to do when that happens in [a follow-up rhythm after sending a proposal](https://salesbond.app/blog/follow-up-after-proposal-pipedrive/). The follow-up should already exist before you press send.

## Where deals stall: AIDA laid over your pipeline

For a sales manager, AIDA works as a diagnostic: lay the four stages over the pipeline stages in your CRM and each stalled deal shows a missing stage.

![Four AIDA stages laid over five CRM pipeline stages, with a stall sign under each: no reply, silent after meeting, silent after demo, no next activity](https://salesbond.app/wp-content/uploads/2026/11/aida-model-in-b2b-sales-2.png)

The mapping is not exact and shouldn’t be. A pipeline stage is something the team did, an AIDA stage is something the buyer felt. If your stages are built from the steps of your sales process, as in our piece on [sales process steps as CRM stages](https://salesbond.app/blog/sales-process-steps-crm-stages/), the two line up well enough to ask better questions in a pipeline review than “what’s the status”.

Attention stalls look like a deal that was created, has activities logged and has no reply from the buyer. The question for the rep is what the first line said, and whether it was about the buyer or about us. It usually turns up an opener about the vendor.

Interest stalls are the meeting that was held and then nothing: no follow-up activity, no note with the buyer’s problem in it. Ask what problem they described, in their own words, and whether it is in the note. Most of the time the note field is empty. The rep heard the problem and didn’t write it down, so nobody can check whether the proposal addresses it.

Desire stalls sit after a demo or a second meeting. Silence again, with either no proof sent or everything sent at once. Which one thing did we show, and did it match what they said?

Action stalls are the easiest to see: a proposal sent, no next activity scheduled, a close date that has passed or been pushed. What step did we ask for, and when? This is also the one stall a CRM can show without anyone reading notes, because a deal with no next activity is a fact the CRM already holds.

Each of these is a conversation with the rep. Can the CRM tell you which AIDA stage a deal is in? No. It holds what the team did and what the buyer replied. Feelings are not in it. What it can show is the absence of a stage: a deal with no reply, a meeting with no note, a proposal with no next activity. Those are the places to start the conversation.

That last stall is where this article meets what we build. SalesBond does not know which AIDA stage a buyer is in; no tool that reads only CRM fields can. What Deal Health does is check every deal against more than 20 rules in categories such as activity, progression, data, ownership and forecast, and explain what lowered each deal’s score, which is how a manager sees where activity and progression have stopped. For the Action stall, that gives the review a starting list. Interest and Desire still come from reading the notes and asking the rep. If you want to see deal health across your open deals right now, [check your CRM with SalesBond](https://salesbond.app/); the free audit looks at the last 30 days and sends a PDF report, and a second one arrives a week later with what changed.

A manager who runs this review weekly will notice what we did: the stall is rarely where the stage name says it is. A deal in “Proposal sent” that never had an Interest stage was lost at the meeting. The proposal was written to a problem nobody confirmed. Moving it back a stage feels harsh, and it is the honest move. Our piece on [sales funnel vs sales pipeline](https://salesbond.app/blog/sales-funnel-vs-pipeline/) covers why pipeline stages drift away from what the buyer actually did.

## Is the AIDA model still relevant in B2B?

It is still useful for checking a single conversation, and it cannot describe a multi-stakeholder deal on its own. AIDA is linear, and B2B buying is not. DealHub lists the criticisms plainly: the model assumes buyers move through the four stages in a fixed order, when in practice they skip stages, revisit earlier ones, or jump straight to purchase after a strong referral; it stops at Action and ignores what happens after the purchase; and in B2B, decisions involve multiple stakeholders, long evaluation periods and complex approval chains that four stages cannot capture without adaptation ( [DealHub, What is AIDA?](https://dealhub.io/glossary/aida/)).

The multiple-stakeholder point bites hardest. In a deal with a champion, a controller and a CFO, there is no single AIDA stage. The champion may be at Desire after the demo while the CFO has not reached Attention, because nobody has sent the CFO anything. The deal looks healthy from the champion’s enthusiasm and dies in the budget meeting. The model has no row for “whose Attention”, and a rep who tracks one stage for the whole account will be surprised. Our habit is to ask the AIDA questions per person on the buying side. It’s more work, and it is the only version that holds up.

Going backwards is the other case. A buyer who reached Desire in March and then went through a reorganization is back at Interest in May with a different problem. The pipeline stage says “Proposal sent”. The AIDA stage says “start over”. A model that only moves forward can’t describe that, but a manager who uses AIDA as a set of questions can, because “what problem did they describe, in their words” now has a new answer.

The long cycle itself also undoes the neatness. Over six months, Attention has to be re-won after every gap, because the buyer forgot you. Interest has to be re-confirmed, because the problem moved. So we treat AIDA as a ruler to hold against a conversation, and the pipeline, with its stages and dates, as the map. The ruler tells you whether a given email, call or document did its four jobs. Confuse the two and you get a deal that is “at Desire” on a whiteboard while the buyer has stopped answering.

## AIDA vs PAS vs SPIN: which one to reach for

These three come up together in sales training, and each does a different job.

AIDA is a structure for a message or a meeting: what order do I say things in. PAS (Problem, Agitate, Solution) is a narrower copywriting structure that lives mostly inside AIDA’s Interest and Desire: state the problem, make its cost felt, present the fix. It’s sharper for a single email and useless for a pipeline review, since it has no Attention and no Action. SPIN (Situation, Problem, Implication, Need-payoff) is a questioning method for discovery, and it lives almost entirely inside Interest. If your reps’ calls get attention and never build interest, SPIN is the fix. If they build interest and never ask for a step, SPIN won’t help and the Action line of AIDA will.

So: AIDA for the shape of any outbound touch and for the manager’s stall questions, [SPIN selling: what to ask and what to record](https://salesbond.app/blog/spin-selling-pipedrive/) for once the buyer is talking, PAS when you have one paragraph and need it to land. We compared a longer list of techniques by the trace each one leaves in the CRM in [sales techniques: which ones show up in your CRM](https://salesbond.app/blog/sales-techniques-crm-field-per-technique/).

Want a place to start on Monday? Open the deals in “Proposal sent” and look for the next activity. AIDA’s trace in a CRM is exactly that: if the Action stage happened, there is a dated activity on the deal. If there isn’t, it didn’t, and that is the first conversation to have with the rep.
