36 Professional Prompts for Claude

Act as an editorial systems designer. Build a practical brand voice decision guide from the material I provide.

Inputs:
- Brand promise: [PASTE]
- Audience: [PASTE]
- Approved examples: [PASTE]
- Phrases or tones to avoid: [PASTE]
- Channels: [LIST]

Use only these inputs. If the examples conflict, identify the conflict before resolving it. Produce: a one-sentence voice principle; 4 voice dimensions with “do” and “do not” guidance; a vocabulary table; channel-specific adjustments; 6 before-and-after rewrites; and a final pre-publish checklist.

Do not invent customer language or brand claims. Mark missing evidence as [INPUT NEEDED]. Make every rule observable enough that 2 editors could apply it independently.

You are a positioning strategist. Turn the supplied research into a message map for one offer.

Evidence:
- Offer and actual capabilities: [PASTE]
- Primary audience: [PASTE]
- Interview notes or survey responses: [PASTE]
- Alternatives customers consider: [PASTE]
- Claims we can substantiate: [PASTE]

Create a table with columns for audience situation, desired progress, obstacle, proof, core message, supporting message, and prohibited overclaim. Then write 3 message angles and explain which audience signal makes each angle appropriate.

Quote customer language only when it appears in the evidence. Do not manufacture urgency, statistics, or testimonials. End with the 3 most important research gaps that could change the positioning.

Work as a senior content editor. Create an editorial brief for [TOPIC] using only the attached sources.

Audience: [WHO]
Search or reader intent: [INTENT]
Business goal: [GOAL]
Required sources: [LINKS OR ATTACHMENTS]
Excluded claims or topics: [LIST]

Return: the reader's starting question; a precise promise; proposed title and metadata; an outline with the job of each section; source mapping for every factual section; 5 questions the article must answer; one useful example; internal-link opportunities; and a fact-check queue.

Separate sourced facts from editorial recommendations. Label any claim that lacks support as [VERIFY]. Reject sections that exist only to increase length. The outline should lead to a concrete reader action.

Act as a content distribution editor. Convert one approved source asset into a coordinated set of channel-native pieces without copying the same summary everywhere.

Source asset: [PASTE OR ATTACH]
Audience by channel: [LIST]
Channels and limits: [LIST]
Primary action: [CTA]
Statements that must remain exact: [LIST]

First extract the central thesis, 5 supporting ideas, strongest evidence, and reusable examples. Then build a matrix for each channel showing audience moment, unique angle, format, opening, retained evidence, and CTA. Draft one complete piece per channel.

Each piece must stand alone and earn its format. Do not introduce facts absent from the source. Flag any source statement that needs verification before publication.

You are a lifecycle email strategist. Create a 5-email welcome sequence that moves a new subscriber from first value to an appropriate next step.

Inputs:
- Signup promise: [PASTE]
- Audience and current problem: [PASTE]
- Available resources: [LIST WITH LINKS]
- Paid offer, if relevant: [PASTE]
- Voice constraints: [PASTE]

For each email provide: send timing, job of the email, subject line, preview text, complete body, primary CTA, and success signal. Sequence the jobs as delivery, quick win, deeper problem, proof through a practical example, and next-step invitation.

Never invent testimonials, scarcity, or outcomes. Keep one primary CTA per email. Ensure every email provides value even if the reader never buys.

Act as a performance creative planner. Design a controlled test of ad concepts for [OFFER].

Provide:
- Audience segment: [PASTE]
- Verified offer facts: [PASTE]
- Customer evidence: [PASTE]
- Platform and format limits: [PASTE]
- Conversion event: [PASTE]
- Prohibited claims: [LIST]

Create 4 materially different concepts based on distinct customer tensions. For each, supply the hypothesis, hook, visual direction, complete primary copy, headline, CTA, and the single variable being tested. Add a test order, naming convention, decision threshold supplied by me, and interpretation guide.

Do not promise performance. If no threshold is provided, label it [INPUT NEEDED]. Make concepts different in strategy, not only wording.

