Pricing Change Decision Memo with Scenario Math and Test Plan
Turns current pricing, cost, and customer data into a decision memo comparing hold, adjust, and repackage options, with scenario math, risks, and a controlled pricing test plan.
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.
211 results · page 3 of 9
Turns current pricing, cost, and customer data into a decision memo comparing hold, adjust, and repackage options, with scenario math, risks, and a controlled pricing test plan.
Produces a 60-180 second explainer video script from a brief, with a scene-by-scene table for voiceover and visuals, a fact-check list, and a go/no-go checklist for recording.
Creates an editorial brief and outline for a researched article. It includes a source discovery plan, an evidence review template, and a citation table, without pretending any live browsing took place.
Turns rough notes and supplied source excerpts into a send-ready newsletter issue. It compares lead angles, flags unsupported claims, and ends with a go/no-go checklist before you hit send.
Turns a new role and what you know about the team into a 30-60-90 day plan: learning goals, relationships to build, one early win, and questions to agree with your manager in week one.
Plans 30 days of posts that lead to one offer: content pillars, a mix of value, proof and ask posts, hooks for each day, and the platform and format to use.
Writes a sincere apology for a mistake at work or in personal life that names what happened, owns the impact, avoids excuses and says what changes next.
Maps your current skills to three realistic new roles, shows the gap for each, and gives a 90-day plan to close the smallest gap without quitting your job first.
Writes three short cold emails for one prospect type, each opening with a different relevant trigger, under 90 words, with a low-effort ask and two follow-ups.
Writes a 250-word cover letter that picks the employer's top three needs from the job post and answers each with a specific example from your resume.
Builds a customer persona from your actual reviews or survey answers: jobs, pains, words they use, objections and buying triggers, with quotes as evidence and no invented demographics.
Turns your common support questions and policies into ten reusable reply macros with a warm tone, the right policy detail, and a placeholder only where agents must personalise.
Finds the most likely cause of an error from the message and the relevant code, ranks other possible causes, and gives the smallest fix plus a way to prove it worked.
Turns an agent idea into a build-ready design: the job, the tools with their inputs and permissions, guardrails, failure handling and a set of evaluation cases to test it.
Writes a timed lesson plan with one shared objective and three tiers of tasks, plus support for learners who need scaffolding and stretch tasks for those who finish early.
Writes tests for a single function that cover normal inputs, boundaries, bad input and error paths, in the test framework your project already uses.
A five-minute end-of-day check that records what got done, captures loose ends, and picks three priorities for tomorrow so you can stop thinking about work.
Writes the formula for what you want a spreadsheet to do, in both Excel and Google Sheets syntax, explains each part, and gives a test case so you can check it works.
Translates a confusing bill, lease, contract or government letter into plain language: what it says, what you must do and by when, and what to question.
Produces an onboarding guide for one folder of a codebase: what it does, how data moves through it, the files to read first and the traps a new developer should avoid.
Teaches any topic one idea at a time with plain explanations and analogies, makes you explain it back, re-teaches the gaps, then ends with a marked quiz.
Designs a habit around a tiny minimum version, a clear trigger and a restart rule, so one missed day does not end the whole attempt.
Sorts a batch of pasted emails by what each one needs from you, drafts short replies for the ones that need an answer, and lists deadlines found in the thread.
Writes five versions of the headline, subheadline and button for the top of your landing page, each from a different angle, plus which two to A/B test first and why.
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.