NEAT Selling: Need, Economic Impact, Access to Authority, Timeline

By Calvin D. · Updated Oct 10, 2026

NEAT selling is a sales qualification method that checks four things before a deal earns pipeline space: the buyer's Need, the Economic Impact of solving it, your Access to Authority, and the Timeline for acting. It's presented as a modern variation of BANT. Salesforce credits The Harris Consulting Group and Sales Hacker with developing it.

This article covers what each letter asks, how NEAT differs from BANT, CHAMP, MEDDIC and ANUM, how to run it step by step, and a scorecard you can copy.

What is NEAT selling?

NEAT stands for Need, Economic Impact, Access to Authority, Timeline. It keeps the shape of a four-letter qualification checklist, so it's easy to teach and easy to put in a CRM. What changes is the emphasis, and Salesforce describes it as a close variation of BANT with the focus shifted in key areas.

The three shifts that matter:

• It starts with the problem, not the money. BANT opens with Budget and Authority. NEAT opens with Need, so the first conversation is about the customer's situation.
• It asks what the purchase does, not whether it's affordable. Budget becomes Economic Impact: the revenue gained or cost removed in a critical area of the business.
• It accepts that your contact may not decide. Authority becomes Access to Authority: can your contact reach, or bring in, the people who do?

A note on origin. The credit to The Harris Consulting Group and Sales Hacker comes from Salesforce's write-up of sales methods. Other writers attribute NEAT to the Harris firm alone, so treat the exact authorship as attributed rather than settled. The practical content of the four letters is consistent across descriptions.

The four NEAT criteria

N is for Need

Need asks what is actually driving the buyer. Salesforce's summary says reps start by exploring the customer's core needs, which avoids a pitch that doesn't fit. A stated need ("we want a better dashboard") is a starting point. The underlying need ("our managers can't see which deals are stuck") is what you qualify on.

Good evidence for Need:

• The buyer describes the problem in their own words, with a specific recent example.
• Someone owns the problem and feels it.
• There's a current workaround, and the buyer can say why it's failing.

Weak evidence: a polite "yes, that's interesting," or a need that only you have described.

E is for Economic Impact

Economic Impact asks what solving the problem is worth. Salesforce notes that NEAT looks past return on investment alone to the business outcome, such as added revenue or reduced costs in a critical area. It also contrasts it with BANT: Budget asks whether the buyer can afford the purchase, while Economic Impact asks what the purchase would do for the business.

In practice you want a number the buyer will say out loud and defend. If you calculate it alone and present it, it's your estimate. If the buyer builds it with you, it's their business case. For example, a rep selling a scheduling product might ask the operations lead how many hours a week the team spends fixing double-bookings, and what an hour costs. The answer is the buyer's figure, not the rep's.

A is for Access to Authority

The wording is deliberate. Salesforce says NEAT recognizes that the person a rep is pitching might not be the final decision-maker, and the goal is reaching someone who can relay information or join the buying committee. BANT's Authority question asks whether the buyer is allowed to buy. NEAT asks whether you can get to the people who are.

That moves the qualification question from "Are you the decision-maker?" (everyone says yes) to something you can test:

• "Who else will want a say, and have you worked with them on a decision like this?"
• "Would you be comfortable if I joined a short call with them?"
• "Who's likely to push back, and what would they push back on?"

Access is something you can prove with a meeting on the calendar. A promise to "pass it along" isn't access.

T is for Timeline

Timeline asks when the buyer needs to act and what happens if they don't. Per Salesforce, reps identify the tipping point that drives a purchase and judge urgency by asking whether the company will face dire consequences if they don't move forward or can take their time.

A real timeline has a cause: a contract ending, a launch, an audit, a hiring plan. A date with no cause ("sometime next quarter") will slip.

NEAT vs BANT, CHAMP, MEDDIC and ANUM

Qualification frameworks mostly differ in two ways: what they check first, and how much of the buying process they try to map. Here's how the family lines up.

Three comparisons to keep in mind:

• NEAT vs BANT: NEAT is BANT with the order and the questions changed. If your team already runs BANT fields in the CRM, NEAT is a small change: rename Budget to Economic Impact, rename Authority to Access to Authority, and lead with Need.
• NEAT vs CHAMP: Both start with the customer's problem. CHAMP keeps Money as a literal question and adds Prioritization. NEAT replaces Money with a value question, so it suits deals where budget gets created once the impact is clear.
• NEAT vs MEDDIC: MEDDIC maps the whole decision: metrics, economic buyer, criteria, process, pain, champion. NEAT is lighter. Many teams use NEAT to qualify in and MEDDIC to run a deal once it's large.

