Manufacturing CRM
In manufacturing the sale is not a pick from a catalogue but a quote calculated from the drawing and the quantity that come in; at every revision both the price and the due date change. Machinery, moulds, metal, packaging or textiles — whichever branch you are in, the same question is asked: what was the last price and the last delivery date written to the customer?
Every revision of the quote is a separate version; price, due date and send date are its fields, earlier versions are not deleted, and the order is born from the due date field.
- Record the incoming request together with the technical drawing and the specification, and produce the quote directly from that record
- Keep every revision of the quote as a separate version; see retrospectively on which date it was sent, with which price and which due date
- Keep the delivery date given to the customer in a field on the quote so that sales and planning read the same date
- Tie spare part and warranty requests to the order number and gather the whole history of the same job on one card
| Request and Technical File | The customer request is a record; quantity, material and tolerance are its fields, and the drawing and the specification attachment sit on the same card. |
|---|---|
| Quote Revision | Every revision is a separate version of the quote; price, due date and send date are its fields, and earlier versions are not deleted. |
| Due Date Field | The delivery date is a field on the quote; the order is born from that field, and a change of date is written to the record as an update. |
| After-Sales Request | Spare part and warranty applications are request records; the order number is carried in a field, and the history of the job is collected in a single list. |
In a manufacturing firm, preparing a quote is not a sales job on its own. A drawing or a specification comes in from the customer, quantity and material are asked about, the cost is worked out together with production, and then a price and a due date are written down. Then the revision arrives: the quantity changes, the tolerance changes, a coating is added. After the third revision the final state of the quote sometimes stays in the salesperson's e-mail inbox and sometimes in a copy of a spreadsheet. The promised due date is the most fragile piece of information; it is given in sales, it is not known in planning, and when the customer calls, the two sides say different dates. This picture is the same in machinery manufacturing, in moulds and in packaging — the branches change, the information that gets lost does not.
In Rapitek CRM the request, the quote and the order are records linked to one another. Every revision of the quote is a separate version; which price and which due date it was sent with, and on what date, sit in the record, and the technical drawing stays attached. Because the due date is a field on the quote, what was promised to the customer is read from a single place, and a change of date leaves a trace as an update. A won quote turns into an order and is followed from the same card as its stage moves on. A spare part or warranty application that comes in after the sale is a request record and carries the order number, so the history of the same job does not scatter. We build the connection to the ERP side; there is no out-of-the-box module — the Logo, Netsis, Mikro or SAP connection is built specifically for your project over the REST API, OAuth2 and webhooks.
The scope of the plans and the separately priced items are written on the pricing page.
