# CRM for manufacturing: how to run the pipeline for quotes, long cycles and distributors

https://salesbond.app/blog/crm-for-manufacturing-quote-pipeline-distributors/
Published: 2026-10-20 · Updated: 2026-10-26

A manufacturing CRM tracks inquiries, RFQs (requests for quote), quotes and distributor deals up to the order. So a manufacturer should run the CRM pipeline from the first inquiry to the confirmed order, with a quote version, a validity date and a source field (direct or distributor) on every deal, and leave production and stock to the ERP. That is the whole system. The rest of this article is how to set it up in the CRM you already have, with Pipedrive and HubSpot as the examples, and what a sales manager reads off it once a week.

We are not going to compare CRMs here. The pages that rank for “CRM for manufacturing” already do that, and they mostly agree on what matters: how deep the ERP integration goes, how the CRM handles quotes and RFQs, and whether you can see what distributors and reps are doing ( [NPWS: CRM for manufacturing](https://www.npws.net/blog/crm-for-manufacturing), written by a HubSpot partner, so read the vendor ranking with that in mind). What those pages skip is the day after the purchase: the pipeline is still a blank default, and the first RFQ lands in a stage called “Qualified”.

Still shopping? Then test the candidates against the setup below before you look at feature grids. Can you add your own fields to a deal, and can the CRM refuse to save a deal while one of them is empty, or at least from a given stage on? Can one deal carry two companies, the distributor you talk to and the end customer behind them? Can the deal hold a link to the quote document that lives in your ERP? A CRM that answers yes to all three will run this pipeline. Which one costs less for your team is a separate question, and not one this article tries to answer.

## Why a manufacturing pipeline is not a SaaS pipeline

A SaaS deal moves because the seller moves it. A manufacturing deal moves because a buyer approved a drawing, a purchasing department compared three quotes, or a distributor finally forwarded the order. The seller is often waiting, and waiting is a legitimate state, which is exactly what a default pipeline cannot express. Creatio’s glossary lists the ingredients: long sales cycles, high-value orders and relationships with distributors ( [Creatio: manufacturing CRM](https://www.creatio.com/glossary/manufacturing-crm)). Pipedrive’s own industry page sells the same picture of quotes, specifications and CAD files attached to the deal, plus the supply chain behind them ( [Pipedrive: CRM for the manufacturing industry](https://www.pipedrive.com/en/industries/crm-for-manufacturing-industry)). Its a product page, so treat it as a vendor’s description, not a study.

Three things follow for the pipeline itself.

The quote is the deal. In SaaS the proposal is a formality after the demo. In manufacturing the quote is where the engineering happens: SKUs, tolerances, lead times, a price that depends on volume. It gets revised, sometimes several times, and each revision resets the buyer’s clock.

The buyer is often not the customer. A distributor asks for a price on behalf of an end customer you may never talk to. If the CRM does not know which deals came that way, the forecast and the win rate mix two different businesses.

Time is not a warning sign on its own. A deal that has been quiet for six weeks might be dead, or it might be sitting with a buyer’s procurement team until the next budget review. The CRM has to tell these two apart. “Last activity date” alone won’t.

## Stages: inquiry, RFQ, quote, revision, approval, order

Seven stages, one of them an exit. Name them in the buyer’s language, not the seller’s, so a rep can place a deal without arguing about it.

![Flow of the seven pipeline stages with an entry rule under each, a loop from Revision back to Quote sent, and Lost reachable from any stage.](https://salesbond.app/wp-content/uploads/2026/10/crm-for-manufacturing-quote-pipeline-distributors-2.png)

An Inquiry means someone asked: a form, a call, a distributor’s email with “do you make this”. There is no spec yet. Most of these die here and that is fine; the stage exists so the dead ones do not pollute RFQ.

A deal reaches RFQ when you have enough to price it: a drawing or part number, a quantity, a delivery date. The entry rule is strict on purpose. If the rep cannot name the quantity, it is still an inquiry. How one request is handled once it lands is covered in [the RFQ process on the seller side](https://salesbond.app/blog/rfq-process-seller-side-crm-response-tracking/), with response tracking in the CRM.

Quote sent means a priced document left your company. Record the version and the validity date (more on both below). This is the stage that fills up in every manufacturer’s pipeline, and the one teh weekly review spends most of its time on.

Revision is where the deal goes when the buyer comes back with changes: a different quantity, a substitute material, a split delivery. It does not go backwards to RFQ. When the new quote goes out, the deal moves forward to Quote sent again with a new version number. Moving it back a stage hides the fact that you were close.

Approval means the buyer has said yes in some form and the paperwork is in motion: the purchase order (PO) being raised, sign-off from their management, a credit check on your side. In some industries deals sit here for weeks. That is a known wait, not a stall.

Order confirmed means the PO is in. For the CRM this is “won”. What happens next belongs to the ERP, and the deal should not stay open to track production.

Lost can be reached from any stage, always with a lost reason. “No response after quote” and “lost on price” are different problems and the manager needs to see them separately.

In both Pipedrive and HubSpot this is one deal pipeline. Map Order confirmed and Lost to whatever your CRM counts as won and lost, so the win reports stay honest; in HubSpot that means the Closed won and Closed lost stages ( [HubSpot: set up and customize pipelines](https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines)). If you sell both made-to-order and catalogue items and the catalogue side rarely needs an RFQ, keep one pipeline anyway and let catalogue deals skip from Inquiry to Quote sent. Two pipelines for one sales team is a reporting problem you will regret.

## Five fields every deal needs

Stages say where a deal is. These five fields say what kind of deal it is and when it needs attention. Everything else (part numbers, shipping terms, the account’s credit limit) lives on the quote document or in the ERP, not on the deal. We made the general case for a short deal record in [what to record on every B2B deal](https://salesbond.app/blog/b2b-sales-deal-records/); this is the manufacturing version.

| Field | Type | Why it exists |
| --- | --- | --- |
| Request type | single option: catalogue / made-to-order / repeat order | A repeat order and a custom build have different cycle lengths; mixing them wrecks any average. |
| Source | single option: direct / distributor | Splits the pipeline into two businesses with different win rates and different owners of the next step. |
| Quote version | number | Tells you how many times the buyer sent you back to the drawing board. We treat three or more as a reason to talk. |
| Quote valid until | date | The one date in a long cycle that is real. Everything else is an estimate. |
| Next contact | date | The date the rep committed to doing something, or the date the buyer promised an answer. Never empty on an open deal. |

All five are ordinary custom deal fields. Pipedrive lets you mark a field as required, which blocks saving the deal until it is filled, or as important, which only highlights the gap in the deal view; required fields need the Premium plan and important fields the Growth plan ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). HubSpot has the matching property types: dropdown select, number and date picker ( [HubSpot: property field types](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)).

Then decide when each field becomes mandatory. Source from Inquiry, Request type from RFQ, Quote version and Quote valid until from Quote sent, Next contact everywhere. In Pipedrive a required deal field can apply to chosen pipelines and stages only, and a rep who moves a deal into that stage with the field empty is asked to fill it in ( [Pipedrive: required fields](https://support.pipedrive.com/en/article/required-fields)). Where a field can’t be enforced by stage the weekly review below catches the blanks. Either way, don’t demand a field before the information exists. A required field that nobody can fill yet is a field reps learn to fake.

Do not add a “probability” field. Reps in long-cycle sales guess it, managers read it as fact, and the stage already carries the only probability that means anything.

## Direct vs distributor-sourced deals

A distributor deal looks like a direct deal and behaves like a different animal. The quote goes to the the distributor, the distributor marks it up and sends it on, and the yes or no comes back through them, often late and with the end customer’s reasons filtered out. If the Source field is missing, your win rate and cycle length are an average of two things that should never be averaged.

Our rule: the deal is owned by whoever your rep talks to, and the end customer, when known, goes on the deal as a second organisation or in a dedicated field, not as the deal’s main organisation. We worked through the mechanics of that split in [how to record reseller and end-customer deals](https://salesbond.app/blog/reseller-end-customer-deals-pipedrive/). In HubSpot the same structure works with an association label on the second company, which needs a Professional or Enterprise subscription ( [HubSpot: association labels](https://knowledge.hubspot.com/object-settings/create-and-use-association-labels)).

What changes in the weekly review once Source is set:

- Distributor deals get a longer leash before anyone calls them stalled, because the next step is often not yours to take.
- Next contact on a distributor deal is the date you agreed to call the distributor, not the date the end customer might decide.
- When the same end customer shows up on two distributor deals, you have a channel conflict to settle before the quote goes out.

If more than a handful of your RFQs are formal tenders rather than distributor requests, the bid or no-bid decision deserves its own gate inside the RFQ stage. We have a [bid / no-bid checklist](https://salesbond.app/blog/rfp-bid-no-bid-pipedrive/) for that, and it does not need a separate stage.

## Quotes: versions and validity dates

Every quote that leaves the building has a version number and a date it stops being valid. Both go on the deal the moment the document is sent, not when someone remembers.

The version number does two jobs. It stops the classic manufacturing argument (“we ordered against the quote you sent us”, “which one?”) because the deal shows which version was current when the PO arrived. And it gives the manager a cheap signal: a deal on version four has either a buyer who cannot decide or a rep who priced the first three without asking enough questions. Either way it is a conversation. The step-by-step for keeping versions straight, including what to do with the old PDF, is in [how to handle revised quote versions](https://salesbond.app/blog/revised-quote-versions-pipedrive/).

The validity date is the only honest deadline in a long cycle. Close dates slide; validity dates are written on a document the buyer has. When it passes, the rep picks one of three options that week: extend it, reprice it or close the deal as no decision. Doing nothing means the buyer can come back in month four holding a price from month one, after your material cost has moved. We wrote about [what to do on the day a quote expires](https://salesbond.app/blog/quote-expiry-validity-date-pipedrive/) in Pipedrive terms, and the decision is the same in any CRM.

One practical detail: when a revision goes out, update both fields together. New version, new validity date. A deal with version three and a validity date from version one looks fine in a report and is wrong.

## Long cycles: what a manager checks weekly

Each week a manufacturing sales manager should check four filtered lists, not the whole pipeline. A manufacturer’s pipeline is too long and too slow for a stage-by-stage walk every week; the meeting would go on re-reading deals that have not changed and should not have. The four lists, in this order:

Quotes expiring before the review after next. That window is our habit, not a law; pick one that gives reps time to act. Filter: stage is Quote sent or Revision, and Quote valid until falls inside the window. For each deal the rep names the action: extend, reprice, chase or close. This list is the heart of the meeting, because it is the only one where the deadline is real.

Open deals with no next contact, or a next contact in the past. Any stage. This is hygiene, and the list should be short. If it is long, the problem is not the deals but a field that is not required where it should be ( [keeping a B2B pipeline clean](https://salesbond.app/blog/b2b-sales-pipeline-hygiene/) goes into the habit side of this).

Deals in Approval for longer than your usual paperwork time. There is no universal number. A plant that sells to public bodies waits longer than one that sells to machine shops, so take the number from your own won deals and revisit it twice a year. A deal past it needs a call to the buyer’s purchasing team, not another email to the engineer who said yes.

Distributor deals with no update since the last review. Keep them apart from the direct list, because the question is different: “have we heard from the distributor?” rather than “have we heard from the customer?” If the answer is no for two reviews running, the rep calls the distributor. And if the distributor has gone quiet on the end customer too, the deal is probably lost and should say so.

A disclosure, since this is where tooling comes up: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. The filters above are not hard to build in any CRM, though. What is hard is running the review every week for a year, and no tool does that part for you. If you want to see how your own pipeline holds up, [check your CRM with SalesBond](https://salesbond.app/).

## Where the manufacturing CRM stops and the ERP starts

The CRM ends at Order confirmed. Production scheduling, stock, material purchasing, invoicing and delivery dates belong to the ERP, and the deal should not stay open to shadow them. The CRM answers “will we get the order, and when?”. The ERP answers “can we build it, and when will it ship?”. A team that tries to answer both in one system ends up with a deal record carrying dozens of fields, half of them stale.

Two things do cross the line, and someone has to decide who owns them.

The first is the quote document itself. The price and the bill of materials usually come from the ERP or from a quoting tool, because that is where the costs live. The CRM holds the version, the validity date and a link or attachment, not a second copy of the line items. Type the line items into the CRM by hand and sooner or later they will disagree with the ERP.

The second is repeat orders. When an existing customer reorders the same part, some teams leave it entirely to the ERP. We lean towards recording it as a deal with Request type set to repeat order, because the account manager needs to see it when thier next custom quote comes up. But it enters at Quote sent or Approval, not at Inquiry, and nobody should pretend it was sold from scratch.

What flows the other way, from ERP to CRM, is mostly one fact: the order was confirmed, shipped or cancelled. That is enough to close the loop and keep the pipeline honest about what actually became revenue.

So here is the next step. Set up the seven stages and the five fields this week, in whatever CRM you have, before you spend another month evaluating a different one. The deals you are quoting right now will be in Approval by the time an evaluation ends, and they deserve a pipeline that knows what a quote is.