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

1. Company overview & snapshot

NATCO Pharma Limited is a listed Indian specialty generics / oncology-focused pharma company (group scale multi-thousand crore). The Dehradun / Selaqui finished-dosage (FDF) unit was NATCO’s first FDF plant (≈2006) and remains one of five+ formulations sites (Kothur, Nagarjuna Sagar, Vizag, Guwahati, Dehradun). Sustainability Report / AR materials cite Dehradun certifications including WHO-GMP and ISO 14001:2015 / ISO 45001:2018, plus group RE goals (25%+ of electricity from renewables FY24–25 group; planned additional 65 kW onsite solar at Dehradun among other sites). Group energy programmes mention VFDs, IE3 motors, BMS for HVAC/labs. Engineering Head on site: Sumeet Negi (Senior Manager Engineering, Dehradun since Sep 2023).

1.1 Legal identity & corporate structure

Listed NATCO Pharma Limited (Hyderabad). Dehradun is a manufacturing unit — HT account may still be NATCO Pharma Ltd. Directory addresses vary (Plot 19 Pharma City vs UPSIDC A-3 in lead report) — confirm plot and GSTIN on invoice. Corporate engineering sponsor P.S.R.K. Prasad (Director & EVP Corp Engineering) may own vendor standards centrally.

1.2 What they make & where money comes from

Finished dosages including oncology and niche generics for India and regulated exports. Dehradun historically exports-capable FDF. Energy cost is secondary to quality/compliance but material at HVAC base load.

1.3 Plants, addresses & footprint

Pilot: Selaqui / Pharma City Dehradun unit (exact plot confirm). Other FDF sites useful later for multi-site SEC benchmarking — not first pilot. HQ Hyderabad IR phone 040-23547532; investors@natcopharma.co.in.

1.4 Leadership & CRM map

Sumeet Negi — Engineering Head Dehradun (primary). Unit Head Dehradun — confirm. P.S.R.K. Prasad — corporate engineering. CMD/VC Nannapaneni family — do not cold-email. Path: Sumeet → Unit Head → Corp Eng if purchase order needs Hyderabad.

1.5 Recent news (24 months) & timing for Stamped

Group ESG solar roadmap to 2026–27; ISO certifications progressing across sites; cricket tournament posts confirm active Dehradun operations into 2026. No Dehradun-specific capacity crisis found. Timing: solar expansion narrative — wedge MD/hold after kWh share falls.

2. Energy profile

DISCOM / supply (name early): UPCL for Selaqui Pharma City. Always name UPCL in call prep.

2.1 Bill band, tariff & demand

Single FDF site at NATCO scale often ₹30–100+ lakh/month HT [~] depending on utilisation and HVAC. Group power numbers are not unit bills. Qualify Dehradun invoice separately.

2.2 Generation, fuel & renewables

Planned 65 kW Dehradun solar is small vs plant load — symbolic for RE %. Group wind/solar/PPAs mainly South India. Ask site DG and boiler fuel.

2.3 EnMS, PAT, ISO, BRSR

ISO 14001/45001 at Dehradun; energy conservation teams at group; ISO 50001 not asserted for Dehradun specifically. BMS mentioned at group. Strong Path A candidate.

2.4 Likely ₹ leak categories (hypothesis)

(1) AHU always-on between batches; (2) chiller/compressor MD; (3) solar reducing kWh but not MD; (4) legacy first-plant sequencing vs newer FDF sites; (5) WFI/PW; (6) PF.

3. Operations, equipment & digital stack

3.1 Process flow & critical loads

Standard OSD/FDF: dispensing → granulation/compression/coating → packing → warehouse with cleanroom HVAC hierarchy. Critical utilities: HVAC, chillers, compressors, purified water, dust extraction.

3.2 Shifts, seasonality, production pattern

Batch campaigns; regulatory shutdowns for maintenance. Normalise packs/batches.

3.3 Automation, metering, SCADA/EMS/DCS

Mature pharma automation + BMS. Expect historian; security review for vendor access.

