🗃️ Proposal Archive and Search Automation with AI

Taskade Genesis builds a searchable proposal archive that captures every document, client, outcome, and value figure in a relational database — so finding a past proposal takes a keyword search, not a file drawer dig. ## What Is Proposal Archive and Search Automation? It's a structured repository that automatically logs every proposal you send — including the client, industry, deal size, template used, and outcome — and stores it in a queryable workspace. Agents index the content so you can retrieve any proposal, or the best template for a similar deal, in plain-language search. ## Why Use Proposal Archive and Search Automation? Your best proposals are already written. Automation makes them findable and reusable. - Automatic archiving: Every sent proposal is logged with full metadata the moment it leaves your workspace. - Plain-language search: Ask an agent "show me all proposals for logistics clients above $20K" and get instant results. - Template extraction: Identify your highest-performing proposals and convert them into reusable templates. - Relationship linking: Each archive record links to the client, outcome, and any resulting contract via the Relationship field. - Audit-ready: A complete, searchable record of every proposal is available for compliance or business review. ## Who Should Use Proposal Archive and Search Automation? - Agencies with hundreds of past proposals and no systematic way to reuse them. - Consultants who revisit past work when scoping similar new engagements. - Legal service firms maintaining a record of every engagement letter and scope document. - Enterprise sales teams needing audit trails for compliance and procurement reviews. - Business development managers analyzing proposal history to spot trends by vertical or deal size. ## How To Use Proposal Archive and Search Automation? 1. Clone the template from /automate — existing proposals can be imported in bulk. 2. Set the automation: proposal status → Sent → archive record created with metadata. 3. Link each archive entry to the client, template, and