Scalatris
ENGINEERED TO ELEVATE ISSUE #12
THE FACTORY FORWARD · 18 AUGUST 2026 · 6 MIN READ, DESIGNED TO RUN IN 12
Your case is right. Your ask is wrong.
Last issue I said the decision log makes your judgment visible. One line came back more than once: “they still won't give me the budget.”
Being visible is not the same as being funded.
You can prove ops creates value and still lose the ask, because the case and the ask are two different documents. Most of us only ever build the first one.
Same plant. Same month. Same ₹8 lakh.
VERSION ONE ✕ REJECTED
“We need ₹8 lakh for vibration monitoring on the two critical lines.”
✓ Cost stated
✕ No payback date
✕ No downside case
Reads as risk.
VERSION TWO ✓ APPROVED
“₹8 lakh. Assume it prevents a recurrence of downtime equivalent to the two breakdowns that cost us 14 dispatch days last year. On our numbers that pays back in 11 months. If the benefit comes in at half, 22.”
✓ Cost stated
✓ Base-case payback
✓ Downside-case payback
Reads as a decision.
Composite field scenario, built from recurring patterns in operations investment requests. Not a named or identifiable client. Every figure below is an illustrative assumption.
The arithmetic, so you can check it
Two things make version two work. It converts a maintenance problem into a monthly rupee figure, and it states what happens if that figure is wrong.
Line | Value |
|---|---|
14 dispatch days lost, at an assumed ₹62,500 per day | ₹8,75,000 a year |
Assumed monthly value if that downtime does not recur | ₹73,000 |
Monthly recurring cost | ₹0 |
One-time investment | ₹8,00,000 |
Base-case payback, 8,00,000 ÷ 73,000 | 11 months |
Stress test, benefit reduced by 50 percent | ₹36,500 |
Downside payback, 8,00,000 ÷ 36,500 | 22 months |
Illustrative payback calculation. Substitute your own plant figures. This example assumes no recurring monthly cost, because the investment is hardware with no subscription attached. The 50 percent reduction is a stress test, not a measured probability. And avoided downtime only becomes cash if the released capacity, protected contribution or avoided cost is real and verified. Check that before you present anything.
A case proves you are right. An ask proves the business gets its money back.
Where your request sits
Scenario | Net monthly benefit | Payback |
|---|---|---|
Base case | ₹73,000 | 11 months |
Downside stress test | ₹36,500 | 22 months |
Screening hurdle | Not applicable | 24 months |
Both scenarios clear the screening hurdle used in this exercise. 24 months is not an industry benchmark. It is the default used here because the tool needs a starting point. Replace it with your organisation's actual approval threshold.
BEFORE YOU PASTE ANYTHING
Use only a company-approved AI tool. Consumer and enterprise versions of the same product do not carry the same privacy and data-retention controls, so check which one you are in. Strip customer names, employee details, supplier terms and pricing agreements first. Whatever comes back is draft analysis. Verify every number and assumption yourself before it goes anywhere internal.
The prompt
Run it on what you already have: downtime logs, dispatch records, maintenance notes. Fill both bracketed fields before you send it, so it finishes in one pass.
You are helping me turn an operations request into an
investment case for internal review. You are producing
draft analysis a human must verify, not a decision.
INPUTS
Item and one-time cost: [PASTE]
Monthly recurring cost: [PASTE, or NONE]
What it protects or releases, however messy: [PASTE]
My maximum acceptable payback: [MONTHS, or blank]
Downside reduction to test: [PERCENTAGE, or blank]
STEPS
1. Split my inputs into VERIFIED (from records) and
ASSUMED (inferred). Show both. Never move an item
from ASSUMED to VERIFIED.
2. Restate the request in one sentence a promoter would
use, with no ops jargon.
3. Name the value released or protected, and convert it
to rupees per month. Show the arithmetic line by line.
If a number is missing, name it and stop. Do not
estimate it.
4. Net monthly benefit = benefit minus recurring cost.
Print it on its own line.
5. If net monthly benefit is zero or negative, stop.
Say so plainly, explain why, print no payback figure.
6. Payback = one-time cost divided by net monthly
benefit. Round up.
7. Re-run steps 4 and 5 with my downside percentage. If
I left it blank, use 50 percent and label it an
unvalidated stress test, not a forecast.
8. Compare both against my hurdle. If blank, use 24
months and tell me in one line to replace it with my
organisation's approval threshold.
9. Name the single biggest reason this gets rejected,
and write the one-sentence answer to it.
10. End with one line, under 20 words, that the finance
lead can repeat to their CA when I am not there.
Close with: "Draft analysis. Verify all inputs and
assumptions before internal presentation."
Do not use the words optimise, streamline or efficiency.Step 10 is the one that matters. A budget case has to survive after the meeting, when someone else repeats it without you in the room. If your ask cannot survive that retelling, it was never an ask. It was a presentation.
If it does not clear
Most requests fail on the first run, and that is the point of running it before the meeting rather than during it. Two moves, in order.
Cut scope until it clears. Half the sensors. One line instead of two. A three-month trial instead of a purchase. A smaller ask that clears your hurdle beats a complete one that does not, because the smaller one buys you a track record and the complete one buys you a rejection.
If it still will not clear, that is your answer. Take it off the list and say so. An ops leader who withdraws a request on their own arithmetic is more credible the next time than one who keeps resubmitting the same thing in new packaging.
WHAT THIS DOES NOT DO
Simple payback screens requests. It tells you which ones are worth taking further. It is not the capital-investment decision. Before approval the business will still want total cost of ownership, implementation and ramp-up costs, cash-flow timing, NPV or discounted payback, a risk check and a finance review. Use this to get into that conversation, not to replace it.
YOUR ONE MOVE THIS WEEK
Run it on the one request you stopped asking for.
The template carries the final prompt, a fill-in payback sheet, a completed example, the downside check and a one-page usage note.
Button not working? Open the template link here.
What did you stop asking for?
Reply with one request you gave up on after two rejections. I read every one, and the sharpest answers become the spine of a future issue.
Coming next Tuesday
You got the budget. Now the first thirty days, when the thing you bought is running and the number you promised has not moved yet. How to report a payback in progress without losing the room.
Still owed from Issue #11: headcount and mandate. Budget was the first of three.
Until next Tuesday,
Sachin
Founder, Scalatris LLP · scalatris.com
Know a plant head sitting on a request they stopped asking for? Forward this to them. That is how almost everyone here found The Factory Forward.