{ "schemaVersion": "1.0", "item": { "slug": "proposal-writing", "name": "Proposal Writing", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/staybased/proposal-writing", "canonicalUrl": "https://clawhub.ai/staybased/proposal-writing", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/proposal-writing", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=proposal-writing", "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", "slug": "proposal-writing", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T10:55:16.464Z", "expiresAt": "2026-05-07T10:55:16.464Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=proposal-writing", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=proposal-writing", "contentDisposition": "attachment; filename=\"proposal-writing-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "proposal-writing" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/proposal-writing" }, "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", "agentPageUrl": "https://openagent3.xyz/skills/proposal-writing/agent", "manifestUrl": "https://openagent3.xyz/skills/proposal-writing/agent.json", "briefUrl": "https://openagent3.xyz/skills/proposal-writing/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": "Proposal Writing — Confirmation-First Closing Framework", "body": "Write proposals that confirm verbal agreements and close deals, not proposals that try to sell.\nSources: Consulting Success (reviewed 100s of proposals, 60%+ win rate benchmark), Aura/Prosal (2024 survey: 30% RFP win rate), McKinsey SCR framework, Melisa Liberman.\nAll outputs go to workspace/artifacts/." }, { "title": "Use when", "body": "Writing a proposal after a discovery call where the client verbally agreed\nCrafting Upwork proposals for fixed-price or hourly jobs\nFormalizing a service agreement (like Alfred's automation)\nResponding to an RFP with a structured bid\nReviewing/improving an existing proposal before sending" }, { "title": "Don't use when", "body": "You haven't done discovery yet (use client-discovery skill first)\nCold outreach (use cold-outreach skill — proposals come after interest)\nPricing strategy (use pricing-psychology skill for the pricing, this skill for the wrapper)\nWriting internal project plans (different audience, different format)" }, { "title": "Negative examples", "body": "\"Help me find clients\" → No. This is for closing, not finding.\n\"Write a business plan\" → No. Business plans and proposals are different documents.\n\"Send a follow-up email\" → Borderline. Use cold-outreach for follow-ups." }, { "title": "Edge cases", "body": "Upwork cover letter → YES. It's a micro-proposal. Same principles, compressed format.\n\"They haven't said yes yet\" → STOP. Get a verbal yes first, then send the proposal to confirm it.\nInformal text/email agreement → YES. Even a brief \"Here's what we discussed + next steps\" is a proposal." }, { "title": "The #1 Mistake: Proposals That Sell", "body": "Consulting Success (from reviewing hundreds of proposals):\n\n\"Your consulting proposal isn't a sales tool. It's a confirmation tool. The selling happens before the proposal.\"\n\nMost consultants win less than 60% of their proposals. The top performers win 80-90%. The difference? Top performers only send proposals after getting a verbal yes." }, { "title": "The Right Sequence", "body": "Discovery call → verbal agreement → proposal confirms → signed" }, { "title": "The Wrong Sequence", "body": "Discovery call → send proposal hoping it convinces them → silence\n\nIf you're sending proposals to people who haven't said \"yes\" yet, you're wasting time. Go back to discovery." }, { "title": "The SCR Proposal Framework", "body": "Situation → Complication → Resolution (used by McKinsey, BCG, Bain)\n\nThis mirrors how decisions are made naturally:\n\nSituation: \"Here's where you are\" (recap their context)\nComplication: \"Here's what's in the way\" (the problem + cost of inaction)\nResolution: \"Here's how we fix it\" (your solution + expected outcomes)" }, { "title": "1. Executive Summary (3-5 sentences)", "body": "The most important section. Many decision-makers read ONLY this.\n\nFormula:\n\n[Client name] is facing [specific problem] which is costing [quantified impact].\nOur proposed approach [brief method] will deliver [specific outcome] within [timeframe].\nInvestment: [price]. Next step: [action].\n\nRules:\n\nWrite it LAST (after you've written everything else)\nNo jargon\nMust stand alone — if they read nothing else, this closes\nInclude the price here (don't make them hunt for it)" }, { "title": "2. Understanding of the Problem", "body": "Prove you listened during discovery. Use their exact words.\n\nBased on our conversation on [date], [Client] is experiencing:\n- [Problem 1 — in their language]\n- [Problem 2 — quantified if possible]\n- [Impact: what this costs them in time/money/customers]\n\nWhy this works: When a client reads their own words back to them, trust skyrockets. They feel understood." }, { "title": "3. Proposed Solution", "body": "What you'll do, step by step. Be specific but not overwhelming.\n\nPhase 1: [Deliverable] — [Timeline]\nPhase 2: [Deliverable] — [Timeline]\nPhase 3: [Deliverable] — [Timeline]\n\nRules:\n\n3-5 phases maximum\nEach phase has a clear deliverable (noun, not verb — \"Automated SMS system\" not \"Working on SMS\")\nInclude what's NOT included (prevents scope creep)" }, { "title": "4. Expected Outcomes / ROI", "body": "Quantify the value of your solution in their terms.\n\nBased on [data from discovery]:\n- [Outcome 1]: Save [X hours/week] = $[Y/month]\n- [Outcome 2]: Capture [X additional clients/month] = $[Y/month]\n- Total projected value: $[Z/month]\n- Investment: $[price/month]\n- ROI: [X]x return\n\nAnchoring trick (from pricing-psychology): Always show the value before the price. $500/month in captured bookings makes $149/month feel like a no-brainer." }, { "title": "5. Investment (Pricing)", "body": "State the price clearly. No hiding, no apologizing.\n\nOptions structure (from pricing-psychology):\n\nOptionWhat's IncludedPriceStarterCore solution only$XGrowth (recommended)Core + extras$YScaleEverything + premium$Z\n\nRules:\n\nUse the word \"investment,\" not \"cost\" or \"fee\" (frames as value, not expense)\nIf offering tiers, bold or highlight the recommended option\nInclude payment terms (monthly, milestone-based, upfront discount)" }, { "title": "6. Timeline & Next Steps", "body": "Week 1: [Setup/onboarding]\nWeek 2-3: [Build/implement]\nWeek 4: [Launch/go-live]\nOngoing: [Support/optimization]\n\nEnd with a clear call to action:\n\"To proceed, [sign below / reply to this email / schedule kickoff call]. We can begin as early as [date].\"" }, { "title": "7. About Us / Credibility (Brief)", "body": "Keep this SHORT. 2-3 sentences + one relevant result.\n\n[Your name/company] specializes in [relevant expertise].\nRecent result: [Specific client outcome with numbers].\n\nDon't: Write a full company history. They don't care. They care about results." }, { "title": "Upwork Proposal Template (Micro-Format)", "body": "Upwork proposals are mini-proposals. Same principles, 150-300 words:\n\n[Opening — reference THEIR job post specifically, not generic]\n\nHi [name if visible],\n\nI read your post about [specific need]. [One sentence proving you understand the problem.]\n\n[Credibility — one relevant result]\nI recently built [similar thing] for [type of client] — [specific outcome].\n\n[Approach — 2-3 sentences on HOW you'd do it]\nFor your project, I'd [step 1], then [step 2], delivering [outcome] within [timeframe].\n\n[De-risk]\nHappy to start with [small milestone] so you can evaluate before committing to the full scope.\n\n[CTA]\nCan we hop on a quick call to clarify [1 specific question from the post]?\n\n[Name]\n\nUpwork-specific tips:\n\nFirst 2 lines are visible before \"Read more\" — make them count\nAsk a question (shows engagement, invites response)\nReference the budget range (shows you read the post)\nKeep under 250 words (long proposals get skimmed)" }, { "title": "Proposal Delivery Checklist", "body": "Before sending any proposal:\n\nVerbal \"yes\" obtained (or at minimum, strong buying signal)\n Problem statement uses client's exact words from discovery\n Price appears after value/ROI section (anchoring)\n Clear next step with specific date\n Scope boundaries defined (what's NOT included)\n Proofread — typos kill credibility\n Sent within 24-48 hours of discovery call (momentum matters)\n Follow-up scheduled for 3 days after sending" }, { "title": "Common Proposal Killers (Consulting Success)", "body": "Too long — 2-3 pages max for freelance/small consulting. Enterprise RFPs are different.\nWritten for you, not them — Every section should answer \"so what?\" from the client's perspective.\nNo price — Burying or omitting the price wastes everyone's time.\nNo timeline — \"We'll figure it out\" is not a plan.\nSent without verbal agreement — Win rate plummets from 80%+ to <30%.\nNo follow-up — 50% of deals are won in the follow-up, not the initial send.\nScope creep baked in — If you promise everything, you'll deliver nothing well." }, { "title": "Key Numbers", "body": "Average RFP win rate: ~30% (Prosal 2024 survey)\nTop consultants with verbal-first approach: 80-90% win rate\nProposals sent within 24 hours of call convert significantly better than 48+ hours\nOptimal proposal length: 2-3 pages (freelance), 5-10 pages (enterprise)\nFollow-up within 3 days increases close rate substantially" } ], "body": "Proposal Writing — Confirmation-First Closing Framework\n\nWrite proposals that confirm verbal agreements and close deals, not proposals that try to sell. Sources: Consulting Success (reviewed 100s of proposals, 60%+ win rate benchmark), Aura/Prosal (2024 survey: 30% RFP win rate), McKinsey SCR framework, Melisa Liberman. All outputs go to workspace/artifacts/.\n\nUse when\nWriting a proposal after a discovery call where the client verbally agreed\nCrafting Upwork proposals for fixed-price or hourly jobs\nFormalizing a service agreement (like Alfred's automation)\nResponding to an RFP with a structured bid\nReviewing/improving an existing proposal before sending\nDon't use when\nYou haven't done discovery yet (use client-discovery skill first)\nCold outreach (use cold-outreach skill — proposals come after interest)\nPricing strategy (use pricing-psychology skill for the pricing, this skill for the wrapper)\nWriting internal project plans (different audience, different format)\nNegative examples\n\"Help me find clients\" → No. This is for closing, not finding.\n\"Write a business plan\" → No. Business plans and proposals are different documents.\n\"Send a follow-up email\" → Borderline. Use cold-outreach for follow-ups.\nEdge cases\nUpwork cover letter → YES. It's a micro-proposal. Same principles, compressed format.\n\"They haven't said yes yet\" → STOP. Get a verbal yes first, then send the proposal to confirm it.\nInformal text/email agreement → YES. Even a brief \"Here's what we discussed + next steps\" is a proposal.\nThe #1 Mistake: Proposals That Sell\n\nConsulting Success (from reviewing hundreds of proposals):\n\n\"Your consulting proposal isn't a sales tool. It's a confirmation tool. The selling happens before the proposal.\"\n\nMost consultants win less than 60% of their proposals. The top performers win 80-90%. The difference? Top performers only send proposals after getting a verbal yes.\n\nThe Right Sequence\nDiscovery call → verbal agreement → proposal confirms → signed\n\nThe Wrong Sequence\nDiscovery call → send proposal hoping it convinces them → silence\n\n\nIf you're sending proposals to people who haven't said \"yes\" yet, you're wasting time. Go back to discovery.\n\nThe SCR Proposal Framework\n\nSituation → Complication → Resolution (used by McKinsey, BCG, Bain)\n\nThis mirrors how decisions are made naturally:\n\nSituation: \"Here's where you are\" (recap their context)\nComplication: \"Here's what's in the way\" (the problem + cost of inaction)\nResolution: \"Here's how we fix it\" (your solution + expected outcomes)\nProposal Structure (7 Sections)\n1. Executive Summary (3-5 sentences)\n\nThe most important section. Many decision-makers read ONLY this.\n\nFormula:\n\n[Client name] is facing [specific problem] which is costing [quantified impact].\nOur proposed approach [brief method] will deliver [specific outcome] within [timeframe].\nInvestment: [price]. Next step: [action].\n\n\nRules:\n\nWrite it LAST (after you've written everything else)\nNo jargon\nMust stand alone — if they read nothing else, this closes\nInclude the price here (don't make them hunt for it)\n2. Understanding of the Problem\n\nProve you listened during discovery. Use their exact words.\n\nBased on our conversation on [date], [Client] is experiencing:\n- [Problem 1 — in their language]\n- [Problem 2 — quantified if possible]\n- [Impact: what this costs them in time/money/customers]\n\n\nWhy this works: When a client reads their own words back to them, trust skyrockets. They feel understood.\n\n3. Proposed Solution\n\nWhat you'll do, step by step. Be specific but not overwhelming.\n\nPhase 1: [Deliverable] — [Timeline]\nPhase 2: [Deliverable] — [Timeline]\nPhase 3: [Deliverable] — [Timeline]\n\n\nRules:\n\n3-5 phases maximum\nEach phase has a clear deliverable (noun, not verb — \"Automated SMS system\" not \"Working on SMS\")\nInclude what's NOT included (prevents scope creep)\n4. Expected Outcomes / ROI\n\nQuantify the value of your solution in their terms.\n\nBased on [data from discovery]:\n- [Outcome 1]: Save [X hours/week] = $[Y/month]\n- [Outcome 2]: Capture [X additional clients/month] = $[Y/month]\n- Total projected value: $[Z/month]\n- Investment: $[price/month]\n- ROI: [X]x return\n\n\nAnchoring trick (from pricing-psychology): Always show the value before the price. $500/month in captured bookings makes $149/month feel like a no-brainer.\n\n5. Investment (Pricing)\n\nState the price clearly. No hiding, no apologizing.\n\nOptions structure (from pricing-psychology):\n\nOption\tWhat's Included\tPrice\nStarter\tCore solution only\t$X\nGrowth (recommended)\tCore + extras\t$Y\nScale\tEverything + premium\t$Z\n\nRules:\n\nUse the word \"investment,\" not \"cost\" or \"fee\" (frames as value, not expense)\nIf offering tiers, bold or highlight the recommended option\nInclude payment terms (monthly, milestone-based, upfront discount)\n6. Timeline & Next Steps\nWeek 1: [Setup/onboarding]\nWeek 2-3: [Build/implement]\nWeek 4: [Launch/go-live]\nOngoing: [Support/optimization]\n\n\nEnd with a clear call to action: \"To proceed, [sign below / reply to this email / schedule kickoff call]. We can begin as early as [date].\"\n\n7. About Us / Credibility (Brief)\n\nKeep this SHORT. 2-3 sentences + one relevant result.\n\n[Your name/company] specializes in [relevant expertise].\nRecent result: [Specific client outcome with numbers].\n\n\nDon't: Write a full company history. They don't care. They care about results.\n\nUpwork Proposal Template (Micro-Format)\n\nUpwork proposals are mini-proposals. Same principles, 150-300 words:\n\n[Opening — reference THEIR job post specifically, not generic]\n\nHi [name if visible],\n\nI read your post about [specific need]. [One sentence proving you understand the problem.]\n\n[Credibility — one relevant result]\nI recently built [similar thing] for [type of client] — [specific outcome].\n\n[Approach — 2-3 sentences on HOW you'd do it]\nFor your project, I'd [step 1], then [step 2], delivering [outcome] within [timeframe].\n\n[De-risk]\nHappy to start with [small milestone] so you can evaluate before committing to the full scope.\n\n[CTA]\nCan we hop on a quick call to clarify [1 specific question from the post]?\n\n[Name]\n\n\nUpwork-specific tips:\n\nFirst 2 lines are visible before \"Read more\" — make them count\nAsk a question (shows engagement, invites response)\nReference the budget range (shows you read the post)\nKeep under 250 words (long proposals get skimmed)\nProposal Delivery Checklist\n\nBefore sending any proposal:\n\n Verbal \"yes\" obtained (or at minimum, strong buying signal)\n Problem statement uses client's exact words from discovery\n Price appears after value/ROI section (anchoring)\n Clear next step with specific date\n Scope boundaries defined (what's NOT included)\n Proofread — typos kill credibility\n Sent within 24-48 hours of discovery call (momentum matters)\n Follow-up scheduled for 3 days after sending\nCommon Proposal Killers (Consulting Success)\nToo long — 2-3 pages max for freelance/small consulting. Enterprise RFPs are different.\nWritten for you, not them — Every section should answer \"so what?\" from the client's perspective.\nNo price — Burying or omitting the price wastes everyone's time.\nNo timeline — \"We'll figure it out\" is not a plan.\nSent without verbal agreement — Win rate plummets from 80%+ to <30%.\nNo follow-up — 50% of deals are won in the follow-up, not the initial send.\nScope creep baked in — If you promise everything, you'll deliver nothing well.\nKey Numbers\nAverage RFP win rate: ~30% (Prosal 2024 survey)\nTop consultants with verbal-first approach: 80-90% win rate\nProposals sent within 24 hours of call convert significantly better than 48+ hours\nOptimal proposal length: 2-3 pages (freelance), 5-10 pages (enterprise)\nFollow-up within 3 days increases close rate substantially" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/staybased/proposal-writing", "publisherUrl": "https://clawhub.ai/staybased/proposal-writing", "owner": "staybased", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/proposal-writing", "downloadUrl": "https://openagent3.xyz/downloads/proposal-writing", "agentUrl": "https://openagent3.xyz/skills/proposal-writing/agent", "manifestUrl": "https://openagent3.xyz/skills/proposal-writing/agent.json", "briefUrl": "https://openagent3.xyz/skills/proposal-writing/agent.md" } }