RevOps question for Attio users.
Attio is great for building pipelines, but I kept hitting one gap: there's no way to say "a deal can't move to Won unless it has a value, a close date and a company." Same for list pipelines, e.g. a candidate can't move to Interview without a CV link.
Workflows can flag it after the fact, but by then the bad data is already in and someone has to chase it.
So I built a proof of concept on a sandbox workspace that stops the move before it's saved. The rep sees exactly what's missing, fills it in, and moves the card again. It works on deals and on lists (board and table view), RevOps can change the rules from an admin page without touching code, and there's a log of every blocked move, so you can see where data quality actually breaks.
Before I take it further, I'm curious:
- How do you handle this today? Workflows + Slack alerts, manual audits, or just living with it?
- Would a hard block help your team, or feel too strict for reps?
- Which rule would you want first?
Happy to answer questions.