ANUM is a four-letter screen like BANT with a different order, putting Authority first. For a wider view of how these methods sit beside selling styles like consultative selling, see sales methodologies compared.

How to run a NEAT qualification, step by step

1. Open with the situation. Ask about the problem before price, process or people. Let the buyer talk until you can restate the need in one sentence and they agree.
2. Separate stated need from core need. Ask "What's behind that?" until you reach a business consequence, not a feature request.
3. Build the impact with the buyer. Ask for the quantities: hours, errors, churned customers, delayed revenue. Write their numbers down and read them back.
4. Find out who else decides. Ask who's involved, who benefits and who might object. Note names and roles.
5. Test access. Ask for an introduction or a joint call. Record whether it was granted, deferred or declined.
6. Find the trigger. Ask what happens if nothing changes by a given date, and what's driving that date.
7. Score it and decide. Rate each letter with evidence. Advance, nurture, or disqualify.
8. Record it where the team can see it. Put the four answers in the opportunity record so managers can review them in a deal inspection.

NEAT scorecard template

Copy this into your CRM notes or a deal review doc. Score each row from 0 to 2: 0 means no evidence, 1 means partial, 2 means the buyer has confirmed it.

A simple rule of thumb: 6 or more with Need and Access both at 1 or higher is worth active pursuit. Anything with Need at 0 isn't a deal yet, whatever the other scores say. Adjust the thresholds to your own win data.

NEAT in practice: examples by deal type

These are illustrative situations, not case studies.

Software renewal and expansion. A rep selling an add-on module to an existing customer already has Need and Access. The work is Economic Impact: what the current limit costs in manual work, and who signs the expansion. NEAT keeps the rep from assuming the champion controls the money.

Inbound lead from a webinar. The contact is a manager who wants to "look at options." Need is vague and Access is unproven. A good NEAT call asks about the problem, asks who the manager would show this to, and sets a second call with that person. If neither happens, the lead goes to nurture.

Services engagement. A consultant selling a project finds the buyer's Timeline is real (a regulatory deadline) but the Economic Impact is unquantified. The next step is a short scoping exercise with the buyer's finance partner, which also builds Access.

Outbound to a new account. The contact responds to the message but can't describe a problem. That's Need at 0. NEAT's value here is permission to stop: it gives the rep a reason to close the opportunity before it inflates the pipeline.

NEAT do's and don'ts

Do:

• Lead with the buyer's problem and let them quantify it.
• Treat Access as a thing you can see: a meeting, an introduction, a named person.
• Tie Timeline to an event the buyer owns.
• Keep the scorecard short enough that reps use it on every call.
• Pair it with a shared plan once a deal qualifies, such as a mutual action plan.

Don't:

• Treat Economic Impact as your own ROI slide. A figure the buyer didn't help build is weak evidence.
• Accept "I'm the decision-maker" without asking who else is involved.
• Skip Timeline because Need looks strong. A real problem with no trigger often stalls.
• Use NEAT as a script. Ask in the order the conversation allows.
• Replace your whole methodology with it. Adding NEAT to what you already run is easier to adopt than a swap.

Where NEAT falls short

NEAT is a qualification screen, not a full sales methodology. It won't tell you how to differentiate, how to manage a six-person buying committee through procurement, or how to forecast. It also doesn't name a champion, a competitor or the formal decision criteria, which is why MEDDIC-style methods exist for larger deals. Treat it as the front door of opportunity qualification and add structure behind it as deal size and complexity grow.

Key Facts

• What it is: a four-part sales qualification method: Need, Economic Impact, Access to Authority, Timeline.
• Origin: credited by Salesforce to The Harris Consulting Group and Sales Hacker; other sources credit the Harris firm alone.
• Relationship to BANT: a close variation that opens with Need and swaps Budget and Authority for Economic Impact and Access to Authority.
• Main idea: qualify on the problem and its value first, and on whether you can reach the real decision-makers.
• Best for: B2B deals where the first contact may not decide and budget follows value.
• Not enough alone for: large enterprise deals with formal procurement and many stakeholders.

For the broader picture, see opportunity qualification and the original BANT framework.