For the past 18 months, we’ve been closely involved in digitising operations for an automotive rubber components manufacturer.

On paper, it sounded straightforward: Build an internal E-Catalogue. Launch a Dealer Management System. Improve efficiency.

In reality, it turned into a much deeper operational shift than any of us initially anticipated.

Here’s what we personally learned.

1. The Problem Wasn’t Software — It Was Visibility

Before we wrote a single line of code, we discovered something uncomfortable.

Different teams were working with different versions of product information. Sales had one sheet. Operations had another. Management had summaries.

The real issue wasn’t a lack of technology. It was a lack of alignment.

The E-Catalogue forced us to standardise how products were structured, described and accessed. That discipline alone created more impact than the UI ever did.

2. SKU Complexity Is Easy to Ignore Until You Try to Structure It

Automotive components sound simple until you map:
  • Thousands of SKUs
  • Multiple vehicle applications
  • Kits vs individual components
  • Material variations
Designing filtering logic made us realise how messy the underlying classification had become over time.

Reducing product search time by 40% wasn’t about speed; it was about forcing clarity.

3. Dealers Don’t Want Phone Calls — They Want Control

When we began designing the Dealer Management System, we assumed ordering was the main pain point.

It wasn’t.

Dealers wanted:
  • Visibility
  • Predictability
  • Fair pricing
  • Transparency in order status
The self-service portal changed the tone of the relationship. Engagement increased by 25%, but more importantly, trust improved.

4. Automation Is Only Helpful If It Removes Friction

We automated order closure after 75 days.

Simple rule. Big impact.

But getting there required debate: What if someone forgets? What if dispatch delays happen? What if pricing disputes exist?

Every “small automation” forces operational decisions.

Technology surfaces process ambiguity. It doesn’t hide it.

5. Pricing Logic Is Emotional, Not Just Mathematical

Introducing custom rate cards based on dealer turnover was powerful.

But it required careful communication.

Dealers compare. They talk. They calculate.

The system could manage dynamic pricing, but alignment conversations were human.

6. Adoption Was the Real Project

The tech stack (Django, PostgreSQL, mobile interface) was structured and reliable.

What took longer:
  • Data cleaning
  • Access controls
  • Internal training
  • Process documentation
Some team members quietly reverted to old habits in the early weeks. That’s when I realised digital transformation is behaviour change.

7. Metrics Build Confidence

When we saw:
  • 30% faster order processing
  • 15% increase in dealer-driven revenue
The organisation stopped asking, “Why did we do this?” Numbers remove doubt.

8. Software Exposes What Was Hidden

The most uncomfortable lesson? Systems reveal inefficiencies. Duplicate SKUs. Inconsistent pricing. Manual overrides. Untracked orders. None of this was visible before digitisation. The platform didn’t create problems. It illuminated them.

9. Transformation Is Ongoing

We’re now discussing:
  • AI-based product recommendations
  • Predictive order analytics
  • Supply chain visibility
But the real shift has already happened. The company now thinks digitally.

Final Reflection

This wasn’t an IT upgrade. It was a clarity exercise.
Digitising an automotive OEM taught me that:
Technology is rarely the bottleneck. Structure, discipline, and alignment usually are. If you’re about to start a similar journey, expect fewer technical problems and more organisational conversations. And that’s not a bad thing.

Awards & Recognition's

Let's Discuss Your Project!

Share the details of your project like scope or business challenges. Our team will carefully study them and then we’ll figure out the next move together.