30 Claude Prompts for Pipedrive
Practical prompts for pipeline stage design, deal cleanup, activity cadences, and reports, each one ready to paste into Claude with your own deal data.
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Pipeline Stage Design
5 promptsDesign a Pipeline Stage Structure
1/30✨ What it does
Produces a proposed 5 to 7 stage pipeline structure with entry triggers for each stage.
You are a senior sales operations manager. <context> I am rebuilding our Pipedrive pipeline because reps skip stages and forecasts do not match reality. </context> <inputs> - Business type: [B2B SAAS OR SERVICE TYPE] - Average deal size: [AVERAGE DEAL VALUE] - Current sales cycle length: [NUMBER OF DAYS] - Number of reps: [REP COUNT] - Current stage list: [PASTE CURRENT STAGE NAMES] </inputs> <task> Propose a revised pipeline stage structure with 5 to 7 stages, a one line definition for each stage, and the specific event that moves a deal into it. </task> <constraints> Keep stage names short enough to fit in the Pipedrive kanban column header. Avoid stages that describe internal admin work rather than buyer behavior. Do not merge qualification and discovery into one stage. </constraints> <format> Return a numbered list of stages, each with a bolded name, a one sentence definition, and the entry trigger in parentheses. </format>
Pro tip: Paste your actual current stage names so Claude points out exactly which ones to cut or split, not a generic template.
Audit Stage Definitions for Overlap
2/30✨ What it does
Produces a table of stage naming conflicts with a recommended fix for each.
You are a Pipedrive administrator responsible for pipeline data quality. <context> Our reps keep asking which stage a deal belongs in because two stages sound almost the same. </context> <inputs> - Full stage list with descriptions: [PASTE STAGE LIST AND DESCRIPTIONS] - Pipeline name: [PIPELINE NAME] - Common rep complaints: [PASTE 2 TO 3 REP QUOTES] </inputs> <task> Identify any stages whose definitions overlap or contradict each other, and propose a fix for each conflict, either a merge, a rename, or a clearer entry rule. </task> <constraints> Do not suggest adding more than one new stage. Keep the total stage count at [MAX STAGE COUNT] or fewer. Explain the reasoning for every change in one sentence. </constraints> <format> Return a table with columns: Conflict, Stages Involved, Recommended Fix, Reason. </format>
Pro tip: Include the real rep complaints verbatim, vague versions make it harder for Claude to spot the actual point of confusion.
Write Exit Criteria for Each Stage
3/30✨ What it does
Produces a checklist of exit criteria a rep must confirm before advancing a deal at each stage.
You are a sales enablement lead building a Pipedrive playbook. <context> Reps move deals forward based on gut feeling instead of a checklist, which inflates our forecast. </context> <inputs> - Stage names in order: [PASTE STAGE NAMES] - Product or service sold: [PRODUCT NAME] - Buyer role that signs the contract: [DECISION MAKER TITLE] </inputs> <task> Write exit criteria for each stage, meaning the specific facts a rep must confirm before moving a deal to the next stage. </task> <constraints> Use checklist items a rep can verify in under a minute, no vague language like probably or seems interested. Limit each stage to 3 or 4 checklist items. </constraints> <format> Return one heading per stage followed by a bullet checklist under it. </format>
Pro tip: Print the resulting checklist and pin it next to the pipeline view, reps ignore criteria buried in a wiki page.
Map a New Sales Process to Pipedrive Stages
4/30✨ What it does
Produces a table mapping an existing sales process onto Pipedrive stages with required fields noted.
You are a revenue operations consultant onboarding a new sales team onto Pipedrive. <context> We are migrating from spreadsheets and need our existing sales process translated into Pipedrive stages. </context> <inputs> - Current sales process steps: [PASTE STEPS FROM YOUR PLAYBOOK] - Sales motion type: [INBOUND, OUTBOUND, OR HYBRID] - Typical objections at each step: [PASTE OBJECTIONS LIST] </inputs> <task> Translate the process steps into a Pipedrive pipeline with stage names, and note which custom fields should be marked required at each stage to capture the objections handled. </task> <constraints> Keep the mapping practical for a team that has never used Pipedrive. Flag any process step that does not need its own stage and can live as an activity type instead. </constraints> <format> Return a two column table: Pipedrive Stage, Required Fields and Notes. </format>
Pro tip: If a step gets flagged as an activity instead of a stage, set it up as an activity type before your first team meeting on the new pipeline.
Build a Multiple Pipeline Strategy
5/30✨ What it does
Produces a recommendation on single versus multiple pipelines plus the resulting stage list.
You are a Pipedrive systems architect for a company selling two different products. <context> We sell both [PRODUCT LINE A] and [PRODUCT LINE B] through the same team and are debating one pipeline versus separate pipelines. </context> <inputs> - Product line A sales cycle: [CYCLE LENGTH A] - Product line B sales cycle: [CYCLE LENGTH B] - Overlap in buyer contacts: [PERCENTAGE OVERLAP] - Reporting needs: [PASTE WHAT LEADERSHIP WANTS TO SEE] </inputs> <task> Recommend whether to run one pipeline with a product field or two separate pipelines, and lay out the stage list for whichever structure you recommend. </task> <constraints> Base the recommendation on the sales cycle difference and reporting needs given, not on general best practice alone. State the tradeoff you are accepting either way. </constraints> <format> Return a short recommendation paragraph, then the stage list as a numbered list. </format>
Pro tip: Run this again in six months as cycle lengths change, the right call for two products often flips once volume grows.
Deal Hygiene and Cleanup
5 promptsFlag Stale Deals for Cleanup
6/30✨ What it does
Produces a rep grouped list of stale deals with a suggested next action for each.
You are a sales operations analyst reviewing Pipedrive data quality. <context> Our pipeline value looks healthy on paper but many deals have not moved in months. </context> <inputs> - Export of open deals with last activity date: [PASTE DEAL LIST WITH DATES] - Stage aging thresholds: [DAYS PER STAGE BEFORE FLAGGED] - Rep names tied to each deal: [PASTE REP ASSIGNMENTS] </inputs> <task> List every deal that has exceeded its stage aging threshold, group the list by rep, and suggest one next action per deal such as close as lost, schedule a check in call, or escalate. </task> <constraints> Do not recommend closing a deal as lost without a stated reason tied to the data provided. Keep the next action to one short phrase per deal. </constraints> <format> Return a table grouped by rep with columns: Deal Name, Days Stale, Suggested Action. </format>
Pro tip: Run this monthly on a fresh export, a stale list from last quarter will just repeat deals that already got handled.
Write a Deal Hygiene Checklist
7/30✨ What it does
Produces an 8 item or fewer checklist reps run through before marking a deal as won.
You are a Pipedrive administrator setting standards for a growing sales team. <context> New reps enter deals inconsistently, which breaks our reports every quarter. </context> <inputs> - Required fields today: [PASTE CURRENT REQUIRED FIELDS] - Common data entry mistakes: [PASTE EXAMPLES OF BAD DEAL ENTRIES] - Team size: [NUMBER OF REPS] </inputs> <task> Write a deal hygiene checklist reps must run through before marking a deal as won, covering naming, value, close date, contact info, and next steps. </task> <constraints> Keep the checklist to 8 items or fewer so it fits on one printed page. Word each item as a yes or no check, not a paragraph of instructions. </constraints> <format> Return a numbered checklist, each item starting with a checkbox character. </format>
Pro tip: Add the checklist as a required activity type due before the won stage so it actually gets used, not just read once.
Draft a Lost Reason Taxonomy
8/30✨ What it does
Produces a fixed 8 to 10 category lost reason taxonomy for a Pipedrive dropdown field.
You are a sales analytics lead standardizing loss data in Pipedrive. <context> Our lost reason field is a free text box, so every rep writes something different and we cannot analyze why we lose deals. </context> <inputs> - Sample of free text lost reasons: [PASTE 15 TO 20 EXAMPLES] - Products sold: [PRODUCT LIST] - Main competitors: [COMPETITOR NAMES] </inputs> <task> Group the free text reasons into a fixed list of 8 to 10 lost reason categories suitable for a Pipedrive dropdown field, with a short definition for each category. </task> <constraints> Every category must be distinct enough that a rep would not be confused about which one to pick. Include a category for no decision and a category for lost to a named competitor. </constraints> <format> Return a numbered list of categories, each with a one sentence definition. </format>
Pro tip: Once you switch the field to a dropdown, keep the old free text field around read only for a quarter so historical notes are not lost.
Standardize Deal Naming Conventions
9/30✨ What it does
Produces a single deal title naming formula with worked examples and a field description.
You are a Pipedrive administrator cleaning up deal titles across the team. <context> Deal titles are inconsistent, some just say the company name and others include random notes, which makes search painful. </context> <inputs> - Sample of current deal titles: [PASTE 10 TO 15 CURRENT TITLES] - Fields available on the deal: [COMPANY, CONTACT, PRODUCT, VALUE, ETC] - Team size: [NUMBER OF REPS] </inputs> <task> Propose a single naming convention formula for deal titles, show 5 examples using the sample data, and write the one line rule reps will see in the field description. </task> <constraints> The formula must work whether the deal has one product or multiple. Keep the final title under [MAX CHARACTER COUNT] characters. </constraints> <format> Return the formula, 5 worked examples, and the field description text in that order. </format>
Pro tip: Bulk rename existing open deals to the new formula in one pass, a mixed format pipeline defeats the point of standardizing.
Build a Duplicate Deal Merge Plan
10/30✨ What it does
Produces a step by step duplicate record merge plan with a flagged review list.
You are a data quality specialist cleaning up a Pipedrive account before a migration. <context> Years of manual entry have left us with duplicate organizations, contacts, and open deals for the same accounts. </context> <inputs> - Sample of suspected duplicate records: [PASTE ORG OR CONTACT NAMES] - Fields that differ between duplicates: [PASTE DIFFERING FIELD VALUES] - Deadline for cleanup: [TARGET DATE] </inputs> <task> Write a step by step merge plan that decides which record survives as the primary in each duplicate pair, and lists which fields need manual review before merging. </task> <constraints> Never recommend merging two records tied to different active deals without flagging it for human review first. Keep the plan usable by someone who is not a Pipedrive expert. </constraints> <format> Return the plan as numbered steps, with a separate flagged list of pairs needing manual review. </format>
Pro tip: Export a backup of the organizations and deals involved before running any merge, Pipedrive merges cannot be fully undone.
Activity Templates and Cadences
5 promptsCreate a Follow Up Activity Sequence
11/30✨ What it does
Produces a 5 touch follow up activity sequence with day offsets and channel mix.
You are a sales enablement manager building activity templates in Pipedrive. <context> Reps forget to follow up after a demo, so warm deals go cold within a week. </context> <inputs> - Deal stage this sequence starts at: [STAGE NAME] - Typical buyer response time: [DAYS UNTIL REPLY] - Channels available: [EMAIL, CALL, LINKEDIN, ETC] </inputs> <task> Build a 5 touch follow up activity sequence with the activity type, the day offset from the trigger event, and a one line goal for each touch. </task> <constraints> Space touches so the last one lands within [MAX FOLLOW UP WINDOW] days of the trigger. Mix at least two different channels, do not make every touch an email. </constraints> <format> Return a table with columns: Day Offset, Activity Type, Channel, Goal. </format>
Pro tip: Turn each row into a Pipedrive activity template so the sequence gets scheduled with one click after a demo.
Write Call Script Activity Notes
12/30✨ What it does
Produces a call outline plus a fill in the blank post call note template for the activity log.
You are a sales trainer preparing call activity templates for new reps. <context> New reps freeze on discovery calls and their Pipedrive activity notes end up blank or one word. </context> <inputs> - Call purpose: [DISCOVERY, DEMO FOLLOW UP, OR RENEWAL] - Product being discussed: [PRODUCT NAME] - Common objections heard: [PASTE OBJECTIONS] </inputs> <task> Write a call script outline with 5 to 6 talking points and the note template a rep should fill in and paste into the Pipedrive activity note after the call. </task> <constraints> Keep talking points as prompts, not a word for word script. The note template must capture next steps and a rebooking date field. </constraints> <format> Return two sections, Call Outline and Post Call Note Template, each as a bullet list. </format>
Pro tip: Paste the note template into the Pipedrive activity type description so it shows up automatically when a rep logs the call.
Build a Demo to Close Activity Cadence
13/30✨ What it does
Produces a week by week activity cadence from demo day to target close date.
You are a sales manager designing the activity cadence between demo and close in Pipedrive. <context> Deals stall after the demo because there is no defined rhythm of touches pushing toward a decision. </context> <inputs> - Average time from demo to close today: [NUMBER OF DAYS] - Decision makers usually involved: [ROLES INVOLVED] - Common stall reasons: [PASTE REASONS DEALS STALL] </inputs> <task> Design an activity cadence from demo day to target close date, specifying each activity, who it involves, and the day it should be logged. </task> <constraints> Include at least one activity aimed at each decision maker role listed. Do not schedule more than 2 touches per week to avoid annoying the buyer. </constraints> <format> Return a week by week list, each week showing the activities planned for it. </format>
Pro tip: Adjust the cadence length per deal size, a small deal does not need the same 6 week push as an enterprise one.
Draft Activity Templates for Renewals
14/30✨ What it does
Produces a reverse timeline of renewal activities counting back from the contract end date.
You are a customer success operations lead managing renewals inside Pipedrive. <context> Renewal deals get created too late because there is no standard activity trail leading up to the contract end date. </context> <inputs> - Contract length: [CONTRACT TERM LENGTH] - Renewal lead time policy: [DAYS BEFORE EXPIRY TO START] - Account tier: [ENTERPRISE, MID MARKET, OR SMALL BUSINESS] </inputs> <task> Create a set of renewal activity templates counting back from the contract end date, including a usage review, a pricing conversation, and a signature reminder. </task> <constraints> The first activity must trigger at least [MINIMUM LEAD DAYS] days before expiry. Adjust urgency and touch count based on the account tier given. </constraints> <format> Return a reverse timeline table with columns: Days Before Expiry, Activity, Owner. </format>
Pro tip: Set the first activity as an automated task tied to the contract end date field so renewals stop depending on someone remembering.
Design a Cold Outreach Activity Plan
15/30✨ What it does
Produces a multi touch cold outreach plan with channel and message angle per day.
You are a sales development manager setting up outbound activity templates in Pipedrive. <context> Our SDRs log outreach inconsistently, some give up after one email and others spam the same contact daily. </context> <inputs> - Target persona: [JOB TITLE OR PERSONA NAME] - Outreach channels approved: [EMAIL, PHONE, LINKEDIN, ETC] - Campaign length allowed: [NUMBER OF DAYS] </inputs> <task> Design a multi touch cold outreach activity plan across the campaign length, specifying the channel, day, and message angle for each touch. </task> <constraints> Limit total touches to [MAX TOUCH COUNT] across the whole campaign. Vary the message angle each touch so it does not read as the same email resent. </constraints> <format> Return a table with columns: Day, Channel, Message Angle. </format>
Pro tip: Cap the touch count before you ask Claude to plan it, otherwise the plan will keep adding touches until it fills the whole campaign window.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Reports and Forecasting
5 promptsBuild a Weekly Pipeline Report
16/30✨ What it does
Produces a short weekly pipeline report with a summary, stage movement, and risks section.
You are a sales operations manager preparing the weekly pipeline update for leadership. <context> Leadership wants a five minute readable summary instead of scrolling through the Pipedrive dashboard themselves. </context> <inputs> - Pipeline data export for this week: [PASTE STAGE TOTALS AND DEAL COUNTS] - Same week last month for comparison: [PASTE PRIOR NUMBERS] - Target for the quarter: [QUARTERLY TARGET VALUE] </inputs> <task> Write a weekly pipeline report summarizing total pipeline value, movement by stage, and pace against the quarterly target. </task> <constraints> Keep the report under 200 words. Call out any stage where deal count dropped versus last month by name, do not bury it in a general statement. </constraints> <format> Return three short sections: Summary, Stage Movement, Risks. </format>
Pro tip: Save this exact prompt as a recurring weekly task, swapping only the data, so the report format stays comparable week over week.
Write a Sales Forecast Summary
17/30✨ What it does
Produces a weighted forecast calculation plus a written summary naming the top deals at risk.
You are a sales director preparing the monthly forecast call with the CEO. <context> I need to turn raw Pipedrive deal data into a forecast number I can defend in the meeting. </context> <inputs> - Open deals with stage, value, and close date: [PASTE DEAL LIST] - Historical win rate by stage: [PASTE WIN RATE PERCENTAGES] - This month's target: [TARGET VALUE] </inputs> <task> Calculate a weighted forecast using the historical win rates, and write a summary explaining the gap or surplus against target and the biggest deals driving the number. </task> <constraints> Show the weighted calculation, not just the final number, so it can be checked. Name the top 3 deals that most affect whether the forecast is hit. </constraints> <format> Return the calculation as a small table, then a short written summary below it. </format>
Pro tip: Double check the win rate percentages you paste in, a stale win rate will make the whole weighted forecast wrong even if the deal data is fresh.
Draft a Win Loss Analysis Report
18/30✨ What it does
Produces a win loss analysis with three findings, each backed by evidence and a recommendation.
You are a revenue operations analyst studying why deals are won or lost. <context> We closed [NUMBER OF DEALS] deals last quarter and leadership wants to know the real patterns behind wins and losses. </context> <inputs> - Won deals with lost reason field blank and notes: [PASTE WON DEAL SUMMARIES] - Lost deals with lost reason categories: [PASTE LOST DEAL SUMMARIES] - Competitors named in notes: [PASTE COMPETITOR MENTIONS] </inputs> <task> Analyze the won and lost deals for patterns by deal size, source, and competitor, and write a win loss report with the top 3 findings and a recommendation for each. </task> <constraints> Base every finding on a pattern that appears at least twice in the data, not a single anecdote. State the recommendation as an action, not just an observation. </constraints> <format> Return the report as three numbered findings, each with Finding, Evidence, and Recommendation. </format>
Pro tip: Include enough deals from both sides, a report built from mostly won deals cannot honestly explain why deals are lost.
Create a Rep Performance Scorecard
19/30✨ What it does
Produces a per rep scorecard flagging whether a gap to quota is an activity or conversion problem.
You are a sales manager building individual performance scorecards from Pipedrive activity and deal data. <context> I want a fair way to compare reps beyond just who closed the most revenue this month. </context> <inputs> - Per rep data, activities logged, deals created, deals won, average deal size: [PASTE PER REP TABLE] - Team average for each metric: [PASTE TEAM AVERAGES] - Quota per rep: [QUOTA VALUE] </inputs> <task> Build a scorecard for each rep comparing their numbers to the team average and quota, and flag whether their gap is an activity problem or a conversion problem. </task> <constraints> Do not rank reps against each other in a single leaderboard, score each rep against their own quota and the team average only. Keep each rep's summary to 3 sentences. </constraints> <format> Return one short section per rep with their name as the heading. </format>
Pro tip: Use this before a one on one, not in a group setting, the framing works best as private coaching input rather than a public ranking.
Build a Conversion Rate by Stage Report
20/30✨ What it does
Produces stage by stage conversion rates and flags the biggest drop off point with causes to investigate.
You are a sales operations analyst measuring pipeline efficiency in Pipedrive. <context> We do not know which stage is actually leaking deals, we just know the overall win rate feels low. </context> <inputs> - Deal counts entering and exiting each stage: [PASTE STAGE ENTRY AND EXIT COUNTS] - Time period covered: [DATE RANGE] - Pipeline name: [PIPELINE NAME] </inputs> <task> Calculate the conversion rate between each consecutive stage and identify the single stage with the biggest drop off, then suggest two possible causes to investigate. </task> <constraints> Show the conversion rate math for every stage transition, not just the worst one. Keep suggested causes specific to the stage identified, not generic sales advice. </constraints> <format> Return a table of stage transitions with conversion rate, then a short paragraph on the worst stage and causes to investigate. </format>
Pro tip: Pull entry and exit counts from the same fixed date range on both ends, mismatched ranges will distort the conversion math.
Deal Coaching and Pipeline Reviews
5 promptsPrepare a Deal Review Agenda
21/30✨ What it does
Produces a time boxed deal review agenda with a key question for each deal.
You are a sales manager running weekly one on one deal reviews with reps. <context> Our deal reviews ramble without structure and rarely produce a clear next action for the rep. </context> <inputs> - Deals to review this week with stage and value: [PASTE DEAL LIST] - Rep name: [REP NAME] - Time allotted for the review: [MEETING LENGTH IN MINUTES] </inputs> <task> Build a deal review agenda that allocates time across the deals listed, prioritizing the largest and most at risk deals first, with a question to ask for each deal. </task> <constraints> Keep total time within the allotted meeting length. Give the smallest, healthiest deals no more than 2 minutes each. </constraints> <format> Return a table with columns: Deal Name, Minutes Allocated, Key Question. </format>
Pro tip: Send the agenda to the rep before the meeting, a surprise question list turns a coaching conversation into an interrogation.
Write Coaching Notes for a Stuck Deal
22/30✨ What it does
Produces a diagnosis of a stalled deal plus 3 concrete next actions for the rep.
You are a sales coach helping a rep unstick a deal that has stalled in Pipedrive. <context> A rep brought me a deal that has not moved in [NUMBER OF DAYS] days and they are not sure what to do next. </context> <inputs> - Deal stage and value: [STAGE AND VALUE] - Last three activity notes: [PASTE LAST 3 ACTIVITY NOTES] - Known stakeholders involved: [PASTE STAKEHOLDER NAMES AND ROLES] </inputs> <task> Write coaching notes diagnosing why the deal may be stuck based on the activity history, and give the rep 3 specific next actions to take this week. </task> <constraints> Base the diagnosis only on evidence in the activity notes provided, do not invent stakeholder motivations not mentioned. Make each next action something the rep can do without new information. </constraints> <format> Return a short Diagnosis paragraph followed by a numbered list of Next Actions. </format>
Pro tip: Paste the activity notes verbatim rather than summarizing them yourself, the wording often carries clues about who is actually stalling.
Draft Questions for a Pipeline Review Meeting
23/30✨ What it does
Produces 8 to 10 pointed review questions grouped by stage or metric.
You are a sales director preparing a monthly pipeline review with the full sales team. <context> Our pipeline reviews turn into status updates instead of surfacing the deals that actually need help. </context> <inputs> - Number of reps attending: [REP COUNT] - Pipeline stages in use: [PASTE STAGE NAMES] - Focus area for this month: [FORECAST ACCURACY, STAGE VELOCITY, OR WIN RATE] </inputs> <task> Draft a set of 8 to 10 pointed questions the manager can ask during the review to expose risk in the pipeline, tied to the focus area given. </task> <constraints> Write questions that require a specific answer, not yes or no. Avoid generic questions like how is it going, tie each question to a stage or metric. </constraints> <format> Return a numbered list of questions grouped under the relevant stage or metric. </format>
Pro tip: Rotate which stage gets the sharpest questions each month, asking about the same stage every time trains reps to have a canned answer ready.
Build a Deal Risk Assessment
24/30✨ What it does
Produces a risk score, low, medium, or high, for each deal closing this quarter with a one line reason.
You are a sales operations lead flagging at risk deals before the quarter closes. <context> We want to catch deals that look healthy in Pipedrive but have warning signs before they slip to next quarter. </context> <inputs> - Deals closing this quarter with stage and last activity date: [PASTE DEAL LIST] - Days since last stage change per deal: [PASTE STAGE AGE DATA] - Single threaded contact flag per deal: [PASTE YES OR NO PER DEAL] </inputs> <task> Score each deal as low, medium, or high risk based on stage age and single threaded contact status, and explain the scoring logic in one line per deal. </task> <constraints> Any deal that is single threaded and has not changed stage in over [STAGE AGE THRESHOLD] days must be scored high risk, no exceptions. Keep the explanation to one line per deal. </constraints> <format> Return a table with columns: Deal Name, Risk Score, Reason. </format>
Pro tip: Refresh the single threaded flag right before running this, a contact that added a second stakeholder last week will otherwise score wrong.
Write a Quarterly Business Review Deck Outline
25/30✨ What it does
Produces an 8 slide quarterly business review outline with the headline number placed up front.
You are a sales leader preparing a quarterly business review for the executive team using Pipedrive data. <context> I need to turn a quarter of deal and activity data into a deck the executives will actually sit through. </context> <inputs> - Quarter results, revenue closed, pipeline generated, win rate: [PASTE QUARTER RESULTS] - Compare to prior quarter: [PASTE PRIOR QUARTER NUMBERS] - Biggest wins and losses of the quarter: [PASTE TOP DEALS] </inputs> <task> Outline a quarterly business review deck with slide titles and the one key point each slide should make, using the results and comparisons given. </task> <constraints> Limit the deck to 8 slides. Order slides so results come before explanations, do not bury the headline number on slide 5. </constraints> <format> Return a numbered list of slides, each with a title and one sentence describing its key point. </format>
Pro tip: Have the biggest lost deal ready to discuss even if it is not on a slide, executives often ask about it the moment they see the win rate.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Automation and Workflow Rules
5 promptsDesign a Deal Rotting Alert Rule
26/30✨ What it does
Produces a deal rotting automation rule set with the exact alert message text included.
You are a Pipedrive administrator configuring automation rules for deal aging. <context> Deals sit untouched for weeks because nobody gets notified until it is too late to save them. </context> <inputs> - Rotting threshold per stage: [DAYS PER STAGE] - Who should be alerted: [REP, MANAGER, OR BOTH] - Notification channel available: [EMAIL, SLACK, OR IN APP] </inputs> <task> Design an automation rule set that flags a deal as rotting after the threshold and routes an alert to the right person, including the exact alert message text. </task> <constraints> Write the alert message under 25 words so it is not ignored. Escalate to the manager only after the rep has already been alerted once and ignored it for [ESCALATION WINDOW DAYS] days. </constraints> <format> Return the rule logic as numbered steps, followed by the exact alert message text in quotes. </format>
Pro tip: Test the escalation window on one pilot pipeline first, a window that is too short will train managers to ignore the alerts too.
Write Automation Rules for Stage Changes
27/30✨ What it does
Produces a table of trigger and action pairs for automating manual tasks tied to stage changes.
You are a revenue operations engineer building Pipedrive workflow automations. <context> Every time a deal moves stage, several manual tasks should fire but reps forget to do them by hand. </context> <inputs> - Stage transitions needing automation: [PASTE STAGE PAIRS] - Manual tasks currently done by hand: [PASTE TASK LIST] - Tools connected to Pipedrive: [PASTE CONNECTED TOOLS] </inputs> <task> Write the trigger and action pairs needed to automate each manual task, specifying which Pipedrive event fires it and which tool or field it updates. </task> <constraints> Only automate tasks that are purely mechanical, flag any task that requires human judgment instead of automating it. State the trigger event precisely, not just the stage name. </constraints> <format> Return a table with columns: Trigger Event, Action, Tool or Field Updated. </format>
Pro tip: Build the flagged judgment based tasks as a checklist for the rep instead of forcing an automation onto something that needs a human call.
Draft a Lead Routing Rule Set
28/30✨ What it does
Produces an ordered lead routing rule set with a fallback rule for unmatched leads.
You are a sales operations manager setting up lead routing automation in Pipedrive. <context> Inbound leads currently get assigned manually and sit in a queue for hours before a rep claims them. </context> <inputs> - Rep territories or specialties: [PASTE TERRITORY OR SPECIALTY LIST] - Lead source types: [WEBSITE FORM, CHAT, REFERRAL, ETC] - Round robin or specialty based preference: [ROUTING METHOD PREFERRED] </inputs> <task> Draft a lead routing rule set that assigns each incoming lead to the correct rep automatically based on the routing method and territory data given. </task> <constraints> Include a fallback rule for leads that do not match any territory or specialty. Keep response time expectations under [MAX RESPONSE TIME MINUTES] minutes in the rule description. </constraints> <format> Return the rules as an ordered list, with the fallback rule listed last. </format>
Pro tip: Watch the fallback rule's volume closely after launch, a high hit rate there usually means your territory list has a gap.
Build a Task Automation Plan for New Deals
29/30✨ What it does
Produces an automation plan that creates a short setup task list on deal creation, varied by source.
You are a Pipedrive administrator standardizing what happens the moment a new deal is created. <context> Reps create a deal and then forget the basic setup tasks, so half our deals are missing key information within a day. </context> <inputs> - Setup tasks currently done manually: [PASTE TASK LIST] - Deal source types: [OUTBOUND, INBOUND, PARTNER, ETC] - Fields required before a deal can move to the next stage: [PASTE REQUIRED FIELDS] </inputs> <task> Build an automation plan that creates the setup tasks automatically when a deal is created, varying the task list slightly based on deal source. </task> <constraints> Keep the automatically created task list to 4 items or fewer per deal source so reps are not overwhelmed. Tie at least one task to filling in the required fields listed. </constraints> <format> Return one section per deal source, each listing its automatically created tasks. </format>
Pro tip: Review the generated task lists with reps before turning the automation on, tasks nobody reads just add clutter to the deal view.
Write Email Trigger Rules for Follow Ups
30/30✨ What it does
Produces a trigger to template mapping for automated deal event emails, with delay timing and conflict checks.
You are a marketing operations specialist connecting Pipedrive deal events to automated email follow ups. <context> We want emails to go out automatically at key moments in a deal instead of relying on reps to remember. </context> <inputs> - Deal events to trigger on: [PASTE EVENTS, EG STAGE ENTERED, DEAL WON, DEAL LOST] - Email templates available: [PASTE TEMPLATE NAMES] - Sending account: [SALES REP OR SHARED INBOX] </inputs> <task> Write the trigger rules mapping each deal event to the correct email template and sending account, including a short delay recommendation for each so the email does not feel instant and robotic. </task> <constraints> Never trigger an automated email on the same event as a scheduled human call for the same deal, note where that conflict would happen. Keep delay times realistic, between [MINIMUM DELAY] and [MAXIMUM DELAY]. </constraints> <format> Return a table with columns: Trigger Event, Email Template, Sending Account, Delay. </format>
Pro tip: List any event where a rep is also expected to call, this prompt will flag the overlap so the automated email does not step on that call.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides