RFQ and quoting
Recording the request, technical assessment, costing and approval stages.
Industrial sales cycles are long and technical. The quote is revised several times, samples get involved, and the decision passes through several people. That cannot be tracked in email.
At a glance
What comes up with industrial firms:
The structure we build with manufacturers:
Recording the request, technical assessment, costing and approval stages.
Each revision stored as a version, with the one that was sent marked.
Product tree, unit prices, discount tiers and customer-specific price lists.
Dealer records, territory assignment, dealer requests and limited-access dealer users.
Tracking sample requests, dispatch and customer feedback.
Warranty, fault and spare part requests in their own SLA-tracked pipeline.
In manufacturing a quote is rarely accepted first time. Quantities change, specifications change, prices are revised. Run through email, "which quote are we discussing" becomes inevitable.
We hold quotes as versions attached to the record. Each revision is stored as a separate document, the version that was sent is marked, and you can see which revision the customer replied to.
Sales passes a technical question to production, the answer comes back by email, sales relays it to the customer. Every link in that chain adds delay and loses information.
We make technical assessment a step on the quote record. The question is asked through the record and answered there; sales gets a notification and the history stays searchable.
When dealer requests come by phone, what was asked, what was promised and who is following up can all get lost.
We bring dealers into the system: each with a record, a territory and an owner. If you want, dealers get limited-access users so they can see their own requests and statuses; which cuts down the "any news?" calls.
In industrial sales a decision can take months. An opportunity left unfollowed in that time is forgotten and a competitor steps in.
We build follow-up plans by stage: tasks open at set intervals after a quote goes out, and pending opportunities collect on the manager's screen. Opportunities with no movement raise an alert.
The structure we build most often in manufacturing.
| Stage | Owner | Output |
|---|---|---|
| Request received | Sales | RFQ record with customer and specification |
| Technical assessment | Technical team | Feasibility decision, lead time estimate |
| Costing | Costing / sales | Unit cost and proposed price |
| Internal approval | Management | Price and terms approved |
| Quote sent | Sales | A versioned quote document |
| Revision | Sales + technical | A new version with a change note |
| Order | Sales | Confirmed order, passed to production |
How would this work in your process?
In a free 30-minute call we listen to your workflow and map out how this would run in your company.
The order we follow in manufacturing setups:
The flow from RFQ to order and its decision points are mapped.
Product tree, price lists and discount tiers are built.
Stages, approval steps and the revision structure are defined.
Dealer management and the service process are built.
Sales, technical and service teams are trained.
The modules we most often roll out alongside this one; they reinforce each other in the same setup.
Preparing a quote should not start with hunting for the right Word file. We build quote templates that pull straight from deal data, then turn approval and follow-up into a process.
When the pipeline is unclear, nobody knows which deals are moving and which are stuck. We design your stages around your real sales process and make the next step visible on every card.
Whichever channel a service request arrives through, it should land in the same queue with an owner and a deadline. That is exactly how we configure the Bitrix24 Contact Center.
Bitrix24 is not a closed box. The REST API gives programmatic, scope-controlled access to your CRM entities over standard HTTP; and we design, build and monitor the integration for you.
In health tourism running ads is easy; turning the leads into treatments is not. The difference sits in your reachability rate, your speed to first contact, and knowing which form actually brings patients.
The most expensive loss in a clinic is a no-show. The second is a check-up nobody remembered. Systematic reminders solve most of both.
In property you do not sell a product, you sell a specific unit. Which apartment went to whom, at what price and on what payment plan has to live in the system.
No, it complements it. The ERP stays on production, stock and accounting; Bitrix24 handles the pre-sales process and the customer relationship. We build the integration so data passes to the ERP once an order is confirmed.
Yes. Several price lists can be defined in the catalogue and assigned per customer or dealer. The right list is applied automatically when a quote is prepared.
Yes. Dealers can be given limited-access users that show only their own requests, orders and statuses. Defined as extranet users they cannot reach internal data.
Yes. We design the quote document with your branding, terms and signature blocks. It fills automatically from CRM data and can be signed electronically.
Yes. We define sample handling as its own step: request, preparation, dispatch and customer feedback, with automatic reminders if feedback does not arrive.
Book a free intro call and we'll walk through your process and show which settings fit you.