Skip to content
GullySales

B2B SaaS startups · Sales approval workflow design

Decide who may approve a discount, a pilot or a custom term before the quote goes out.

Sales approval workflow design for a B2B SaaS startup decides who may agree what before an offer reaches the buyer: discounts, pilot terms, annual prepayment, custom integrations and security or contract changes. GullySales writes the routes, the request format and the exceptions record with you, then sets them up in your CRM or on WhatsApp.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A sales analyst and approving manager review a quotation exception

What sales approval workflow design means

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.

Last updated 14 Nov 2026.

For B2B SaaS startups

Where it usually goes wrong, and what we would do.

  • “Every discount is settled in a founder's chat thread”

    A rep asks on WhatsApp whether a customer can have a lower rate for paying a year ahead. The founder answers from a phone, the answer is not recorded, and the next rep asks the same question for a similar account and hears something else.

  • “Pilots and free extensions have no owner”

    A buyer asks for a longer trial, a paid pilot or free onboarding. Each is a concession with a cost to your team's time, yet no one is named to say yes. Without a route, pilots are granted by whoever replies first and are hard to close later.

  • “Custom work gets promised before engineering is asked”

    A prospect wants a custom report, a single sign-on setup or an integration with a billing tool. A rep says it is possible to keep the deal moving, and engineering hears about it after signing. The route should put an engineering view before the offer, not after.

  • “Contract and data terms need a person with authority”

    A buyer's legal team returns edits to your terms or asks for data-protection wording. A rep has no route, so edits sit in an inbox. The workflow names who reviews them and sends legal questions to your own adviser, so the buyer hears from one person.

What we do

What we deliver for B2B SaaS startups.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Approval route map

    One page listing each request type, such as discount, pilot, prepayment term, custom build and contract change. It names the approver, the stand-in and the next level up.

    Result: A rep knows whom to ask for each kind of request.

  2. Limits sheet signed by the founder

    The founder writes the limits per role and per request type. The sheet records the date set and the person who signed it, so a later change is visible. We write down your decisions and do not propose the figures.

    Result: A limit can be traced to a date and a signature.

  3. Request form with the facts an approver needs

    A short form or CRM screen carrying the account, plan, quote reference, what is asked, the reason and the margin figure your finance lead supplies. The approver can decide without a second question.

    Result: Requests arrive complete enough to decide in one reading.

  4. Engineering check for custom work

    A step in the route where a named engineer states whether a custom request is feasible and what it costs in team time before an offer is made.

    Result: No custom promise reaches a buyer without a recorded engineering view.

  5. Exceptions record

    A sheet or CRM list logging each approval or refusal with the date, approver, condition and quote version. Repeat exceptions show where a limit or a plan needs rethinking.

    Result: You can see which concessions repeat across accounts.

  6. CRM or WhatsApp set-up

    The routes are built into your CRM's approval feature where your current plan includes one. Where the team lives on WhatsApp, a structured request message and a named group carry the same steps.

    Result: The route runs in the tool your team already opens.

How the result is measured

  • Requests raised, by type
  • Time from a complete request to a recorded answer
  • Requests returned as incomplete

Recorded as a baseline before work starts, so every later report has an honest comparison.

Who it is for

This is written for these B2B SaaS startups.

  • Early-stage SaaS selling to Indian SMEs and mid-market firms
  • Vertical SaaS for one trade, such as clinics, schools, dealers or builders
  • Developer tools and APIs sold to engineering teams
  • HR, payroll and compliance software for growing companies
  • Finance and accounting tools sold through CA firms
  • Indian-built SaaS selling to buyers in the US, UK or Middle East
  • Spin-offs from services firms that turned an internal tool into a product
  • Bootstrapped founders who have not raised and cannot hire a sales team yet

Before you decide

Agree the work. Know how to judge it.

Sales approval workflow design for B2B SaaS startups: 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.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from B2B SaaS startups. Anything missing is noted in the written scope, with who will supply it.

