---
name: proposal-pricing-draft
description: Drafts a customer proposal and pricing table from discovery evidence, approved offerings, rate cards, and commercial rules. Use for proposal drafting, quote preparation, statement-of-work outlines, pricing assembly, or sales offer review.
license: Apache-2.0
metadata:
  adlass.categories: "sales-crm/quotes-proposals"
  adlass.industries: ""
  adlass.tags: "proposal, quote, pricing, scope, commercial, sales"
  adlass.adaptation: "reference-doc"
  adlass.source: "n8n:4359, original"
  adlass.version: "1"
---

# Proposal pricing draft

## Purpose

Create a review-ready proposal draft that reflects the customer's stated need, uses approved commercial inputs, and makes scope, assumptions, exclusions, price logic, and open decisions visible.

## Scope

Customer need, desired outcomes, deliverables, service levels, timeline, pricing components, discounts, assumptions, dependencies, exclusions, and validity language.

**Excluded:** accepting terms, approving discounts, sending the proposal, and making promises absent from approved sources.

## Data basis

- Discovery notes and customer requirements.
- Approved offer catalogue, rate card, proposal template, and discount policy.
- Reference cases or proof points in scope.

## Result

A proposal document, an auditable pricing sheet, and an assumptions register.

## Quality criteria

- Every priced item maps to an approved source.
- Arithmetic reconciles across line items, subtotals and totals.
- Customer requirements are covered or listed as gaps.
- Discount and validity rules are applied exactly.
- Unapproved terms are clearly marked for review.

## Instructions

Use the customer's language for needs but do not promise outcomes beyond the evidence. Separate included work from assumptions and exclusions. Do not invent rates, taxes, delivery dates, or legal terms. Where the source documents conflict, preserve both values and flag the conflict. Keep the proposal commercially clear and internally auditable.

## Adapt before use
Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

- Add the approved offer catalogue, rate card, discount rules, and template.
- Define currency, validity, tax, and date conventions.
- Name the required commercial reviewers.