Depth bar: Due-diligence dossier for Stamped outreach. Estimates marked [~]; directory facts [dir]; unverified claims [!]. Never invent bill numbers, court outcomes, or emails.

1. Company overview & snapshot

Sri Jaibalaji Steel Rolling Mills Pvt Ltd operates a TMT / re-rolling mill at 4th Km Stone, Village Sujroo, Meerut Road, Muzaffarnagar 251001 — the dense western UP steel corridor. Directors Shourya Jain and Akash Kumar. Operating revenue range Rs 100–500 Cr FY24 [~] (Tofler). Fit score 8 rests on utilisation and MD physics; historical Excise/CGST appeal matter (search origins 2015; CESTAT July 2025 reporting) requires operational-only opening language.

1.1 Legal identity & corporate structure

CIN U27100UP2008PTC182403, ROC Kanpur, unlisted private company, authorised ~Rs 3 Cr / paid-up ~Rs 2.96 Cr. Confirm exact legal spelling (Sri Jaibalaji vs Shri Jai Balaji variants appear in court captions).

1.2 What they make & where money comes from

TMT Fe500/550 rolling / re-rolling. Customers local/regional construction. Thin website presence — rely on MCA/Tofler and plant visit intel.

1.3 Plants, addresses & footprint

Single primary address Sujroo Meerut Road. Ask if sister concerns (Crystal Balaji / other Jain DINs) share meters — usually no, but check.

1.4 Leadership & CRM map

Shourya Jain Director (primary). Akash Kumar WTD long tenure. Electrical in-charge unnamed publicly. LinkedIn thin — phone/field introduction may outperform email.

1.5 Recent news (24 months) & timing for Stamped

Indian Kanoon / CESTAT material around Sri Jai Balaji Steel Rolling Mills appeal vs CE & CGST Meerut-I (order text dated 10 July 2025 in search results) referencing 2015 search at secret premises and alleged parallel ledgers — historical duty evasion investigation context. Use for internal risk flag only; never open with tax history.

2. Energy profile

DISCOM / supply (name early): PuVVNL (Paschimanchal) for Muzaffarnagar Meerut Road belt — confirm invoice (sometimes still spoken as “UPPCL”).

2.1 Bill band, tariff & demand

At Rs 300–400 Cr [~] Band A rolling, monthly HT often ≥ Rs 30–60 lakh [~] if utilisation high — unverified. Demand from simultaneous stand starts is classic.

2.2 Generation, fuel & renewables

Likely DG; reheating may be coal/oil/gas — separate electrical MD from fuel.

2.3 EnMS, PAT, ISO, BRSR

No public ISO 50001/BRSR. Path B.

2.4 Likely ₹ leak categories (hypothesis)

Simultaneous stand starts; reheat hold; cooling bed auxiliaries; PF; night overtime peaks.

3. Operations, equipment & digital stack

3.1 Process flow & critical loads

Billet/ingot receive → reheat → roughing/intermediate/finishing stands → cooling → shear → stock. Critical: mill motors, reheat fans, water pumps.

3.2 Shifts, seasonality, production pattern

Construction seasonality; Meerut Road peer utilisation high — ask actual shifts.

3.3 Automation, metering, SCADA/EMS/DCS

Unknown automation maturity; assume Path B.

3.4 Capex / tech projects affecting energy

No public solar mega-claim. Do not invent.

4. Stamped Energy fit analysis

4.1 ICP scorecard

Geography/vertical pass. Bill unknown. Decision owner-operated favourable if trust built. Integrity flag elevates commercial caution.

4.2 Fit score rationale

8/10 process; integrity history is top commercial risk, not a fit-score nullifier if bill qualifies and culture accepts ops vendors.

4.3 Wedge (parser-critical)

The strongest wedge is: overlapping rolling-stand starts and reheating holds that stack PuVVNL MD on the Meerut Road mill — rupee owners, read-only meters, verification on the next bill (operational value only).

