Units
1. Customer Support Chatbot: Role, Scope and Safe Boundaries 2. Request Summarization and Classification (Ticket Triage) 3. Generating Answers from Knowledge Base (Introduction to RAG) 4. Response Drafts and Tone Management 5. Difficult Customers and Crisis Moments: De-escalation 6. Multi-Channel Support and Macro/Template Management 7. Pre-Sales: Lead Qualification and Research 8. Sales Emails and Follow-Up Sequences 9. Preparing Offers and Suggestions 10. Objection Response and Negotiation 11. CRM Notes, Interview Summaries and Action Inference 12. Quality, Compliance and Confidentiality: Not Providing False Information
Unit 9 / 12

Preparing Offers and Suggestions

Gains:

  • Ability to produce benefit-oriented and structured offer text that connects to the customer's needs
  • Ability to write a proposal structure with options (package) that frames price with value
  • Ability to create and validate a reusable quote template with placeholders

A proposal (proposal) is one of the most critical documents in the sales process. Here the customer says "yes" or "no". A weak quote is just a price list: features, items, total amount. A strong offer is a story: it shows that you understand the customer's problem, explains the solution in their language, demonstrates the benefit in concrete terms, and presents the price as a natural consequence of that value.

Artificial intelligence (AI) brings great speed in transforming dispersed needs information into a structured, benefits-focused offering. But it also has a trap: AI doesn't know your product and price; It can fit any blank space. In this unit we will use AI as a “writing accelerator” and build a reusable quote flow where you control the actual numbers and commitments.

Note: AI-generated price, duration and scope statements should never be sent to the customer without verification. The model may produce a nonexistent package or an incorrect amount; Every binding figure must be approved by you.

The Power of Benefit-Oriented Expression

Customers buy results, not features. See the difference:

  • Feature: "Our software offers automatic reporting." (What is he doing?)
  • Benefit: "You prepare the monthly report in 10 minutes, not 4 hours; your team will allocate that time to sales." (What does it gain me?)

A good quote ties each feature to a benefit, a number if possible. Instructing the AI ​​not to “feature list” but to “tie each feature to a customer win outcome” radically changes the persuasive power of the offer.

Skeleton of the Offer

A strong proposal usually consists of these parts:

  1. Situation/Need summary: Repeat the customer's problem in their language (shows understanding).
  2. Proposed solution: What do you offer, how does it work?
  3. Benefit and result: What does this solution bring? Concrete, numerical if possible.
  4. Scope and delivery: What's included, what's not; time plan.
  5. Investment (price): Framed by value, preferably with options.
  6. Next step: Clear and unique.

Step by Step: Generating a Quote

  1. Collect the need. Interview notes, answers to discovery questions.
  2. Clarify the value proposition. These are the 2-3 most important benefits for the customer.
  3. Give the skeleton to the AI. Impose the above sections.
  4. You put in the real numbers. Let the price, duration, and scope remain as placeholders; fill by hand.
  5. Offer options. 2-3 packs (good/better/best) instead of one price.
  6. Review. Is there fabricated coverage, false promises, exaggerations?

Copiable Prompts

Basic prompt that generates a structured offer from requirement information:

