Deal desk: Create customer proposals with Glass

Overview

Early Access. For access information, see Request access to Glass.

Use a shared Glass project to turn approved pricing, proposal examples, and customer context into a customer-proposal draft. Keep commercial decisions separate from presentation feedback, and review the proposal with your team before sending it to a customer.

Who this is for: Sales representatives and teams that prepare or review customer proposals.

Prepare your Glass proposal sources

Gather the following approved context before setting up the workflow. Use reference examples for structure and style, not as proof of current facts or approval to take an action.

• Approved pricing, packages, terms, and commercial rules.
• Proposal instructions and approval requirements.
• Strong proposal examples for structure, tone, and visual style, not authorization to reuse their prices or terms.
• Customer context, including the customer name, annual managed volume and currency, requested package, term, and approved requirements.

Review who can access your project before adding sensitive information. If you need information from a connected app, check the project's plugin access; a personal connection is not proof that the project can use it.

Set up your Glass deal desk workflow

In Glass, create a shared project for customer proposals. Check its audience before adding the approved sources listed above. For setup or access help, follow Get started with Glass.

Paste this prompt, then check the proposed source rules, audience, and review requirements before approval.

Draft reusable guidance for this project's customer-proposal workflow using the sources I provide:

- Use approved pricing and commercial rules as the only authority for prices, packages, and terms. Use customer context for customer facts and reference proposals for structure and style only. Follow our approval requirements.
- Establish the customer, annual managed volume and currency, requested package, term, approved requirements, and output format. Ask for missing information or clarification of conflicting sources.
- Label outputs Draft for teammate review. Return them to this project or linked Slack channel. Request editable PowerPoint and matching PDF when supported; otherwise disclose the limitation and return the draft here.
- Retain workflow, wording, structure, or formatting feedback as standing guidance only with explicit approval. Never turn one-off commercial exceptions into permanent rules.

Never invent pricing, discounts, terms, customer facts, capabilities, or approval status. Do not send or publish a proposal, update a CRM, edit a contract, or create an order form without explicit confirmation.

Identify missing sources or connections and show the guidance for approval before applying it.

After approval, follow Save and reuse instructions in a Glass space.

Prompt instructions do not restrict a connected account's permissions; review Glass access to connected apps separately.

Draft a customer proposal in Glass

Replace every bracketed field in the request below, then send it in the prepared project. Request an editable PowerPoint and matching PDF if those are the formats your team needs. If Glass cannot produce an export, ask for the draft content in the chat rather than treating a missing attachment as a completed proposal.

Create a customer pricing proposal using this project's approved sources. Read the saved workflow and source-rule files: [File names].

Customer: [Company]
Annual managed volume: [Volume and currency]
Requested package: [Package]
Desired term: [Term]
Approved customer requirements: [Requirements]
Output: Editable PowerPoint and matching PDF, if supported; otherwise state the limitation and return the draft content here

Use approved pricing and commercial rules for all prices, packages, and terms. Use the customer context for customer facts and the reference proposals for structure and style only.

Keep both outputs labeled Draft for teammate review and return them to this shared project or linked Slack channel. Ask before proceeding if required information is missing or the sources conflict.

If required customer information or approved pricing is missing, provide it or resolve the conflicting sources before continuing.

For a Slack-based request, first check how to message Glass and link the intended channel. Check the project audience before using a channel. The Slack app and a personal Slack plugin connection are separate; do not assume connecting your personal account installs the app.

Review and refine your Glass proposal

Keep the result as a draft until you have checked it against the approved sources. Ask Glass to make gaps and conflicts explicit instead of filling them in, and review any requested follow-up before it changes records or reaches another audience.

• Check every price, package, term, and customer statement against its controlling source. A proposal example is not approval for a discount or commercial exception.
• Open the returned files and confirm they contain the requested draft. Keep "Draft for teammate review" visible until your team has reviewed it.
• Give focused feedback on wording, structure, or formatting. Say explicitly whether that feedback should become a standing instruction or apply only to this proposal. Keep customer-specific commercial exceptions separate.
• Do not send the proposal, update a CRM, edit a contract, or create an order form until you have reviewed the result and explicitly authorized that action.

All starter workflows