proposal-writer

Name: proposal-writer
Author: jezweb

937stars96forks

How to install proposal-writer?

jezweb/claude-skills/proposal-writer

$npx -y skills add jezweb/claude-skills --skill proposal-writer

Installs into the current project.

Summary

Write a client proposal, quote, scope of work, or engagement letter for a service business. Covers project understanding, scope, timeline, pricing presentation, and terms. Use whenever the user asks for a proposal, quote, project proposal, client proposal, SOW, statement of work,

Files · 1

View on GitHub

SKILL.md

1	# Client Proposal Writer
2
3	Produces proposals for service businesses — web development, consulting, trades, professional services, creative agencies. The goal is a document that wins the work by showing you understood the problem, have a clear plan, and are easy to work with.
4
5	## Before You Start
6
7	Gather these inputs. Ask for anything missing:
8
9	1. Client name and business — who is this for, what do they do
10	2. What they asked for — the brief, the problem, the conversation summary
11	3. What you are proposing — your recommended solution at a high level
12	4. Pricing — your numbers, or ask for guidance on range
13	5. Timeline — how long, any fixed deadlines
14	6. Tone — match the client relationship (new vs existing, corporate vs casual, local tradie vs enterprise)
15
16	If the user has notes from a discovery call or email thread, use those to write the "project understanding" section in the client's own language.
17
18	---
19
20	## Proposal Structure
21
22	Present sections in this order. Every section earns its place — cut any that do not apply.
23
24	### 1. Project Understanding
25
26	This is the most important section. It proves you listened. Restate the client's problem in their words, not yours. Show you understand what they are trying to achieve, not just what they asked you to build.
27
28	Too corporate:
29	> We understand that your organisation is seeking to leverage digital transformation to enhance customer engagement across multiple touchpoints and drive sustainable growth through an integrated online presence.
30
31	Right tone:
32	> You have been running the business for 12 years on word-of-mouth alone, and it has worked — you are booked out most weeks. The problem is that when someone searches "plumber Newcastle" you do not show up, and you are losing jobs to competitors with half your experience. You want a website that shows up in local search and makes it easy for people to call or book online.
33
34	Rules for this section:
35	- Use the client's language, not industry jargon
36	- Reference specific details from the conversation ("you mentioned", "as we discussed")
37	- State the business problem, not just the technical requirement
38	- Keep it to 2-3 short paragraphs
39
40	### 2. Proposed Solution
41
42	High-level description of what you will do and why this approach makes sense for them. This is the "what and why", not the detailed scope.
43
44	Connect the solution back to their problem. "Because you need local customers to find you, we will build the site on WordPress with a focus on local SEO structure from day one" is better than "We will build a WordPress website with SEO."
45
46	One to two paragraphs. Save the detail for the scope section.
47
48	### 3. Scope and Deliverables
49
50	Numbered list of specific items the client will receive. Each item should be concrete enough that both parties can agree on whether it was delivered.
51
52	Too vague:
53	> - Website design and development
54	> - SEO optimisation
55	> - Ongoing support
56
57	Right level of detail:
58	> 1. Custom WordPress website — up to 8 pages (Home, About, Services x4, Contact, Blog)
59	> 2. Mobile-responsive design matching your brand colours and logo
60	> 3. Local SEO setup — Google Business Profile optimisation, schema markup on all pages, location-based meta titles
61	> 4. Contact form with email notifications to your nominated address
62	> 5. Online booking integration with your existing Calendly account
63	> 6. Basic analytics setup (Google Analytics 4 + Google Search Console)
64	> 7. 30-minute training session on how to update content yourself
65	> 8. 30 days of post-launch support for bug fixes and minor adjustments
66
67	What is NOT included is just as important as what is. Add an exclusions note at the bottom of this section:
68
69	> Not included in this scope: Ongoing content writing, paid advertising setup or management, additional pages beyond the 8 listed above, custom functionality not described here. These can be quoted separately if needed.
70
71	### 4. Timeline
72
73	Phases with durations or target dates. Show the client what happens when.
74
75	\| Phase \| Duration \| What happens \|
76	\|-------\|----------\|--------------\|
77	\| Discovery and planning \| Week 1 \| Content gathering, sitemap sign-off \|
78	\| Design \| Weeks 2-3 \| Homepage mockup, revision, remaining pages \|
79	\| Development \| Weeks 3-5 \| Build, integrations, internal testing \|
80	\| Review and launch \| Week 6 \| Client review, revisions, go-live \|
81
82	If there is a fixed deadline (event, season, campaign), state it and work the timeline back from it. Flag any dependencies on the client: "This timeline assumes content and images are provided by [date]."
83
84	### 5. In

