Scalatris
ENGINEERED TO ELEVATE
ISSUE #13
THE FACTORY FORWARD · 25 AUGUST 2026 · 6 MIN READ, DESIGNED TO RUN IN 12
The Budget Is Spent. The Number Isn't Here Yet.
▸ FIELD NOTE. A cycle-time number that held the room at day 30, before the ₹ number showed up.
▸ TOOL TO TRY. A prompt that writes your 30-day status update honestly, with no invented wins.
▸ THIS WEEK'S NUMBER. Even formal capex review frameworks don't expect proof this early.
Two Tuesdays ago I told you the next one was about this: you got the budget, the machine is running, and the number you promised the room hasn't moved. That's not a failure. Thirty days is too soon for a payback figure to move at all. What you say in that gap decides whether you get asked back for the next request.
If you're the one who signed the request, you already know the silence is the hard part. The dashboard says nothing yet. The rejection numbers move for reasons that have nothing to do with your six lakh. And your promoter, or your CFO, or the bank that financed it, is going to ask anyway.
THE GAP
What formal review expects. What you actually have.
FORMAL PIR TIMELINE
3 to 24 months
Before a formal capex review expects a real payback figure.
WHAT YOU HAVE AT DAY 30
Partial data.
One Monday meeting. No verdict yet, and that's fine.
The frameworks don't expect proof yet. Your promoter's questions can't tell.
Timeline sourced below in This Week's Number. International capex-framework research, not an India-specific benchmark.
ONE FIELD NOTE
The number that held the room wasn't the ₹ number
DISCLOSURE, READ THIS BEFORE THE NUMBERS.
This is a constructed scenario, not a client. We don't have a named engagement to cite for this one yet, and Scalatris's own numbers aren't ready to publish either. What follows is built from the pattern we see repeat across MSME capex reviews, not one real plant's figures. Read it as a shape, not a record.
What happened. A press-parts unit near Nashik got sign-off in July on a ₹6 lakh vision-inspection add-on for a stamping line. Thirty days in, the rejection rate hadn't visibly moved. Rejection is noisy at low weekly volume, one bad batch of raw stock can swing it either way, so there was nothing honest to say about it yet.
Why it worked. The plant head didn't report rejection rate. He reported cycle time at the inspection station: down from 40 seconds a piece to 24. That's a leading indicator, not the ₹ saved, and it moved inside the first two weeks because it's mechanical, not statistical. He had one true sentence for Monday's check-in instead of zero.
"He had one true sentence for Monday's check-in instead of zero."
What it costs you to skip this. Say nothing for thirty days and the next conversation with the promoter isn't about the machine. It's about whether you're the kind of person who tracks what he spends the family's money on. That reputation cost compounds faster than any single stalled metric. Compare that to the plant that says nothing: the promoter fills the silence with his own worst guess, and his worst guess is rarely generous.
ONE TOOL TO TRY
The 30-day status update, written honestly
Ask this of Claude, ChatGPT or Gemini, any of them, thirty days after any capital purchase goes live and the money hasn't proven itself yet:
It works off whatever you already have: a WhatsApp thread with the vendor, a downtime log kept on paper, an Excel sheet nobody's touched since the sign-off meeting. You don't need clean data. You need honest data.
You are helping me report on a capital purchase 30 days after it went live. The financial payback has not shown up yet, that is expected. I need an honest status update for [the promoter / my manager / the bank], not a sales pitch.
Here is what I have: [paste your notes, WhatsApp thread, downtime log, production log, Tally export, whatever you actually have, in whatever shape it's in]
Write a status update with exactly four sections:
1. WHAT MOVED. Only things I can point to with a number or a log entry.
2. WHAT DIDN'T MOVE. Name it without excuses. If you don't know why, write "not yet diagnosed," don't guess at a reason.
3. WHAT WE'RE WATCHING. The 1 or 2 leading indicators (cycle time, rejection rate, downtime, output per shift) that will move before the money does, and roughly when to expect them to.
4. WHEN THE REAL NUMBER LANDS. The honest date the payback figure becomes visible, based on my original business case, not an optimistic guess.
Keep it under 150 words total. No hedging language like "early signs are promising" unless a number I gave you actually supports it. If my notes don't have enough to fill a section honestly, tell me what's missing instead of filling the gap with a guess.The line doing the heavy lifting: "If nothing moved yet, say so plainly, do not invent a small win." That's the instruction standing between a status update and a cover story.
YOUR ONE MOVE THIS WEEK
Get the fill-in template
The prompt above, a worked example filled in, and a blank version for your own numbers. Takes 5 minutes. Nothing to install.
Was this issue worth 5 minutes?
THIS WEEK'S NUMBER
3 to 24 months
That's the window standard capital-project practice gives itself before it expects a real answer. Some organisations run an initial cost check at the three-month mark just to catch the numbers while they're fresh. Formal post-investment reviews on larger projects wait 12 to 24 months for the full benefit to show. If the frameworks built for professional capex governance don't expect proof at day 30, neither should the promoter asking you for one. Day 30 isn't even the halfway point of the fastest version of that timeline. If the machine at your plant hasn't proven itself yet, it's on schedule, not behind.
Source: eCapEx, "How a post investment review improves future CapEx decisions." Read the article. International capex-software research, not an India-specific MSME benchmark, flagged so you can weigh it accordingly.
What's the one leading indicator on your last capex approval that you never actually reported back?
Hit reply and tell me. I'm collecting the honest ones for #14.
COMING NEXT TUESDAY
Budget was the first of three asks. Next: what happens when the 30-day update goes well and you're ready to ask for the second one, headcount. Same discipline applies there too: you don't get to ask for people until you can show what the money already bought is actually doing.
P.S. Run this update every 30 days until the real number lands. Four honest paragraphs a month is cheaper than one bad quarter of silence. Keep a copy of each one. Six months from now, when the number finally lands, you'll want the paper trail showing you called it early and got it right, or called it early and course-corrected before it became a bigger problem.
Until next Tuesday,
Sachin
Founder, Scalatris LLP · scalatris.com
REFER A COLLEAGUE
Know the plant head three cubicles over who signed something in July and hasn't said a word about it since? Forward this. That's the whole ask. It's how almost everyone here found it.