Lead-to-order process design · Sales
Every enquiry has a path to a confirmed order, and someone owns each step.
The buyer says yes on a call. Then the quotation waits for a discount approval, the purchase order arrives on someone's personal WhatsApp, and accounts asks for a proforma invoice before it will release the advance. The deal has not stalled with the buyer. It has stalled between your own desks.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.
In one paragraph
Lead-to-order process design draws the whole path from first enquiry to confirmed order: the stages, who owns each one, the record each leaves behind and the documents that pass between buyer and seller. GullySales maps how your orders really get confirmed, redesigns the hand-offs and builds the path into a document set and your CRM or shared sheet.
We draw the path as it runs today, from the first enquiry to the order confirmation the buyer receives. Each step gets an owner, the record it must leave and the document that goes out.
This page covers the full path end to end. The wider selling method belongs to sales process design and implementation, the desk that keys the order belongs to order booking process improvement, and the weekly stage review belongs to pipeline management.
Who it is for
This is written for you if these sound familiar.
- Manufacturers whose quotations need a price, discount or technical sign-off before they can go out
- Dealers and distributors who take advances against a proforma invoice before supplying
- Interior studios and builders who confirm an order only after a signed quotation and a first payment
- Owners who hear "the order is confirmed" from sales and "we have nothing in writing" from accounts
Not for
It is not the right fit if.
- You close small orders at the counter or on one phone call. A written path for that would be heavier than the sale itself.
- Your path is sound and the trouble is too few enquiries. Marketing or lead generation is the better first step.
- You want us to issue invoices or take payments. Your own accounts team and tax adviser do that.
The problem
Does this sound like your business?
Common situations this work addresses.
“The buyer agreed, but we still have no order”
Agreement on a call is not an order. Without a confirmation point, the deal waits until someone asks for the purchase order.
“The quotation waits on someone's desk”
Margin, credit or technical approval is asked for over chat and answered whenever. The quotation records nobody's name against the decision.
“Accounts books something different from what sales promised”
The order is typed again from a message or a screenshot. A discount, a delivery term or an address changes on the way.
“We chase the advance for weeks”
The buyer's accounts team wants a proforma invoice and sales has not sent one. Nobody knows whose job that is.
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.
Path map
One page showing every stage from enquiry to order confirmation, drawn from your recent won, lost and stuck deals. Your sales head and accounts lead mark where it differs from daily practice.
Stage and owner sheet
For each stage, the person who owns it, the record that proves it is done, and the person who receives the deal next. A quotation stage, for example, names who prices it and who approves a discount.
Document set
The quotation, proforma invoice, advance receipt and order confirmation, with the fields each carries. Whether you need the buyer's purchase order or a signed quotation in its place is decided deal type by deal type.
Numbering and linking rules
Each document quotes the number of the one before it, so a purchase order points to its quotation and the confirmation points to both. A stray advance can then be matched to a deal.
Approval rules
Written limits on who may approve a discount, special terms or credit, and where that approval is recorded. Approval by message is kept, with the date, against the deal.
CRM or sheet setup
Stages, required fields and document links built into your CRM, or a shared sheet where that is what you use, tested on real deals.
Stall log
A record of where each deal waited and why, kept by the stage owner. It shows whether delay sits with the buyer or inside your own approvals.
How the result is measured
- Orders confirmed in writing, separate from verbal agreement
- Quotations waiting on internal approval, by approver
- Advances received against proforma invoices issued
- Orders booked that match the quotation and purchase order
- Deals waiting at each stage, with the reason logged
- Enquiries traced from first contact to a confirmed order
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.
Lead-to-order process design: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
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 lead-to-order process 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
Requirements and scope
You send the requirements brief and we talk through your products, buyers and order types. Scope, fee and term follow in writing.
- 2
Tracing recent deals
We follow a sample of confirmed, lost and stalled deals through the people and papers that handled them. You confirm the traced path matches what happened.
- 3
Redesigning the path
We settle the stages, owners, approvals and documents. Your sales head and accounts lead approve the design together.
- 4
Building the documents and records
Templates, checklists and the CRM or sheet fields are prepared from the approved design. Your team tests them against deals already in progress.
- 5
Rollout with live deals
Your team moves current orders through the new path with us alongside, so unclear rules get fixed while a real deal depends on them.
- 6
Review of the stall log
We read the stall log with your sales head and adjust approvals or hand-offs that still hold deals up. Day-to-day ownership then sits with your named process owner.
Before you hire anyone
Do this first yourself.
Trace three recent orders from the first enquiry to the order confirmation and note every wait.
- Pick one order that was confirmed, one that was lost and one that is still stuck after a quotation.
- For each, list every person and every document it passed through, with the date each one moved.
- Mark each wait as the buyer's or your own, such as a discount approval or a missing proforma invoice.
- Check whether the order booked in accounts matches the quotation and the purchase order line by line.
- Write down who, on the day, was meant to hold the deal at each stage, and note where nobody was.
Judge any provider
What to ask any provider of this service.
Useful whoever you choose, including us.
- Will you trace our own recent deals before designing anything, or start from a template?
- Which documents will the path define, and who sends each one?
- How will approvals for discounts and special terms be recorded against a deal?
- What must accounts receive before an order is booked, and who can refuse an incomplete one?
- Where does your work stop, and which parts stay with our accounts team and tax adviser?
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 6, closing. 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.
Is a proforma invoice the same as a quotation?
Do I always need a purchase order from the buyer?
Is this different from sales process design?
Will this change how we book orders in accounts?
How long will it take and what will it cost?
How long is the contract?
Who will actually do the work?
What do you need from us?
What if we are not happy with the work?
By industry
Lead-to-order process 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.