playbooks

home / skills / christopheryeo / claude-skills / new-proposal

new-proposal skill

/new-proposal

This skill guides turning discovery inputs into a first-draft Sentient proposal, aligning with brand, using existing artifacts for a quick, shareable draft.

npx playbooks add skill christopheryeo/claude-skills --skill new-proposal

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.3 KB
---
name: new-proposal
description: Outline the lightweight process for turning discovery inputs into a first-draft Sentient proposal.
version: 0.2.0
author: Sentient GTM Enablement Team
updated: 2025-05-19
keywords: proposal, sales enablement, sentient.io
---

# New Proposal Drafting (Lightweight)

## Overview
The **new-proposal** skill is now a streamlined playbook. It explains how to assemble a first-draft Sentient proposal using
existing skills and source folders in this repository—no custom scripts or bundled assets required. Follow these instructions to
move quickly from discovery to a shareable document while keeping messaging aligned with Sentient's positioning.

## Quick Start
1. Run the latest **customer-brief** skill to capture discovery findings for the account.
2. Open the relevant product narrative in `product-white-paper/` and flag the sections that map to the customer's needs.
3. Reference the tone and messaging guidance in **sentient-brand-guideline** to keep language on-brand.
4. Combine the above into a proposal outline using your preferred editor (Docs, Notion, Markdown). The sample outline in
   `presentation-outline/` is a good starting point when you need structure.

## Recommended Workflow
1. **Validate inputs**: Confirm you have the newest intake form, customer brief, and stakeholder list from the account team.
2. **Draft the executive summary**: Highlight customer objectives, Sentient's solution fit, and expected outcomes in 2–3
   paragraphs.
3. **Detail the solution**: Use content from `product-white-paper/` to explain architecture, differentiators, and implementation
   plan.
4. **Showcase proof**: Pull relevant success metrics from `smartchat-service-costs/` or other collateral to reinforce value.
5. **Outline next steps**: Define timeline, owners, and required follow-up actions. Link to the **work-day** skill if the deliverable
   should live in the shared Workday folder.

## Success Criteria
- Proposal mirrors Sentient's structure (executive summary → solution overview → roadmap → next steps).
- Messaging stays aligned with the brand guidelines and references approved differentiators.
- Source documents are cited or linked so reviewers can verify claims quickly.
- Output is saved using the `<YYYYMMDD>-<CustomerName>-Proposal-R<Revision>` naming convention.

## Limitations & Notes
- This lightweight skill intentionally omits automation scripts, bundled samples, and tests. It is documentation-only.
- Teams that need repeatable generation or validation should add back scripts in a dedicated branch and update this guide.
- Keep sensitive customer data out of the repository; store working drafts in approved collaboration tools.

## Related Skills & Artifacts
- **customer-brief** – Use to gather and refresh account discovery notes before drafting.
- **product-white-paper** – Provides canonical product positioning and technical capabilities.
- **sentient-brand-guideline** – Supplies tone, terminology, and styling cues for all outbound materials.
- **work-day** – Automates saving final drafts to the shared Workday folder once ready for review.

## Extending Later
If you decide to reintroduce automation:
1. Stand up generator scripts in `scripts/` or a new `automation/` folder.
2. Document new usage patterns here so others know how to run them.
3. Add tests under `tests/` to cover the automated workflow.

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.

FAQ

Do I need any scripts or assets to use this playbook?

No. This is a documentation-only process that relies on existing skills and source folders; no custom scripts are required.

Where should I save working drafts with customer data?

Store working drafts in approved collaboration tools or secure folders; do not keep sensitive customer data in the code repository.