You are a social content designer. Build a 9-slide Instagram carousel that teaches [NARROW TOPIC] and leads to [NEXT ACTION].

Audience: [PASTE]
Source material: [PASTE]
Brand voice: [PASTE]
Visual constraints: [PASTE]

Return a table with slide number, purpose, on-slide copy, visual cue, and accessibility note. Slide 1 must make a specific promise. Slides 2 to 7 must create a logical teaching sequence. Slide 8 must summarize the method. Slide 9 must give one relevant CTA. Then write the caption and alt text.

Keep each slide scannable. Do not split one sentence arbitrarily across slides. Use only claims supported by the source and mark uncertain facts [VERIFY].

Act as an experienced show producer. Create a recording-ready episode outline on [TOPIC].

Format and duration: [VIDEO OR PODCAST, MINUTES]
Audience knowledge level: [PASTE]
Episode promise: [PASTE]
Available evidence or guest expertise: [PASTE]
Desired listener action: [PASTE]

Provide a cold open, 4 to 6 timed segments, transition lines, host questions, likely follow-ups, examples to prepare, and a concise close. For every segment, state what the audience should understand by its end. Add a pre-recording fact-check list and a post-production cut list.

Do not script expertise the host or guest has not demonstrated. Keep timing realistic and remove segments that do not advance the promise.

You are an organic search editor. Prepare a content brief for the query [PRIMARY QUERY] from the supplied search and product evidence.

Inputs:
- Audience: [PASTE]
- Search results or keyword data: [PASTE]
- Official sources: [LINKS]
- Existing site pages: [LINKS]
- Relevant product connection: [PASTE]

Deliver: likely intent; scope boundary; recommended title, URL, and metadata; heading architecture; questions to answer; evidence assigned to sections; internal links with anchor rationale; unique value beyond current results; and a review checklist.

Do not infer volume, difficulty, or ranking probability without supplied data. Avoid keyword repetition. The brief must satisfy the reader's task first and connect to the product only where genuinely relevant.

Act as a careful account researcher. Produce a briefing for a conversation with [ACCOUNT].

Use only these materials: [COMPANY WEBSITE, FILINGS, INTERVIEWS, CRM NOTES, NEWS LINKS].
Our relevant offer: [PASTE]
Meeting type: [PASTE]

Create sections for verified company context, current priorities, relevant changes, likely stakeholders, evidence-backed hypotheses, open questions, and conversation risks. Cite the supplied source beside every external fact. Distinguish company statements from third-party reporting and your inference.

Do not guess budget, internal politics, technology use, or purchase intent. Label inferences [HYPOTHESIS] and stale information [RECHECK]. End with 5 discovery questions that would validate or disprove the most important hypotheses.

You are a consultative sales coach. Design a [MINUTES]-minute discovery call for [PROSPECT TYPE] considering [OFFER CATEGORY].

Known context: [PASTE]
Our qualification criteria: [PASTE]
What we must not claim: [PASTE]

Provide a timed agenda, permission-based opening, 10 prioritized questions, optional follow-ups, transition language, and a closing summary template. Cover current process, consequence, desired outcome, constraints, decision process, and timing without turning the call into an interrogation.

For each question, state the decision it informs. Avoid leading questions that assume the prospect has a problem. Include a respectful exit path when there is no fit.

Act as a revenue operations analyst. Convert our sales criteria into a transparent lead qualification rubric.

Inputs:
- Ideal customer profile: [PASTE]
- Disqualifiers: [PASTE]
- Required capabilities or constraints: [PASTE]
- Current sales stages: [PASTE]
- Historical evidence, if available: [PASTE]

Create 5 to 8 criteria. For each, define the evidence source, scoring rule from 0 to 2, and examples of confirmed, uncertain, and disqualifying states. Add total-score interpretations, mandatory overrides, and fields the CRM must capture.

Do not assign predictive weights without historical evidence. Treat missing data as unknown, not negative. Finish with a calibration exercise for 3 sample leads and the disagreements a sales manager should review.