4.4 Objections & competitors

“We watch the MD meter.” → prescriptions + invoice. Peer mills already approached → cluster courtesy. Procurement informal → WhatsApp-friendly owner path.

4.5 Pilot design

One HT. Kill quickly if bill < floor or data refused.

5. Before you reach out

5.1 Discovery checklist

• Exact legal name on GST + bill.
• Two PuVVNL bills.
• Electrical in-charge WhatsApp.
• Sister plant meter sharing?
• Stand count and typical start sequence.
• Fuel for reheat.
• Approver for opex.
• Willingness to share interval data.
• Preferred language Hindi/English.
• Visit window vs call-only.

5.2 Do not lead with

• Do not lead with dashboards, AI buzzwords or ESG-first pitch.
• Do not lead with GST/Excise/search history.
• Do not threaten “compliance software.”
• Do not invent website claims.

5.3 Opening hooks

“On Meerut Road TMT, stand starts often create the MD you pay on PuVVNL — we assign ₹ to those events and verify with evidence.”

6. Risks, flags, controversies & sources

6.1 Integrity / controversy / regulatory (search explicitly)

1. Historical Excise/CGST investigation & appeal: Indian Kanoon record Sri Jai Balaji Steel Rolling Mills Pvt … vs Ce & Cgst Meerut-I (10 July 2025) discussing 22.9.2015 search, alleged secret premises Agrasain Vihar, and parallel ledgers under fake names — cite only as public appellate record; do not allege current evasion.
2. MSME payment-delay mentioners on aggregator pages — verify if any; treat as soft commercial diligence.
3. Search terms also covered NGT/PCB/pollution/labour/tax raid 2024–26 — no fresh NGT headline located this pass.
4. Thin digital footprint increases entity-collision risk with other Balaji / Jai Balaji steel names — confirm CIN and Sujroo address. Initiatives: corridor utilisation; TMT Fe500/550 product push. Failures: public transparency / website absence.

6.2 Data quality flags

• Revenue range wide Rs 100–500 Cr.
• Website absent.
• Champion LinkedIn unreliable.
• Court caption spelling variants.

6.3 Sources consulted

• Tofler / Tracxn company pages; Indian Kanoon CESTAT text; MCA director pages; UP lead report.

Operating diligence addendum (meter → bill → owner)

A1. How to read the first two PuVVNL invoices

Ask the plant to share the latest two HT/EHT invoices with account name unredacted for legal matching, and demand/energy pages intact. Record: sanctioned or contract demand; billing demand; recorded maximum demand; power-factor reading and incentive/penalty line; ToD or peak/off-peak segmentation if present; fuel surcharge / electricity duty / municipal cess; any open-access or captive adjustment; and whether multiple meters roll into one consumer. Photograph or PDF the tariff category. Convert every line that can move with operational behaviour (MD, PF, ToD energy) into a ranked opportunity list — that list is the only list Stamped should sell into on day one.

For Muzaffarnagar Meerut Road, the immediate commercial question is whether the consumer that matches the gate address is also the P&L that can approve a 90-day opex pilot. Many North India groups present a trading name on the gate and a different limited-company name on the bill. If they diverge, stop and re-paper the CRM record before proposing Scope of Work language.

A2. Process-specific measurement plan — TMT / re-rolling stand motors + reheating

Build a one-page event dictionary with the electrical owner: which start-up, hold, changeover, CIP, campaign or utility header historically coincides with bill pain. For each event type, ask (a) earliest safe start time, (b) whether the event can stagger versus a peer feeder, (c) what quality/safety interlock forbids delay, and (d) who today gets a WhatsApp if MD warns. Stamped’s value appears only when (d) exists — prescriptions without owners become another unread report.

Interval data preference order: (1) DISCOM 15-minute or AMI pull if available; (2) plant energy-meter logger CSV; (3) DCS/SCADA historian tags for large motors/utility headers; (4) daily energy + production register if interval is impossible. Never claim a percentage saving without production normalisation. Tonnes, batches, pairs, hours of sterile HVAC, or caustic MT are acceptable proxies depending on site.

