Skip to content
GullySales

Granite, marble and stone processors · Sales approval workflow design

Your salespeople promise things to buyers that nobody approved.

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.

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

A supervisor shows granite and marble slabs to an architect

Start with the buying decision

Which record or handover breaks between the enquiry and its outcome?

Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief.

Your team approves the scope and any commitments to buyers. GullySales does not assume authority over pricing, staffing, or delivery promises unless a specific responsibility is agreed in writing.

The context for Granite, marble and stone processors

Start with the decisions in your own enquiry records.

Trace a real enquiry across the people and systems involved. Record missing information, duplicate work, and the decision that is still waiting for an owner.

How people choose in this industry

A buyer chooses stone on the look first and the supplier second. An architect or an interior designer shortlists a few materials from a sample board, a catalogue or a showroom visit, and the client signs off on the stone itself. Builders and contractors compare rates and delivery. Dealers and exporters ask about the block source, the finish, the packing and the container loading.

Trust comes from seeing the real lot. A buyer who has been told 'Makrana' or 'Tropical Green' by three suppliers needs the slab photographs, the thickness, the finish and the lot number, ideally a visit to the yard. Samples, a clear price basis (per square foot, per slab or per tonne) and a delivery plan do most of the selling.

The calendar matters. Building activity rises after the monsoon and before the year-end, wedding and festival months bring interior orders, and export buyers plan around trade fairs and shipping slots. A processor in Kishangarh, Jaipur, Tumkur, Madurai or Ongole has the same customers as the next one, so the one with a record of every enquiry is the one that follows up.

The decision before implementation

Define the process and access permissions before changing software settings or adding automation.

Existing industry priorities to review

  • Architect and interior designer sample library
  • Builder and contractor project supply
  • Dealer and showroom supply
  • Export enquiries and sample shipments
  • Kitchen countertop and vanity work for homes

These describe the industry's wider priorities. The written scope identifies which this service will address.

Industry application review

Test the service against a problem in your own records.

These review scenarios connect the industry context to a possible output and a checkable next step. They are scope questions, not client results or a promise that every industry problem belongs in this engagement.

Quotations are written by hand and nobody follows them up

A quotation goes out for a large project, the salesman moves on to the next call, and the order is decided by somebody else.

Output to assess: Approval route map

Review whether “Approval route map” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Walk the selected record through the proposed steps. Identify who acts at each handover, what information they receive, and how an exception is assigned without inventing a missing step.

Our website is a catalogue with no way to ask

The page lists stones and photographs but has no form, no WhatsApp button and no sample request, so visitors leave.

Output to assess: Approval route map

Review whether “Approval route map” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Walk the selected record through the proposed steps. Identify who acts at each handover, what information they receive, and how an exception is assigned without inventing a missing step.

The problem

What sales approval workflow design is meant to address.

  • “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.

Who it is for

Check your operating model against the scope.

  • 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

Before you decide

When this may not be the right fit.

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

What we do

Agree the outputs before work begins.

These are the sales approval workflow design deliverables available for granite, marble and stone processors. Your written scope identifies the included work and responsibilities.

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

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

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

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

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

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

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

Industry baseline

Keep the industry's wider measures beside the service measures.

Use the existing baseline to understand the context. These figures are not all targets for this engagement, and a change must not be attributed to the service without evidence.

  • Enquiries by source and by stone
  • Quotations sent and quotations followed up
  • Orders won and reasons for losing
  • Sample requests and yard visits
  • Architect, dealer and export enquiries
  • Repeat orders from contractors and dealers

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

Deal desk services
Choose deal desk services when non-standard pricing and credit decisions need a standing function, an approval matrix and quote templates built around your margins. Choose sales approval workflow design when you need the routes, request format and tool set-up for approvals of every kind, not only pricing.
Sales discount management
Choose sales discount management when the problem is discounting by habit and you want give-and-get rules and a discount register. Choose sales approval workflow design when discounts are one of several requests, alongside credit, special terms and custom specifications, that need a defined route.
Sales workflow automation
Choose sales workflow automation when repeat manual steps should be replaced by rules that create tasks or update records. Choose sales approval workflow design when the open question is who is allowed to agree what, which must be decided before any rule is automated.

A sample of the output

An approval limits sheet states who may agree each kind of request, and what must accompany it.

This sheet is for a machinery distributor. Each row is a request type, the person who may approve it, what the request must include, and what happens when that person is away.

Illustrative example, not client data. Yours is built from your own records.
Request typeApproverMust accompany the requestIf approver is away
Discount on a standard itemSales managerBuyer name, item, reason, what the buyer gives backOwner approves, or the offer waits
Extended credit termsOwnerBuyer's payment history and the order valueFinance lead gives a view, owner decides
Custom specificationTechnical leadDrawing or description and a note on stock or lead itemsSales manager holds the buyer until the lead returns
Large orderOwnerStock position, delivery plan and payment termsOffer is held; no verbal commitment is made
Special warranty wordingOwnerThe exact wording the buyer asked forStandard wording is sent instead

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

A list of recent approval requests
The routes are drawn from what your team actually asks for, such as discounts, credit and special specifications. A recent set from messages or email is enough. Without it, the routes cover guessed cases and miss the awkward ones.
The owner's decision on limits
Only you can say who may agree what, and up to which level. A first view is acceptable and can be refined. If the limits are left open, the routes are drawn but nobody can say where an approval ends.
Names for each approver and a stand-in
An approval route fails when its approver is away. Each role needs a named person and a named alternate. Without alternates, requests stall and your team goes back to asking whoever answers first.
Access to the CRM or WhatsApp group
The routes are built where requests are made, so admin rights to the CRM or a controlled WhatsApp set-up are needed. If access is limited, the sheet and forms are delivered and set-up is left with your team.
A statement of what is never approved
Some terms, such as certain credit or wording, may be off the table. State them plainly. If they are not stated, the sheet may route a request to an approver who would never agree, and time is lost.

How it works

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

Approval and acceptance

Use an observable check before accepting an output.

These are proposed review checks for the named outputs. Agree the final conditions in the written scope, then record any missing requirement before accepting the handover.

  • Approval route map

    Walk the selected record through the proposed steps. Identify who acts at each handover, what information they receive, and how an exception is assigned without inventing a missing step.

  • Approval limits sheet

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Request form

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Response expectation note

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Exceptions record

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • CRM or WhatsApp set-up

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • Rep and approver guide

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How is sales approval workflow design scoped for granite, marble and stone processors?
Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief. Define the process and access permissions before changing software settings or adding automation.
Will every discount need approval?
No. Requests inside the limits your owner sets stay with the rep. Only requests outside them reach an approver, so ordinary quotes do not wait.
Do you decide the discount limits?
No. Your owner and finance lead set them, and finance confirms the margin basis. Policy on how discounts are structured is the subject of sales discount management.
Is this the same as deal desk services?
No. This page designs the routes and records for your team to run. Deal desk services is the better fit when you want the approval step run as a service.
Can approvals happen on WhatsApp?
Yes, as a structured request message in a named group, with the answer copied to the exceptions record. A CRM keeps the record more reliably, so we say which suits your team.
Does it cover credit and contract terms?
It routes the request and records the decision. Credit policy is for your finance lead, and contract wording is for your own legal adviser.

Continue your review

Compare the service scope and the related work.

The scope, responsibilities, fee, reporting frequency, and term are agreed in writing after the requirements brief and conversation. Tell us what you need.

Your brief

Tell us what you need, and we will read it before we call.

Eight short steps about your business, what you want and who decides. Most questions are a tap, and you can skip any you would rather answer on the call.