AI
← Use case library
Sales & Lead GenerationB2B ServicesAgencies

AI Proposal Follow-up Assistant

Recover stalled proposals with timely, relevant follow-ups.

Identifies quotes and proposals that have not received a response and drafts follow-up messages based on proposal details and customer context.

proposalsfollow-upquotesrecoveryclosing

What you need to build this

Connect these tools, give the AI this data, expect these outputs.

1

Connect

APIs & tools to set up

OAuth, API keys, or webhooks depending on the tool.

3

Give to AI

Inputs per run

  • Proposal sent date, amount, line items, and recipient
  • Days since send with no response or open signal
  • Prior email thread context and objections raised
  • Call notes from discovery and proposal walkthrough
  • Follow-up cadence rules (day 3, 7, 14 after send)
4

Expect

AI outputs

  • List of stalled proposals ranked by deal value and silence duration
  • Follow-up email draft referencing specific proposal sections
  • Alternative angles: value recap, objection address, deadline, break-up email
  • CRM task creation payload for rep review
  • Suggested call script if email unresponsive after 2 touches
BeginnerSemi-automatedHigh value3 no-code · 3 low-code · 5 custom options

Business problem

Proposals go out and get forgotten — reps move to new opportunities while sent quotes sit unopened. Studies show most deals need 3+ follow-ups after proposal, but most reps stop after one.

Expected outcome

Automated detection of silent proposals with tiered follow-up drafts referencing specific proposal content, prior conversations, and appropriate urgency — ready for rep send.

Who it's for: B2B sellers who send formal quotes or proposals via email or CRM and lose deals to silence rather than explicit rejection.

Required data sources

What data goes into the AI

  • Proposal sent date, amount, line items, and recipient
  • Days since send with no response or open signal
  • Prior email thread context and objections raised
  • Call notes from discovery and proposal walkthrough
  • Follow-up cadence rules (day 3, 7, 14 after send)

What the AI should output

  • List of stalled proposals ranked by deal value and silence duration
  • Follow-up email draft referencing specific proposal sections
  • Alternative angles: value recap, objection address, deadline, break-up email
  • CRM task creation payload for rep review
  • Suggested call script if email unresponsive after 2 touches

APIs needed to automate this

System behavior

  • Runs daily scan of proposal-stage deals — not instant on send
  • Draft-only — rep reviews and sends every follow-up
  • Stops cadence on reply, meeting booked, or explicit opt-out
  • Escalates high-value silent proposals to manager after 14 days
  • Never discounts or changes proposal terms without rep input

No-code vs low-code vs custom

No-code

Lowest effort

Non-technical owners, quick validation, under 50 runs/day

3 options listed

Low-code

Medium effort

Operators comfortable with Zapier/n8n, need more control

3 options listed

Custom build

Highest effort

High volume, custom logic, or strict data privacy requirements

5 options listed

No-code optionsLow-code optionsCustom build stack
HubSpot deal stages + task reminders with ChatGPT draft pasten8n daily: CRM proposal stage deals → silence check → Claude draft → GmailCRM query for deals in proposal-sent stage beyond threshold
Zapier: deal in 'Proposal Sent' 5+ days → GPT follow-up → Gmail draftGoogle Sheets proposal tracker + Apps Script + OpenAIGmail thread search for proposal attachment and reply detection
PandaDoc/Proposify notifications + manual GPT follow-upMake.com: proposal tool webhook → follow-up schedule → email draftOpenAI/Claude with proposal context and objection-aware prompts
Gmail draft API — human sends
Recovery metrics: proposal-to-close rate before and after automation

Start with no-code to validate the workflow. Move to low-code when you hit rate limits or need branching logic. Custom build when volume, privacy, or integration depth requires it.

Step-by-step implementation

  1. 1Define proposal-sent stage in CRM and required fields (amount, sent date)
  2. 2Set follow-up cadence rules: 3, 7, 14 days with different message angles
  3. 3Connect Gmail to detect replies — exclude deals with recent responses
  4. 4Build prompts that reference proposal line items and prior objections
  5. 5Deliver as morning Gmail drafts or CRM tasks for rep approval
  6. 6Track recovery rate and adjust cadence based on industry sales cycle

Risks and limitations

  • Aggressive follow-up on proposals annoys buyers and damages relationships
  • Misdetecting replies in CC'd threads creates duplicate follow-ups
  • Break-up emails can prematurely kill deals still in internal review
  • Proposal content in AI prompts may include confidential pricing

Related use cases