From Excel to an Operating Layer: What a Manufacturer Should Build First

A manufacturer with ₹50 crore in sales can still run its dealers, stock, sales targets and staff incentives on a handful of spreadsheets and WhatsApp groups. It works until two people edit the same sheet, a formula breaks in the middle of the month, or the person who understands the incentive file goes on leave.

The usual next step is a large ERP project. Many businesses get further by replacing the one or two sheets that cause the most trouble, then building outward.

Start with the sheet that breaks most

Ask three questions about each spreadsheet the business depends on:

• How many people edit it?
• What goes wrong when it's wrong: a missed dispatch, an angry dealer, a wrong salary?
• How much time goes into checking it each month?

The sheet with the most editors and the most expensive mistakes goes first. In agricultural inputs and building materials, that is usually the dealer order and ledger sheet, or the sales incentive calculation.

Keep accounting where it is

Your accounts, GST returns and statutory records belong in your accounting software. An operating layer should read from it and feed it, not replace it. Build only what your accounting software can't do for your people: field orders, dealer schemes, targets, incentives, loyalty and approvals.

What the first version needs

• One record per dealer, product and employee. Every screen reads from the same record, so a dealer's address or credit limit is never in two places.
• Roles. A sales officer sees their territory, a manager sees the region, accounts sees payments.
• A history of changes. Who changed a price, a target or an order, and when.
• Phone first. Field staff will use it on a mid-range Android phone on a patchy connection, so it has to load fast and survive a dropped signal.
• WhatsApp for alerts. Order confirmations and approval requests go where people already are.
• An import from the old sheets, so nobody retypes a year of history.

How the move should go

1. Import the current sheet and run both side by side for one cycle, usually a month.
2. Compare the totals at the end of the cycle. When they match, retire the sheet.
3. Add the next module only after the first one is in daily use.

This order matters more than the feature list. A system people use every day for one job beats a complete ERP that half the team avoids.

An example

Balaji Agro Chemicals' website brings in more than 150 leads a month. Behind it, their staff run sales tracking, incentive tracking, a loyalty programme, HR workflows and day-to-day operations on one Node.js system we built. Leads from the website land in the same place the sales team works, so the first enquiry and the final incentive sit in one record. The BACF story covers it in more detail.

Build or buy

Buy when a packaged product fits how you already work, for accounting, payroll and GST filing especially. Build when your dealer schemes, territories or incentive rules are what make the business different, and every packaged product would force you to change them.

Our internal platforms practice builds these systems, starting with a paid audit that maps the sheets and decides what to replace first. For connecting them to your accounting software or Shopify store, see API integration engineering.