Sales · Specialized agent role

Proposal Generator Agent

The Proposal Generator Agent organizes confirmed discovery context, approved solution language, scope inputs, and commercial terms into a consistent proposal draft.

Get StartedReview the workflow

Best for

  • Sales teams producing recurring proposals from structured discovery and approved content libraries
  • Organizations with standard sections, product facts, legal clauses, pricing sources, and review responsibilities

Typical inputs

  • Qualified opportunity details, stakeholders, needs, success criteria, timeline, and confirmed discovery notes
  • Approved solution descriptions, scope options, pricing source, case material, legal language, and brand template

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Validate that required discovery, scope, and stakeholder information is available

2

Gather context

Select only approved product, service, evidence, and clause content relevant to the opportunity

3

Prepare the work

Assemble the narrative, scope, responsibilities, timeline, assumptions, and pricing references

4

Review and hand off

Flag gaps and route the draft through commercial, technical, and legal review as configured

Actions it can perform

  • Map discovery notes to proposal sections, reuse approved language, format tables, and identify missing decisions
  • Check names and terms for consistency, surface unsupported claims, and prepare versioned review comments

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • A structured proposal draft with customer context, scope, assumptions, responsibilities, and next steps
  • A gap checklist, source references, unresolved term list, and review trail for designated approvers

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • proposal-generator
  • organizes-confirmed
  • confirmed-discovery
  • solution-language
  • language-scope
  • scope-inputs
  • commercial-terms
  • consistent-proposal
  • proposal-draft
  • draft-shorten
  • shorten-proposal
  • proposal-assembly
  • ensuring-pricing
  • pricing-commitments
  • commitments-legal
  • legal-language
  • language-customer
  • customer-claims
  • final-scope
  • scope-remain
  • qualified-opportunity
  • opportunity-details
  • details-stakeholders
  • stakeholders-needs
  • needs-success
  • success-criteria
  • criteria-timeline
  • discovery-notes
  • solution-descriptions
  • descriptions-scope
  • scope-options
  • options-pricing
  • case-material
  • material-legal
  • brand-template
  • template-validate
  • required-discovery
  • discovery-scope
  • stakeholder-information
  • available-select
  • select-only
  • product-service
  • service-evidence
  • clause-content
  • content-relevant
  • opportunity-assemble
  • narrative-scope
  • scope-responsibilities
  • responsibilities-timeline
  • timeline-assumptions
  • pricing-references
  • references-flag
  • flag-gaps
  • draft-through
  • through-commercial
  • commercial-technical

Human approval and escalation

Approval boundary

Authorized people approve pricing, discounts, legal terms, security statements, delivery commitments, customer references, scope, and final transmission.

Escalation rule

Nonstandard terms, missing discovery, conflicting scope, unsupported capability requests, and unusual commercial risk go to named specialists.

What remains under human control

  • Sales and delivery owners define scope, feasibility, assumptions, responsibilities, and customer-specific strategy
  • Finance and legal owners decide pricing, discounts, contractual language, liability, and whether the proposal may be sent

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

HubSpotReview integration scopeSalesforceReview integration scopeGoogle WorkspaceReview integration scopeNotionReview integration scope

Example workflow

A qualified opportunity supplies agreed goals and scope; the agent builds a branded draft from approved modules and marks a custom data requirement for technical review.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

CRM Assistant

See the responsibilities, controls, and handoffs for this related specialist role.

Explore CRM Assistant

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible Proposal Generator Agent workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started