You are writing follow-up after a real sales meeting. Use the notes below to create a sequence that advances the agreed decision without inventing commitments.

Meeting notes: [PASTE]
Participants and roles: [PASTE]
Confirmed needs: [PASTE]
Agreed actions and dates: [PASTE]
Useful resource: [LINK]

Draft 3 messages: a same-day recap, a value-adding follow-up, and a polite close-the-loop message. For each, include subject, full body, intended timing, and the condition for sending it.

Quote decisions accurately. If ownership or timing is unclear, mark [CONFIRM]. Use one direct next step per message. Do not fabricate rapport, urgency, or a prospect statement.

Act as a solutions consultant. Translate the supplied discovery evidence into a proposal scope that can be reviewed before pricing.

Inputs:
- Discovery notes: [PASTE]
- Available services or capabilities: [PASTE]
- Delivery constraints: [PASTE]
- Commercial assumptions: [PASTE]

Produce: problem statement in the buyer's language; desired outcomes; in-scope deliverables; exclusions; responsibilities by party; dependencies; milestones; acceptance criteria; risks; and unresolved decisions. Add a traceability table connecting each deliverable to a confirmed need.

Do not introduce features, dates, or results not supported by the inputs. Mark an assumption [ASSUMPTION] and a missing commercial term [INPUT NEEDED]. Keep scope boundaries precise enough to estimate later.

You are a sales enablement editor. Build an ethical response guide for the objections supplied below.

Objections from calls: [PASTE]
Verified product evidence: [PASTE]
Customer proof we are allowed to use: [PASTE]
Known limitations: [PASTE]

For each objection, identify the concern underneath it, a clarifying question, the evidence that may help, a concise response, the limitation to acknowledge, and the condition under which we should recommend no purchase. Group objections by risk, fit, trust, timing, and cost.

Never invent proof or dismiss the concern. If evidence is insufficient, say so and recommend what the seller should verify. End with coaching notes on when to pause rather than persuade.

Act as a B2B outbound copywriter. Write 3 short cold emails that test different relevance hypotheses for [PROSPECT SEGMENT].

Verified account signal: [PASTE]
Likely role priority: [PASTE]
Offer capability: [PASTE]
Credible proof: [PASTE]
Requested next step: [PASTE]

Variant A should lead with the observed trigger. Variant B should lead with the current workflow cost. Variant C should lead with a useful insight. Give each a subject and a body under [WORD LIMIT] words.

Use no false familiarity, manufactured urgency, or unsupported personalization. Do not state that the prospect has a problem. End with a low-pressure question that fits the evidence. Explain what response would validate each hypothesis.

You are a neutral deal reviewer. Analyze the supplied sales call transcript without rewarding confidence or talk time.

Transcript: [PASTE]
Qualification framework: [PASTE]
Deal stage: [PASTE]

Return: confirmed facts; prospect goals; current process; constraints; stakeholders; decision steps; risks; objections; commitments by each party; and unanswered questions. Cite a short transcript excerpt or timestamp for every confirmed item. Score evidence completeness by qualification dimension, not the seller's performance.

Separate direct statements from interpretations. Flag contradictions and moments where the seller led the answer. Finish with the 5 highest-value follow-up questions and a draft CRM update containing facts only.

Act as a sales operations partner. Review this pipeline snapshot for evidence quality and next-action risk.

Pipeline data: [PASTE TABLE]
Stage definitions: [PASTE]
Required exit criteria: [PASTE]
Review date: [DATE]

Create a deal-by-deal table with current stage, evidence supporting the stage, missing exit criterion, last meaningful buyer action, next action, owner, date, and risk reason. Then summarize concentration risk, stalled decisions, unsupported close dates, and data-quality gaps.

Do not change probabilities or forecast categories unless the supplied rules permit it. Treat seller activity as different from buyer progress. Mark missing fields [UNKNOWN]. End with a prioritized review agenda for the manager.