People who liked this also viewed

6 picks

Type

proposal-writer

937stars96forks

View on GitHub

How to install proposal-writer?

jezweb/claude-skills/proposal-writer

$npx -y skills add jezweb/claude-skills --skill proposal-writer

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Client Proposal Writer
2
3	Produces proposals for service businesses — web development, consulting, trades, professional services, creative agencies. The goal is a document that wins the work by showing you understood the problem, have a clear plan, and are easy to work with.
4
5	## Before You Start
6
7	Gather these inputs. Ask for anything missing:
8
9	1. Client name and business — who is this for, what do they do
10	2. What they asked for — the brief, the problem, the conversation summary
11	3. What you are proposing — your recommended solution at a high level
12	4. Pricing — your numbers, or ask for guidance on range
13	5. Timeline — how long, any fixed deadlines
14	6. Tone — match the client relationship (new vs existing, corporate vs casual, local tradie vs enterprise)
15
16	If the user has notes from a discovery call or email thread, use those to write the "project understanding" section in the client's own language.
17
18	---
19
20	## Proposal Structure
21
22	Present sections in this order. Every section earns its place — cut any that do not apply.
23
24	### 1. Project Understanding
25
26	This is the most important section. It proves you listened. Restate the client's problem in their words, not yours. Show you understand what they are trying to achieve, not just what they asked you to build.
27
28	Too corporate:
29	> We understand that your organisation is seeking to leverage digital transformation to enhance customer engagement across multiple touchpoints and drive sustainable growth through an integrated online presence.
30
31	Right tone:
32	> You have been running the business for 12 years on word-of-mouth alone, and it has worked — you are booked out most weeks. The problem is that when someone searches "plumber Newcastle" you do not show up, and you are losing jobs to competitors with half your experience. You want a website that shows up in local search and makes it easy for people to call or book online.
33
34	Rules for this section:
35	- Use the client's language, not industry jargon
36	- Reference specific details from the conversation ("you mentioned", "as we discussed")
37	- State the business problem, not just the technical requirement
38	- Keep it to 2-3 short paragraphs
39
40	### 2. Proposed Solution
41
42	High-level description of what you will do and why this approach makes sense for them. This is the "what and why", not the detailed scope.
43
44	Connect the solution back to their problem. "Because you need local customers to find you, we will build the site on WordPress with a focus on local SEO structure from day one" is better than "We will build a WordPress website with SEO."
45
46	One to two paragraphs. Save the detail for the scope section.
47
48	### 3. Scope and Deliverables
49
50	Numbered list of specific items the client will receive. Each item should be concrete enough that both parties can agree on whether it was delivered.
51
52	Too vague:
53	> - Website design and development
54	> - SEO optimisation
55	> - Ongoing support
56
57	Right level of detail:
58	> 1. Custom WordPress website — up to 8 pages (Home, About, Services x4, Contact, Blog)
59	> 2. Mobile-responsive design matching your brand colours and logo
60	> 3. Local SEO setup — Google Business Profile optimisation, schema markup on all pages, location-based meta titles
61	> 4. Contact form with email notifications to your nominated address
62	> 5. Online booking integration with your existing Calendly account
63	> 6. Basic analytics setup (Google Analytics 4 + Google Search Console)
64	> 7. 30-minute training session on how to update content yourself
65	> 8. 30 days of post-launch support for bug fixes and minor adjustments
66
67	What is NOT included is just as important as what is. Add an exclusions note at the bottom of this section:
68
69	> Not included in this scope: Ongoing content writing, paid advertising setup or management, additional pages beyond the 8 listed above, custom functionality not described here. These can be quoted separately if needed.
70
71	### 4. Timeline
72
73	Phases with durations or target dates. Show the client what happens when.
74
75	\| Phase \| Duration \| What happens \|
76	\|-------\|----------\|--------------\|
77	\| Discovery and planning \| Week 1 \| Content gathering, sitemap sign-off \|
78	\| Design \| Weeks 2-3 \| Homepage mockup, revision, remaining pages \|
79	\| Development \| Weeks 3-5 \| Build, integrations, internal testing \|
80	\| Review and launch \| Week 6 \| Client review, revisions, go-live \|
81
82	If there is a fixed deadline (event, season, campaign), state it and work the timeline back from it. Flag any dependencies on the client: "This timeline assumes content and images are provided by [date]."
83
84	### 5. In

People who liked this also viewed

6 picks

Type