Detalle del Skill

consulting-proposal

Directly supports writing outcome-focused consulting proposals and RFP responses.

CoincidenciaDirectaRevisado para consultoría
Fuentemohitagw15856/pm-claude-skillsFuente externa
Instalaciones reportadas4Solo señal de popularidad

Revisar antes de usar

La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.

Vista previa guardada

SKILL.md

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: consulting-proposal
description: "Write a consulting proposal that wins the engagement — outcomes over hours. Use when asked to write a consulting proposal, a project proposal, a pitch for a client engagement, or to respond to an RFP. Produces a proposal — the client's problem in their words, your approach & deliverables, outcomes/value, timeline & phases, investment with options, and why-you — framed around results, not a task list. Ready to export as a designed PDF."
---

# Consulting Proposal Skill

Clients don't buy hours — they buy an outcome and the confidence you'll deliver it. Losing proposals
lead with the consultant's process and a flat day-rate; winning ones lead with the client's problem and
the value of solving it. This skill writes a proposal framed around results, with tiered options that
anchor on value — ready to drop into the themed PDF export.

## Required Inputs

Ask for these only if they aren't already provided:

- **The client & their problem** — who they are, the pain, and (crucially) the *cost* of not solving it.
- **Your approach** — how you'd solve it and the concrete deliverables.
- **Outcomes** — the results the client gets, ideally quantified.
- **Commercials** — your pricing model (fixed/retainer/value-based), timeline, and what's out of scope.

## Output Format

### Proposal: [engagement] for [client]

**1. The problem (their words)** — restate their situation and the cost of the status quo. Show you *get it* before you pitch. This earns the read.

**2. Objectives & outcomes** — what success looks like, in their metrics. Lead with the value, not the activity.

**3. Approach & deliverables** — the phases and the concrete artifacts they'll receive. Enough detail to build confidence, not a padded task list.

**4. Timeline** — phases with milestones and rough dates.

**5. Investment** — the price, framed against the value/cost-of-inaction. Offer **2–3 tiered options** (e.g. core / recommended / comprehensive) — options shift the conversation from "yes/no" to "which," and anchor on the bigger one. State what's included per tier and what's out of scope.

**6. Why me/us** — relevant proof: comparable results, credentials, a short case reference. Brief.

**7. Next step** — one clear action to move forward (sign, a kickoff call, a deposit).

## Quality Checks

- [ ] Opens with the client's problem and the cost of inaction, not your bio/process
- [ ] Framed around outcomes/value, not hours or a task list
- [ ] Offers tiered options (anchors on value, gives a "which" not a "whether")
- [ ] Scope and out-of-scope are explicit (prevents scope creep later)
- [ ] Proof is specific and relevant, kept brief
- [ ] Ends with one clear next step

## Anti-Patterns

- [ ] Do not lead with "About us / our methodology" — lead with their problem; they care about themselves
- [ ] Do not sell hours/day-rate as the headline — price the outcome; hours invite haggling
- [ ] Do not give a single take-it-or-leave-it price — tiered options win more and at higher value
- [ ] Do not leave scope fuzzy — undefined scope is how fixed-price engagements bleed
- [ ] Do not pad the deliverables list — confidence comes from clarity, not volume

## Based On

Value-based consulting-proposal practice (Alan Weiss-style outcomes-over-hours, tiered options, anchor on value).
Leer la fuente completa en GitHub (abre una página externa)
Contexto

Trabajo relacionado