🤝
CRM & sales ops
A CRM is mostly other people's typing. Half-filled records, deals that have sat in Negotiation since March, three accounts for the same company spelled three ways, and a pipeline report nobody trusts enough to act on. The prompts below are for that work rather than for selling: they ask a model to look at what is actually in the system, say what is wrong with it, and produce something you can paste back. Some are tool-specific — Salesforce validation rules, HubSpot workflow logic, SOQL you would rather not write by hand — and some work anywhere, because a stalled deal reads the same in Pipedrive as it does in Dynamics. Paste in an export, a field list, or a single record, and be specific about which system you are in: the answer changes a lot between them.
47 prompts in 5 groups
CRM & sales ops21 categories
Length
Tag
Pipeline and deals
Working out which deals are real, what is actually blocking them, and what to do next week.
- Find the deals that are quietly deadLongA pipeline export where some deals have not moved in months but nobody has closed them.
- Write stage definitions people will actually followLongWhen two reps put the same deal in different stages and the forecast is meaningless as a result.
- What could kill this dealLongBefore a forecast call, on the deal you keep saying is fine.
- Score this deal against MEDDIC and show the gapsLongQualifying an opportunity properly instead of on a feeling about how the last call went.
- Sanity-check these close datesMediumA forecast where suspiciously many deals land on the last day of the quarter.
- Find the pattern in why we loseLongA pile of closed-lost records with reasons that are all 'price' and probably are not.
- Write the handover note for this accountLongPassing a customer to someone else without them having to read two years of activity history.
- Set up HubSpot deal stages and their automationLongConfiguring a HubSpot pipeline, including what should happen automatically at each stage.
Data hygiene
Duplicates, inconsistent fields, messy imports, and records that technically exist but say nothing.
- Find the duplicate accounts in this exportLongThe same company in the CRM three times, spelled three ways, with activity split across all of them.
- Map these columns to CRM fields before importingLongA spreadsheet from a trade show or an old system that has to land in the CRM without wrecking it.
- Which of these records are actually worth keepingLongThousands of contacts where most have a name, an email, and nothing else.
- Clean up this picklistLongAn industry or lead-source field with 60 values, half of them typos of the other half.
- Write the data quality rules for this objectLongDeciding what "complete" means for a record, before arguing about it in a meeting.
- Normalise these company namesMediumA list to import where the same company appears as four different strings.
- Decide which value survives a mergeLongTwo records for the same company that disagree on half their fields.
- Plan a Salesforce bulk update safelyLongBefore pushing thousands of records through Data Loader on a live org.
- Design HubSpot properties that will not rotLongBefore adding properties to HubSpot, which is easy and almost never undone.
Outreach and follow-up
Emails, sequences and call prep written from what the record already tells you.
- Write the follow-up from what the record saysLongA follow-up email that refers to the actual conversation instead of 'touching base'.
- Prep me for this call in one pageLongTen minutes before a call with an account you have not touched in months.
- Re-engage a contact who went quietLongSomeone who was interested, then stopped replying, and a generic nudge would make it worse.
- Critique this outreach sequenceLongA sequence with poor replies, before blaming the list.
- Turn these call notes into a CRM updateLongMessy notes after a call that need to become fields and tasks before you forget.
- Write a first email that earns a replyMediumCold outreach where you actually have a reason to be writing to this specific person.
- Prepare honest answers to the objections comingLongBefore a call where you already know what they are going to push back on.
- Build a HubSpot sequence worth receivingLongSetting up a sequence that does not read like five automated emails in a row.
Reports and forecasting
Turning a question about the business into a report, a query, or a number you can defend.
- Write the SOQL for this questionLongA Salesforce question you can describe in a sentence but not write as a query.
- Turn this question into a report specLongSomeone asked for a dashboard and described a feeling rather than a metric.
- Stress-test this forecastLongA committed number you have to defend at the end of the week.
- Pin down what this metric actually meansLongWhen two teams report different numbers for the same thing and both are right.
- Build this as a HubSpot reportLongKnowing the number you want and not which HubSpot report type produces it.
- Work out retention from this customer exportLongRenewal and churn data in a spreadsheet, and a question about whether it is getting worse.
- Summarise this pipeline for someone with two minutesMediumA weekly update for a manager who does not want the deal-by-deal walkthrough.
- Pick the right Salesforce report typeLongA Salesforce report that will not show the field you need, because the report type cannot reach it.
- Write the HubSpot list criteria for this segmentLongA segment you can describe in a sentence but cannot get HubSpot's filters to produce.
- Work out what HubSpot attribution is telling youLongAn attribution report being used to make budget decisions it may not support.
Automation and admin
Workflows, validation, field design and the documentation nobody wrote at the time.
- Design this HubSpot workflowLongAutomating something in HubSpot without discovering the edge cases in production.
- Write a Salesforce validation ruleLongStopping bad data at entry without blocking every legitimate edge case.
- Design the field before anyone creates itLongA request for a new CRM field, which is easy to add and very hard to remove.
- Write the lead routing rulesLongDeciding who gets which lead, including the cases nobody thought about.
- Define lifecycle stages that mean somethingLongWhen MQL and SQL are used differently by marketing and sales, and handovers keep failing.
- Audit these automations for conflictsLongA CRM where several workflows have accumulated and something keeps overwriting a field.
- Document how this CRM is actually set upLongAn inherited CRM whose logic lives only in the head of someone who left.
- Plan a migration between CRMsLongMoving from one CRM to another without losing history or trust.
- Review who can see and change whatLongBefore an audit, or after realising everyone has been an admin for two years.
- Design a Salesforce Flow before building itLongA Salesforce automation request, worked out on paper before you discover the limits in production.
- Turn these profiles into permission setsLongA Salesforce org where access lives in profiles and every new role means cloning another one.
- Find the accumulated debt in this Salesforce orgLongAn org that has been configured by many hands over several years.
Got one that isn't here?
Send a prompt you keep coming back to. A person reads every one.
Suggest a prompt