Budget Objection Response

This drill handles the full lifecycle of a single budget objection: diagnose the root cause (is this a real constraint or a smokescreen?), generate a navigation response that helps the prospect find or unlock budget, propose creative payment structures that preserve deal value, and log the outcome. Budget objections are fundamentally different from price objections — the prospect may agree with the value but cannot access the money.

Input

• A budget objection received during a proposal call, follow-up email, or negotiation
• Deal record in Attio with existing pain data (from pain-discovery-call drill)
• The objection itself: call transcript segment, email text, or manual entry

Steps

1. Extract and classify the budget objection

Run budget-objection-classification on the objection text with the full deal context from Attio.

The classifier returns one of 6 root causes:

• no_allocated_budget: No line item for this category
• budget_exhausted: Budget existed but is spent this period
• wrong_budget_owner: Talking to the wrong person about money
• competing_priorities: Budget earmarked for other initiatives
• procurement_friction: Process blocking, not money
• budget_smokescreen: Not a real budget issue

If is_smokescreen: true, STOP budget navigation. The real objection is elsewhere. Re-qualify the deal: check value perception, champion strength, and competitive situation. Log the deal as needing re-qualification and exit this drill.

If root_cause: "ambiguous", ask the diagnostic questions before proceeding. Do not generate a budget navigation response without a clear root cause.

2. Validate the value foundation

Pull the deal record from Attio. Check pain-to-price ratio:

• If pain_to_price_ratio >= 5: Strong value foundation. Budget navigation has a high chance of success because the ROI story is compelling for internal justification.
• If pain_to_price_ratio is 3-5: Moderate. Budget navigation is possible but the champion will need stronger materials.
• If pain_to_price_ratio < 3: Weak value foundation. Even if budget is found, the deal may stall. Recommend running additional discovery to strengthen the pain case before investing effort in budget navigation.

If pain data is missing, run pain-quantification-prompt using context from the objection conversation.

3. Generate the budget navigation response

Run budget-navigation-response with the classified objection, navigability score, and deal context. This returns:

• Selected response framework (e.g., find_discretionary_funds, defer_and_lock, navigate_to_budget_owner)
• Verbal response script (3-5 sentences, empathetic and collaborative)
• Diagnostic questions to deepen understanding of the budget situation
• Follow-up email
• Champion asset recommendation (budget justification memo, cost-of-delay analysis, etc.)
• Escalation path if the direct approach fails

4. Generate payment structure options

If the root cause is no_allocated_budget, budget_exhausted, or competing_priorities, also run payment-structure-generation to create 3-5 creative payment structures.

Rank the structures by fit for this prospect's situation. Attach the top 2 options to the follow-up email as concrete alternatives.

Do NOT generate payment structures for wrong_budget_owner (need to find the right person first), procurement_friction (not a money problem), or budget_smokescreen (not a real objection).

5. Human review checkpoint

Human action required: Review the generated response before delivery. Check:

• Does the verbal response acknowledge the budget constraint empathetically (not dismissively)?
• Are the payment structure options realistic for your company's billing flexibility?
• Is the champion asset recommendation something you can actually produce?
• Do the diagnostic questions explore the budget situation without being invasive?

Adjust tone and specifics. The response should feel like a strategic partner helping solve a procurement problem.

6. Deliver the response

On the next call or in a follow-up:

1. Deliver the verbal response — acknowledge the constraint, express willingness to help navigate it
2. Ask the diagnostic questions to understand the budget landscape
3. If appropriate, share payment structure options as concrete alternatives
4. Propose a clear next step (intro to budget owner, deferred start, pilot, etc.)

7. Log the outcome

Update the deal record in Attio:

{
  "budget_objection_root_cause": "budget_exhausted",
  "budget_navigation_framework": "defer_and_lock",
  "budget_response_delivered_date": "2026-03-30",
  "budget_objection_outcome": "resolved|partially_resolved|unresolved|escalated|lost",
  "days_to_resolution": 5,
  "payment_structure_accepted": "deferred_start|quarterly|phased|standard|none",
  "deal_value_preserved": true,
  "discount_offered": 0,
  "navigability_score": 7
}

Fire PostHog events:

{
  "event": "budget_objection_handled",
  "properties": {
    "deal_id": "...",
    "root_cause": "budget_exhausted",
    "framework_used": "defer_and_lock",
    "outcome": "resolved",
    "navigability_score": 7,
    "pain_to_price_ratio": 12.5,
    "days_to_resolution": 5,
    "payment_structure_accepted": "deferred_start",
    "deal_value_preserved": true,
    "discount_percentage": 0,
    "was_smokescreen": false
  }
}

8. Route based on outcome

• Resolved: Deal moves forward. Update deal stage in Attio. If a payment structure was accepted, flag the deal for finance team to process the non-standard billing.
• Partially resolved: Budget path identified but not yet approved. Schedule a follow-up. Arm the champion with the budget justification materials.
• Unresolved: Escalation needed. If wrong_budget_owner, request intro to the actual budget holder. If competing_priorities, build a comparative business case. If budget_exhausted, set a reminder for next budget cycle.
• Lost: Log lost reason as "Budget" in Attio. Critically: tag whether this was a genuine budget constraint or a smokescreen. Add to loss analysis dataset.

Output

• Classified budget objection with root cause and navigability assessment
• Tailored navigation response with verbal script, follow-up email, and champion materials
• Payment structure options (when applicable) that preserve deal value
• PostHog events for budget navigation effectiveness tracking
• Routing recommendation for next action based on outcome

Triggers

Run manually after each budget objection is received. At Scalable+ levels, triggered automatically by budget-detection-automation drill when a budget objection is detected in a call transcript or email.