ANUM Framework: Authority, Need, Urgency, Money

By Calvin D. · Updated Oct 10, 2026

The ANUM framework is a sales qualification method that checks four things in a fixed order: Authority, Need, Urgency, and Money. It reorders the older BANT checklist so a rep confirms they're talking to someone who can buy, and that a real problem exists, before asking about budget. InsideSales.com published it as a BANT replacement.

If your reps burn discovery calls on contacts who can't sign anything, ANUM is the fix to look at. This guide covers where it came from, what each letter asks, how it compares with BANT, CHAMP, and MEDDIC, and how to turn it into a scorecard your team will actually fill in.

Where ANUM came from

ANUM comes out of InsideSales.com, the inside sales software company. In a February 2013 post, the company's team wrote that they believed the principles of BANT were correct, but that the order was now a little different. That's the whole idea in one sentence: same four ideas, new sequence, and "Timing" sharpened into "Urgency."

The person most associated with it is Ken Krogue, InsideSales.com's co-founder. A 2014 write-up by sales consultant Lori Richardson of a day spent with Krogue presents ANUM as the model to sell with in place of the old BANT order, and describes him as a co-founder of the company.

Two honest caveats before you adopt it:

• ANUM is a reorder of BANT, not a new science. Its case rests on practitioner logic (who you talk to first matters), not on a controlled study comparing the two.
• The framework came out of an inside sales setting, where reps run many short calls and the first conversation decides whether a lead gets more time. It travels best to similar motions.

ANUM in one table: what each letter asks

Notice the order. Money is last, and it's framed as "will funds exist" rather than "do you have a budget line today." That's the main philosophical break from BANT.

Why authority goes first

The standard BANT sequence opens with budget, which is a sensitive question to ask a stranger. ANUM's argument is that budget and need are both meaningless until you know whether the person on the phone can influence a purchase. A manager with a strong need and no sign-off authority will tell you everything you want to hear and then stall.

InsideSales' own account of the sequence is practical rather than theoretical. In their post, each letter doubles as a research cue before the call: note the decision maker's title and function for Authority, look at target companies and their size for Need, track company news such as a new sales leader for Urgency, and look for signs of funds such as growth or a funding round for Money. In other words, ANUM was framed as something a rep can start working before the first conversation.

The argument in practice:

1. Authority first saves calls. If the contact can't buy, you spend your next call getting to someone who can, instead of building a case for a person who can't act on it.
2. Need second stays honest. With authority confirmed, a need statement carries weight because it comes from someone who feels the consequences.
3. Urgency separates "interesting" from "scheduled." A real problem without a date is a nurture lead.
4. Money last avoids the early-interrogation feel. By the time you ask, the buyer has already told you what the problem is worth.

The four ANUM criteria, one by one

Authority

Authority means the person can approve the purchase or has a clear route to the person who can. It doesn't require a C-level title. A team lead who controls a departmental tool budget has authority for that deal. A VP who must "run it past procurement, legal, and three directors" might have influence, not authority.

Questions that surface it without sounding like an audit:

• "How have you bought software like this before?"
• "Who else would want a say before this goes ahead?"
• "If you loved what you saw, what happens next on your side?"

Record the answer as a name and a role, not a feeling. "Talking to the Head of Ops; CFO signs anything over a threshold; haven't met the CFO" is a useful note. "Seems like the decision maker" is not.

Need

Need is the problem the buyer would pay to remove, stated in their language and tied to a consequence. Weak need sounds like curiosity. Strong need names a cost: lost deals, extra hours, missed targets, compliance exposure.

Questions that pull it out:

• "What's the issue you're trying to fix?"
• "What does it cost you today, in time or deals?"
• "What have you tried so far?"

If the buyer can't describe the problem without you prompting every detail, the need is probably yours, not theirs.

Urgency

Urgency is the reason the decision can't drift. The best triggers are external and dated: a contract ending, a new fiscal year, a product launch, a leadership change, an audit. Internal pressure counts too, as long as someone owns it.

Questions:

• "What's driving the timing?"
• "What happens if this waits another quarter?"
• "Is there a date this has to be in place by?"

"Sometime this year" isn't urgency. A date with a consequence is.

Money

Money asks whether funds will be available and whether the range fits. It's the softest of the four checks on purpose. In the version Richardson relays, the logic is that if you reach the right decision maker and the need is strong enough, they will find the money. That holds in many mid-market and transactional deals and breaks down when budgets are locked annually, so treat money as a risk flag, not a verdict.

Questions:

• "Is there a budget set aside, or would this need approval?"
• "How have you funded tools like this in the past?"
• "What range were you expecting?"

ANUM vs BANT, CHAMP, and MEDDIC

Qualification frameworks are mostly the same ingredients in different orders and depths. Here's how the four compare.

A few reading notes:

• ANUM vs BANT. Both ask four questions. ANUM moves authority to the front, replaces Timeline with Urgency (a reason, not just a date), and moves money to the end. If your team already runs BANT and the main failure is wasted calls on non-buyers, ANUM is a small change with a clear payoff.
• ANUM vs CHAMP. CHAMP leads with challenges and ends on prioritization, which asks where this problem ranks against the buyer's other work. ANUM leads with the person. If your reps are great at pain discovery but waste time on contacts without influence, choose ANUM. If they reach decision makers fine but pitch too early, choose CHAMP.
• ANUM vs MEDDIC. MEDDIC goes much deeper on how the decision gets made and how success will be measured. The two aren't rivals. ANUM screens a lead in a few minutes; MEDDIC governs a complex opportunity over months.