Act as a customer onboarding architect. Build a plan that gets [CUSTOMER TYPE] from purchase to [FIRST VALUE MILESTONE].

Inputs:
- Product and verified capabilities: [PASTE]
- Customer goal and starting state: [PASTE]
- Users and roles: [PASTE]
- Required setup: [PASTE]
- Support boundaries: [PASTE]

Map the journey by milestone, not by internal department. For each stage provide customer action, team action, required asset, owner, completion evidence, likely blocker, and recovery step. Include a kickoff agenda, first-week checklist, progress message, and handoff to ongoing success.

Do not assume adoption because a task was sent. Define observable completion. Mark any missing access, owner, or deadline [CONFIRM]. Keep the plan proportional to the product's real complexity.

You are a help-center editor. Create an FAQ from the supplied tickets, product documentation, and approved policies.

Materials: [ATTACH OR PASTE]
Audience: [PASTE]
Product version or date: [PASTE]
Escalation path: [PASTE]

Cluster questions by user intent, then select the questions that are frequent, consequential, or easy to misunderstand. For each answer, lead with the direct resolution, give numbered steps when needed, state prerequisites, and link to the supporting source. Add “contact support” criteria only where self-service should stop.

Do not generalize from one ticket without noting it. Resolve conflicts in favor of current approved documentation and flag unresolved conflicts [POLICY REVIEW]. End with gaps that require a new product or policy source.

Act as a support operations lead. Turn the following incident categories and service rules into a triage decision tree.

Issue examples: [PASTE]
Severity definitions: [PASTE]
Service commitments: [PASTE]
Teams and escalation routes: [PASTE]
Safety or privacy rules: [PASTE]

Produce a numbered decision flow beginning with immediate safety, security, or data-loss checks. Define category, severity, evidence to collect, first response, owning team, response target supplied by me, and escalation trigger. Add 6 edge-case examples and route each through the tree.

Never invent response targets. Use [INPUT NEEDED] where policy is absent. Minimize collection of personal or sensitive data. Make every branch end in an owner and next action.

You are an incident communications editor. Draft a factual customer update from the verified incident record.

Incident facts: [PASTE]
What is still unknown: [PASTE]
Affected users or functions: [PASTE]
Current mitigation: [PASTE]
Next update time: [PASTE]
Approved contact route: [PASTE]

Write a status-page version and a direct customer-email version. Each must state current status, observed impact, actions underway, safe customer actions, and next communication time. Include a short internal fact-check table showing which input supports each sentence.

Do not speculate about cause, resolution time, blame, or data exposure. Use plain language, acknowledge uncertainty directly, and omit technical detail that does not help the customer act.

Act as a retention-aware customer advocate. Draft a respectful response to the cancellation request below.

Customer message: [PASTE]
Account facts: [PASTE]
Cancellation and refund policy: [PASTE]
Permitted alternatives: [PASTE]
Required compliance language: [PASTE]

First classify the customer's stated reason without guessing. Write a reply that confirms the request, explains the exact next step and timing from policy, answers any direct question, and offers one relevant alternative only if it genuinely addresses the stated reason. Provide a version with no retention offer when cancellation must be immediate.

Do not create friction, hide consequences, or promise an exception. Mark a policy ambiguity [ESCALATE]. Keep the customer's choice explicit and easy to complete.

You are a product research facilitator. Create a 30-minute interview guide about [WORKFLOW OR EXPERIENCE].

Research question: [PASTE]
Participant profile: [PASTE]
Known assumptions: [PASTE]
Decisions this research should inform: [PASTE]
Topics that require consent: [PASTE]

Build a timed guide with introduction, consent reminder, recent-behavior questions, workflow reconstruction, moments of difficulty, alternatives considered, outcome, and close. Add neutral probes for each section and note the evidence each question seeks.

Avoid asking participants to predict future behavior or agree with our solution. Do not embed product praise in questions. End with a note-taking template that separates observation, direct quote, interpretation, and follow-up.

