agentleFS
mikulgohilmikulgohil/claude-skills/skills/personal/proposal-writer/SKILL.md

proposal-writer

Skill0 starsChanged 5 months agoMITView on GitHub

Draft client proposals, quotes, scopes of work, and engagement letters for service work — project understanding, scope, timeline, pricing presentation, and terms. Use when writing any B2B service engagement document.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sop-writer, weekly-report and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Dokkabei97Skill

    sop-writer

    Creates Standard Operating Procedures for repetitive tasks. Generates step-by-step documentation with checklists, decision trees, and responsibility assignments to eliminate single points of failure.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    weekly-report

    **WORKFLOW SKILL** — Generate weekly executive reports for the azd team. Pulls PR/issue/release data from GitHub, reads changelogs, combines with team notes, and produces a polished markdown report.

    Also in 5 projects that use this

  • akhilkannurSkill

    content-repurposer

    Also in 4 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 3 projects that use this

  • LangChainSkill

    linkedin-post

    Write a LinkedIn post based on research findings or a given topic. Use this skill when asked to create LinkedIn content, professional posts, or thought leadership pieces.

    Also in 3 projects that use this

  • seikaikyoSkill

    interview-me

    需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    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 …

    line 25
  2. Distinctive:

    Use the client's language, not industry jargon

    line 44
  3. Distinctive:

    Keep it to 2-3 short paragraphs

    line 47
  4. Distinctive:

    If there is a fixed deadline (event, season, campaign), state it and work the timeline back from it.

    line 91
  5. Distinctive:

    Only use value framing when you can back it up with real numbers or reasonable estimates.

    line 132
  6. Distinctive:

    Do not offer three different next steps.

    line 152
  7. Distinctive:

    Keep it short and plain-language.

    line 156
  8. Distinctive:

    Do not write a legal contract.

    line 164
  9. Distinctive:

    Brief, not padded: If a section can be said in two sentences, do not write four.

    line 174
  10. Distinctive:

    Human, not robotic: Write like you are explaining the plan to someone sitting across the table.

    line 176
  11. Distinctive:

    Honest about limits: If something is not included, say so up front.

    line 178
  12. Distinctive:

    Burying the price: Put the investment section where the client expects it — after scope and timeline.

    line 187

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Client Proposal Writer

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.

Before You Start

Gather these inputs. Ask for anything missing:

  1. Client name and business — who is this for, what do they do
  2. What they asked for — the brief, the problem, the conversation summary
  3. What you are proposing — your recommended solution at a high level
  4. Pricing — your numbers, or ask for guidance on range
  5. Timeline — how long, any fixed deadlines
  6. Tone — match the client relationship (new vs existing, corporate vs casual, local tradie vs enterprise)

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.


Proposal Structure

Present sections in this order. Every section earns its place — cut any that do not apply.

1. Project Understanding

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.

Too corporate:

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.

Right tone:

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.

Rules for this section:

  • Use the client's language, not industry jargon
  • Reference specific details from the conversation ("you mentioned", "as we discussed")
  • State the business problem, not just the technical requirement
  • Keep it to 2-3 short paragraphs

2. Proposed Solution

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.

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."

One to two paragraphs. Save the detail for the scope section.

3. Scope and Deliverables

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.

Too vague:

  • Website design and development
  • SEO optimisation
  • Ongoing support

Right level of detail:

  1. Custom WordPress website — up to 8 pages (Home, About, Services x4, Contact, Blog)
  2. Mobile-responsive design matching your brand colours and logo
  3. Local SEO setup — Google Business Profile optimisation, schema markup on all pages, location-based meta titles
  4. Contact form with email notifications to your nominated address
  5. Online booking integration with your existing Calendly account
  6. Basic analytics setup (Google Analytics 4 + Google Search Console)
  7. 30-minute training session on how to update content yourself
  8. 30 days of post-launch support for bug fixes and minor adjustments

What is NOT included is just as important as what is. Add an exclusions note at the bottom of this section:

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.

4. Timeline

Phases with durations or target dates. Show the client what happens when.

PhaseDurationWhat happens
Discovery and planningWeek 1Content gathering, sitemap sign-off
DesignWeeks 2-3Homepage mockup, revision, remaining pages
DevelopmentWeeks 3-5Build, integrations, internal testing
Review and launchWeek 6Client review, revisions, go-live

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]."

5. Investment

Frame pricing as an investment, not a cost. Present confidently — no hedging, no apologising for the number.

Choose the pricing format that suits the project:

Single price (simple projects):

Investment: $4,500 + GST

This covers everything listed in the scope above — design, development, SEO setup, training, and 30 days of post-launch support.

Good / Better / Best packages (gives the client choice):

