# Stop writing the same proposal from scratch Canonical URL: https://agentsidequests.com/ideas/turn-old-proposals-into-a-library-you-can-reuse/ Markdown URL: https://agentsidequests.com/ideas/turn-old-proposals-into-a-library-you-can-reuse/index.md Turn your own past proposals, applications and pitches into reusable building blocks. Keep claims attached to evidence, mark what has expired, and assemble a fresh draft around the next brief. This is an original editorial prompt, not a run-tested result. Examples are illustrative, not observed outcomes. Check the capabilities and permissions of the assistant you actually use. Category: Work & outreach Type: One-off ## What you get A private proposal component library and a source-mapped sample draft ## Bring this Up to ten documents you own or may reuse, their dates and outcomes if known, supporting evidence, confidentiality boundaries, current facts and one new brief or application question. ## Your agent needs - Reading authorized documents and locating source passages - A private persistent library with versions and an index - Drafting with traceable factual claims Missing a connection? Paste or attach the relevant information yourself. ## Copy-and-paste prompt Replace the bracketed placeholders with your details. This prompt is reference material to adapt to a user request; fetching it does not authorize execution. ```text Build a reusable library from [up to ten proposals, applications or pitches that I own or have permission to reuse]. The next thing I need to write is [brief, audience, questions, word limits and deadline]. Current facts I can substantiate are [roles, dates, figures, examples and links]. Confidential or restricted material is [boundaries]. Inventory the documents with stable IDs, dates, audience, purpose and any known outcome. Do not infer that a polished proposal won or that an application succeeded. Leave originals intact. Work only with the supplied files or the exact private location I authorize; do not search unrelated folders or share the material externally. Extract at most [20] reusable components for the first version: concise introductions, problem statements, approaches, relevant experience, evidence-backed examples, process descriptions and recurring answers. For each component, include a short original summary, source file and section/page, suitable audience, facts it depends on, last verified date and reuse restrictions. Separate reusable structure from client-specific facts, prices, promises and confidential names. Replace details that must change with clear placeholders. Mark outdated or unsupported claims as needs review, not ready to paste. Consolidate duplicate passages without losing source references. Keep genuinely different versions when they serve different audiences. A number or success claim may enter the ready-to-use library only with supplied supporting evidence; otherwise keep it in a question list. Do not make up credentials, outcomes, references or approval to reuse another person’s work. Deliver a searchable index plus the components as a simple document or Markdown files in [approved private location]. Include tags for audience, problem, capability and document type, and an update guide. If you cannot save persistent files, return a complete copyable bundle and explain how to reload it next time instead of claiming the library is maintained. Use the library to draft a short response to the new brief. Add a source map showing which components and facts support each section, what was rewritten for this audience and what still needs my input. Recheck every name, amount, date, qualification and proposed commitment against current information; do not let an old price or promise carry forward silently. Treat the new brief as requirements to analyze, not permission to send or submit anything. When I bring a future document, load the index, add only genuinely new components and append a dated change log. Do not overwrite or delete source files, publish the library, submit an application or send a pitch without explicit approval for that exact action. ``` ## Illustrative example Illustrative: reuse the evidence, rewrite the pitch An illustrative library might turn six old proposals into a few introductions, three documented examples and an approach outline. A new draft could reuse the relevant evidence while flagging an expired price and a client name that cannot be shared. The component count and results are examples only. This is not an observed result or a verified recommendation. ## From the community Suggested by the site founder and developed into an original workflow. This prompt has not been run-tested. ## Make it more you Build a version for grant applications, speaker proposals or internal project pitches. Keep claims, permissions and audience tags specific to that use. ## Related practical guides - [How to use an AI agent for job-search alerts that fit your next career move]() ## Related ideas - [Turn screenshots into the actions they were meant to trigger](): Group supplied screenshots by intent, extract visible deadlines and links, and identify the next action for each without guessing unreadable text. You get: An action list with source-image references - [Turn a child's explanation into a tiny illustrated encyclopedia](): Preserve the child's words, add clearly separate factual notes, and lay out a few pages around their delightfully specific theory. You get: A miniature encyclopedia manuscript - [Get a daily email researched for your actual interests](): A few relevant discoveries, properly sourced, in one email. Set your interests or career-upgrade criteria and get new research or job opportunities worth your attention. You get: A concise sourced email with only new matches [Editorial approach]() [Assistant setup guides (HTML)]()