The enquiry-to-order process, explained

What the enquiry-to-order process is

The enquiry-to-order process is the workflow a make-to-order manufacturer runs to turn an incoming enquiry into a confirmed order. In plain terms: a lead is captured and qualified into an enquiry, the enquiry is checked for feasibility and costed against a bill of materials, a quotation is raised and approved, sales chase it until the customer decides, and on a win that quotation converts into a confirmed order that hands off to production and billing. It is the front half of quote-to-cash — everything that happens before the factory starts making anything.

This guide is about the process — the hand-offs, who does what, and what each step produces — rather than the named pipeline stages and their status codes, which the sales pipeline stages guide covers in detail. Here the question is different: as an enquiry moves from the salesperson's inbox to the estimator's desk to the customer and back to the shop floor, what document is being created, who owns it, and what is passed on? Get that chain right and the sale flows; get it wrong and enquiries stall, quote versions get confused, and orders are re-typed by hand.

The document chain: LD → EQ → QT → OA

Every enquiry-to-order journey rides four linked documents. Each has a short code, a clear owner and a defined job, and — crucially — each one references the one before it, so the whole chain can be traced end to end.

Because a QT references its source EQ and an OA references its QT, the enquiry-to-quotation-to-order chain is fully reconstructable. You can stand on a confirmed order and walk backwards to the exact quotation revision that won it and the original enquiry it grew from — the source, the drawings, the first price and every change since. That linkage is the whole point: nothing is re-keyed on conversion. When a quote is won, the order is generated from it, inheriting the same item lines, quantities and agreed rates rather than being typed afresh into a separate system.

The six steps, and what each one produces

Here is the whole workflow, step by step. Each step has an owner, an input it receives and a concrete output it produces for the next desk.

1. Capture and qualify the lead. The process begins before there is even an enquiry — with a raw lead (LD), often captured on a mobile form at an exhibition or a site visit. Qualification decides whether the prospect has a real, quotable need. Produces: a qualified lead ready to become an enquiry, with its source recorded so you later know which channel it came from.

2. Log the enquiry. A qualified request for a quote becomes an enquiry (EQ) — a document carrying the customer, the enquired items and quantities, any drawings, and the source it arrived from. This is the first structured record of the deal, and everything downstream references it. Produces: an EQ with all the technical and commercial context an estimator needs, so nobody has to email around chasing the drawing again.

3. Assess feasibility. Before anyone spends effort on a price, sales and engineering ask a simple question: can we make this, and do we want to? Feasibility filters out enquiries that are not a fit, so estimation effort goes only where it can pay off. Produces: a go / no-go decision. A "no" is recorded as regretted, not deleted — it stays in the numbers for conversion analysis.

4. Estimate against a BOM/BOR. A feasible enquiry is costed against a bill of materials and routing — the child materials with their quantities, and the operations and resources each level consumes — so the price is derived from real cost rather than a guess. A techno-commercial review finalises the number. Produces: a defensible cost and price, tied to the enquired item, ready to be quoted.

5. Raise the quotation, then follow up. The costed enquiry becomes a quotation (QT) — a priced offer with configurable commercial terms, referencing the enquiry, and gated by an approval step before it goes out. Revisions are versioned with full history, so a re-negotiated price never overwrites what was sent before. Then the real work begins: the quotation sits on a follow-up dashboard while sales chase it, logging calls and notes until the customer decides. Produces: an approved, sent quotation and a running follow-up trail.

6. Accept the order. On a win, the quotation converts into an Order Acceptance (OA) — the confirmed customer order, inheriting the quotation's items, rates and terms. It is checked, released and completed, and the released OA is the handoff document to production and billing. Produces: a firm order the factory can plan against and accounts can invoice — with nothing re-typed.

Inside the flow: from won quote to released order

The most error-prone hand-off in the whole process is the one at the end — turning a won quotation into an order the factory can build. This is exactly where a generic system forces a re-type. Here is what the flow looks like when the documents are linked instead.

Notice what did not happen in that sequence: nobody re-typed the item list into a production system, and nobody re-entered the order into accounts. The released OA is the single handoff artifact — the same document production builds and billing invoices, on the same shared customer record. That is the practical meaning of "nothing re-keyed", and it is where a document-driven process quietly saves hours of double entry and eliminates the transcription errors that come with it.

A worked example, end to end

To make the flow concrete, here is one enquiry walked all the way through — the sort of journey a quotation-driven engineering supplier runs many times a week.

The value is not any single step — it is that the whole chain rides one customer record and one linked set of documents. The manager gets conversion by source and salesperson for free, because the source captured at the lead stage is still attached at the order stage. And because the estimate already understood the BOM, the factory is not decoding a fresh set of requirements when the order lands.

Where the process leaks — and how to plug it

Most manufacturers already run this process informally. The problem is rarely that a step is missing — it is that the hand-offs leak. Three leaks account for the majority of lost orders and wasted effort in a quotation-driven business.

• Enquiries going cold. An enquiry is received, then quietly forgotten because no one owns the next action. Without a stage-wise follow-up view showing the age of every open enquiry, the first sign of trouble is a lost order. The fix is a dashboard that surfaces ageing and a next-action date on every open item.
• Quote versions lost. A quotation is revised twice over email, and no one is sure which price the customer is holding. When revisions are versioned with full history and an approval gate, the "current" quote is never ambiguous and the negotiation trail is intact.
• Orders re-typed. The quote is won, and someone re-keys the item list into a production or accounts system — introducing transcription errors and delay. Converting the quotation straight into an order, which production and billing then act on, removes the re-type entirely.

Each leak has the same root cause: the document is not carried through the process intact, so information is re-created — and lost — at a hand-off. The difference between running this on a spreadsheet and running it on a CRM is precisely whether those hand-offs are seams where things fall through, or joins where the same document is passed along. The broader benefits for manufacturers and the Customer 360 view that sits under the whole chain build directly on this.

How Fast CRM runs the process

Fast CRM Software is a working implementation of exactly this workflow, built by Improsys in Pune. Rather than bolting a pipeline onto a contact database, it treats every step as a real commercial document on one engine — so the enquiry-to-order process runs as one unbroken chain.

Because it is one platform, the enquiry a salesperson captures becomes the order the factory builds and the invoice accounts raises — the same document, advanced, never re-created. It deploys in the cloud or on-premise, suits manufacturers of every kind across India and worldwide, and can run standalone as a sales office feeding an external ERP or as part of a full Fast ERP install. For a closer look at how the named stages and status codes fit on top of this workflow, see the sales pipeline stages guide, or start from the manufacturing CRM pillar.

Frequently asked questions