A3. Path A vs Path B data access

Path A: read-only connection or scheduled export from existing EMS/SCADA/BMS/meter gateway; Stamped never writes setpoints. Path B: weekly CSV drops plus a shared campaign/production calendar. Either path must clear OT/IT security, retention, and need-to-know access. Expect an Indian industrial cyber questionnaire; answer in plain language — software layer, no PLC write, no remote control, bill verification.

If the site already paid for ISO 50001 consultants, VFDs, solar EPCs, or OEM analytics, acknowledge those spend lines explicitly. Stamped should be framed as the closure layer that turns residual observations into assigned rupees and invoice checks — not as a replacement capital project.

A4. 90-Day Bill Verification Program — local framing

Week 0: entity + bill + champion map. Weeks 1–2: baseline MD and energy components with production context. Weeks 3–8: weekly ranked prescription cards (max 5) with owner, due date, expected rupee line, and operational constraint. Weeks 9–12: reconcile executed cards to PuVVNL invoice components; document kill or expand. Commercial Band A working fee Rs 2–5 lakh [~] fixed for the proof — present as structured verification, not a discount pilot. Kill criteria: bill below ICP floor; no accessible data; no plant owner; unstable production without usable normalisation; zero controllable lever after two review cycles.

A5. Cluster and reference context

Field sequencing for this campaign batch should respect peer density: Mandi Gobindgarh steel day; Derabassi–Baddi–Rajpura chemistry day; Ghaziabad–Muzaffarnagar steel day; Kanpur–Unnao leather/packaging day. Peer references are for routing confidence, never for inventing shared bills. Keep each legal entity’s invoice private.

A6. Safety, quality and integrity boundaries

No outreach message may imply Stamped will change validated recipes, membrane current density, Tempcore quench parameters, sterile differential pressures, or tannery finish formulas. Those domains stay with process owners; Stamped only sequences and attributes cost to events inside already-approved envelopes. Controversies, historical tax matters, rating actions or inspections are pre-call awareness — they are not cold-call openers.

Integrity flag is internal only — operational MD language exclusively.

Extended call-prep narrative (Stamped field use)

B1. First 20 minutes of discovery

Open with process respect, not software. Confirm legal entity on the invoice, DISCOM name, and who owns the largest feeder MD event in the last 90 days. Ask for two invoices and one production calendar export before any platform demo. If the champion cannot produce bills within a week, treat the opportunity as stalled — Bill Verification Program without invoices is theatre. Record whether Path A (historian/meter export) or Path B (CSV) is realistic given OT policy. Confirm the economic buyer who can approve a Rs 2–5 lakh [~] fixed 90-day fee without a full ERP tender.

B2. Prescription card discipline

Every recommendation must name: event, owner, due date, expected rupee line on the DISCOM invoice, operational constraint, and evidence of execution. Cards without owners are deleted. Cap weekly cards at five so plant teams are not flooded. Prefer MD sequencing and idle-hold cuts before exotic tariff products. Never propose changing validated recipe, membrane current, sterile pressure, or Tempcore quench parameters. If quality or safety forbids a schedule change, mark the lever as blocked and move on — credibility beats aggressive savings claims.

B3. Verifying savings without gaming

A lower bill alone is not success if tonnes, pairs, or batches fell. Normalise against a production proxy agreed in week 1. Document holidays, forced outages, new-line commissioning, captive/solar settlement changes, and weather-sensitive HVAC. Keep a decision ledger shared with the plant: recommendation, owner, status, expected vs observed invoice delta. Present kill or expand at day 90 with the same ledger — this is how Stamped differs from audit PDFs that never close.

B4. Competitive and incumbent handling

