Sales approval workflow design · Sales
Your salespeople promise things to buyers that nobody approved.
A dealer asks for a lower rate, thirty days of credit and a changed specification, all in one call. The salesperson says yes to keep the order warm. Finance learns about the credit when the invoice is already raised.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.
In one paragraph
Sales approval workflow design decides who may agree what before an offer reaches the buyer: discounts, credit, special terms, custom specifications and large orders. GullySales writes the routes, the request format and the exceptions record with you, then sets them up in your CRM or on WhatsApp.
This service settles the question before the call happens. For each kind of request, your owner decides who approves it, who stands in, and what the approver must see to decide. The limits themselves are yours; GullySales does not set them.
Running approvals for you is a different job and sits with deal desk services. Discount policy sits with sales discount management, and the tools that carry the routes sit with sales workflow automation. This page is the design of the routes.
Who it is for
This is written for you if these sound familiar.
- Manufacturers and distributors whose quotes carry discount, credit and delivery terms
- Equipment and vehicle dealers where each salesperson bargains differently
- Software and service firms that agree custom scope during the sale
- Real estate sales teams handling price holds and payment-plan requests
- Schools, clinics and shops with package or fee concessions that staff grant informally
Not for
It is not the right fit if.
- You decide every price and term yourself and always will. A short written note to your team is enough.
- You need an outside party to approve on your behalf. The people who carry the commercial risk must approve.
- You have no agreed price list or credit practice yet. Settle those first; the routes need something to refer to.
The problem
Does this sound like your business?
Common situations this work addresses.
“I find out about the concession after the order”
Credit, free delivery or a changed specification was agreed on a call. The approver sees it only on the invoice or the dispatch note.
“Every request comes to me”
Small and large requests land in the same WhatsApp chat. The owner becomes the queue, and requests wait while the buyer cools.
“Approvers change the answer later”
A yes given in a voice note is disputed a month on. No record shows what was asked, what was approved and on what condition.
“The approver was travelling”
The route stops at one person. Nobody holds authority in their absence, so reps either wait or decide alone.
What we do
The work we can include.
Each deliverable and the purpose it serves. Your written scope confirms what is included, who is responsible, and what it costs.
Approval route map
One page lists each request type, such as discount, credit, special terms, custom specification and large order. It names the approver, the stand-in and the next level up.
Approval limits sheet
Your owner writes the limits per role. The sheet records the date set and the person who signed it, so a later change is visible.
Request form
A short form or CRM screen carries the buyer, quote reference, what is asked, the reason and the margin your finance lead supplies. An approver can decide without a second question.
Response expectation note
You set how quickly each type should be answered. The note says what the rep tells the buyer while waiting and what happens when the approver is silent.
Exceptions record
A sheet or CRM list logs each approval or refusal with the date, approver, condition and quote version. Repeat exceptions show where a limit needs revisiting.
CRM or WhatsApp set-up
The routes are built into the approval feature of your CRM, such as Zoho CRM or HubSpot where your plan includes it. Where the team lives on WhatsApp, a structured request message and a named group carry the same steps.
Rep and approver guide
A one-page guide shows how to ask, how to answer and how to record. It includes what never leaves the team without a written yes.
How the result is measured
- Requests raised, by type
- Time from a complete request to a recorded answer
- Requests returned as incomplete
- Approvals and refusals by approver
- Offers sent that match an approved request
- Repeat exceptions by customer and request type
Recorded as a baseline before work starts, so every later report has an honest comparison.
Before you decide
Agree the work. Know how to judge it.
Sales approval workflow design: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Draw the current handover from trigger to final action. Mark where information is missing and who handles exceptions when the normal path fails.
Make the scope clear
Agree the systems, permissions, triggers, and actions in scope. Specify what remains manual, how a failed run is noticed, and who can pause or change the workflow.
Check the work in use
Test a successful case, a duplicate, a missing field, and a failed connection. Confirm that records and messages are not created twice and that a person can recover the work.
Know when to change course
If the team cannot agree the manual rule, do not automate it yet. Resolve ownership and exceptions first so the system does not repeat a bad decision faster.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
How it works
How the work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Collect recent requests
You share a few recent quotes where a concession was asked, with the chat or email that settled it. We list who decided, how long it took and what was lost on the way.
- 2
Owner sets the limits
Your owner and finance lead decide which requests need approval and at what level. We write down their decisions and do not propose the numbers.
- 3
Draft routes and forms
We draw the route map, the request form and the exceptions record. Your sales head tests them against the recent requests from step one.
- 4
Set up in the tool
Routes are built in your CRM or as a WhatsApp format, after we check what your current plan supports. A route that needs a higher plan comes back to you as a decision.
- 5
Run with live requests
A few reps and approvers use the routes on real quotes. We note where requests arrive incomplete or stall, and adjust the form and the stand-ins.
- 6
Hand over
A named person in your team owns the limits sheet and the record. Changes to a limit go through the owner and are dated.
Before you hire anyone
Do this first yourself.
Gather what is already happening informally, so the routes describe your business and not a template.
- List the last ten quotes where a buyer asked for a concession, and note who actually agreed to each.
- Write down each kind of request your team receives: discount, credit, special terms, custom specification, large order.
- For each kind, name one approver and one stand-in who can say yes while the first is away.
- Write the limit each role may agree alone, in your own figures, and sign and date the page.
- Choose where requests will be raised and answered, either one CRM screen or one named WhatsApp group.
- Open a sheet to log every approval or refusal with the date, approver and condition.
Judge any provider
What to ask any provider of this service.
Useful whoever you choose, including us.
- Who sets the approval limits, and will you propose figures or write down ours?
- What does your request form carry, and can an approver decide from it without asking again?
- What does the route do when the approver is away or silent?
- Which approval features does our current CRM plan include, and what would need an upgrade?
- How will each decision be recorded against the quote version it applied to?
- Where does your work stop and our finance lead or legal adviser take over?
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 5, objections and negotiation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Will every discount need approval?
Do you decide the discount limits?
Is this the same as deal desk services?
Can approvals happen on WhatsApp?
Does it cover credit and contract terms?
What does it cost and how long does it take?
Who will actually do the work?
What do you need from us?
What if we are not happy with the work?
By industry
Sales approval workflow design, written for your industry.
Related services
Often bought with this, or instead of it.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.