MEDDIC and BANT in Oracle deals.

Oracle's sales teams are trained on qualification frameworks, principally MEDDIC and BANT. These are the structured methods reps use to assess a deal and to gather the information that drives their strategy. Every discovery question maps to a field in one of these frameworks, and most of those fields are things the buyer would be wise to keep to itself. Understanding what the rep is filling in, and why, lets the buyer answer the questions without handing over the leverage they are designed to extract.

1. What MEDDIC and BANT are.

BANT stands for Budget, Authority, Need, and Timeline, a simple qualification method that asks whether the buyer has money, the power to spend it, a genuine need, and a date. MEDDIC is more elaborate, covering Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion. Oracle's reps use these to decide which deals to pursue, how to position, and crucially how hard to push on price.

Each framework is a set of fields the rep wants to complete. The discovery conversation, which we cover in our note on sales discovery questions, is the mechanism for filling them in. The buyer who recognises the framework behind the friendly questions can decide deliberately what to reveal and what to withhold.

2. Budget, and why you should not name yours.

The first thing both frameworks seek is budget. A rep that learns the buyer's budget has learned the buyer's price ceiling, and Oracle's proposal will rise to meet it. This is the single most valuable piece of information a buyer can withhold, and the one buyers most often volunteer, often in the belief that sharing it speeds the process.

The disciplined answer is to discuss requirements rather than budget. The buyer reveals what it needs and the standards a solution must meet, never the figure it is prepared to spend. When pressed for a budget, the buyer redirects to value and to competitive alternatives. We treat budget discipline as a foundation of every renewal negotiation engagement, because revealing the budget undoes most of the work that follows.

3. Authority and the economic buyer.

Both frameworks seek to identify who controls the money. MEDDIC calls this the economic buyer, and the rep's goal is to reach that person directly, because the economic buyer can approve a purchase that procurement might resist. A rep that bypasses the negotiating team to reach an executive sponsor can often secure a deal on softer terms than a disciplined procurement process would allow.

The buyer's defence is to keep the negotiation channelled through a single, prepared point of contact, and to ensure executives do not make commitments outside that channel. When Oracle reaches the economic buyer directly, the buyer's negotiation discipline can collapse. Managing this is part of the procurement governance we describe in our note on Oracle's deal desk process and the buyer side equivalent.

4. Timeline, and the deadline trap.

The frameworks seek the buyer's timeline because a known deadline is leverage. A rep that knows the buyer must close by a certain date will let that date approach, then use it to press for signature on Oracle's terms. The buyer that reveals its internal deadline, a board approval, a fiscal date, a renewal expiry, has handed Oracle the timing advantage.

The disciplined buyer keeps its timeline private and, where possible, starts early enough that no deadline pressures it. Oracle's own deadline, the fiscal year end we cover in our year end tactics note, should be the only deadline in the room. A buyer with no visible deadline of its own, facing an Oracle with a pressing one, holds the timing leverage.

5. The champion, and being coached against yourself.

MEDDIC's champion is the internal advocate the rep cultivates to sell on Oracle's behalf inside the buyer's organisation. The rep equips the champion with arguments, urgency, and reasons to push the deal forward. A champion who is not aware of being coached can become Oracle's voice in internal discussions, advancing Oracle's timeline and Oracle's framing against the buyer's own interests.

The buyer should ensure its internal stakeholders understand the negotiation strategy and do not become unwitting channels for Oracle's pressure. This is a matter of internal alignment, the same discipline that prevents a business unit from committing to a product purchase that undermines a coordinated ULA position. The buyer's people should advocate for the buyer, not relay Oracle's case.

6. Answering the framework on your terms.

None of this means stonewalling the rep. A buyer that refuses every question signals weakness and stalls the deal. The skill is to answer generously on the things that do not cost leverage, the technical requirements, the standards, the use case, and to answer carefully on the things that do, the budget, the authority, the timeline. The buyer controls the conversation by being open about needs and disciplined about limits.

This applies across the product line, whether the deal concerns Oracle Database options or an applications renewal. The framework is the same, and so is the discipline. The buyer who knows which questions feed which fields answers in a way that informs the rep without arming Oracle's pricing.

7. What disciplined buyers do.

• Never name a budget. Discuss requirements and standards, not the figure you can spend.
• Channel the negotiation. Keep a single prepared point of contact and protect the economic buyer.
• Hide your timeline. Reveal no internal deadline and start early enough to need none.
• Align your stakeholders. Ensure internal advocates work for you, not as Oracle's channel.
• Answer needs, withhold limits. Be open on requirements, disciplined on budget, authority, and timing.

For the wider framework see our sales discovery questions note, the renewal negotiation service, the ULA deal page, and the Oracle Negotiation Playbook.