For a wider view of how these sit alongside Challenger, SPIN, and others, see sales methodologies compared.

How to run ANUM step by step

1. Prep before the call. Look up the contact's title and function, the company's size and industry, any recent news (a new sales leader, a funding round, an expansion), and any signs of funding capacity. This mirrors InsideSales' own research cues for each letter.
2. Open with a business question, not a checklist. Start with how they handle the problem today. The four ANUM answers should emerge as a conversation.
3. Confirm authority early, in the first half of the call. Ask how purchases like this get approved. Name the roles involved.
4. Dig into need with specifics. Get one concrete cost or consequence in the buyer's words.
5. Establish urgency with a date and an owner. Ask what happens if nothing changes by that date.
6. Check money last and lightly. Ask how similar purchases are funded and what range they have in mind. Don't demand an exact number on a first call.
7. Score and decide. Fill in the scorecard below and decide: advance to an opportunity, continue discovery, or nurture.
8. Book the next step with the missing letter in mind. If authority is partial, the next meeting should include the decision maker. If urgency is missing, the next step is a trigger-event follow-up, not a demo.

A copy-ready ANUM scorecard

Paste this into your CRM notes or a call template. Score each letter 0 to 2: 0 means unknown or negative, 1 means partial, 2 means confirmed with evidence.

Suggested decision rules (adjust to your own win data):

• 6 to 8, with Authority at 2: open an opportunity and schedule the next step.
• 4 to 5: continue discovery; name the weakest letter and fix it on the next call.
• 0 to 3, or Authority at 0: nurture, or find a better contact.

One rule matters more than the totals: don't let a high Need or Money score compensate for a zero on Authority. That's the whole point of putting authority first.

ANUM in practice: examples by deal type

These are illustrative scenarios, not case studies.

Inside sales, mid-market software. A rep gets an inbound request from a team lead at a 150-person company. Authority: the lead owns the tool budget up to a limit and loops in finance above it. Need: the team's follow-up is slow and leads go cold. Urgency: a new sales director starts next month and wants a system in place. Money: funded from a departmental line. Scorecard: 2, 2, 2, 1. Advance.

Services sale to a growing business. An agency rep speaks with an operations manager who loves the idea but says the owner decides everything and "doesn't do calls." Need is strong and urgency is real, but authority is a 0 until the owner is in the room. The next step isn't a proposal; it's a short meeting request that includes the owner.

Renewal and expansion. A customer success manager asks an existing client about adding seats. Authority is clear (the same sponsor signed last year), need is shown in usage, urgency comes from a team launch, and money depends on the renewal cycle. ANUM works as a ten-minute check here, with money as the only open item.

Enterprise deal, early touch. An AE reaches a director in a large company. Authority is partial because a committee approves anything above a threshold. ANUM tells the AE where they stand on the first call; from there, the deal moves to a deeper method such as MEDDIC and a shared mutual action plan that maps the rest of the buying group.

Where ANUM fits in your pipeline process

ANUM is a lead-to-opportunity screen. It belongs at the point where a contact turns into a pipeline entry, which means it should line up with your opportunity entry criteria. A workable setup:

• Require the four ANUM fields before an opportunity can be created.
• Make "Authority confirmed (name and role)" a hard requirement, and the others soft requirements with a score.
• Re-score at each stage review so notes don't go stale.

For the broader practice of deciding what counts as a qualified deal and who gets to say so, see opportunity qualification.

Strengths and limits of ANUM

Strengths

• Fast to learn and fast to run. Four letters, four questions.
• Protects rep time by confirming buying power first.
• Urgency asks for a reason, which makes forecasting less guessy than a date alone.
• Works as a lightweight first filter ahead of a heavier method.

Limits

• It's rep-centered: it tells you what the seller needs to know, not what the buyer needs in order to buy.
• One authority check doesn't capture a buying committee. For group purchases, use it as the first screen and move to a method built for committees.
• Money-last can hide a hard budget wall. If funds are locked for the year, a high ANUM score will still produce a deal that stalls.
• It says nothing about competitors, buyer success metrics, or the formal approval process.

ANUM dos and don'ts

Do

• Name the person and the role for Authority, every time.
• Capture Need in the buyer's own words.
• Tie Urgency to an event, a date, and a consequence.
• Ask about Money as a funding question, not an interrogation.
• Re-score when new information arrives.

Don't

• Don't treat a contact's title as proof of authority.
• Don't let a strong need override a missing decision maker.
• Don't write "has budget" without knowing how it's approved.
• Don't ask all four questions in a row like a form.
• Don't run ANUM on a complex enterprise deal and stop there.

Key Facts

• What it is: a four-letter sales qualification framework: Authority, Need, Urgency, Money.
• Origin: published by InsideSales.com as a reordering of BANT, in a February 2013 company post; the company's co-founder Ken Krogue is the person most associated with it.
• Main change from BANT: authority moves to the front, money moves to the end, and Timeline becomes Urgency.
• Best for: short-cycle and inside sales, inbound lead triage, and first-call screening.
• Not enough for: complex, multi-stakeholder deals; pair it with a deeper method such as MEDDIC.
• Scoring: 0 to 2 per letter, 0 to 8 total, with Authority treated as a gate rather than an average.