Monthly KPI Variance Review with Drivers and Action Plan for Leadership
Converts pasted monthly KPI results and targets into a variance analysis, driver hypotheses, and prioritized actions that a leadership team can decide on in one meeting.
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.
23 results
Converts pasted monthly KPI results and targets into a variance analysis, driver hypotheses, and prioritized actions that a leadership team can decide on in one meeting.
Diagnoses where a workflow slows down using your process steps and metrics, then ranks causes and produces a 30-day improvement plan with owners, measures, and risks.
Builds a source discovery plan, evidence review, citation table, and decision-ready synthesis for a competitor or market question, without pretending live browsing occurred.
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.
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.
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 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.
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.
Writes a first-person LinkedIn About section from your background: what you do, for whom, proof, and how to reach you, in under 1,500 characters with three opening options.
Turns a side-business idea into a one-page plan: customer, offer, price, channel, costs, and the cheapest 30-day test that would prove people will pay.
Turns a messy list of what you did this year into a self-assessment organised by your company's review criteria, with impact stated plainly and one honest growth area.
Builds a negotiation script for a job offer: your anchor number with a reason, word-for-word replies to common pushback, and a walk-away line, using market data you supply.
Matches your existing resume to one job description: keyword gap table, rewritten bullets that use only your real experience, and a list of requirements you cannot honestly claim.
Designs Good-Better-Best pricing for your service or SaaS: what goes in each tier, price points with reasoning, the tier you want most people to pick, and what to test first.
Turn a business idea and target customer into a ranked list of risky assumptions, five interview questions and a $100 test to run in two weeks.
Turn your job offer and target number into a polite counteroffer email, phone talking points and replies to the three likeliest pushbacks.
Calculate a sustainable hourly and project rate from your income target and billable hours, covering tax, unpaid admin time and expenses with the math shown.
Get 8 predicted interview questions for a specific job, each with a STAR model answer built only from facts in your CV.
Compare the avalanche and snowball methods on months to debt-free and total interest using your own debts and extra payment, as education only.
Run a realistic one-question-at-a-time mock interview for your role and company, with a score and one concrete fix after every answer.
Build a zero-based monthly budget from typed income and spending amounts, flag overspending and get three realistic cuts, with no account access.
Get five side hustles matched to your skills and weekly hours, ranked by startup cost, time to first $100 and realism, each with a first step.
Runs a realistic interview for a role you name: one question at a time, a score out of 5 for each answer, and a stronger version of your answer built from what you said.
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.