A raw lead captured in the field, an enquiry over the phone, a web form or an exhibition contact — each one lands in the pipeline as a numbered document with its customer, item lines, drawings, terms and the source it came from, ready to convert into a quotation and an order without re-typing.
However demand reaches you — a field visit, a phone call, a website form or an exhibition — the capture flow is the same, so every enquiry starts life ready to be estimated, quoted and won. New to a document-driven pipeline? Start with our guide, what is manufacturing CRM software?
A prospect met at a plant visit or an exhibition should not wait for someone to be back at a desk. Fast CRM logs a raw prospect as a Lead (code LD) with its customer name, contact person, mobile number, priority and enquired items — and the mobile-friendly Add New Lead screen lets a field salesperson do all of that on a phone. Save and start a new lead in one tap; every mobile lead joins the same pipeline as office entries.
In Fast CRM an enquiry is not a note in an inbox — it is a real document (code EQ) in the shared engine, with a header and item lines. It holds the customer, item lines with quantity and unit, drawings and attachments, delivery address, reference type and commercial terms, and a full status history from status 31. Because it is the same structure the quotation and the order use, nothing is re-typed as the deal advances.
Marketing spend is guesswork until you know which channels produce real enquiries. Every enquiry records its source and reference — referral, campaign, website, exhibition or an existing customer — as a maintained reference type on the document. Web-enquiry forms feed the same pipeline automatically, so an enquiry that started on your website arrives already tagged. It is one habit at capture that unlocks reference-wise reporting later.
Capturing the source is only half the value; the payoff is the reporting. Enquiry-versus-order analytics compare enquiries against confirmed orders reference-wise and salesperson-wise, so you can see which channels and which executives close. Enquiries you choose not to pursue are marked status 36 — Enquiry Regretted — never deleted — so lost demand and the reasons behind it stay in the same conversion picture, feeding cleanly into follow-up dashboards.
Capture a raw prospect as a numbered Lead document with customer, contact, priority and enquired items — before it is qualified into an enquiry.
An Add New Lead screen built for a phone or tablet, so a salesperson logs the prospect and items on-site and starts a new lead in one tap.
An enquiry is a real header-plus-lines document at status 31 — item lines, drawings, delivery and terms — the same structure the quote and order reuse.
Enquiries submitted through your website feed straight into the pipeline, already tagged with their source — no inbox, no manual re-entry.
Maintain your own reference types — referral, campaign, website, exhibition, existing customer — and tag each enquiry with reference type and description.
Reference-wise and salesperson-wise enquiry-vs-order reporting, with regretted enquiries (status 36) retained so lost demand stays measurable.
Most sales pipelines leak at the very first step — the enquiry arrives, but never becomes a tracked, sourced document. Here is what changes.
A raw prospect is logged as a Lead document (code LD) and, once qualified, becomes an Enquiry document (code EQ) at status 31 — Enquiry Received. The enquiry carries the customer, item lines, drawings, delivery and commercial terms, plus the source it arrived through — exactly the same document structure that later drives the quotation and the confirmed order, so nothing is re-keyed on conversion.
Yes. A mobile-friendly Add New Lead screen lets a field salesperson capture the customer name, contact person, mobile number, address, priority, reference and enquired items on a phone or tablet while in front of the prospect. Each mobile lead lands in the same pipeline as office-entered leads and can be saved and a new lead started in one tap.
It is a real document. An enquiry is a header-plus-lines record in the shared document engine, discriminated by the EQ code, carrying item lines with quantity and unit, drawings and attachments, delivery address, reference type and commercial terms, and a full status history from status 31 onward. That is why a Fast CRM enquiry can convert straight into a quotation and an order without retyping.
Every enquiry records its source and reference — referral, campaign, website, exhibition or an existing customer — through the enquiry reference capture. Because the source is a maintained reference type on the document, you can later report reference-wise on which channels actually produce enquiries and, more importantly, which ones convert to orders.
Yes. Conversion analytics compare enquiries against orders reference-wise and salesperson-wise, so you can see which lead sources and which executives turn enquiries into confirmed orders. Enquiries that are not pursued are closed as status 36 — Enquiry Regretted rather than deleted, so lost demand stays visible in the same conversion reporting, and Dhruv AI analytics can take it further.
Live demo on your sales workflow — your enquiry sources, your item lines, your conversion questions. Cloud or on-premise. No generic slideshow.