A record of recent discount requests
The messages or notes where discounts and exceptions were agreed recently. Chat threads count. Without them the limits sheet is written in the abstract, and the founder's real habits stay out of the discussion. Include requests for pilots and extensions, since those are the ones with no owner today. Dates and the names of who agreed help us trace the routes.
The founder's time for the limits session
A block of the founder's time to decide what the team may approve alone. This cannot be delegated. Without it, the workflow has routes and no limits, and every request still arrives in the founder's chat. Put it in the diary as a decision session, not a catch-up. Prepare by listing which approvals you resent giving, since those are the ones to hand over.
Your standard contract and order form
The contract, order form and any data terms you send buyers today. A lawyer or adviser may hold them. Without them, we cannot mark which edits need a person with authority, and contract changes continue to be agreed informally. Any template with data terms, such as a data processing agreement, is useful. Your adviser should confirm which clauses need a person with authority.
An engineering contact for custom requests
The engineer or product lead who is asked about custom work, available to answer the check. Without a named person, custom work is promised before engineering is asked, and the workflow only records the promise. Say also who answers if that engineer is away, since custom promises are made in the gaps. Short answers on effort and risk are enough for the first routes.
The tool where requests will live
The CRM, ticket tool or messaging group where your team will raise requests, and someone who can configure it. Without a decision, the routes stay on paper and the team continues to use whichever chat is open. If your team works in a messaging group, say which one. The routes copy what people already use, because a new place is skipped.

How it works

How the sales approval workflow design 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. 1

    Collect the last requests for approval

    We ask you for the recent requests that went to the founder: discounts, free extensions, custom features, contract changes. We read how each was settled and by whom. You tell us which ones you regret. These cases show what the workflow must handle. We also note the requests that the team did not bring to you because they guessed the answer.

  2. 2

    Sit with the owner to set limits

    We bring the cases to the founder and ask what the team could have agreed alone and what needed a decision from above. The founder signs the limits sheet. We keep the limits in your terms and do not suggest numbers of our own. The sheet is kept in your terms and signed by the founder, with a deputy named for absences.

  3. 3

    Draw the routes and write the request form

    We draw the route a request follows for each type and write a short form of the facts an approver needs: buyer, plan, what is asked, the reason and the alternative. You edit the form. A request with missing facts is sent back at once. Requests are sorted by type, so a discount form differs from a request for an extension.

  4. 4

    Ask engineering about custom work

    We write a check that sends any request for custom work to an engineer before a promise is made, with space for their answer on effort and risk. Your engineering lead agrees to the check. Sales stops quoting dates it has not asked about. Engineering answers in a line or two about effort and risk, and the answer is attached to the request.

  5. 5

    Set it up in your CRM or chat

    We build the routes in your CRM or in a WhatsApp group with a fixed format, whichever you actually use. Everyone tries it on a made-up request. Approvals land in one place, and the exceptions record starts to fill. A request that does not arrive in the format is returned with a note, and routes carry the name of the approver.

  6. 6

    Run live requests, then hand over

    The team uses the workflow on real requests while we watch for requests that go around it. After several cases we compare the exceptions record with the cases collected at the start, you decide which limits to change, and the log is handed to a named reader. Requests that skipped the route are listed, with the reason given by the person who skipped it.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. 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.

  2. 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.

  3. 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.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Will you set our discount limits?
No. The founder and finance lead decide which requests need approval and at what level. We record the decisions, build the route and keep the sheet dated. People who carry the commercial risk must be the ones who approve.
We use rupee quotes for India and dollar quotes abroad. Does that matter?
It can mean separate routes, as the margin, tax display and payment terms differ. Tell us at the start which markets you quote in, and we draw the routes to match.
Who reviews a buyer's edits to our contract?
Your own legal adviser. The workflow only decides who receives the edits inside your team, who sends them on, and what the rep tells the buyer in the meantime.
Who approves when the founder is travelling?
A named deputy, written on the limits sheet, with the same form and the same record. If nobody is named, the request waits, and the sheet says what the buyer is told to expect. We would sooner see a deal wait than see a promise made in a chat that nobody can find later. The founder reviews the deputy's approvals on return and may change the limits. The deputy's name is shared with the team and with the person who raises the request, so nobody has to ask the founder who covers.
What counts as an exception worth logging?
Any offer outside the limits sheet: a discount beyond the salesperson's limit, a longer trial, a custom feature, a change to contract terms. Each line records who asked, who agreed, what was given and why. The log is short on purpose. If the same exception appears repeatedly, the owner decides whether to change the limit or stop granting it, and the decision is written next to the entry. The reader of the log asks about any exception that was not recorded at the time. This is a record, not a punishment.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

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.