If the site has EMS/SCADA/BMS, OEM analytics, ISO consultants, or solar EPCs, congratulate the spend and ask what residual bill lines still surprise them monthly. Position Stamped as the closure layer: rupee assignments and invoice reconciliation. Refuse head-to-head dashboard bake-offs. If Gujarat, Panipat, or Noida corporate IT appears, keep plant electrical as the proof owner and let corporate rubber-stamp after a verified bill line — not before.

B5. Geographic and cluster logistics

Batch 3 spans Mandi Gobindgarh, Paonta/Derabassi/Rajpura, Ghaziabad/Muzaffarnagar, and Kanpur–Unnao. Plan field days by corridor. Carry printed one-pagers: Fit score, DISCOM hypothesis, strongest wedge sentence, and two discovery questions. After each visit, update extras field intel — especially corrected phones, electrical names, and whether the bill cleared Rs 30 lakh/month.

B6. Messaging hygiene for this batch

Owner-operated steel/leather accounts tolerate Hindi-friendly WhatsApp and short calls. Listed pharma/chemical accounts prefer email plus LinkedIn with technical depth. Never open with controversies (GST/Excise history, EuGMP observations, rating actions) — those are internal briefings only. Always name DISCOM early in research-backed prep sheets so call-prep UI can render correctly.

Site-specific residual diligence

C1. Meter boundary sketch (draw with plant on first call)

Sketch incomers, captive/solar settlement meters, critical process feeders, and utility headers. Mark which boundaries are inside the proposed 90-day scope and which are watch-only. If Modinagar consolidation, membrane upgrade, EU HVAC expansion, or multi-unit FIBC feeds muddy the sketch, freeze scope to one consumer number until maps exist.

C2. Production normalisation contract

Agree the production proxy in writing in week 1: caustic MT, bright-bar tonnes, TMT tonnes, footwear pairs, or extruded tonnes. Without that contract, day-90 debates become opinion. Record weather, holidays, and forced outages beside each verification month.

C3. Champion backup path

If the primary champion is travelling or in CAPA/audit mode, name a backup electrical or utilities owner before week 3. For family businesses, confirm WhatsApp is an acceptable channel. For listed parents, confirm whether plant P&L can approve opex under Rs 5 lakh without board paper.

C4. Red-team questions (ask yourself before send)

Is the DISCOM named the one on the invoice? Is the email pattern inferred only? Did we invent a bill band as fact? Did we lead with controversy? Did we propose control writes? If any answer is yes, rewrite before outreach.

C5. Final pre-send checklist

Confirm prospect_id matches campaign basename; strongest wedge sentence present; DISCOM token in section 2; at least three controversy/initiative bullets or explicit none-found with search terms; champion email first-backtick valid for mailto; cold-call Open/Hook/Proof/Ask quoted. Re-open company website homepage the morning of send — addresses and phones drift.

6.4 Evidence discipline and next research actions

This dossier separates three evidence classes. Verified public facts come from corporate websites, MCA aggregators, annual/BRSR filings, rating rationales, court databases and named LinkedIn profiles. Directional operating hypotheses use disclosed process profiles to decide what to check on the first call; they are not allegations of failure. Commercial estimates—especially monthly electricity spend—remain labelled [~] until the site provides a current HT invoice and production context.

Immediate sequence after first contact: (1) verify legal entity and invoice ownership; (2) collect two DISCOM invoices and document tariff, demand and PF lines; (3) identify the top three load events with the electrical/utility owner; (4) map production or quality constraints that cannot move; (5) agree the smallest controllable boundary for a 90-day trial. Security and governance: confirm permitted interface (historian export, meter CSV, secure file exchange) plus retention and OT approvals. No proposal implies PLC/DCS writes, recipe changes or unapproved remote control.

Treat adverse information proportionately. A negative search is not clearance that no legal, environmental, labour or financial issue exists. When a named proceeding exists, cite source, date, procedural status and exact entity; do not imply guilt or current business impact without reliable evidence. Re-check material sources and contact tenure immediately before a campaign send.