BANT Field Structure — Checkbox Pattern

Overview

When implementing BANT (Budget, Authority, Need, Timeline) qualification fields in HubSpot, use checkboxes rather than text or dropdown fields. This pattern enables clean boolean logic in workflow automation and is the recommended structure for driving SQL (Sales Qualified Lead) status changes.

This approach was established during Citrus HubSpot setup work, where initial BANT fields were created as single-line text and dropdown types — which proved too complex to use reliably in workflow trigger logic.

Recommended Field Structure

All five fields should be added as Deal properties and made visible on the Deal record card via Customize Properties.

Why Checkboxes?

Text and dropdown fields require string-matching logic in workflow conditions, which is fragile and harder to maintain. Checkboxes expose a simple true / false value that maps directly to workflow filter conditions:

• Checkbox = true → criterion is met
• Checkbox = false / unchecked → criterion is not met

This makes it straightforward to build an AND condition requiring all four BANT fields to be true before a record qualifies for the next stage.

"The logic is going to be easier with checkboxes. You're going to say, is the checkbox checked? If it's true, then you've got B. And if they've got A, then you're going to say true." — Mark Hope

Automation Pattern: MQL → SQL Workflow

The BANT checkbox structure is designed to power an SQL workflow built by cloning the existing MQL workflow:

1. Clone the MQL (Marketing Qualified Lead) workflow.
2. Rename the clone to "Sales Qualified Lead" (or equivalent).
3. In the top trigger tile, add a new criteria group containing all four BANT checkbox conditions:
   - BANT: Budget is true
   - BANT: Authority is true
   - BANT: Need is true
   - BANT: Timeline is true
4. Leave all existing MQL criteria intact — the SQL workflow requires MQL criteria plus a completed BANT assessment.

This means a contact/deal must satisfy all MQL data requirements and have a fully checked BANT assessment before the SQL workflow fires.

See also: ^[1]

Implementation Notes

• Delete old fields first. If text/dropdown BANT fields already exist, remove them from the Deal record card and delete the properties before creating the checkbox versions. HubSpot may resist deletion if fields are in use — remove from views first, then delete from property settings.
• Add to Deal record card. After creating the properties, navigate to a Deal record → About this deal → Actions → Customize Properties → Add Properties to make them visible to sales reps.
• BANT Notes field type. A standard single-line text field is sufficient for most teams. Use a long-text field only if reps need to capture extended notes.
• Seat access. Verifying Deal record changes may require access to the main CRM Deals tab if the Sales Workspace seat is unavailable. Both views expose the same deal properties.

Client Example

Citrus — BANT fields were initially created as single-line text (Budget) and dropdown (Authority), which would have required complex string-matching in the SQL workflow. The decision was made to rebuild all four as checkboxes with a separate BANT Notes text field, then use those checkboxes as the qualifying criteria group in a cloned SQL workflow.

Related meeting: ^[2]