OdooBots
Loading
Case study · Automotive components

Sanjeev Autoparts case study

Sanjeev Autoparts manufactures automotive components and handles a steady flow of customer RFQs, each covering several parts. In that business an enquiry is not one opportunity — it is as many opportunities as there are parts in it.

Managed in spreadsheets, that distinction disappears. The project rebuilt it: part-wise opportunity tracking, quotation follow-up and forecasting on one platform.

Arun KumarOdoo Functional Consultant, 8+ years| Reviewed by Karthik Raj| Updated 21 October 2026| Customised Odoo ERP implementation
0Odoo projects delivered
0Consultants & developers
Per partOpportunity, not per enquiry
ChennaiAmbattur, Tamil Nadu
Sanjeev Autoparts — Odoo ERP implemented for Automotive parts in India
SA
Sanjeev AutopartsAutomotive components

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

What we implemented for Sanjeev Autoparts

Sanjeev Autoparts runs its RFQ and opportunity lifecycle on a customised Odoo CRM with part-wise tracking. Customer enquiries are captured centrally; each part within an RFQ is tracked as its own opportunity with its own quotation; business forecasting runs on an SOP basis; turnaround time on RFQ response is reported; and dashboards cover business potential and awarded business from the same records the sales team maintains.

Tracking opportunities per part rather than per enquiry is the decision this project turns on. An RFQ covering twelve parts where three are won is not a lost enquiry or a won one, and a CRM that cannot express that cannot forecast.

RFQ
A customer request covering one or more parts, each quotable separately.
Part-wise opportunity
One opportunity per part, so a partly-won enquiry reports correctly.
TAT
Turnaround time — how long an RFQ waits for a response. A number customers notice.
Awarded business
What was actually won, against what was quoted. The denominator for conversion.
Experience · the project

The project at a glance

Taken from the project itself rather than from a capability list.

Sanjeev Autoparts logo

Sanjeev Autoparts

Automotive parts · India
Task

Customised CRM for RFQ management, opportunity tracking, sales analytics and business dashboards.

Solution provided

Customised CRM and dashboard solution

Location

India

See every Odoo implementation case study, or the full Odoo ERP implementation service.

The challenge

What was not working at Sanjeev Autoparts

Customer RFQs, multiple part enquiries, quotation follow-ups, business projections and sales performance were managed through spreadsheets and manual processes. That produced delayed responses, limited visibility and inefficient decision-making — and in a components business, a delayed RFQ response is often the whole reason a part is lost.

  1. RFQs arrived into spreadsheets

    Enquiries were logged manually, so response times depended on who saw them and when.

  2. Parts were not tracked separately

    With the enquiry as the unit, an RFQ where some parts were won and others lost could not be reported honestly.

  3. Follow-up was uneven

    Quotation follow-up depended on individual memory rather than on a dated next action.

  4. Forecasting was manual

    Business projections were assembled rather than derived, which makes them slow and hard to revise.

  5. Response time was invisible

    Without turnaround time reporting, the delay customers actually experience was not a number anyone managed.

What we built

What the implementation covered

The implementation digitised the complete RFQ and opportunity lifecycle.

Centralised RFQ management

Customer RFQs and enquiries captured in one place, so a request has an owner and a clock from the moment it arrives.

CentralOwnedTimed

Part-wise opportunities

Each part within an RFQ tracked as its own opportunity with its own quotation, so a partly-won enquiry reports as what it is.

Per partOwn quoteHonest status

Quotation tracking

Quotation generation and follow-up against each part opportunity, so chasing is driven by the record rather than by recollection.

GenerationFollow-upStatus

SOP-based forecasting

Business forecasting and projections on a sales and operations planning basis, derived from the pipeline rather than assembled separately.

ForecastProjectionsFrom pipeline

TAT reporting

Turnaround time performance reporting on RFQ response, making the delay a customer experiences into a number the business manages.

TurnaroundMeasuredManaged

Dashboards

Business potential and awarded business reports with management dashboards, read from the same records the sales team works in.

PotentialAwardedLive
How it works now

How Sanjeev Autoparts runs on Odoo today

The sales operation now works per part rather than per enquiry, with response time measured and forecasting derived from the pipeline.

  • Every RFQ owned and timed — a request has an owner from arrival, and the clock on it is visible.
  • One opportunity per part — so an RFQ with twelve parts and three wins reports as three wins, not as an ambiguity.
  • Follow-up from the record — quotation chasing driven by the system rather than by whoever remembers.
  • Forecasting derived, not assembled — SOP-based projections come from the pipeline itself.
  • Turnaround time reported — the delay customers feel is a managed number rather than an impression.
Sanjeev Autoparts — the Odoo screens built for this implementation
In the system — the configuration built for this project.
Results

What changed

What the client reports back, in their terms. We publish no percentages here because the project did not measure any, and a number we cannot stand behind is worth less than one we can.

Faster RFQ processing

Centralised capture and part-wise tracking shortened both RFQ handling and quotation preparation.

Opportunity visibility

Customer opportunities became visible at part level rather than hidden inside an enquiry.

Better follow-up and conversion

Tracking follow-up against each part opportunity improved both the discipline and the conversion reporting.

Stronger forecasting

SOP-based projections derived from the pipeline made planning faster to produce and easier to revise.

Management dashboards

Business potential and awarded business reporting gave management current numbers rather than compiled ones.

Less duplication

Teams collaborate on the same records, which removed both manual effort and duplicated data.

FAQ

Sanjeev Autoparts: frequently asked questions

What did OdooBots build for Sanjeev Autoparts?
A customised Odoo CRM and dashboard solution covering centralised RFQ and enquiry management, part-wise opportunity and quotation tracking, SOP-based business forecasting, turnaround time performance reporting, and business potential and awarded business dashboards.
Why track opportunities per part?
Because a components RFQ covering twelve parts where three are won is neither a won enquiry nor a lost one. With the enquiry as the unit, that result cannot be reported honestly, and conversion and forecasting both become guesswork.
What is TAT reporting and why does it matter?
Turnaround time is how long an RFQ waits for a response. In a components business a slow reply often loses the part before price is even discussed, so making it a measured number rather than an impression is usually worth more than any other reporting on the project.
Is this an ERP or just a CRM?
This project was a customised CRM and dashboard solution rather than a full ERP implementation. The RFQ and opportunity lifecycle was the problem worth solving, and we scoped to that rather than to everything.
Could this suit our component business?
If you respond to RFQs covering several parts and your conversion is tracked in a spreadsheet, the shape is the same. What differs is your part structure and how you forecast, which the free diagnosis call establishes.

Running something similar to Sanjeev Autoparts?

Tell us how many parts a typical RFQ covers and how response time is tracked today. Those two answers shape the configuration, and the diagnosis call is free.