Act as a survey methodologist. Design a short survey that informs [DECISION].

Target population: [PASTE]
What we need to learn: [PASTE]
Distribution channel: [PASTE]
Maximum completion time: [PASTE]
Known segments: [PASTE]

Return the survey introduction, screening logic, complete question set, response options, branching rules, and analysis plan. Label each question with the decision it supports. Use behavior-based time frames, balanced response scales, and mutually understandable options. Include “not applicable” or “prefer not to answer” where appropriate.

Do not combine 2 ideas in one question or imply a preferred answer. If the requested decision cannot be supported by self-reported survey data alone, state the limitation and recommend complementary evidence.

You are a customer communications specialist. Draft a review request for customers who reached [VERIFIED MILESTONE].

Channel: [EMAIL, IN-APP, OR SMS]
Milestone evidence: [PASTE]
Review destination: [LINK]
Incentive policy, if any: [PASTE]
Brand voice: [PASTE]

Write a primary version and one shorter follow-up. Acknowledge the real milestone, explain why an honest review is useful, disclose any permitted incentive clearly, and provide one direct link. Include a graceful opt-out sentence.

Do not ask only satisfied customers, suggest a rating, write the review for them, or imply that support depends on participation. If milestone evidence is missing, return [DO NOT SEND] with the information required.

Act as a community experience designer. Build a welcome pathway for a new member joining [COMMUNITY].

Community purpose: [PASTE]
Member types: [PASTE]
Rules and moderation policy: [PASTE]
Key spaces or channels: [LIST]
First useful action: [PASTE]

Create: a welcome message, 10-minute orientation, profile prompt, first-post template, 7-day participation pathway, and moderator check-in. For every step, state the member benefit and the point at which it can be skipped. Include guidance for privacy, accessibility, and asking for help.

Do not pressure public introduction or disclosure. Avoid listing every channel. Lead members to the smallest action that demonstrates the community's value and make the rules easy to find.

Act as a process documentation specialist. Convert the supplied expert notes into an executable standard operating procedure for [PROCESS].

Source notes or transcript: [PASTE]
Operator skill level: [PASTE]
Approved tools: [LIST]
Required controls: [PASTE]
Definition of done: [PASTE]

Produce purpose, scope, prerequisites, roles, numbered procedure, decision points, exception paths, evidence to retain, and completion checklist. For each step, include the expected result and what to do if it fails. Extract unresolved choices into a separate review list.

Do not silently fill process gaps. Mark them [OWNER DECISION]. Keep policy statements traceable to the source and distinguish mandatory controls from helpful tips. Test the procedure against one normal case and one exception.

You are a meeting operations editor. Turn this transcript or set of notes into a decision record that prevents future ambiguity.

Meeting material: [PASTE]
Participants: [LIST]
Meeting purpose: [PASTE]

Return: concise context; decisions made; options rejected and stated reasons; open questions; action items with one owner and date; dependencies; and items explicitly deferred. Cite a timestamp or source line for every decision and commitment when available. Draft a 5-sentence recap for attendees.

Do not treat suggestions as decisions or attendance as ownership. If owner, date, or decision status is unclear, mark [CONFIRM]. Preserve disagreement that affects implementation instead of smoothing it away.

Act as an operations chief of staff. Convert the supplied weekly data into a focused operating review.

Goals and thresholds: [PASTE]
Current metrics: [PASTE]
Prior commitments: [PASTE]
Project updates: [PASTE]
Known incidents or constraints: [PASTE]

Produce a one-page review with outcomes, metric exceptions, completed commitments, missed commitments, blocked work, decisions required, and next-week owners. Compare metrics only with the supplied target or prior period. For each exception, name the evidence, likely cause if supported, and next diagnostic action.

Do not invent trends from a single point or present correlation as cause. Mark stale or incomplete data [DATA GAP]. End with a meeting agenda ordered by decision value, not department.

You are a delivery lead. Turn the following request into a project brief that a team can estimate and challenge.

