Permissions, data and numbers you can defend
For the person who has to answer “where did that number come from?”
The problem
RevOps owns the definitions, the access model and the numbers. When those live across five tools with five interpretations of “meeting booked”, reconciliation becomes the job.
How Leadey solves it
How it works in practice
One system of record, so a meeting is a meeting. Twelve permission modules with scope axes for a real access model. The API returns exactly what the dashboard shows, because they share the same code. Sit rate excludes un-dispositioned meetings and tells you how many there were, so you can defend it.
Frequently asked questions
Can I define custom roles?
Yes, unlimited, plus per-person overrides.
Does the API match the UI?
Yes, by design, shared metric libraries.
Can I export everything?
Yes, CSV with all custom fields plus full API read access.