Skip to content
Curious Kaizer · case study

AUCO × AIWA ERP and CRM Case Study

This AUCO AIWA ERP case study covers the dual-brand ERP and CRM we built for AUCO and AIWA. One workspace holds the sales pipeline, orders, stock, dispatch, GST billing and repair tickets for both brands, with each brand's data kept apart. It is a private client system, so this page has no link to it.

The project

The AUCO × AIWA Operations Portal is a dual-brand ERP and CRM. It puts the sales pipeline, orders, stock, dispatch, GST billing and repair tickets for two brands in one workspace, with a single control to switch between the brands.

The CRM side runs a 7-stage sales pipeline and a client map across 12 industrial cities. The ERP side covers inventory, orders and dispatch, repair tickets and GST billing. For how we scope systems like this for other businesses, see our custom ERP software development page and our custom CRM development page.

AUCO × AIWA ERP and CRM dashboard with the brand switch, sales pipeline and India client map
The portal dashboard, with the brand switch, sales pipeline and India client map.

The AUCO × AIWA portal is a private client system, so this page has no link to it, no demo login and no client records. It describes what the system does.

Two brands, one workspace

The portal serves two brands in one workspace. A single control flips the workspace between AUCO and AIWA. Clients and numbers stay separate for each brand, and the owner can see both.

In technical terms this is entity isolation per brand, with oversight across both. If you are planning a multi-brand system, decide early which records must never mix between brands, and who is allowed to see both.

AUCO × AIWA portal after switching brands, with one control flipping the workspace and each brand's data kept apart
The brand switch: one control flips the workspace and keeps each brand's data apart.

How a sale moves through the system

This is the sales path the modules support, from a lead to a payment.

  1. A lead enters the pipeline. It sits on the board in one of seven stages, with a next step on its card.
  2. The team makes contact. WhatsApp and call buttons sit on the card.
  3. The deal moves forward. It goes stage by stage until it is won.
  4. An order is raised. Its status can be filtered and followed through to delivery.
  5. Dispatch is recorded. The courier and AWB details sit on the order, and a dispatch note and invoice can be opened from it.
  6. The GST invoice is tracked. It shows what is billed, paid and outstanding, and part payments show as progress.
  7. Stock is watched. Units per SKU are checked against a minimum level, and every adjustment is logged.

Repair tickets and the client map sit beside this path, each in its own module.

Modules

ModuleWhat it does
Brand workspaceOne control switches between AUCO and AIWA. Clients and numbers stay separate for each brand, and the owner sees both.
Sales pipelineA 7-stage visual pipeline with a next step on every card, and WhatsApp and call buttons.
Client mapAn interactive geospatial map of the client network across 12 industrial cities, with value and orders by state.
Orders and dispatchStatus filters, courier and AWB details on the order, a dispatch note and an invoice, tracked through to delivery.
InventoryUnits per SKU, a bar against each minimum stock level, and logged stock adjustments.
Invoices and GST billingBilled, paid and outstanding views, part-payment progress and one-click collection from the invoice.
Repair ticketsRepair ticket tracking alongside equipment dispatches.
Roles and reportsFour role-based accounts, and business reports.

The portal has 13 modules in all, from leads to reports. This table groups the main ones.

AUCO × AIWA portal facts: 2 brands in one workspace, 13 modules and 4 role-based accounts
What was built in: 2 brands, 13 modules and 4 role-based accounts.

Screens from the pipeline to the client map

These flyers follow a sale from the pipeline to payment, then show the client map.

AUCO × AIWA sales pipeline with seven stages and a next step on every card
The sales pipeline, with seven stages and a next step on every card.
AUCO × AIWA orders and dispatch screen with status filters and courier details
Orders tracked to delivery, with status filters and courier details.
AUCO × AIWA inventory screen with units per SKU and minimum stock bars
Inventory, with units per SKU and a minimum stock bar on each item.
AUCO × AIWA invoices screen with billed, paid and outstanding totals and part-payment progress
Invoices, with billed, paid and outstanding views and part-payment progress.
AUCO × AIWA India client map with a state-by-state summary of value and orders
The India client map, where tapping a state shows its value and orders.

What this case study does not claim

We are not publishing sales, speed or savings results for the AUCO × AIWA portal, or its cost, build time or stack. The numbers on this page, such as 2 brands, 7 pipeline stages, 12 cities and 13 modules, describe what was built, not what it achieved. This page also does not discuss any client record, name or figure.

Is a build like this right for you?

A system like this is worth pricing when one team runs more than one brand, or when leads, orders, stock and invoices sit in different tools. Use the table to see where to start.

If this sounds like youWhere to start
You run two brands or entities with one team and need clients and numbers kept apart.A multi-brand ERP like this one. Read about custom ERP software development.
Leads, orders, stock and invoices sit in separate tools or spreadsheets.One system for the whole path, scoped module by module. See custom software development.
Your enquiries come from WhatsApp and Meta ads and end in a GST invoice, with little stock to track.A custom CRM may be enough. Read the WatFix CRM case study or custom CRM development.

Our published starting point for custom software is from ₹33,900, or $1,000 for international clients. An ERP and CRM is quoted after scoping. See pricing for the full list. Dates and scope are confirmed in the written proposal. You can also browse other projects in our portfolio.

How we would scope it, and what you own

Our projects are fixed price, with a written scope and milestones confirmed in the proposal. Source code handover and private repository handover are listed on the pricing page, and support terms are confirmed in writing.

Before we price a multi-brand system, we need answers to a few questions.

  • Which records must stay separate between brands, and who may see both.
  • Which stages your sales pipeline has, and what moves a deal to the next one.
  • How orders, couriers and dispatch notes are handled today.
  • Which stock items need a minimum level.
  • Which GST invoice formats and part-payment rules you use.
  • Which cities or regions your clients are in.

Questions about the AUCO × AIWA portal

Can I see the live AUCO × AIWA portal?

No. The portal is a private client system, so there is no public link or demo login. The flyers on this page are how we show the work.

Does this page describe real client data?

No. This page describes what the system does. It does not discuss any client record, name or figure, and the system itself stays private.

How does the dual-brand setup work?

One control switches the workspace between AUCO and AIWA. Each brand's clients and numbers stay separate, and the owner can see both.

What does the sales pipeline look like?

It is a 7-stage visual pipeline. Every card shows a next step and has WhatsApp and call buttons.

What does the client map show?

It is an interactive geospatial map of the client network, covering 12 industrial cities. Tapping a state shows its value and orders.

Does it cover stock, dispatch and repairs?

Yes. Inventory shows units per SKU against minimum stock levels, with logged adjustments. Orders are tracked to delivery with courier and AWB details, and repair tickets are tracked too.

Did the system improve sales or save time?

We do not publish results for this project, so this page makes no claim about sales, speed or savings. It describes what the system does.

What would a similar ERP and CRM cost?

The price of the AUCO × AIWA portal is not published. Our published starting point for custom software is from ₹33,900, or $1,000 for international clients. An ERP and CRM is quoted after scoping, and dates and scope are confirmed in the written proposal.

Talk to us about your ERP

Send us your brands or entities, your pipeline stages and a sample invoice, and we will tell you what we would build first.