new-proposal_skill

Overview

This skill outlines a lightweight playbook for turning discovery inputs into a first-draft Sentient proposal. It shows how to assemble an executive summary, solution details, proof points, and next steps by reusing existing discovery notes and product content. The goal is a shareable draft that stays on-brand and review-ready without custom tooling.

How this skill works

Start by running the customer-brief to capture the latest discovery, then map customer needs to relevant sections in the product-white-paper. Use the brand guideline to align tone and terminology, combine findings into a clear outline, and add proof points and a concise roadmap. Save the draft with the agreed naming convention and link source documents so reviewers can verify claims.

When to use it

• Preparing a first draft proposal after a discovery call or intake form is complete.
• When you need a quick, brand-aligned proposal without building automation.
• Before handing a proposal to sales engineering or an account owner for review.
• When you must produce a reusable outline that references canonical product content.
• When a shareable document is needed for internal review or customer preview.

Best practices

• Validate you have the latest intake form, customer brief, and stakeholder list before drafting.
• Draft a 2–3 paragraph executive summary that states objectives, solution fit, and expected outcomes.
• Pull architecture, differentiators, and implementation steps from product-white-paper rather than inventing new claims.
• Cite or link source documents and performance metrics so reviewers can verify statements quickly.
• Name the file using <YYYYMMDD>-<CustomerName>-Proposal-R<Revision> and store the draft in approved collaboration tools.
• Keep sensitive customer data out of the repository and use secure folders for working drafts.

Example use cases

• Convert discovery notes into a concise proposal for an upcoming customer review meeting.
• Create a shareable first draft for the account team to iterate on before sales engineering builds a technical response.
• Produce a quick proposal outline to estimate timeline, owners, and next steps after initial scoping.
• Assemble collateral and proof points for an internal funding or prioritization discussion.
• Prepare a draft to upload to the shared Workday folder for stakeholder visibility and formal review.