Function: Follow-up

Proposal Follow-Up

Deployment Brief

Proposal follow-up should help the buyer decide, not pester them. This workflow links the message to the proposal, open questions, objections, and the next decision the buyer needs to make.

Difficulty

Low

Revenue impact

High

Operational impact

Medium

Risk level

Low

When it runs

A proposal has been sent and the buyer has not accepted, declined, asked a question, reached a decision date, or completed the next milestone.

Evidence in

proposal sent date and delivery channelscope, assumptions, exclusions, and pricing basisproposal viewed or engagement signalbuyer objection or open questiondecision date and stakeholder statusprior follow-up attemptsaccount owner and approval rulesapproved follow-up language and commercial boundaries

What AI prepares

proposal follow-up task with owner and due date
context summary with scope and open questions
draft follow-up message for review
commercial-change exception note
measurement event for proposal response, stale proposal count, and decision reason capture

Decision rules

Follow up when the decision date is approaching, the proposal is viewed, or an open question remains.
Use proposal engagement as internal context, not creepy customer-facing language.
Route discounts, scope changes, legal terms, and timeline promises to review.
Stop after explicit decline, opt-out, expired opportunity, or confirmed competitor decision.
Move future-fit opportunities to nurture instead of repeating the same proposal prompt.

Human approval point

A proposal owner checks scope, price, exclusions, legal language, proof claims, dates, and customer-visible commitments before the draft leaves the business.

What stays human

Do not discount automatically.
Do not change scope, assumptions, exclusions, or legal terms in follow-up copy.
Do not mention proposal tracking in a way that feels invasive.
Do not continue after clear decline, opt-out, or expired opportunity.

Quality and stop gates

The follow-up references the actual proposal and open decision.
Scope, assumptions, exclusions, and pricing basis are visible.
The buyer engagement signal is attached without sounding invasive.
Commercial changes require owner review.
The message has one clear next step.
Stop rules are visible after decline, opt-out, or expired opportunity.

How it is measured

Time from proposal sent to first follow-up.
Proposal response rate by follow-up reason.
Stale proposal count.
Open question resolution rate.
Commercial-change exception rate.
Win/loss or decision reason capture rate.

Systems involved

CRMproposal toolemailcalendarcall notesinternal alerting

Worked example

consulting firm · account owner

a proposal has been viewed twice after the decision date but the buyer has not replied

What the owner reviews

proposal scope, assumptions, exclusions, pricing basis, engagement signal, decision date, and stakeholder status
draft follow-up, open question, owner review task, and a flag for any scope, pricing, or timeline change

Workflow Dataset Record

Deployment evidence and duplicate boundary

This section is generated from the enriched workflow dataset. It is designed for pilot planning, not as validated outcome evidence.

Buyer Problem

Proposals stall when the team treats send date as the finish line. The buyer still has stakeholders, objections, procurement steps, open questions, and timing risk, but follow-up often becomes a generic nudge with no link to the decision process.

Economic Logic

The value is late-stage pipeline discipline. Better proposal follow-up should make next steps, decision dates, unresolved objections, and stakeholder gaps visible early enough for the seller to act before a deal quietly becomes no-decision.

Baseline Metric

proposal_next_step_integrity_rate

Share of sent proposals with decision date, stakeholder map, open objections, follow-up owner, next action, buyer response, and stage disposition captured before the forecast period closes.

Source system: CRM opportunities, proposal tool, email/calendar activity, call notes, sales engagement tasks

Minimum Viable Pilot

Duration: 30 days
Sample: First 50 sent proposals from one sales segment or all proposals in one monthly cohort
Owner: Sales manager
Threshold: At least 90% of sent proposals have next action, decision date or reason absent, stakeholder context, and disposition before aging past the follow-up SLA.

Unique Workflow Test

Audit sent proposals for proposal sent date, next-step task, decision date, stakeholder list, open objections, buyer response, follow-up content, stage movement, and close/lost reason. The workflow should separate active deals from no-decision drift.

Duplicate Guard

Do not merge with quote follow-up or post-consultation follow-up. Proposal follow-up owns stakeholder, objection, decision-date, and stage-movement evidence after a formal proposal is sent, while the adjacent workflows handle priced quote status or meeting recap next steps.

Not Ready If

Proposal sent dates are not tracked.
Opportunity stages do not distinguish proposal sent.
Close-lost/no-decision reasons are blank.

Claim level: Pilot-shaped. Sources support workflow mechanics and pilot design unless field evidence is attached.

HubSpot Sales Automation Guide

Sales automation should start with repetitive revenue work, clean CRM data, routing, sequences, baseline metrics, and regular audit.

NIST AI Risk Management Framework

AI workflows should include risk mapping, measurement, governance, and accountable human oversight.

Keep moving

Where this workflow connects next

A useful AI build rarely lives on one page. Check the surrounding workflow, the decision rule, and the deployment path before you commit budget.

Workflow group

Sales Follow-Up

Compare the nearby workflows that usually break before or after this one.

Open

Sales pillar

AI Sales Workflow Deployment

See how sales teams can use AI for pipeline briefs, meeting prep, follow-up, account plans, and stalled deals.

Open

Decision tool

First workflow selection rubric

Score this against other revenue workflows before you commit build time.

Open

Industry fit

Professional Services

Use this where partner capacity, proposal speed, delivery handoffs, and reporting decide margin.

Open

Service path

AI Workflow Implementation

Build the first version around a sales or revenue workflow that already has demand.

Open

Sales review

Pressure-test this sales workflow

Bring the sales motion, the source evidence, and the number this workflow should move.

Open