3.4 Capex / tech projects affecting energy

Incremental solar and continuous upgrades; not a greenfield story — position as brownfield bill optimisation.

4. Stamped Energy fit analysis

4.1 ICP scorecard

Above Band A parent; unit must still clear ₹30L. Geography UK — pass. Corporate procurement — slower.

4.2 Fit score rationale

Fit 8/10 (Above Band A parent): technical champion on site; subtract Hyderabad CoE gravity.

4.3 Wedge (parser-critical)

The strongest wedge is: legacy Dehradun first-FDF HVAC and compressor sequencing versus the UPCL invoice after incremental solar — prove which clean-utility holds still own demand charge and assign ₹ actions without replacing BMS or writing setpoints.

4.4 Objections & competitors

“Group energy team already runs programmes” → unit bill proof still missing. “We have BMS” → BMS ≠ rupee prescriptions on UPCL. “ISO already” → continuous bill-tied EnMS.

4.5 Pilot design

Dehradun one HVAC/utility feeder, 90 days. Optionally compare SEC to one peer NATCO FDF later.

5. Before you reach out

5.1 Discovery checklist

• Exact plot + UPCL account.
• ₹ lakh/month; MD; solar export now.
• BMS vendor and export path.
• Sumeet vs Unit Head vs Hyderabad approver.
• Two bills + batch calendar.
• Any ZLD/ETP electrical share.

5.2 Do not lead with

• Do not lead with dashboards, AI buzzwords, generic ESG, or a promised percentage reduction presented as fact.
• Do not lead with oncology product claims.
• Do not open with Hyderabad IR.
• Do not confuse Mekaguda API energy stories with Dehradun FDF.

5.3 Opening hooks (email / call / WhatsApp)

“Dehradun was NATCO’s first FDF — after solar, which AHU holds still fail to reconcile to the UPCL MD line?“

6. Risks, flags, controversies & sources

6.1 Integrity / controversy / regulatory (search explicitly)

• Enterprise process: Long PO cycles.
• Regional Selaqui PCB studies: Historical academic/UPPCB cluster effluent studies name multiple pharma units generically — NATCO not isolated as a 2024–25 show-cause target in the July 2026 search sample.
• Litigation: No Dehradun-unit-specific major lawsuit found; group-level IP litigation is normal for specialty generics — irrelevant to plant energy pitch.
• Search: NATCO Pharma Dehradun/Selaqui + PCB, NGT, labour, lawsuit, FDA warning letter site-specific 2023–2026.

6.2 Data quality flags

• Plot number conflict across directories.
• Bill estimate only.
• s.negi@ email inferred from aggregator mask.

6.3 Sources consulted

• NATCO Sustainability Report / AR PDFs (admin.natcopharma.co.in).
• Sumeet Negi LinkedIn; Moneycontrol management page.
• SidculIndustries / Justdial directory pages (address cross-check).
• Lead report UK gap July 2026.

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.

6.4 Evidence discipline and next research actions

This dossier separates three evidence classes. Verified public facts come from company websites, CRISIL/ICRA ratings, BSE/NSE filings, press releases, and named LinkedIn profiles. Directional operating hypotheses follow from disclosed process (press lines, dairy utilities, fryers, forging, pharma HVAC/BFS) and are not claims about a specific machine failure. Commercial estimates—especially monthly electricity bills—remain estimates until the site shares a current HT invoice and production context.

Practical sequence after first contact: (1) verify legal entity and invoice ownership; (2) collect two DISCOM invoices with tariff, demand and PF lines; (3) identify the top three load events with the electrical/utility owner; (4) map production constraints that cannot move; (5) agree the smallest controllable boundary for a 90-day trial. Calculate demand, energy, reactive/PF and tariff components separately. Normalise against strokes, litres, batches or tonnes. Record baseline dates, shutdowns, commissioning, fuel/captive changes and weather-sensitive HVAC. Keep a decision ledger: recommendation, owner, due date, constraint, expected ₹ line, evidence, invoice result.

