Sales & Leads
Proposal Assembly Line
Assemble a proposal from your rate card and the discovery note. Fees come from the menu. A red team catches scope you did not offer.
Updated 30 Oct 2026
- Difficulty
- Intermediate
- Time to implement
- About 1 day to install, then about 40 minutes per proposal
- Monetization potential
- Very high
Goal
Assemble a proposal from a discovery note and a priced menu you control: scope, assumptions, exclusions, timeline language, and a fee that matches your rate card. A human sends it. The agent never does.
Tools required
Direct is the vendor's public site. Affiliate appears only when ShipPlays is enrolled in that program.
Your discovery notes
DirectA doc or the CRM record of the call. Mark inferences so they cannot sneak in as client requirements.
A rate card you maintain
DirectThe only place numbers live. If a price is not on the menu, the draft is not allowed to name one.
PandaDoc
DirectOptional signature page after you like the doc. A Google Doc or PDF is enough to start.
Step-by-step setup
Write the menu before the next sales call
Three to six offers. Each has a name, who it is for, deliverables, exclusions, a price rule (fixed fee or a range you actually honor), and assumptions: access, timeline, how many revision rounds. If you cannot exclude something, you do not yet have an offer. You have a hope.
Fill a discovery note the same day as the call
What they want, what they have tried, constraints they stated, deadline they stated, budget if they stated one, and open questions. Mark anything you inferred with the word inference. An inference is not a requirement.
Assemble from the menu and the note
The prompt selects one offer or says no offer fits and stops. Stopping is a success. It drafts scope in their words, lists assumptions, lists exclusions, and copies the price from the menu. It does not discount. It does not blend two offers unless your menu has a bundle with its own price.
Red-team the draft against the menu
Look for a promise the menu does not include, an inference treated as a fact, and a fee that does not match the card. Fix those before you make the doc pretty. Pretty proposals hide scope.
Add a short letter in your voice and send it yourself
Two to five sentences at the top. You send it. The agent does not email the buyer. If you need contract terms, paste your standard terms. Do not ask the model to draft a contract from scratch.
Change the menu, or write the exception by hand
When a prospect wants a change, you update the menu for next time or you write a one-off by hand and you can explain it. You do not quietly teach the prompt to hide a discount you have not decided to give.
Exact prompts
Assemble from the menu
After the discovery note is filled and inferences are marked.
Assemble a proposal from the menu and the note. Do not invent prices, discounts, legal terms, or deliverables.
Menu:
{MENU}
Discovery note:
{NOTE}
Rules:
- Pick one offer that fits, or return exactly: NO OFFER FITS, and the closest offer plus what is missing. Then stop.
- Do not blend offers unless the menu contains that bundle.
- Copy the price from the menu. If the note contains a budget below the price, do not discount. Say the budget is below the menu and stop for a human.
- Inferences in the note become questions, not scope.
- Timeline language stays conditional: if kickoff is the week of X, then Y. Do not promise a date the note does not contain.
- Exclusions are copied from the menu, not softened.
Return: offer name, scope, assumptions, exclusions, fee line copied from the menu, open questions, and a do-not-promise list.Red team
Before the doc is designed or sent.
Red-team this draft against the menu and the note. Do not improve the tone.
Menu:
{MENU}
Note:
{NOTE}
Draft:
{DRAFT}
Find:
- Deliverables not in the chosen offer
- Exclusions from the menu that the draft dropped or softened
- Inferences treated as facts
- Any fee, discount, or date that is not in the menu or the note
- Legal or warranty language the menu does not contain
Quote the offending line and say delete or replace-with, using menu language. If you find nothing, list the checks you ran. Do not say the draft looks strong.Expected results
- Proposals that match an offer you are willing to deliver.
- Assumptions and exclusions a buyer can see.
- Fees that trace to the rate card.
- A clean stop when the work is custom. That stop is a success.
Guardrails
- The model does not invent prices, discounts, or legal terms.
- Inferences never appear as client requirements.
- Do not promise dates the delivery team has not seen.
- No auto-send.
- Keep discovery notes in an account your client allows. Do not paste them into a tool they forbade.
Common mistakes
Starting from an old proposal you liked and asking for one like this for a new client.
Start from the menu and this client's notes. Old proposals smuggle old scope.
Smoothing exclusions because they sound negative.
The red team checks exclusions first. Clear beats pleasant.
Discounting inside the draft to win the deal before you have decided.
A discount is a manual edit you can explain, or it does not exist.