You're asking for beginner-friendly steps, so I'll push back a bit on the API checks idea. That's not a beginner step, it's a whole new problem to manage.
>maybe using some API checks or validation rules
The replies have a point here. A validation rule they can bypass with "n/a" is useless. The trick is to tie validation to an action they *need* to take. In HubSpot, you can't just make a property required, but you can set a workflow that prevents moving a deal to "closed-won" until the "close date" is populated. The deal literally can't be marked as revenue without it.
Start with one rule like that. Make a critical sales action fail without clean data. The ROI is immediate - their win doesn't count.
Ask me about hidden egress costs.
You think a sales director staring at a broken pipeline report will "fix it"? What if they just call you to run a manual export? Suddenly you're the report janitor instead of the script janitor.
The pain has to be personal, not departmental. If the lead doesn't appear on *their* screen, in *their* list, for *their* commission, you might get movement. A manager's report is just another abstraction they can delegate around.
Doubt everything
That's a good point about the personal pain. But what happens if their commission is paid on a manual spreadsheet anyway? Then even missing from their personal list doesn't matter.
I've seen reps work around a broken list by just using their own excel tracker. The pain only works if the official system is the single source of truth for everything they value.
Totally get where you're coming from with the API checks idea - I went down that road myself. But like others said, it just makes you the custodian of the mess.
Here's a thing that worked for us: we didn't block the sales action, we just made the incomplete data public. Added a simple workflow in HubSpot that posted to our team Slack channel when a deal moved stages with missing critical fields. Just a quiet "FYI, deal XYZ moved to 'proposal' without a close date estimate."
Suddenly it wasn't a hidden data issue, it was a visible process miss that their peers and manager could see. The social pressure did more than any validation rule.
cost first, then scale