What is different in manufacturing sales
An industrial buyer is not buying a product. They are qualifying a supplier. Before the first real order, your material passes a specification review, a sample test, often a trial production run, and a purchasing negotiation. Each step involves different people: an engineer who cares about tolerances, a plant manager who cares about reliability, and a buyer who cares about price and terms. The deal survives only if all three say yes.
This makes cycles long and lumpy. Six months of technical evaluation can precede a first order worth €8,000, which then grows into a €300,000 annual account. The economics live in the account, not the deal, so the CRM has to make existing customer growth as visible as new logos.
Many manufacturers also sell through dealers or distributors, which adds a second question to every deal: who owns the relationship? A setup that cannot distinguish direct from dealer revenue produces reports nobody in the boardroom believes.
An example manufacturing pipeline
This is the new business pipeline we deploy for component and materials manufacturers. The stages mirror the qualification ladder a buyer actually climbs.
| Stage | Exit criterion |
|---|---|
| Requirement confirmed | Application, volumes and target price documented with the engineer. |
| Sample sent | Sample or spec package delivered, test date agreed. |
| Sample approved | Technical sign-off received in writing. |
| Quote sent | Commercial offer delivered with volumes and terms. |
| Trial order placed | First paid order received and in production. |
| Framework agreed | Repeat volumes or annual agreement confirmed. |
A second pipeline handles existing account growth: new applications at current customers, reactivation after silence, and dealer development. The split logic follows our guide to pipeline design: separate processes get separate pipelines, product lines get a field.
The fields and automations that matter
The fields that earn their keep: product group as a fixed list, annual volume potential as a number, channel as direct or dealer, the dealer organisation where relevant, target application, and expected first order date. Annual volume potential deserves emphasis. A €5,000 trial deal with €200,000 yearly potential must rank above a €20,000 one-off, and only a field makes that visible. Keep the rest of the list ruthless, per custom fields that earn their place.
Automations should attack the silences. When a sample is sent, create a follow-up activity at the agreed test date plus three days. When a quote goes out, schedule the chase, the pattern from automations that matter. And when an account with orders in the ERP goes a set number of months without a new order, open a reactivation deal automatically. Manufacturers rarely lose accounts loudly. They lose them quietly, order by order, to a competitor's rep who kept visiting.
Common mistakes
The most common failure is treating the CRM as an order administration copy. Reps are asked to retype what the ERP already knows, they stop after three weeks, and the rollout dies. Pipedrive earns its licence on the funnel the ERP cannot see: the samples, trials and quotes that precede every order.
The second is a pipeline with date-based stages like Q3 target. Stages must mark buyer commitment. Close dates handle the calendar.
The third is invisible dealers. If half the revenue flows through distributors and every deal names only the end user, channel reporting is fiction. Link both organisations from day one.
The fourth is importing the entire ERP customer base as open deals. Import organisations, yes. Open deals only where a real opportunity exists. The rest is addressed in data hygiene, because a pipeline of ghosts rots faster than an empty one.
Questions
Should Pipedrive replace our ERP quoting?
No. Complex configured quotes with bills of materials belong in the ERP or a CPQ tool. Pipedrive tracks that a quote exists, its value, its date and its status. The moment you try to rebuild ERP logic in CRM custom fields, you are maintaining two systems that both do the job badly.
How do we handle repeat orders from existing customers?
Routine reorders that sales never touches should stay in the ERP. Orders that need a salesperson, such as expansions, new lines or win-back after silence, become deals in a dedicated existing business pipeline. The dividing line is human effort, not order size.
Can Pipedrive model dealers and distributors?
Yes, with linked organisations. The dealer is one organisation, the end customer another, and the deal links to both, with a relation field naming the dealer. You then report sell-through per dealer, which most manufacturers cannot see in their ERP at all.
What connects Pipedrive to our ERP?
Usually a middleware such as Make or a direct API integration built once. The common pattern is one way on win: a won deal creates or updates the sales order and the customer record in the ERP. Keep the ERP as the system of record for orders and invoices.
Our sales cycle runs a year or more. Does a pipeline still work?
Yes, but stages must mark commitment milestones, not months. Specification agreed, sample approved, trial order placed. With long cycles, activity discipline matters more than stage count, because a deal that sits quiet for eight weeks may still be healthy.