A Second Set of Eyes Before a Proposal Goes Out
As your team grows, more people are building proposals. A wrong price, a missing service, or a discount nobody agreed to only has to reach one client to cost you.
With approval workflow, reps with the Creator role request approval before they can send. Your approvers get an email, review the proposal, and approve it or decline it with a note. Nothing goes to a client until someone you trust says yes.
Request, Review, Send
A simple hand-off between the person building the proposal and the person who signs off on it.
Turn It On
In Settings, turn on Approval Workflow and choose who can approve: all of your Admins, or specific people you pick.
A Rep Requests Approval
When a Creator finishes a proposal, they click Request Approval and add a note if they want. Your approvers get an email.
Approve or Decline
Approvers review the proposal and click Approve or Decline. A decline includes a note, so the rep knows exactly what to fix.
The Rep Sends It
Approval does not send anything on its own. It unlocks sending, so the rep can send the proposal when the timing is right.
One Button to Ask for a Review
When approval is on, a bar on the Creator's proposal tells them a review is needed. They click Request Approval, add a note if they want, and your approvers are emailed.
While they wait, they can send a reminder or cancel the request to keep editing. The proposal stays locked until someone decides, so it cannot change mid-review.
Every Request in One Place
Approvers get an email for each request, plus an Approval(s) Needed list at the top of their proposals, oldest first, with who built it and when they asked.
Open the proposal, read the rep's note, and click Approve or Decline. A decline includes a note, so the rep knows exactly what to change.
Oversight for New Reps. No Extra Steps for Everyone Else.
Approval workflow uses the roles you already have, so it only applies where you need it.
Ask before they send
Creators build proposals as usual. Before one of their proposals can reach a client, it needs an approval.
- Request approval with an optional note
- Get a reason when a proposal is declined
- Send once it is approved
Review and sign off
Choose all of your Admins, or pick specific Admins and Editors. They are emailed when a request comes in.
- Approve or decline right on the proposal
- See every waiting request at the top of your proposals
- Add a note either way
Keep moving
Experienced team members send without asking. Approval only applies to Creators, so your senior people are never slowed down.
- No approval needed to send
- Can send a proposal that is waiting for review
- Nothing changes until an admin turns it on
Control Without the Bottleneck
Reviews happen inside the proposal, not over email threads and screenshots.
Nothing Slips Out Early
Until a Creator’s proposal is approved, they cannot send it, start signing, mark it as sent, or share a trackable link.
What You Approved Is What Goes Out
If the proposal is edited after it is approved, the approval clears and it goes back for review. No quiet changes after sign-off.
Frozen While in Review
While a request is waiting, the proposal is locked for the Creator, so approvers review a proposal that is not changing under them.
Approvers Never Miss a Request
Approvers get an email for every request, a count next to Proposals in the sidebar, and an Approval(s) Needed list at the top of their proposals.
Reminders in One Click
Waiting on a busy manager? The Creator can send a reminder straight from the proposal instead of chasing them in chat.
Works With Version Control
Approval is per version. Once a Creator’s proposal goes out, their changes happen in a new version, and each new version gets its own review.
Want to see approvals with your own team?
Built for Teams That Are Growing
The more people writing proposals, the more a quick review is worth.
Onboarding New Reps
Let a new hire build real proposals from day one while a manager checks their work before it reaches a client.
Protecting Your Pricing
Make sure discounts, scope, and totals match what you are willing to sell before your client ever sees a number.
MSPs With Standard Packages
Keep every managed services quote consistent with your stack and your margins, no matter which rep put it together.
Agencies With Account Managers
Account managers build the proposal. A director signs off on scope and price before it goes to the client.
Approval workflow pairs well with version control and your Library, so proposals start from your standard content and every revision gets reviewed.
Grow the Team Without Losing Control
More people can build proposals, and you still decide what reaches your clients.
Fewer Costly Mistakes
Catch the wrong price, the missing service, or the unapproved discount before your client does.
New Reps Ramp Faster
Every decline comes with a note, so newer team members learn what good looks like on real deals.
Senior People Stay Fast
Only Creators need approval. Editors, Admins, and the Owner send without waiting.
No Review Email Threads
Requests, notes, and decisions live on the proposal, so nobody is digging through chat for a thumbs-up.
Off Until You Want It
Nothing changes for your team until an admin turns it on. Turn it off again any time.
Included With Business
Approval workflow comes with the Business plan, along with version control.
Review Every Proposal Before It Reaches a Client
Approval Workflow FAQ
Common questions about requiring approval before a proposal is sent.
What is approval workflow in Smart Pricing Table?
It requires team members with the Creator role to get approval before a proposal they created can reach a client. They click Request Approval, your approvers get an email, and an approver approves or declines it right on the proposal.
Who has to request approval?
Only Creators, and only on proposals they created. Editors, Admins, and the Owner send without asking, and Viewers stay read-only.
Who can approve a proposal?
You choose. Set it to all of your Admins, or pick specific people. Admins, the Owner, and Editors can be chosen as approvers.
What does a Creator need approval for?
Sending the proposal, starting signing, marking it as sent, and sharing a trackable link. With version control, they also need approval before making their version the one the client sees.
Does approving a proposal send it to the client?
No. Approving lets the Creator send it. They still choose when it goes out.
What happens if a proposal is edited after it is approved?
The approval clears and the Creator has to request approval again, so what goes out is always what was approved.
How does approval workflow work with version control?
Approval is per version. Once a Creator’s proposal has gone to the client, their changes go into a new version, and that new version needs its own approval.
Which plans include approval workflow?
The Business plan, along with version control. It is off until an admin turns it on in Settings, so nothing changes for your team until you are ready.