Request: [PASTE]
Business context: [PASTE]
Users affected: [PASTE]
Constraints: [PASTE]
Known deadline and reason: [PASTE]

Create: problem statement, desired outcome, measurable success criteria, in-scope and out-of-scope work, deliverables, stakeholders, dependencies, risks, milestones, approval points, and open questions. Add a small table linking each deliverable to an outcome and acceptance criterion.

Do not convert a proposed solution into the problem statement. Identify unsupported deadlines and metrics as [VALIDATE]. Keep the brief neutral enough that the team can recommend a better implementation.

Act as a project owner preparing a contractor for successful delivery of [WORK PRODUCT].

Context and objective: [PASTE]
Audience or end user: [PASTE]
Required deliverables and formats: [PASTE]
Brand or technical standards: [PASTE]
Timeline, budget boundary, and review process: [PASTE]
Reference examples: [LINKS]

Write a complete brief with background, scope, exclusions, supplied assets, deliverable specifications, milestones, communication cadence, acceptance criteria, rights or confidentiality notes supplied by me, and change-request process. Add a kickoff question list.

Do not create legal terms or assume asset licenses. Mark missing commercial or rights information [CONFIRM BEFORE START]. Make subjective preferences concrete through examples or review criteria.

You are an internal process reviewer. Audit [PROCESS] using the supplied procedure, incidents, and controls.

Current process: [PASTE]
Recent failures or near misses: [PASTE]
Required policies: [PASTE]
Systems and owners: [PASTE]

Map each process stage to its input, output, owner, control, evidence, and failure mode. Rate impact and likelihood only with the scale I provide. Identify single points of failure, unclear handoffs, missing detection, excessive access, and recovery gaps. Recommend fixes in priority order with owner, effort band, and verification test.

Do not claim regulatory compliance or assign numeric risk without criteria. Separate observed weakness from hypothetical exposure. Highlight any recommendation that needs security, legal, privacy, or domain review.

Act as a market intelligence analyst. Compare [COMPETITORS] for [BUYER DECISION] using only current, supplied sources.

Sources with dates: [LINKS OR ATTACHMENTS]
Comparison criteria: [LIST]
Target customer: [PASTE]
Our verified product facts: [PASTE]

Create a matrix with one row per criterion and columns for each company, source, date, confidence, and unresolved question. Separate directly verified features, vendor claims, independent evidence, and your inference. Then summarize meaningful differences, parity areas, and information gaps.

Do not label a company better overall, infer pricing, or repeat an undated comparison. Mark inaccessible or contradictory facts [RECHECK]. Finish with buyer questions the matrix can answer and questions it cannot.

You are a strategy analyst. Prepare a decision memo for [DECISION] from the evidence below.

Decision owner: [PASTE]
Deadline and reason: [PASTE]
Options under consideration: [LIST]
Decision criteria and weights, if approved: [PASTE]
Evidence: [PASTE]
Constraints and reversibility: [PASTE]

Return a one-sentence recommendation, context, options, evidence table, tradeoffs, risks, assumptions, dissenting case, and next step. If weights are supplied, show the calculation. If not, compare criteria without manufacturing a score. State what new evidence would change the recommendation.

Distinguish fact, assumption, and judgment. Do not hide uncertainty behind confident language. Prefer a reversible test when evidence is weak and delay has a measurable cost.

Act as an implementation planner. Convert the approved objective into a realistic 30-day plan.

Objective and measurable result: [PASTE]
Starting state: [PASTE]
Available people, time, and budget: [PASTE]
Dependencies: [PASTE]
Non-negotiable constraints: [PASTE]

Organize the plan into 4 weekly outcomes. For each week list actions, owner, effort estimate, dependency, deliverable, verification method, and stop or adjust condition. Add a day-1 setup checklist, twice-weekly progress check, risk register, and day-30 review agenda.

Do not assume unlimited capacity or compress unresolved dependencies into week 1. Identify the critical path. If the objective cannot fit the stated resources, propose a smaller validated outcome and explain the tradeoff.