Security: confirm historian export, meter CSV or supervised read-only access; retention; IT/OT roles. No proposal implies changing PLC logic, recipes, interlocks, setpoints or operator authority. Treat adverse information proportionately — a negative search is not a clearance; a regional NGT matter is not automatic guilt for an unrelated site.

7. Extended plant diligence notes (Batch 4 depth addendum)

7.1 First-FDF legacy

Being NATCO’s first finished-dosage plant means legacy AHU sequences, older BMS quirks, and cultural “we’ve always run it this way” ballast. Newer FDF sites may already have tighter utilities discipline. The wedge is comparative without being insulting: what still fails to reconcile to UPCL here versus Kothur/Vizag? Sumeet Negi’s ISO 14001/45001 ownership shows process maturity — complement it with bill verification, don’t compete with EHS.

7.2 Solar optics vs MD reality

Group sustainability PDFs listing 65 kW additional Dehradun solar are easy to misread as “energy problem solved.” Quantitatively, 65 kW is a parking-lot gesture versus HVAC base load. Use the number gently: celebrate RE progress, then ask which demand spikes remain on the UPCL invoice.

7.3 Hyderabad CoE gravity

P.S.R.K. Prasad’s corporate engineering remit can override plant software choices. Pre-wire the pilot as a unit experiment with Hyderabad information rights, not a bypass. Share anonymised weekly prescription cards upward. Avoid surprising corporate Eng.

7.4 Address ambiguity

Directories disagree on plot numbers (Plot 19 versus A-3). First physical visit or invoice resolves it. Do not hard-code the wrong plot into legal docs.

7.5 Multi-site endgame

If Dehradun works, the account expands to other FDF sites as a benchmarking network — but sell one feeder first. Listed-company IR emails are last resort only; they create the wrong ticket type.

7.6 ZLD and ETP electrical share

Group ZLD narrative may include Dehradun effluent systems. Ask whether ETP/ZLD motors sit on the same HT account as HVAC — attribution matters for prescriptions.

8. Call-prep annex — NATCO Dehradun FDF

8.1 Sixty-second plant story (memorise)

NATCO’s Dehradun unit is the group’s first FDF plant, ISO 14001/45001 certified, with small additional solar planned. Group RE stories can hide residual UPCL MD from HVAC holds. The sell is legacy sequencing versus the bill — read-only on BMS/meters with Sumeet Negi as engineering head.

8.2 Corporate versus unit language

Never imply Hyderabad energy programmes failed. Ask what unit-level gaps remain after group initiatives. That framing keeps Sumeet safe in internal politics.

8.3 Sample discovery questions (extra)

• Exact plot and UPCL account number?
• BMS brand and historian export feasibility?
• Current onsite solar kW and monthly export?
• AHU count and classification mix?
• Who approves opex software under Rs 5L?
• Last unexplained MD event and its cost?

8.4 Benchmark optionality

If Dehradun succeeds, propose a lightweight SEC comparison to one peer FDF site — only after Hyderabad Eng blesses data sharing. Do not promise multi-site in the first email.

8.5 Regulatory blackout awareness

USFDA/EU/ANVISA histories at group level mean inspection seasons freeze OT experiments. Align 90 days with Sumeet’s inspection calendar.

8.6 Evidence pack for Corp Eng

Weekly cards: event time, feeder, expected Rs, owner, invoice line anticipated. That pack travels to Hyderabad better than a demo deck.

9a. NATCO Dehradun-specific contingency notes

If Hyderabad Eng asserts an existing EMS project, ask for the gap between EMS screens and UPCL lines — position as add-on. If 65 kW solar commissioning is imminent, fold it into baseline normalisation, not into “savings credit.” If Unit Head is rotational, keep Sumeet as the continuous technical thread.

9. Scenario planning & commercial contingencies

9.1 Three scenario tree

Scenario A — Fast proof: Bill clears the Band A floor, champion shares two invoices in week one, and Path A data export works. Compress discovery, issue first prescription cards by day 14, chase a clear invoice line by day 75.