StarterProfessionalPremium
Pages5812
DesignTemplate-basedCustom designCustom + brand guide
SEOBasic on-pageLocal SEO packageLocal SEO + content strategy
Support14 days30 days90 days
Investment$2,500$4,500$7,500

Package pricing works well when the client is unsure of scope. The middle option is typically where you want them to land — price it as the best value.

Line items (transparency-focused):

ItemInvestment
Design (homepage + 7 inner pages)$1,800
Development and integrations$1,500
Local SEO setup$600
Training and documentation$300
30-day post-launch support$300
Total$4,500 + GST

Line items invite line-item negotiation ("Can we drop the training?"). Use when the client has asked for a breakdown or when transparency builds trust.

Value-based framing (optional addition to any format):

For context: businesses in your area that rank on the first page for "plumber Newcastle" report an average of 15-20 inbound enquiries per month. At your average job value, this site should pay for itself within the first 2-3 months of consistent rankings.

Only use value framing when you can back it up with real numbers or reasonable estimates. Do not invent statistics.

6. About Us

Brief credibility section. Two to three sentences, not a company history.

We have been building web platforms for B2B clients since 2015, working primarily with enterprise marketing and content teams. Dozens of clients trust us to keep their sites fast, accessible, and easy to maintain.

Include one or two proof points: years in business, number of clients, relevant case study, industry-specific experience. Skip the mission statement and founding story.

7. Next Steps

Clear, single call to action. Tell the client exactly what to do next.

To get started, reply to this email with a "go ahead" and we will send through an invoice for the first payment. We will then schedule a 30-minute kickoff call to gather your content and lock in the timeline.

Or:

If you are happy to proceed, sign the attached agreement and return it by [date]. We will invoice the deposit and start the discovery phase the following week.

Do not offer three different next steps. One action, clearly stated.

8. Terms

Keep it short and plain-language. Cover the essentials:

  • Payment schedule — e.g., 50% deposit to commence, 50% on completion (or milestone-based for larger projects)
  • Revision limits — e.g., 2 rounds of design revisions included; additional rounds at $X/hour
  • Timeline assumptions — e.g., timeline assumes client feedback within 5 business days at each review point
  • Ownership — e.g., all design files and code are yours once final payment is received
  • What happens if scope changes — e.g., changes beyond the agreed scope will be quoted separately before work begins

Do not write a legal contract. This section sets expectations. If the client needs formal terms, reference a separate T&C document.


Tone Rules

Confident, not arrogant. "We will" not "We would endeavour to." State what you will do as a matter of fact.

Specific, not vague. "8 pages" not "a multi-page website." "$4,500" not "competitive pricing." "Week 3" not "in due course."

Brief, not padded. If a section can be said in two sentences, do not write four. The client is busy. Respect that.

Human, not robotic. Write like you are explaining the plan to someone sitting across the table. Contractions are fine. First person is fine.

Honest about limits. If something is not included, say so up front. If there is a risk (timeline depends on client providing content), name it. Clients trust people who are straight with them.


Avoid List

  • Jargon the client will not understand. "Headless CMS with SSR via edge functions" means nothing to a plumber. Say "a fast, modern website that is easy for you to update."
  • "We're passionate about..." Nobody is passionate about building websites for a plumbing company. You are good at it and you will do a thorough job. That is enough.
  • Company history padding. "Founded in 2009 by Jeremy Dawes with a vision to..." — save it for the About page. The proposal is about the client, not about you.
  • Burying the price. Put the investment section where the client expects it — after scope and timeline. Do not hide it on page 7 after three pages of methodology.
  • Weasel words. "Up to", "as low as", "starting from" — be direct about what it costs.
  • Promising what you cannot deliver. "Guaranteed first page rankings" or "Your investment will generate $X in revenue." If you cannot guarantee it, do not write it.

Pricing Section Examples

Too corporate:

We are pleased to present our proposed investment framework for the delivery of the aforementioned scope of work. Our pricing model reflects our commitment to delivering exceptional value while maintaining the highest standards of quality and innovation in our deliverables.

Total proposed investment: $4,500.00 (exclusive of GST)

Right tone:

Investment: $4,500 + GST

That covers everything listed above — design, build, SEO setup, training, and a month of support after launch. No hidden fees.

Payment is split 50/50: half up front to get started, half when the site goes live.


Output Format

Deliver the proposal as clean markdown with clear section headings. If the user needs a formatted file, offer to create it as markdown they can paste into Google Docs, Canva, or their proposal tool.

For proposals that need to look polished (PDF to a corporate client), suggest the user paste the content into their branded template. The skill produces the words, not the layout.

Match the regional tone of the client. Default to Australian English unless told otherwise.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.