Lubricant additives

Lubricant additive sales run on multi-year OEM approval cycles, blender qualifications, and category-specification work. Corial captures the engine test data, blender conversations, and OEM influence chains that decide commercial position.

$20B

Global lubricant additives market (2027)

24-48 mo

OEM approval cycle (passenger car motor oil)

$1-3M

Typical engine test program cost

Specification regimes per category

Industry overview

Suppliers of detergents, dispersants, antiwear additives, viscosity index improvers, friction modifiers, antioxidants, corrosion inhibitors, and base oil specialties sell into lubricant blenders, OEM lubricant programs, and industrial end-users. Sales are shaped by API, ACEA, ILSAC, JASO, and OEM-specific category specifications that govern which additive packages qualify for which performance level. Engine test programs cost millions and run for years, making technical sales conversations deeply consequential.

Typical challenges

Category-specification cycles

API, ACEA, ILSAC, and JASO publish lubricant categories that define performance for new vehicle generations. Each category cycle requires new engine test data, additive package reformulation, and blender requalification. Suppliers who shape the category cycle early carry an advantage.

OEM-specific approvals

BMW, Mercedes, GM, Ford, Volkswagen, Toyota, JCB, and major heavy-duty OEMs each publish their own lubricant specifications. A passenger car motor oil might carry six or seven OEM-approval claims, each requiring its own engine test data.

Engine test economics

Engine test programs cost one to three million dollars and run for months. The decision to run a test is a major commercial commitment. Capturing the conversations and data behind every test program is essential for managing risk and prioritization.

Base oil interaction effects

An additive package qualified on Group II base oil may behave differently on Group III or Group IV. Each base oil grade and supplier combination affects performance. Sales conversations cover not just the additive but the base oil ecosystem around it.

Industrial lubricant fragmentation

Industrial lubricants (hydraulics, gear oils, metalworking, greases) have their own specification regimes (DIN, ISO, AGMA, ASTM) and end-user qualification processes. The same additive supplier often spans automotive and industrial customers with completely different sales dynamics.

Why Corial fits

Built for ingredient sales

Corial recognizes lubricant terminology: API SP, ILSAC GF-6, ACEA C5, OEM approvals (MB 229.5, VW 504 00, BMW LL-04), Sequence engine tests, Noack volatility, TBN, HTHS, Mack T-13, Cummins ISB. Voice notes from blender visits and OEM technical meetings are captured with the right context.

Designed for long sales cycles

Pipeline tracks each engine test program, each OEM approval, and each blender qualification as a distinct project. The multi-year cadence of category cycles and OEM specifications is built into stalled-project thresholds.

Relationship intelligence

Map relationships across blender R&D, blender production, OEM engine engineers, fleet customers, and category-specification committees. Identify where competitor engagement is closer than yours.

Institutional memory

Engine test results, OEM technical correspondence, blender formulation history, and category-cycle positioning notes are captured and searchable. The next OEM meeting starts with the full account history, not a slide deck rebuilt from memory.

Lubricant additive sales is a long game

An additive package developed today will qualify for a category cycle three years out. The OEM engineers writing the next specification today will define which test methods you must pass two years from now. The blender deciding which additive supplier to partner with is making a five-year commitment, not a quarterly purchase.

This time horizon makes institutional memory the central commercial asset. Which OEM engineer raised an oil-aging concern at last year's industry meeting. Which blender's R&D director changed jobs. Which competitor passed a key engine test in the previous category cycle. Corial captures all of that as your team works, and surfaces it when it matters.

Tracking OEM approvals as projects

Every OEM approval a blender chases is its own engineering project, with its own test schedule, its own technical contacts, and its own commercial significance. A blender pursuing an MB 229.5, a VW 504 00, and a BMW LL-04 in parallel for a new product launch has three distinct programs running, each consuming engine test capacity.

Corial models each OEM approval as a separate project under the blender account. You see the full set of active approvals at each blender, the test status of each, and where additive package decisions are open. Stalled-project alerts respect engine test timelines, not generic SaaS thresholds.

Lubricant additive suppliers who track OEM approvals at the project level inside each blender account see 2-3x more program activity than those who track at the account level only. Most blenders have five to ten parallel programs running at any time.

Bridging automotive and industrial sales

Many lubricant additive suppliers sell into both automotive blenders (high-volume, OEM-driven) and industrial customers (specialty, application-driven). The two sides have different sales rhythms, different specification regimes, and different competitive sets. Forcing them into one CRM pipeline obscures both.

Corial models the two pipelines distinctly while keeping them inside the same Corial tenant. Automotive engine test cycles and industrial application qualifications coexist without forcing a fictional uniformity onto either.

Frequently asked questions.

Which lubricant additive segments does Corial cover?

Corial supports suppliers of passenger car motor oil additives, heavy-duty diesel engine oil additives, transmission and driveline additives, industrial hydraulic and gear oil additives, metalworking fluid additives, grease additives, and base oil specialties. The pipeline adapts to each segment's specification regime.

Can Corial track OEM approvals individually?

Yes. Each OEM approval is modeled as a separate project. Test schedules, technical contacts, and approval status are tracked per OEM, so a blender pursuing multiple OEM approvals in parallel shows all of them clearly.

How does Corial handle category-specification cycles?

Category cycles (API SP, ILSAC GF-6, ACEA C5, future categories) are tracked at the additive package level. Engine test programs, additive performance data, and committee position notes are linked to the category cycle, so historical context is preserved across multi-year cycle work.

Does Corial work for both automotive and industrial lubricant sales?

Yes. Both customer types are supported. Automotive blender relationships with their OEM-driven specifications and industrial customer relationships with their application-driven qualifications coexist in the same tenant, with separate pipelines as needed.

Can Corial capture engine test data and technical correspondence?

Yes. Test results, OEM technical correspondence, blender formulation discussions, and competitor benchmarking notes are captured from voice notes and email. Pre-meeting briefs include the full engine test history of the account.

Stop letting relationships fall through the cracks

Join ingredient companies already using Corial to capture every conversation, track every project, and never miss a follow-up.

Get early access