Adjacent workflows

Quote Follow-Up Proposal Compliance Review Lead Follow-Up No-Response Follow-Up

TL;DR

Proposal follow-up turns proposal status, buyer questions, and decision timing into a useful next message and owner task.

What is proposal follow-up?

Proposal follow-up is the process of moving a sent proposal toward a clear decision, question, revision, or close-loop outcome.

Who is this workflow for?

Service businesses, consulting firms, construction companies, SaaS teams, agencies, and professional firms with commercial follow-up volume.
Teams where good conversations still go stale because next steps are not owned.
Companies that need helpful follow-up without pressure, spam, or accidental promises.
Operators who want buyer context and stop rules before adding more automation.

What breaks in the manual process?

The manual process usually breaks when context disappears between the buyer signal and the next message:

the message ignores the actual proposal;
scope and exclusions disappear from the conversation;
tracking data is used in a way that feels invasive;
discounting starts before the buyer asks;
the decision date passes with no owner action;
commercial changes are made in a casual email.

The workflow should make the next action useful, specific, and reviewable.

How does the AI-enabled process work?

The workflow gathers proposal details, engagement signal, decision date, stakeholder status, prior attempts, and approval rules. It drafts a useful follow-up and flags any commercial change for review.

AI prepares the work. The accountable owner still approves anything that changes pricing, scope, timing, terms, ownership, or expectations.

What does this look like in practice?

Example scenario: A proposal has been viewed twice after the decision date but the buyer has not replied. The workflow checks proposal scope, assumptions, exclusions, pricing basis, engagement signal, decision date, and stakeholder status. It prepares draft follow-up, open question, owner review task, and a flag for any scope, pricing, or timeline change.

What decision rules should govern this workflow?

Follow up when the decision date is approaching, the proposal is viewed, or an open question remains.
Use proposal engagement as internal context, not creepy customer-facing language.
Route discounts, scope changes, legal terms, and timeline promises to review.
Stop after explicit decline, opt-out, expired opportunity, or confirmed competitor decision.
Move future-fit opportunities to nurture instead of repeating the same proposal prompt.

What are the implementation steps?

Trigger: A proposal has been sent and the buyer has not accepted, declined, asked a question, reached a decision date, or completed the next milestone.
Inputs collected: proposal sent date and delivery channel, scope, assumptions, exclusions, and pricing basis, proposal viewed or engagement signal, buyer objection or open question, decision date and stakeholder status, prior follow-up attempts, account owner and approval rules, approved follow-up language and commercial boundaries.
AI/system action: The system checks the required evidence, summarizes the buyer context, applies the follow-up rule, and prepares the next action.
Human review point: The account owner reviews discounts, scope changes, timeline promises, legal language, objections, strategic accounts, and any follow-up that changes the proposal or customer expectation.
Output generated: proposal follow-up task with owner and due date, context summary with scope and open questions, draft follow-up message for review, commercial-change exception note, measurement event for proposal response, stale proposal count, and decision reason capture.
Follow-up or next action: The owner approves, sends, routes, suppresses, nurtures, or closes the loop based on the evidence.

Required inputs

proposal sent date and delivery channel.
scope, assumptions, exclusions, and pricing basis.
proposal viewed or engagement signal.
buyer objection or open question.
decision date and stakeholder status.
prior follow-up attempts.
account owner and approval rules.
approved follow-up language and commercial boundaries.

Expected outputs

proposal follow-up task with owner and due date.
context summary with scope and open questions.
draft follow-up message for review.
commercial-change exception note.
measurement event for proposal response, stale proposal count, and decision reason capture.

Human review point

The account owner reviews discounts, scope changes, timeline promises, legal language, objections, strategic accounts, and any follow-up that changes the proposal or customer expectation.

Risks and stop rules

Stop when consent is unclear, the buyer declined, the lead opted out, the record conflicts with existing ownership, the follow-up would change commercial terms, or there is no useful reason to contact the buyer.

Best first version

Start with proposal sent date, scope summary, open question, decision date, engagement signal, owner, and a draft that requires review before any commercial change.

Advanced version

Add buyer engagement signals, account-level suppression, stakeholder mapping, nurture paths, manager review dashboards, and monthly exception review after the basic owner workflow is reliable.

Related workflows

Measurement plan

Time from proposal sent to first follow-up.
Proposal response rate by follow-up reason.
Stale proposal count.
Open question resolution rate.
Commercial-change exception rate.
Win/loss or decision reason capture rate.

FAQ

What is proposal follow-up?

Proposal follow-up is the process of helping a buyer move from proposal review to a clear decision, question, revision, or close-loop outcome.

What should AI check before proposal follow-up?

AI should check proposal scope, assumptions, exclusions, pricing basis, engagement signal, decision date, stakeholder status, prior attempts, and approval rules.

What should stay under human control?

Discounts, scope changes, timeline promises, legal language, strategic accounts, and commercial terms should stay under account owner review.

What is the simplest first version?

Start with proposal sent date, scope summary, open question, decision date, engagement signal, owner, and review flag for commercial changes.

How should proposal follow-up be measured?

Track time to first follow-up, response rate by reason, stale proposals, open question resolution, exception rate, and decision reason capture.

Related Workflow Group

AI Workflows for Sales Follow-Up

Compare this workflow against nearby operating problems before choosing the first build. The group shows what usually breaks together, what evidence is needed, and where review still matters.

View Workflow Group

Related Workflows

Speed To Lead Response Instant Lead Callback After-Hours Lead Response

Speed-to-lead AI workflow

A field report on faster lead response without losing evidence, routing, consent, or owner review.

Read Report