proposals
Skill0 starsChanged 2 months agoMITView on GitHub
Turn an RFP or opportunity into a win narrative with scope, pricing, timeline, win themes and proof. Use when writing formal sales proposals, Statements of Work, or executive pitches.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- arthur-plautz/research-toolkittheir own version, first seen Oct 15, 2026
- carbon-language/carbon-langtheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- carbon-language/carbon-lang★ 34ksame name
- arthur-plautz/research-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- account-managementSkill
- account-strategistSkill
- analytics-reporterSkill
- churn-analystSkill
- client-onboardingSkill
- cold-outreachSkill
- cross-channel-support-agentSkill
- customer-supportSkill
- discovery-coachSkill
- discoverySkill
- executive-summary-generatorSkill
- finance-trackerSkill
- freelance-biddingSkill
- legal-compliance-checkerSkill
- outbound-strategistSkill
- pipeline-analystSkill
- pipeline-healthSkill
- proposal-strategistSkill
- prospectingSkill
- public-sector-bidsSkill
- renewalsSkill
- renewal-strategistSkill
- sales-coachingSkill
- sales-coachSkill
- sales-data-extraction-agentSkill
- sales-engineerSkill
- sales-outreachSkill
- solution-engineeringSkill
- support-repliesSkill
- win-loss-analysisSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
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
- Distinctive: line 19
Quantified Current State: Document the financial or operational cost of the client's current bottleneck (e.g.
- Distinctive: line 49
Never submit pricing before explicitly defining acceptance criteria for every deliverable.
- Distinctive: line 50
Every proposal must state what happens when change requests occur (e.g.
- Distinctive: line 51
Avoid generic fluff ("we are passionate about customer success").
- Distinctive: line 61
NEVER provide an open-ended "Time & Materials" estimate without an agreed maximum cap and approval trigger.
- Distinctive: line 62
NEVER bury pricing at the end without having established measurable ROI in the Executive Summary.
- Distinctive: line 63
NEVER leave third-party dependencies (client API access, infrastructure provisioning) unassigned.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Proposals
A winning proposal is not a capabilities brochure; it is an executive business case. High-conversion proposals lead with the client's quantifiable problem, establish 2–3 distinct win themes, define rigid Statement of Work (SOW) boundaries, and back every capability claim with verified proof.
1. The Win Narrative Architecture
Structure formal proposals and RFP responses into four distinct decision layers:
A. Executive Pitch & Problem Statement
- Quantified Current State: Document the financial or operational cost of the client's current bottleneck (e.g. "manual reconciliation consumes 35 hours/week, introducing a 4.2% error rate across $12M in transactions").
- Target State & Business Outcomes: State the measurable impact delivered upon completion (e.g. "automated ledger synchronization reducing error rate to <0.1% and saving $180,000 annually").
- Win Themes: 2–3 strategic pillars that distinguish your bid (e.g. Speed-to-value within 30 days; Proven SOC 2 Type II compliance; Zero operational downtime).
B. Statement of Work (SOW) & Milestone Deliverables
Break implementation into discrete, inspectable milestone phases:
- Phase 1: Discovery & Technical Scoping (Weeks 1–2): Architecture blueprint, API audit, migration matrix.
- Phase 2: Core Engineering & Integration (Weeks 3–6): Bi-directional synchronization pipelines, webhook handlers, role-based access.
- Phase 3: Validation, Staging & User Acceptance Testing (UAT) (Weeks 7–8): End-to-end integration tests, load tests, compliance audit sign-off.
- Phase 4: Production Rollout & Knowledge Transfer (Weeks 9–10): Blue/green deployment, runbook documentation, admin training sessions.
C. Scope Boundaries (In-Scope vs. Out-of-Scope)
Explicitly document what is NOT included to prevent scope creep:
- Out-of-scope: Data migration of unformatted records prior to FY2024; customization of third-party legacy ERP endpoints without published REST APIs.
D. Investment & Milestone Schedule
| Milestone / Deliverable | Timeline | Investment | Acceptance Criteria |
| Milestone 1: Blueprint & Architecture | Weeks 1–2 | $15,000 | Signed architectural decision record and schema design |
| Milestone 2: Core Pipeline & Integration | Weeks 3–6 | $35,000 | Staging pipeline processing 10,000 test transactions |
| Milestone 3: UAT & Production Release | Weeks 7–9 | $20,000 | Zero critical defects in UAT and successful cutover |
| Total Engagement | 9 Weeks | $70,000 | Final project sign-off and SLA activation |
2. Risk Reversal & Proof Points
- Relevant Case Studies: Include 1–2 vignettes of comparable engagements with before/after metrics.
- Service Level Agreements & Warranties: 30-day bug-fix warranty on all delivered code post-cutover.
- Decision Timeline: Include explicit offer validity date (e.g. "Pricing and milestone schedule guaranteed through October 31, 2026").
Critical Rules
- Never submit pricing before explicitly defining acceptance criteria for every deliverable.
- Every proposal must state what happens when change requests occur (e.g. "additional requirements billed at $X/hour or scoped as a Phase 2 addendum").
- Avoid generic fluff ("we are passionate about customer success"); cite verified uptime, certifications, or delivery stats instead.
Verification Checklist
- Client problem quantified with specific baseline and target metrics.
- 2–3 explicit win themes woven throughout the narrative.
- Statement of Work contains clear in-scope and out-of-scope boundaries.
- Investment table ties fee payments directly to verifiable milestones, not arbitrary dates.
- Acceptance criteria, warranty period, and change-order procedures documented.
Anti-Patterns
- NEVER provide an open-ended "Time & Materials" estimate without an agreed maximum cap and approval trigger.
- NEVER bury pricing at the end without having established measurable ROI in the Executive Summary.
- NEVER leave third-party dependencies (client API access, infrastructure provisioning) unassigned.
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
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.