BANT Qualification Framework in HubSpot

Overview

BANT (Budget, Authority, Need, Timing) fields provide the structured qualification data needed to automate the transition of contacts to Sales Qualified Lead (SQL) status and trigger automatic deal creation in HubSpot. This article describes how BANT fields are configured, the automation logic that acts on them, and where they surface across the data model.

This pattern was implemented and reviewed during the ^[1] HubSpot engagement. See ^[2] for the originating discussion.

Field Structure

Each BANT dimension is represented as a dropdown field on the Contact record, with tiered values indicating qualification strength. The highest-tier value (e.g., "Has authority") signals a positive qualification for that dimension.

The exact option labels should be confirmed in HubSpot. The pattern above reflects the tiered structure discussed in the source meeting.

SQL Automation Logic

A HubSpot workflow monitors the four BANT fields on the Contact record and fires when all four are set to their highest qualifying value:

IF Budget = [highest tier]
AND Authority = [highest tier]
AND Need = [highest tier]
AND Timing = [highest tier]
THEN → Set Lifecycle Stage = "Sales Qualified Lead"
     → Auto-create Deal
     → Set Deal Owner = Contact Owner

Configuration notes:
- The current implementation requires all four BANT criteria to be met. The team discussed potentially relaxing this to three-of-four; this should be revisited once the workflow has been live for a meaningful period.
- Deal ownership is automatically inherited from the Contact owner at the time of deal creation, ensuring no deals are created without a responsible rep.

BANT on the Deal Record

Once a deal is auto-created, the primary working context for the rep shifts from the Contact to the Deal record. BANT fields should therefore be visible on the Deal form so reps can reference qualification data without navigating back to the Contact.

This was identified as a gap during the CAI review — BANT fields were present on the Contact but absent from the Deal view. The action item is to add all four BANT fields to the Deal record layout.

Relationship to the MQL → SQL Lifecycle

BANT sits at the SQL stage of the qualification funnel, downstream of MQL. The full lifecycle progression is:

Prospect → Lead → MQL → SQL → Opportunity (Deal)

• Lead → MQL is triggered by basic contact completeness fields plus the qualifying "Are you juicing?" question. See ^[3] for details.
• MQL → SQL is triggered by BANT completion (this article).
• SQL → Opportunity is represented by the auto-created Deal record.

BANT fields are intentionally scoped to the SQL transition and deal stage. They are not part of the MQL trigger logic.

Data Model Considerations

Qualifying data — including BANT — is stored at the Contact level for day-to-day sales use, but the broader data model decision for Citrus America places company-level qualifying data (e.g., "Are you juicing?") at the Company record, with an automation syncing it down to associated Contacts.

BANT fields are an exception to this pattern: because BANT reflects the qualification of a specific individual (their authority, their timeline), they remain Contact-scoped rather than Company-scoped.

See ^[4] for the rationale behind storing qualifying data at the company level.

Implementation Checklist

• [x] BANT fields created on Contact record
• [x] BANT fields made visible on Contact view
• [x] SQL workflow built to trigger on all-four BANT completion
• [x] Deal auto-creation wired to SQL workflow
• [x] Deal owner set to Contact owner on auto-creation
• [ ] Reorder BANT fields on Contact record (B → A → N → T)
• [ ] Add BANT fields to Deal record layout

Client Reference

This framework was first implemented for ^[5]. The BANT fields and SQL automation were built by the prior HubSpot admin (Chris) and reviewed/extended by Mark Hope's team in April 2026.