Software Vendor Due Diligence Brief with Cited Evidence Review
Guides a vendor shortlist review: finds primary sources like docs, security pages, and pricing, scores vendors on your criteria, and flags risks and open questions before purchase.
217 prompts
Prompts written for Claude, Anthropic's assistant. Claude handles long inputs well, so many of these prompts ask you to paste a whole document, transcript or code excerpt and then structure the answer around it.
11 results
Guides a vendor shortlist review: finds primary sources like docs, security pages, and pricing, scores vendors on your criteria, and flags risks and open questions before purchase.
Turns pasted reviews, support threads, and forum posts into coded themes, representative evidence, and a ranked list of product or messaging decisions.
Builds a transparent market size estimate from discoverable sources, compares top-down and bottom-up methods, and flags weak assumptions before a go or no-go call.
Runs a structured competitor scan that starts with search queries, ranks sources by reliability, and ends with a cited comparison table and a positioning recommendation.
Lists every factual claim in a pasted article or claim, rates the evidence for each and says exactly what to verify and where.
Explains each clause of a pasted contract or lease in plain English, flags one-sided terms and lists questions to ask before signing.
Explains each pasted lab value and its reference range in plain English and ends with questions to bring to your doctor, without diagnosing.
Turns a broad topic into five researchable questions sized to your assignment, each with the data or sources it needs.
Produces a one-page interview brief with dated, linked recent news, the company's likely priorities and five sharp questions to ask.
Breaks a pasted paper abstract or text into claim, method, key evidence and limitations, then adds three seminar discussion questions.
Pulls the central claims out of a long report or paper, with page numbers, the evidence behind each claim and how strong it is, so you can cite or challenge it quickly.
Put the documents first and the prompt after them. Anthropic's prompting guide suggests wrapping each document in tags such as <document> so Claude keeps the sources apart.
Yes. Paste it into the project instructions and every chat in that project starts from it. Fill its blanks with the details that stay the same from chat to chat.
No. These are for the Claude apps and the API. For work inside a code repository, where the agent reads files and runs commands, use the Claude Code prompts.