agentleFS
koinodkoinod/koino-skills/proposal-generator/SKILL.md

proposal-generator

Skill7 starsChanged 6 months agoMITView on GitHub

Generate a professional service proposal in 60 seconds from client name, industry, and pain points. Proposal Generator creates polished, ready-to-send service proposals in markdown format. Input the client details and pain points; output a complete proposal with scope, timeline, pricing structure, and terms. Stop spending 2 hours writing proposals that should take 2 minutes. This skill activates when: - The user needs to create a proposal, quote, or SOW for a client - The user says "write a proposal" or…

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 10

    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:

    When generating a proposal:

    line 123
  2. Distinctive:

    Ask for missing info: if not provided: client name, industry, pain points, budget range, timeline expectations.

    line 125
  3. Distinctive:

    Mirror their language: If they said "we're drowning in admin work," the proposal says "eliminate the admin bottleneck" — not "optimize …

    line 127
  4. Distinctive:

    Three pricing tiers: Always present 3 options. The middle option should be the one you want them to pick (anchoring effect).

    line 129
  5. Distinctive:

    Quantify the ROI: Every proposal should include at least one line showing: "This costs $X.

    line 131
  6. Distinctive:

    Agency model: Add "Ongoing Management" section with monthly retainer details

    line 145
  7. Distinctive:

    Consulting: Add "Methodology" section describing your framework

    line 147
  8. Distinctive:

    One-time project: Remove retainer option, add maintenance upsell

    line 148
  9. Distinctive:

    Follow up the proposal with a 60-second Loom video walking through it.

    line 153
  10. Distinctive:

    If they ask for a discount, remove scope instead of lowering price.

    line 154

“Common” is measured: kept by at least 6 in 10 of the 6 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

Proposal Generator

Generate a professional service proposal in 60 seconds from client name, industry, and pain points.

Description

Proposal Generator creates polished, ready-to-send service proposals in markdown format. Input the client details and pain points; output a complete proposal with scope, timeline, pricing structure, and terms. Stop spending 2 hours writing proposals that should take 2 minutes.

Activation

This skill activates when:

  • The user needs to create a proposal, quote, or SOW for a client
  • The user says "write a proposal" or "generate a proposal"
  • The user has a prospect ready for a formal offer
  • The user mentions scope of work, project quote, or service agreement

Trigger phrases: "write a proposal", "generate a proposal", "create a quote", "scope of work", "SOW", "send them a proposal", "put together an offer"

Proposal Structure

# Service Proposal

**Prepared for**: [Client Name / Company]
**Prepared by**: [Your Name / Company]
**Date**: [Date]
**Valid until**: [Date + 14 days]

---

## Executive Summary

[2-3 sentences: We understand your problem. Here's what we'll build. Here's the outcome you can expect.]

## The Problem

[Restate their pain points in their own language. Make them feel understood. Be specific — use numbers, timelines, and consequences they mentioned.]

- [Pain point 1 with quantified impact]
- [Pain point 2 with quantified impact]
- [Pain point 3 with quantified impact]

## The Solution

[High-level description of what you'll deliver. Focus on OUTCOMES, not features.]

### Phase 1: [Name] (Week 1-2)
- [Deliverable 1]
- [Deliverable 2]
- **Outcome**: [What changes for them after this phase]

### Phase 2: [Name] (Week 3-4)
- [Deliverable 1]
- [Deliverable 2]
- **Outcome**: [What changes for them after this phase]

### Phase 3: [Name] (Week 5-8)
- [Deliverable 1]
- [Deliverable 2]
- **Outcome**: [What changes for them after this phase]

## What's Included

| Deliverable | Description | Timeline |
|-------------|-------------|----------|
| [Item 1] | [Brief description] | Week X |
| [Item 2] | [Brief description] | Week X |
| [Item 3] | [Brief description] | Week X |
| [Item 4] | [Brief description] | Week X |

## What's NOT Included

[Explicitly list what's out of scope to prevent scope creep]

- [Out of scope item 1]
- [Out of scope item 2]

## Investment

### Option A: [Name] — $X,XXX
[Core package. What most clients choose.]

### Option B: [Name] — $X,XXX
[Premium package with additional value.]

### Option C: [Name] — $X,XXX/month
[Ongoing retainer for continued support.]

**Payment Terms**: [50% upfront, 50% on completion / Monthly / etc.]

## Timeline

| Milestone | Date | Deliverable |
|-----------|------|-------------|
| Kickoff | [Date] | Discovery call + access setup |
| Phase 1 Complete | [Date] | [Deliverable] |
| Phase 2 Complete | [Date] | [Deliverable] |
| Go Live | [Date] | Full system deployed |

## Why Us

[3 bullet points max. Social proof, relevant experience, unique advantage.]

- [Relevant case study or result]
- [Unique methodology or technology]
- [Guarantee or risk reversal]

## Next Steps

1. Reply "approved" to this proposal (or sign below)
2. We'll send an invoice for the deposit
3. Kickoff call scheduled within 48 hours

**This proposal is valid for 14 days.**

---

[Signature block]

Instructions

When generating a proposal:

  1. Ask for missing info if not provided: client name, industry, pain points, budget range, timeline expectations.
  2. Mirror their language: If they said "we're drowning in admin work," the proposal says "eliminate the admin bottleneck" — not "optimize operational efficiency."
  3. Three pricing tiers: Always present 3 options. The middle option should be the one you want them to pick (anchoring effect). The top option makes the middle look reasonable.
  4. Quantify the ROI: Every proposal should include at least one line showing: "This costs $X. It saves/generates $Y. Payback period: Z weeks."
  5. Urgency without pressure: The 14-day validity creates natural urgency. Don't add fake scarcity.

Example

Input

Client: GreenTree Landscaping (Mike, owner). Industry: Landscaping/home services. Pain points: Taking 4+ hours to respond to leads, losing bids to faster competitors, admin work eating 15 hours/week. Budget: $2-5K. Timeline: wants it running in 2 weeks.

Output

(Full proposal generated using the template above, with GreenTree-specific language, 3 pricing tiers at $2,500 / $4,000 / $1,500/mo, and ROI showing 3 recovered leads/month = $18K additional annual revenue.)

Customization

  • Agency model: Add "Ongoing Management" section with monthly retainer details
  • Product/SaaS: Replace phases with "Onboarding → Configuration → Launch"
  • Consulting: Add "Methodology" section describing your framework
  • One-time project: Remove retainer option, add maintenance upsell

Pro Tips

  • Send as PDF, not a link. PDFs feel more official and don't require login.
  • Follow up the proposal with a 60-second Loom video walking through it. Proposals with video close 35% higher.
  • If they ask for a discount, remove scope instead of lowering price. "We can hit that budget — here's what that version looks like."

Built by KOINO Capital — Agentic growth systems that run while you sleep. Want this running autonomously 24/7? Deploy with KOINO

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.