C
client-proposal-generator
About client-proposal-generator
A consulting-proposal generation skill for consultants and firms. It researches client companies, structures a tailored proposal, and writes it to `proposal.md` while guarding against invented facts.
Key features
- 01Client input gathering and research
- 02Problem framing and solution design
- 03Timeline, team, pricing, and terms
- 04Proposal assembly and quality checks
- 05Personalization without fabricated facts
Use cases
- 01Drafting a proposal from a brief
- 02Personalizing a proposal with company research
- 03Structuring project phases, deliverables, and pricing
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ onewave-ai/ claude-skills --skill client-proposal-generatorAfter installing, type/client-proposal-generatorin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/inputs.mdoutput-template.mdpricing.mdproblem-and-solution.mdresearch.mdteam.mdterms.mdtimeline.mdtone-and-quality.mdDetails
From the project READMEClient Proposal Generator
Transform a brief description into a complete, professionally formatted consulting proposal (proposal.md), researching the client company for personalization and structuring the document with proven consulting frameworks.
Contents
references/inputs.md-- Required and optional inputs, defaults, one-liner extractionreferences/research.md-- Client web research checklist and research brief templatereferences/problem-and-solution.md-- Problem decomposition, methodology selection, phase and deliverable templatesreferences/timeline.md-- Duration estimation and timeline formatreferences/team.md-- Role framework and team section formatreferences/pricing.md-- Pricing models, 3-tier framework, rate benchmarks, calibration, payment termsreferences/terms.md-- Standard terms and conditions blockreferences/output-template.md-- Full proposal document structure and delivery summaryreferences/tone-and-quality.md-- Tone variants, pre-delivery quality checklist, error handling
Workflow
- Gather input. Collect required fields (client name, contact, problem, firm name) and optional fields; infer the rest from context. See
references/inputs.md. - Research the client. Pull company overview, recent news, tech signals, industry context, and competitors; organize into a research brief. See
references/research.md. - Frame the problem and design the solution. Decompose into root problem, symptoms, business impact, stakeholders, and urgency; select a methodology and define phases and deliverables. See
references/problem-and-solution.md. - Construct the timeline. Estimate duration, lay out phases with milestones, and state dependencies and assumptions. See
references/timeline.md. - Compose the team. Map roles and allocations; use placeholder names if none provided and never fabricate credentials. See
references/team.md. - Build pricing. Select a model (default: 3-tier fixed), set tier prices from rate benchmarks or a supplied budget, and add payment terms. See
references/pricing.md. - Add terms and conditions. Insert the standard block, adjusting scope, IP, and assumptions to the engagement. See
references/terms.md. - Assemble and write the proposal. Combine all sections into the output structure and write the file. See
references/output-template.md. - Run the quality check. Verify accuracy, consistency, no placeholders, and no fabricated facts; match the selected tone. See
references/tone-and-quality.md. - Deliver and summarize. Write to the output path and present the delivery summary with personalization applied and review recommendations. See
references/output-template.md.
Guardrails
- Never fabricate case studies, team bios, credentials, or client facts. Omit rather than invent.
- If web research yields nothing, proceed without personalization and flag it.
- Leave no placeholder markers in the delivered document.
Comments
Markdown supported