CRM & sales ops21 categories
Design the field before anyone creates it
A request for a new CRM field, which is easy to add and very hard to remove.
Someone has asked for a new field. Work out what it should actually be. Cover: the question it answers, the correct type (and why not text), whether a picklist with fixed values beats free entry, which object it belongs on, who fills it and when, whether it is required, and what reports depend on it. Then challenge it: does an existing field already carry this, would a tag or a note do, and what happens if it is left empty on 80% of records. Recommend for or against creating it. Request:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Automation and admin. Workflows, validation, field design and the documentation nobody wrote at the time.
Related prompts
Design this HubSpot workflowAutomating something in HubSpot without discovering the edge cases in production.Write a Salesforce validation ruleStopping bad data at entry without blocking every legitimate edge case.Write the lead routing rulesDeciding who gets which lead, including the cases nobody thought about.Define lifecycle stages that mean somethingWhen MQL and SQL are used differently by marketing and sales, and handovers keep failing.Audit these automations for conflictsA CRM where several workflows have accumulated and something keeps overwriting a field.Document how this CRM is actually set upAn inherited CRM whose logic lives only in the head of someone who left.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free