{ "schemaVersion": "1.0", "item": { "slug": "proposal-writing-2", "name": "Proposal Writing", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/JK-0001/proposal-writing-2", "canonicalUrl": "https://clawhub.ai/JK-0001/proposal-writing-2", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/proposal-writing-2", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=proposal-writing-2", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/proposal-writing-2" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/proposal-writing-2", "agentPageUrl": "https://openagent3.xyz/skills/proposal-writing-2/agent", "manifestUrl": "https://openagent3.xyz/skills/proposal-writing-2/agent.json", "briefUrl": "https://openagent3.xyz/skills/proposal-writing-2/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Overview", "body": "A proposal is not a quote. A quote is a price list. A proposal is a persuasion document that makes the client feel confident, understood, and excited about working with you — and then makes paying feel like the obvious next step. This playbook builds proposals that win, structured around how buyers actually make decisions." }, { "title": "Step 1: Before You Write Anything — The Discovery Checklist", "body": "A great proposal is 80% listening and 20% writing. Before drafting, confirm you have answers to every one of these from your discovery conversation:\n\nDISCOVERY CHECKLIST\n====================\n- [ ] What specific problem is the client trying to solve?\n- [ ] What outcome do they want? (Be specific — not \"better results\")\n- [ ] What have they already tried? What didn't work and why?\n- [ ] What is the cost of NOT solving this? (In time, money, missed opportunity)\n- [ ] What is their timeline / deadline? Is there urgency?\n- [ ] Who else is involved in the decision? (Decision-maker vs. influencer)\n- [ ] Have they worked with anyone like you before? What was that experience?\n- [ ] What does \"success\" look like to them in 3 months / 6 months?\n- [ ] What is their budget range? (Even a rough number helps structure pricing)\n- [ ] What are their biggest concerns or hesitations about moving forward?\n\nIf you can't answer most of these, you don't have enough information to write a strong proposal. Ask for a follow-up call before writing." }, { "title": "Step 2: Proposal Structure (In This Exact Order)", "body": "The order matters. Each section builds on the one before it, moving the client from \"I feel understood\" to \"I'm ready to say yes.\"" }, { "title": "Section 1: Cover Page", "body": "Their company name (not yours — make it about them)\nProject title (something descriptive and inspiring, not \"Proposal for Services\")\nDate\nYour name and logo (small — this is their document)\nOptional: a one-line summary of the outcome you'll deliver" }, { "title": "Section 2: Executive Summary (The Most-Read Section)", "body": "Many clients read ONLY this section. Make it count.\n\nWrite 3-4 sentences that:\n\nRestate THEIR problem back to them (shows you listened)\nState the outcome you'll deliver (the \"after\" picture)\nGive a one-sentence summary of your approach\nState the investment (price) and timeline\n\nIf they read nothing else, this section alone should make them want to say yes." }, { "title": "Section 3: Understanding Your Challenge", "body": "This is where you prove you actually listened during discovery. Restate their problem, their context, and their goals in YOUR words. Do not copy-paste from their brief — reframe it to show understanding.\n\nStructure:\n\nTheir current situation — where they are now\nThe pain — what this situation is costing them (quantify if possible)\nTheir goal — where they want to be\nThe gap — the distance between now and the goal that you'll bridge\n\nThis section does more to build trust than anything else in the proposal. If the client reads this and thinks \"they actually get it,\" you've already won halfway." }, { "title": "Section 4: Our Approach", "body": "Explain HOW you'll solve their problem. This is not a feature list — it's a narrative. Walk them through what will happen, step by step, from their perspective.\n\nStructure:\n\nPhase 1: [What happens first, why, and what the client can expect]\nPhase 2: [Next step]\nPhase 3: [Final delivery or ongoing work]\n\nFor each phase, include: what you do, what they need to do (their involvement), and what the output looks like.\n\nKeep it high-level. Too much technical detail buries the value. Save the deep details for after they sign." }, { "title": "Section 5: What You'll Get (Deliverables)", "body": "A clear, bulleted list of exactly what they receive. This is the \"contract\" section that clients refer back to. Be specific:\n\nNOT: \"Website redesign\"\nYES: \"5-page responsive website (homepage, about, services, blog, contact) with mobile optimization, SEO-optimized page structure, and 2 rounds of revisions\"" }, { "title": "Section 6: Investment (Pricing)", "body": "Put this AFTER the value sections — never lead with price. By the time they get here, they should already understand what they're getting and why it matters.\n\nPricing presentation rules:\n\nPresent ONE recommended option first (your preferred scope and price). Then offer 1-2 alternatives (a stripped-down version or an expanded version).\nAnchor high → recommend middle → offer low. The middle option should be where you want them to land.\nFrame price in terms of ROI where possible: \"At $X/month, this pays for itself in the first week based on the 5 hours/week you told us you're currently spending on [problem].\"\nInclude what's NOT included (scope boundaries). This prevents scope creep and surprises later.\n\nPricing option template:\n\nOPTION A — [Name that implies scope, e.g., \"Essential\"]\n Includes: [deliverables]\n Investment: $[amount]\n Timeline: [weeks]\n\nOPTION B — [Recommended ★] — [Name, e.g., \"Complete\"]\n Includes: [deliverables — superset of Option A]\n Investment: $[amount]\n Timeline: [weeks]\n\nOPTION C — [Name, e.g., \"Enterprise / Full-Service\"]\n Includes: [deliverables — everything + extras]\n Investment: $[amount]\n Timeline: [weeks]" }, { "title": "Section 7: Why Us (Social Proof)", "body": "Brief. 2-3 bullet points max. This is NOT the place for a long bio.\n\nA relevant case study or result (\"Helped [similar company] achieve [specific result] in [timeframe]\")\nA relevant credential or experience\nA testimonial quote (if you have one from a similar client)\n\nPut this AFTER pricing, not before. It functions as final confidence-building right before the decision, not as a sales pitch." }, { "title": "Section 8: Next Steps", "body": "Make it crystal clear what happens if they say yes. Remove ALL friction from the decision.\n\nIf you'd like to move forward:\n 1. Reply to this email with \"Let's do it\" (or sign the attached contract)\n 2. We'll schedule a kickoff call within [X days]\n 3. [First deliverable or milestone] will be ready by [date]\n\nInclude a deadline or a gentle urgency signal: \"This proposal is valid for 14 days. After that, availability and pricing may change.\" This is honest (your availability IS limited as a solopreneur) and creates gentle urgency." }, { "title": "Step 3: Proposal Design and Delivery", "body": "Format: PDF. Always. Not a Google Doc link, not a Word doc. A polished PDF signals professionalism.\n\nDesign rules:\n\nClean, minimal design. White space is your friend.\nUse your brand colors and fonts (from brand-identity).\nNo walls of text. Use short paragraphs, bullet points for deliverables, and clear section headers.\nInclude a cover image or illustration that's relevant to their industry.\n\nDelivery:\n\nSend via email with a short, warm cover message (2-3 sentences max).\nWalk them through the proposal on a call if possible (talking through it live dramatically increases win rates).\nFollow up within 24-48 hours if they haven't responded." }, { "title": "Step 4: Handle Common Objections In Advance", "body": "A great proposal pre-empts objections so they never need to be raised. Weave these into the relevant sections:\n\nObjectionPre-emption\"This is too expensive\"Anchor with ROI. Show the cost of NOT acting. Offer a lower-scope option.\"We need time to think about it\"Add a validity deadline. Offer a call to answer questions.\"Can you do it cheaper?\"Build in a stripped-down option that's already cheaper. Show what gets cut and why.\"We don't know if we need this yet\"Section 3 (Understanding Your Challenge) should make the need undeniable.\"We've had bad experiences with freelancers before\"Section 7 (Why Us) with specific proof of delivery. Offer a milestone-based payment structure." }, { "title": "Proposal Mistakes to Avoid", "body": "Writing a generic proposal and swapping in the client's name. Clients can tell. Every proposal should feel custom-written for them specifically.\nLeading with your story or credentials. Lead with THEIR problem. Earn the right to talk about yourself later.\nBurying the price. Put it in a clear, dedicated section. Hiding it erodes trust.\nGiving only one price. Options create anchoring and give the client a sense of control.\nNot following up. The proposal is not the end of the conversation — it's the beginning of the closing conversation." } ], "body": "Proposal Writing\nOverview\n\nA proposal is not a quote. A quote is a price list. A proposal is a persuasion document that makes the client feel confident, understood, and excited about working with you — and then makes paying feel like the obvious next step. This playbook builds proposals that win, structured around how buyers actually make decisions.\n\nStep 1: Before You Write Anything — The Discovery Checklist\n\nA great proposal is 80% listening and 20% writing. Before drafting, confirm you have answers to every one of these from your discovery conversation:\n\nDISCOVERY CHECKLIST\n====================\n- [ ] What specific problem is the client trying to solve?\n- [ ] What outcome do they want? (Be specific — not \"better results\")\n- [ ] What have they already tried? What didn't work and why?\n- [ ] What is the cost of NOT solving this? (In time, money, missed opportunity)\n- [ ] What is their timeline / deadline? Is there urgency?\n- [ ] Who else is involved in the decision? (Decision-maker vs. influencer)\n- [ ] Have they worked with anyone like you before? What was that experience?\n- [ ] What does \"success\" look like to them in 3 months / 6 months?\n- [ ] What is their budget range? (Even a rough number helps structure pricing)\n- [ ] What are their biggest concerns or hesitations about moving forward?\n\n\nIf you can't answer most of these, you don't have enough information to write a strong proposal. Ask for a follow-up call before writing.\n\nStep 2: Proposal Structure (In This Exact Order)\n\nThe order matters. Each section builds on the one before it, moving the client from \"I feel understood\" to \"I'm ready to say yes.\"\n\nSection 1: Cover Page\nTheir company name (not yours — make it about them)\nProject title (something descriptive and inspiring, not \"Proposal for Services\")\nDate\nYour name and logo (small — this is their document)\nOptional: a one-line summary of the outcome you'll deliver\nSection 2: Executive Summary (The Most-Read Section)\n\nMany clients read ONLY this section. Make it count.\n\nWrite 3-4 sentences that:\n\nRestate THEIR problem back to them (shows you listened)\nState the outcome you'll deliver (the \"after\" picture)\nGive a one-sentence summary of your approach\nState the investment (price) and timeline\n\nIf they read nothing else, this section alone should make them want to say yes.\n\nSection 3: Understanding Your Challenge\n\nThis is where you prove you actually listened during discovery. Restate their problem, their context, and their goals in YOUR words. Do not copy-paste from their brief — reframe it to show understanding.\n\nStructure:\n\nTheir current situation — where they are now\nThe pain — what this situation is costing them (quantify if possible)\nTheir goal — where they want to be\nThe gap — the distance between now and the goal that you'll bridge\n\nThis section does more to build trust than anything else in the proposal. If the client reads this and thinks \"they actually get it,\" you've already won halfway.\n\nSection 4: Our Approach\n\nExplain HOW you'll solve their problem. This is not a feature list — it's a narrative. Walk them through what will happen, step by step, from their perspective.\n\nStructure:\n\nPhase 1: [What happens first, why, and what the client can expect]\nPhase 2: [Next step]\nPhase 3: [Final delivery or ongoing work]\n\nFor each phase, include: what you do, what they need to do (their involvement), and what the output looks like.\n\nKeep it high-level. Too much technical detail buries the value. Save the deep details for after they sign.\n\nSection 5: What You'll Get (Deliverables)\n\nA clear, bulleted list of exactly what they receive. This is the \"contract\" section that clients refer back to. Be specific:\n\nNOT: \"Website redesign\"\nYES: \"5-page responsive website (homepage, about, services, blog, contact) with mobile optimization, SEO-optimized page structure, and 2 rounds of revisions\"\nSection 6: Investment (Pricing)\n\nPut this AFTER the value sections — never lead with price. By the time they get here, they should already understand what they're getting and why it matters.\n\nPricing presentation rules:\n\nPresent ONE recommended option first (your preferred scope and price). Then offer 1-2 alternatives (a stripped-down version or an expanded version).\nAnchor high → recommend middle → offer low. The middle option should be where you want them to land.\nFrame price in terms of ROI where possible: \"At $X/month, this pays for itself in the first week based on the 5 hours/week you told us you're currently spending on [problem].\"\nInclude what's NOT included (scope boundaries). This prevents scope creep and surprises later.\n\nPricing option template:\n\nOPTION A — [Name that implies scope, e.g., \"Essential\"]\n Includes: [deliverables]\n Investment: $[amount]\n Timeline: [weeks]\n\nOPTION B — [Recommended ★] — [Name, e.g., \"Complete\"]\n Includes: [deliverables — superset of Option A]\n Investment: $[amount]\n Timeline: [weeks]\n\nOPTION C — [Name, e.g., \"Enterprise / Full-Service\"]\n Includes: [deliverables — everything + extras]\n Investment: $[amount]\n Timeline: [weeks]\n\nSection 7: Why Us (Social Proof)\n\nBrief. 2-3 bullet points max. This is NOT the place for a long bio.\n\nA relevant case study or result (\"Helped [similar company] achieve [specific result] in [timeframe]\")\nA relevant credential or experience\nA testimonial quote (if you have one from a similar client)\n\nPut this AFTER pricing, not before. It functions as final confidence-building right before the decision, not as a sales pitch.\n\nSection 8: Next Steps\n\nMake it crystal clear what happens if they say yes. Remove ALL friction from the decision.\n\nIf you'd like to move forward:\n 1. Reply to this email with \"Let's do it\" (or sign the attached contract)\n 2. We'll schedule a kickoff call within [X days]\n 3. [First deliverable or milestone] will be ready by [date]\n\n\nInclude a deadline or a gentle urgency signal: \"This proposal is valid for 14 days. After that, availability and pricing may change.\" This is honest (your availability IS limited as a solopreneur) and creates gentle urgency.\n\nStep 3: Proposal Design and Delivery\n\nFormat: PDF. Always. Not a Google Doc link, not a Word doc. A polished PDF signals professionalism.\n\nDesign rules:\n\nClean, minimal design. White space is your friend.\nUse your brand colors and fonts (from brand-identity).\nNo walls of text. Use short paragraphs, bullet points for deliverables, and clear section headers.\nInclude a cover image or illustration that's relevant to their industry.\n\nDelivery:\n\nSend via email with a short, warm cover message (2-3 sentences max).\nWalk them through the proposal on a call if possible (talking through it live dramatically increases win rates).\nFollow up within 24-48 hours if they haven't responded.\nStep 4: Handle Common Objections In Advance\n\nA great proposal pre-empts objections so they never need to be raised. Weave these into the relevant sections:\n\nObjection\tPre-emption\n\"This is too expensive\"\tAnchor with ROI. Show the cost of NOT acting. Offer a lower-scope option.\n\"We need time to think about it\"\tAdd a validity deadline. Offer a call to answer questions.\n\"Can you do it cheaper?\"\tBuild in a stripped-down option that's already cheaper. Show what gets cut and why.\n\"We don't know if we need this yet\"\tSection 3 (Understanding Your Challenge) should make the need undeniable.\n\"We've had bad experiences with freelancers before\"\tSection 7 (Why Us) with specific proof of delivery. Offer a milestone-based payment structure.\nProposal Mistakes to Avoid\nWriting a generic proposal and swapping in the client's name. Clients can tell. Every proposal should feel custom-written for them specifically.\nLeading with your story or credentials. Lead with THEIR problem. Earn the right to talk about yourself later.\nBurying the price. Put it in a clear, dedicated section. Hiding it erodes trust.\nGiving only one price. Options create anchoring and give the client a sense of control.\nNot following up. The proposal is not the end of the conversation — it's the beginning of the closing conversation." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/JK-0001/proposal-writing-2", "publisherUrl": "https://clawhub.ai/JK-0001/proposal-writing-2", "owner": "JK-0001", "version": "0.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/proposal-writing-2", "downloadUrl": "https://openagent3.xyz/downloads/proposal-writing-2", "agentUrl": "https://openagent3.xyz/skills/proposal-writing-2/agent", "manifestUrl": "https://openagent3.xyz/skills/proposal-writing-2/agent.json", "briefUrl": "https://openagent3.xyz/skills/proposal-writing-2/agent.md" } }