Approval routing for pricing
Send every discount and non-standard term to the named approver with the deal context attached, instead of leaving it in a reply thread for three days.
No ready-made setup for this job yet.
Describe the job in a sentence, the way you would brief a colleague: when it should happen, what to check, and what to hand you. That sentence is the automation.
The job, and what good looks like.
A discount request goes out at four in the afternoon on a Friday, nobody answers, and the quote either ships Monday at the old price or the deal waits another week. This workflow routes the exception instead of forwarding an email thread. It reads the requested discount or term off the quote, matches it against the approval limits the team has already agreed, and names the one person who can decide at that level. The request arrives with the deal value, the close date, the deadline, and what happens if nobody answers, so the approver can decide from one reading rather than opening three files. An exception above every limit on file goes to whoever owns the exception policy itself, with the reason the deal needs it. Requests left unanswered past the deadline escalate along a path the team set in advance rather than waiting for somebody to notice. A human still decides whether the discount is worth the precedent, and who absorbs it. The workflow moves the request; it does not make the trade.
When it is handled
- No discount sent without an approver
- One approver named per exception
- Deadlines visible to the rep
- An escalation path agreed in advance
Works with tools like
- Salesforce CPQ
- Salesforce
- Clari
- Loopio
You stay in charge.
At every step.
It does the legwork. You decide what reaches a customer.
- Nothing reaches a customer unasked
Replies and follow-ups wait in your drafts until you send them, or until you pre-approve them.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only the CRM and inbox you allow
Each automation reaches only the apps and folders you connect for it.
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Your CRM's workflow rules
Updating fields and assigning records the same way every time.
They can't read a call, research a company or write a follow-up that sounds like you.
Flowchart automation tools
Moving data between apps at high volume.
Every exception becomes another branch someone has to build and maintain.
AI chat assistants
Drafting a reply when you ask for one.
Nothing happens until you come back and ask again, and the routine lives in a chat.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Related workflows.
Contract readiness checklist
Check the legal, security, and procurement items against the buyer's own requirements before the first redline goes out.
Write your own
Proposal assembly checklist
Assemble the pricing, the approved terms, and the proof the buyer asked for into one packet, with each missing piece named before the send.
1 automation
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.