Scenario B — Slow politics: Champion is interested but corporate or QA freezes vendor onboarding. Keep a monthly nurture with one process-specific insight; do not burn the economic buyer. Re-open after a dated event (COD, ISO audit, season peak).

Scenario C — Bill gate fail: Site is process-fit but HT spend sits under Rs 30 lakh/month. Offer Path B only if volatility or MD pain is extreme; otherwise park with a reminder to revisit after expansion.

9.2 Red-team of the wedge

Ask: could a competent internal electrical team get 60% of the value with a spreadsheet? If yes, Stamped must emphasise continuity, WhatsApp assignment, and DISCOM verification friction they will not sustain manually. Ask: is the wedge dependent on a single charismatic champion? If yes, recruit a deputy owner in week two.

9.3 Documentation pack for MSA later

Keep: invoice redactions, consumer number, sanctioned demand, feeder sketch, champion org chart, data access memo, kill criteria signed in email, weekly prescription log. These become the audit trail when finance asks why software opex exists.

9.4 Ethics and claims discipline

Do not overstate early-deployment percentages as guarantees. Label estimates. Do not invent lawsuits. Do not use Apollo. Do not commit hardware. Do not imply PLC writes. If a press or pharma quality constraint blocks a prescription, document and skip — credibility compounds.

9.5 Local logistics

Plan travel clusters: Greater Noida Ecotech + YEIDA Jewar in one day; Lucknow Gudamba + PTC SMTC in one trip; Selaqui HAB + NATCO in one morning; Haridwar Themis + Roorkee Axa in one SIDCUL/Roorkee loop. Carry printed one-pagers without confidential third-party data.

10. Source critique & residual unknowns (NATCO Dehradun)

NATCO sustainability PDFs are excellent for group RE and ISO status but coarse for unit bills. Directory plot conflicts (19 vs A-3) remain unresolved without invoice. Residual unknowns: Dehradun monthly HT, BMS vendor, Unit Head name, and whether Corp Eng has pre-selected an EMS incumbent. Sumeet Negi’s ISO posts are strong proof of engagement — use as rapport, not as permission. Re-read latest BRSR/SR before any claim about ZLD at Dehradun specifically.

11. Stamped operating principles for this account

Stay plant-first. Prefer one feeder over campus mythology. Prefer WhatsApp-assigned prescriptions over dashboard logins. Prefer DISCOM lines over kWh hero metrics. Prefer kill criteria over indefinite pilots. Prefer truth about unknowns over false precision. Re-validate champion LinkedIn tenure the morning of outreach. Never commit without two bills. Never write to PLCs. Never expand scope mid-pilot because the champion is friendly — expand only after invoice proof.

12. Outreach sequencing memorandum

Week 0: confirm LinkedIn tenure and email pattern offline. Week 1: LinkedIn connect + short email; request two HT bills. Week 2: 20-minute call using cold-call bullets; map DISCOM lines. Week 3: send written 90-day scope with kill criteria and feeder sketch. Week 4-12: if contracted, weekly prescription cards and invoice checkpoints. If no reply after two touches, try secondary champion once, then park with a calendar reminder tied to a plant event (COD, season peak, audit close). Never pile four channels in 48 hours — it reads as spam. Keep WhatsApp for after a warm yes or phone capture. Log every objection in CRM using the objection table in section 4.4 so future agents do not repeat failed angles. When a champion forwards internally, ask who now owns the decision and restart discovery with that person rather than assuming prior context transferred cleanly.

13. Final residual checklist before first send

Confirm prospect_id matches kit filename. Confirm DISCOM token appears in section 2 (UPCL or UPPCL/PVVNL/Madhyanchal as applicable). Confirm the phrase The strongest wedge is: appears exactly once. Confirm section 6.1 lists controversies searched or none found with terms. Confirm champion email first backtick is syntactically valid. Confirm no Apollo notes were required. Confirm plant phone confidence tag in kit. Print two bills request into calendar follow-up. If any of the above fails, stop and edit before outreach site publish.