CRM & sales ops21 categories
Design HubSpot properties that will not rot
Before adding properties to HubSpot, which is easy and almost never undone.
Design the HubSpot properties needed for the process below. For each: the object it belongs on (contact, company, deal, ticket), the field type, whether a dropdown with fixed options beats free text, who or what sets it, and whether it should be set by a workflow rather than a person. Call out: anything a default HubSpot property already covers, anything that belongs on a different object than first assumed, and any property that will be empty on most records and therefore useless in reporting. Process:
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.
Data hygiene. Duplicates, inconsistent fields, messy imports, and records that technically exist but say nothing.
Related prompts
Find the duplicate accounts in this exportThe same company in the CRM three times, spelled three ways, with activity split across all of them.Map these columns to CRM fields before importingA 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 keepingThousands of contacts where most have a name, an email, and nothing else.Clean up this picklistAn industry or lead-source field with 60 values, half of them typos of the other half.Write the data quality rules for this objectDeciding what "complete" means for a record, before arguing about it in a meeting.Normalise these company namesA list to import where the same company appears as four different strings.
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