RevenueOS for manufacturing
Manufacturers measure the shop floor to the second and run the order book on hope. The order book deserves the same discipline: planning from capacity, dealer coverage somebody owns, and a chain that ends when the money arrives rather than when the truck leaves.
Summary
- Three things make manufacturing different: revenue has a physical ceiling, the product usually reaches the customer through a channel you do not control, and the gap between winning an order and seeing the cash runs into months.
- Plan from capacity rather than from a growth percentage, built two ways at once: by product line, and by customer or channel. Then separate made to order from made to stock, because they are two businesses.
- Execution runs past dispatch. Quote to order conversion, the gap between the price list and what lands in the bank, on-time-in-full and days to collect are all revenue numbers.
Walk onto the shop floor of a well-run Indian factory and you'll find precision everywhere. Cycle times measured to the second. Rejection rates tracked by line and by shift. Machine uptime reviewed daily. Maintenance scheduled by machine hours. Decades of hard work have gone into making the production side of the business visible.
Then walk into the sales office. The order book lives in someone's head and three spreadsheets. Enquiries get tracked by whoever remembers to. The forecast is whatever the regional managers said last month, adjusted down by an amount the promoter has learned from experience. Nobody can tell you how many enquiries turn into orders, or how long that takes, or what the number was last year.
Same company. Same leadership. Two completely different standards on either side of the wall.
A revenue operating system exists to close that gap. It's the same five-part discipline we use everywhere (planning, demand, execution, review, predictability) set up for an order book, a plant and a dealer network.
Different dials, same system
As with every sector, it's worth being clear about what actually changes, because it's less than people expect.
Manufacturers don't need a different system. They need the same one, with different numbers on the dashboard. A manufacturing CFO running RevenueOS is running the same system a SaaS or hospital CFO runs, just measured in order book and price per unit instead of subscriptions or beds.
What genuinely makes manufacturing different is three things. Your revenue has a physical ceiling. Your product usually reaches the customer through a channel you don't control. And the gap between winning an order and seeing the cash can run into months.
Each of those changes how a pillar looks. None of them changes what it's for.
Planning: start from the plant, build by line and by customer
A factory's revenue has a hard limit. Machines, shifts, tooling, hours in a day. So planning starts from capacity, not from a growth percentage.
Build it from the bottom up, two ways at once.
By product line. Volume multiplied by the price you actually get per unit, with a clear view on mix. A tonne of one grade is not a tonne of another.
By customer or channel. OEM contracts, dealer offtake, tenders, exports, and increasingly direct sales. Each one carries a different price, a different payment cycle and a different level of reliability.
Then there's the split that drives everything else: how much of the plan is made to order and how much is made to stock. The first is limited by your order book. The second is limited by how much cash you're willing to turn into inventory and how good you are at guessing what will sell. A plan that doesn't separate the two is planning two businesses as if they were one.
"Grow 20%" is a wish. "Lift the price we get on the export line by shifting to the higher grade, while holding domestic volume and plant steady" is something a team can actually work on.
Demand: the order book is built, not found
Enquiries don't arrive by luck, though in many Indian factories it genuinely feels that way, because the demand engine was built twenty years ago on the promoter's relationships and was never written down.
It has real parts. Dealer and distributor networks, with coverage you can measure and gaps you can name. OEM approval cycles that run for months or years and behave exactly like a long sales pipeline. Tenders and institutional bidding. Trade shows and industry bodies. Export buyers and sourcing agents. And, increasingly, buyers who find you online or through B2B marketplaces.
The logic is the same as any pipeline. If you know how many enquiries turn into quotes, how many quotes turn into orders, and your average order value, you can work backwards to how many enquiries the plan needs, and then hold someone responsible for producing them, instead of treating a thin order book as something the market did to you.
The part most often missing is dealer coverage as a number somebody owns. How many active dealers, in which districts, with how much offtake each, and where are the blank spaces on the map? Most manufacturers can name their top ten distributors. Very few can tell you their coverage gap.
Execution: from enquiry to money in the bank
This is where manufacturing looks least like a software sale, and it runs much further downstream.
Quote to order. How many enquiries became quotes, how many quotes became orders, and what did you lose on: price, delivery time, specification, or credit terms? That last question is the important one, and almost nobody tracks it. A business that can't answer it is guessing about its own competitiveness.
The gap between your price list and what you actually get. Your price list says one thing. What lands in the bank per unit is something else, after volume discounts, dealer schemes, freight you absorbed, credit notes and settlement adjustments. In our experience this gap is both large and rarely looked at, because the schemes are booked centrally and never matched back to the customers who used them.
The tender trap. Where a good share of your revenue comes through reverse auctions and L1 bidding, execution discipline means deciding in advance which bids you will not chase. A business that bids for everything wins the wrong work at the wrong price and calls it market pressure.
Delivering on time and in full. OTIF is a revenue number, not just an operations one. Late and short deliveries create credit notes, lose repeat orders, and cost you the premium your quality was meant to earn.
Delivered isn't collected. The chain doesn't end at dispatch. It ends when the money arrives. In a business running on 60 to 120 day terms, a sale you haven't collected is an expensive loan you never meant to give.
Review: the same rhythm, different agenda
The structure is the same everywhere. What's on the agenda is specific to you.
- Weekly: order book movement, enquiries received, quotes sent out, plant utilisation against plan, dispatches at risk.
- Monthly: price actually realised per unit against the price list, dealer schemes booked versus actually claimed, on-time delivery, profit by product and by customer, receivables ageing.
- Quarterly: capacity and capex, dealer coverage and performance, price revision, and where you stand on passing through input costs.
That last one deserves a permanent slot. When raw material or power costs move, the question isn't whether you noticed. It's how much you've recovered, how long it took, and how much is still exposed. Most manufacturers find out about that gap in the annual accounts rather than in the month it opened.
And as everywhere: every number needs a name against it, a level at which it triggers a conversation, and a meeting where it gets discussed. Without that, schemes creep up, prices slide, and nobody owns the slide.
Predictability: the numbers that move first
Predictable revenue in manufacturing comes from a handful of numbers that move before the P&L does.
Order book cover, how much of next quarter's plan is already confirmed. This is the single best early warning most manufacturers have, and many don't calculate it.
Enquiry to quote to order conversion, tracked by segment, so a drop shows up while it's still upstream.
Plant utilisation trend, which tells you whether your limit right now is demand or capability.
Mix drift, in both product and channel, because a slide toward lower-priced lines shows up in margin long before it shows up in revenue.
Input costs against the price you're getting, which is your early warning on margin squeeze.
As everywhere, predictability is the result of the other four done well.
You can't forecast your way out of an order book nobody manages.
The dashboard
Underneath the five pillars sits the set of numbers that make a factory readable: order book and order book cover, plant utilisation, enquiry-to-order conversion, price realised per unit against list, product and channel mix, on-time-in-full, inventory turns, days to collect, and profit by product and by channel, never blended.
That last point matters more than it sounds. A product that looks healthy on a blended margin is often profitable in one channel and losing money in another. The blend hides both.
Where to start
Most manufacturers we meet are excellent on capacity and quality, decent on review discipline, and quietly weak on demand and execution, because those were built informally decades ago and never held to the standard the shop floor is held to.
The first step isn't a new system. It's an honest read of where each pillar actually stands today.
That's what ROSA does: a short assessment across the pillars of a revenue operating system, so you can see your own profile and decide what to fix first, instead of assuming the answer is always more enquiries.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
Related reading