Role: You are a proposal writing expert. Write a draft of a benefit-oriented proposal based on the needs information below. Use these sections: (1) Needs summary (in customer's language), (2) Proposed solution, (3) Benefit and outcome (tangible, quantified if possible), (4) Scope and delivery, (5) Investment, (6) Next step. RULE: Leave a [FILL: ...] placeholder for price, duration and exact scope, DO NOT FIT the number. Tie each feature to a benefit.Need information: {{ notes }}Product/solution information: {{ product }}

Prompt that turns the feature list into benefits:

Translate the following feature list into utility language. For each feature, write a single sentence like "this gives you that"; If possible, include a concrete outcome (time/cost/risk) from the customer's situation. Using made-up numbers; leave [FILL] if number is required. Features: {{ features }}

Prompt producing option (package) price setup:

Suggest a package structure for the proposal with 3 options: Basic / Recommended / Comprehensive. Write down what need each package addresses and what it covers. Highlight the "Recommended" package in the middle as best suited to this customer. Drop prices[FILL]; I will fill it. Need: {{ need }}

Prompt that checks the offer before sending:

Check and flag this proposal draft before it is sent: - Are there any unverified/fabricated numbers, scope, or promises? - Are there any [FILL] placeholders left unfilled? - Are there any parts that have a weak feature-benefit link? - Are there hyperbole/assurance statements ("will definitely double")? List each issue with a one-sentence correction. Draft: {{ draft }}

Weak Prompt / Strong Prompt

weak bid

strong offer

Feature and price list

Need → solution → benefit → investment flow

"Our product does"

"This gives you this result"

One price, no comparison

2-3 packs, highlighted "Recommended"

Amount made up by AI

Placeholder + actual price entered manually

The difference is that the strong offer prompts the customer to ask “what am I getting?” not "what do I earn?" The question is to persuade.

Three Mini Cases

Case 1 — Fictitious price disaster averted. One representative asked for a “full quote” from AI; The model confidently wrote, "4,900 TL per month"; whereas the real price was different and AI could not know that. Fortunately, the control prompt flagged this line as "unverified number". The team converted the price fields to [FILL] placeholders; The number made up by AI was never sent to the customer again.

Case 2 — Benefit closed the language. Two offers were compared. The first one said “advanced analytics module, API access, role-based authorization.” The second turned the same features into benefits: "Your managers base decisions on data, not guesswork; it automatically talks to your systems, eliminating data entry." The second offer, with the same product and the same price, brought a noticeably higher acceptance rate.

Case 3 — The middle package worked. In single price offers, customers wonder "Is it expensive?" he teased. When moving to the 3-package structure (Basic/Recommended/Comprehensive) most customers chose the middle "Recommended" package. Offering options changed the decision from “yes or no” to “which one?” and the average contract size increased.

Tip: Include a paragraph at the top of the proposal that summarizes the customer's problem in their own words. People trust the seller who understands their problem correctly. Ask the AI ​​to extract this “requirements summary” from the interview notes; The rest of the proposal rests on this foundation of trust.

Templating and Reuse

Instead of writing each proposal from scratch, establish an approved proposal template: fixed sections (company introduction, modus operandi, conditions) do not change; variables ({{customer_need}}, {{recommended_package}}, {{price}}) are filled in each quote. AI adapts the template to the customer's situation; you enter the actual numbers and review them. This maintains both speed, consistency and brand quality.

Attention: Every number and scope statement written in the proposal is a commitment and is often binding. Only write phrases like "delivery in 2 weeks", "unlimited users", "99.9% uptime" etc. if you can actually keep your word. AI conveniently generates such claims; It is your responsibility to confirm.

Common mistakes

  • Writing a feature list and omitting the benefit (what it brings to the customer).
  • Leaving the AI-concocted price/duration/coverage unverified.
  • Offering a single price and forcing the customer into a "yes/no" dilemma.
  • Skipping the requirement summary and going straight to the solution (failing to demonstrate understanding).
  • Leaving promises that cannot be kept (guarantee, definite period) in the offer.
  • Writing every proposal from scratch, creating inconsistency and wasting time.

In summary

  • A strong offer is not a price list, but a story that follows the need-solution-benefit-investment flow.
  • Tie each feature to a concrete outcome (benefit) that the customer will gain.
  • Don't make AI match price, duration and scope; Leave a placeholder and enter the actual value.
  • Optional packages (Basic/Recommended/Comprehensive) make the decision easier and increase value.
  • Maintain speed, consistency, and commitment control together with an approved template.

Application task

Take a customer need scenario (or actual meeting notes) and produce a six-part outline with a proposal prompt. Then: (1) fill in all [FILL] placeholders with real/hypothetical numbers, (2) convert at least three features into benefits with the feature-benefit prompt, (3) add a 3-pack structure and highlight "Recommended", (4) verify that there are no false promises or unfilled fields with the audit prompt.

checklist

  • [ ] I started the proposal by summarizing the customer's problem in their language.
  • [ ] I tied each feature to a concrete benefit.
  • [ ] I left the price/duration/scope as a placeholder and entered the actual value manually.
  • [ ] I presented a price setup with options (package).
  • [ ] I have eliminated the promises that cannot be kept.
  • [ ] I cleared the fabrications and deficiencies with the audit step.
Previous Next