Approvals without the bottleneck
Some deals need a manager's yes before they move on. Approval Processes put that yes inside the CRM, with rules, notifications and a record that waits.
The problem
Discounts and large deals needed sign-off, but the sign-off happened outside the CRM. Nobody could see what was waiting, for whom, or why a deal had stopped.
What it does
A visual builder. Admins draw the approval flow: steps, the conditions that start it, and who approves each step.
The right people are told. When a deal meets the conditions, approvers get a notification and everyone can see who needs to respond.
The record waits. A deal under approval is locked, with a clear banner, until it is approved.
Design decisions
Lock with a reason, not just a lock
A locked record says why it is locked and who it is waiting for, so nobody guesses.
A flow you can read at a glance
The builder shows the whole path, with approve and reject branches, so admins see the process before they switch it on.
In the product
What it taught me
A rule people cannot see feels like a wall. Show the rule, and it becomes a process.
Next case study