1. Company overview & snapshot

1.1 Legal identity & corporate structure

Fine Organic Industries Limited (CIN L24119MH2002PLC136003; NSE: FINEORG; BSE: 541557) is a listed specialty-additives manufacturer. It was incorporated in 2002, succeeding earlier business activity that traces to 1970. Public company sources identify Mukesh Maganlal Shah as Chairman, Jayen Ramesh Shah as Managing Director and Tushar Ramesh Shah as CEO/Executive Director. The company has overseas subsidiaries and joint ventures, including Fine Organics USA, Fine Organics Europe and Fine Zeelandia; those are not assumed to own Maharashtra utility bills.

1.2 What they make & where money comes from

Fine Organic develops plant/oil/oleochemical-based additives for food, polymers, coatings, personal care, feed and other applications. Public profiles cite more than 600 products, sales in roughly 80 countries, and a material export mix. Product families include food emulsifiers, polymer additives, release agents, specialty esters, coating and cosmetic ingredients. Its process mix is more energy-relevant than a simple blender: fatty-acid esters and specialty derivatives can involve heating, reaction, distillation/vacuum, cooling, drying, transfer and packaging. Exact unit operations differ by product and must be confirmed at the chosen pilot site.

1.3 Plants, addresses & footprint

Public materials report seven manufacturing facilities across Ambernath, Badlapur, Dombivli and Patalganga, a Navi Mumbai R&D facility, and multiple zero-liquid-discharge plants. A public source says the original Dombivli facility began in 1973; expanded Ambernath facilities followed; Patalganga is a newer food-ingredient/manufacturing location. This dossier recommends Ambernath as the named outreach site because it is a long-standing core cluster, but it does not assume it is the highest-bill consumer. Ask the company to nominate the largest MSEDCL-connected controllable plant—potentially Ambernath or Patalganga.

1.4 Leadership & CRM map

Tushar Shah is the public executive route, with Jayen Shah as managing director and Sonali Bhadani identified publicly as CFO. No verified plant electrical/utility-head profile was located in this scan. The useful CRM sequence is corporate sponsor → nominated Maharashtra plant head → electrical/utility/process-engineering owner → finance controller. The personal email in the kit is inferred and must not be treated as a verified contact.

1.5 Recent news (24 months) & timing for Stamped

Public financial/profile sources report plant capacity utilisation near full levels, a Dombivli R&D pilot plant becoming operational, and environmental clearance for a JNPA SEZ project under a subsidiary. Capacity, pilot commercialization and distributed manufacturing make plant-level cost and normalised energy evidence timely. A 2024 Badlapur fire/restoration reference appears in secondary web results; verify primary exchange disclosure before quoting any details in outreach.

2. Energy profile

DISCOM / supply (name early): MSEDCL. Ambernath, Badlapur, Dombivli and Patalganga manufacturing sites should be approached as MSEDCL industrial accounts pending confirmation. Each may have a separate consumer, tariff and billing entity.

2.1 Bill band, tariff & demand

At approximately ₹3,000 Cr FY25-scale revenue and multiple specialty-chemical plants, a pilot-site electricity bill of ₹30 lakh–₹1 crore+/month [~] is plausible but not published. Obtain bills before asserting qualification. Inspect HT/EHT status, CMD/recorded MD, kVAh/PF adjustments, ToD windows, taxes/duty, solar/open-access settlement, process fuel substitutions and the correct plant legal entity. Thermal fuel may be a substantial energy cost, but Stamped’s bill-verification offer is initially focused on the electricity invoice.

2.2 Generation, fuel & renewables

No specific public captive solar, open-access PPA, DG capacity, boiler fuel or steam network was verified in the search. Chemical-process energy could include electricity plus thermal utilities; never infer an onsite boiler, fuel or renewable asset from the product category. Ask which batches rely on steam, thermic fluid, electric heating, chilled water or vacuum, and where electricity data can be linked to production.

2.3 EnMS, PAT, ISO, BRSR

Listed-company environmental and quality reporting is likely, and public profiles mention ZLD facilities; neither proves ISO 50001, PAT status or a particular EMS vendor. Verify current BRSR/annual-report energy metrics and site certificates. A plant may have strong compliance systems but still lack a closed operational loop from batch event to MSEDCL bill.

2.4 Likely ₹ leak categories (hypothesis)

Potential levers are reactor/esterification campaign overlap, heating and vacuum scheduling, cooling tower/chiller and pump base load, compressed-air leakage, off-shift HVAC, PF drift and coincident batch starts. Use them as questions. A batch that requires temperature hold for quality or safety is not an idle-load candidate without process-owner approval.

3. Operations, equipment & digital stack

3.1 Process flow & critical loads

Likely steps include receipt/storage of oils and fatty acids, reaction/esterification or blending, heating/cooling, separation/distillation where relevant, filtration, quality control, packing and dispatch. Candidate electrical loads are agitators, pumps, vacuum systems, chillers/cooling towers, air compressors, transfer systems, packaging and HVAC. Product grade, reaction route and safety controls determine flexibility.

3.2 Shifts, seasonality, production pattern

The company does not publish plant shift rosters. Demand can vary with product mix, export schedules, monsoon/cooling conditions, campaign lengths and maintenance shutdowns. Ask for batch start/end records, production volume, cleaning/changeover events and critical product constraints. Normalise bill comparisons for production, weather and batch mix.

3.3 Automation, metering, SCADA/EMS/DCS

No named DCS, SCADA or EMS was verified. Given the process profile, a DCS/PLC and plant utilities instrumentation are plausible but unconfirmed. A safe entry is read-only interval data from the incomer, key utility feeders, batch timestamps and bills. Where access is initially limited, MSEDCL bills plus a utility/batch log can establish whether a deeper integration has value.

3.4 Capex / tech projects affecting energy

The Dombivli R&D pilot plant and reported JNPA SEZ clearance are relevant future-baseline events. Do not mix new/pilot loads with steady manufacturing in an M&V baseline. Focus the first proof on an established, stable line/utility system.

4. Stamped Energy fit analysis

4.1 ICP scorecard

Fine Organic passes revenue, process intensity and multi-site potential. Maharashtra sits outside North-India-first focus, so it is a strategic expansion account. The bill floor, selected plant, MSEDCL account and local decision speed remain unverified. Listed-company systems may increase security/compliance requirements.

4.2 Fit score rationale

Fit score: 8/10. Scale, batch-chemical utility complexity and multiple plants give a high technical ceiling. Score is capped by West-India geography, the absence of a verified plant champion and no public plant-specific bill/SCADA evidence.

4.3 Wedge (parser-critical)

The strongest wedge is: at the largest controllable MSEDCL plant, connect batch and utility timing to the electricity bill so reactor/thermal campaigns, cooling, compressed air, PF and demand events become approved, production-normalised ₹ actions rather than periodic energy-review observations.

4.4 Objections & competitors

Expect: “we have compliance/ZLD/quality systems,” “batch holds cannot move,” and “corporate already tracks energy.” Acknowledge process and safety limits. Stamped does not alter recipes or sell an ESG dashboard; it tests permitted scheduling/utility actions and verifies the bill impact. Existing DCS/EMS, internal EHS, audit consultants, APFC/utility vendors and major energy platforms are alternatives.

4.5 Pilot design

Choose Ambernath only if it is the qualifying, accessible account; otherwise choose the largest MSEDCL facility. Gather six to twelve bills, interval data, batch/utility schedules and a named plant owner. Start with one stable production/utility area and approved action classes—noncritical start sequencing, cooling/air baseline, PF review or off-shift utility discipline. Success requires normalised invoice improvement with no quality/EHS compromise. Kill if the site bill is below ₹30L/month, process data cannot be contextualised or the plant has no operational sponsor.

5. Before you reach out

5.1 Discovery checklist

• Confirm Ambernath versus Patalganga/Badlapur/Dombivli as the highest-bill MSEDCL site.
• Verify legal consumer, HT/EHT status, bill band, CMD/MD, PF/ToD and energy-data access.
• Map batch routes, fixed process holds, thermal/electric utility split and quality guardrails.
• Identify plant head, utility/electrical owner, process engineer and finance validator.
• Ask whether DCS/SCADA/EMS exports can be provided read-only.
• Exclude new R&D/expansion commissioning loads from the initial baseline.

5.2 Do not lead with

• Do not lead with generic sustainability, ZLD, solar or “AI dashboard.”
• Do not claim all reactors/thermal holds are movable.
• Do not quote an MSEDCL bill band or savings before documents confirm it.

5.3 Opening hooks (email / call / WhatsApp)

“For Fine Organic, the first question is not a new energy platform. It is whether one MSEDCL plant can connect approved batch and utility timing to MD, PF and invoice outcomes—without touching recipes or quality.”

6. Risks, flags & sources

6.1 Integrity / controversy / regulatory (search explicitly)

Searches for “Fine Organic Industries controversy”, “Fine Organic pollution/NGT”, “Fine Organic fraud”, “Fine Organic lawsuit” and regulator variants found no credible company-specific court, integrity or pollution outcome that can be asserted in this dossier. Secondary results referred to restoration after a Badlapur fire; that operational item should only be used after checking the company’s official disclosures. This negative result is not legal clearance.

6.2 Data quality flags

• Individual MSEDCL accounts, bill bands, meter architecture and utility mix are not public.
• Exact Ambernath address/selected production unit needs confirmation.
• Personal champion email and LinkedIn are inferred/unverified.
• Secondary financial aggregators disagree on some figures; use FY25 filings for final numbers.

6.3 Sources consulted

• https://www.fineorganics.com/
• https://www.venturasecurities.com/invest/stocks/FINEORG
• https://www.globaldata.com/company-profile/fine-organics-industries-ltd/
• https://www.thecompanycheck.com/company/fine-organic-industries-limited/L24119MH2002PLC136003
• https://blinkx.in/stocks/fine-organic-industries-ltd
• Targeted company, LinkedIn, controversy and regulatory web searches, 13 July 2026.

6.4 Multi-site selection and batch-process baseline protocol

Fine Organic should not receive a generic “all Maharashtra sites” proposal. Its distributed footprint makes the first decision a site-selection exercise. Ambernath is the outreach anchor because of its established manufacturing history, but the correct pilot is whichever MSEDCL consumer has the highest controllable electricity cost, usable meter data, a stable operating period and a local sponsor able to execute actions. Patalganga may be more suitable if its newer capacity is large and sufficiently stable; Dombivli may be unsuitable if R&D/pilot activity makes production normalisation difficult. Badlapur should be selected only after a current operating and compliance context is confirmed.

For each candidate site, request the legal consumer name, 12 months of MSEDCL bills, contract demand, recorded MD, PF/kVAh treatment, ToD bucket data, solar/open-access/Captive arrangements, DG usage and a high-level layout of electrical incomer and utility feeders. Ask the plant to indicate which loads are production-critical and which can be timed or shut down under approved conditions. This avoids conflating group revenue with plant electrical demand and prevents an estimate from becoming a sales claim.

The operating baseline should combine invoice data with batch context. A useful minimum data sheet records product family, batch quantity, start/end time, reactor or vessel assignment where available, heating/cooling demand, vacuum or separation status, cleaning/changeover, utilities in service, planned downtime and abnormal events. Product grades may have radically different thermal and mixing requirements; energy-per-month or energy-per-tonne without grade context can mislead. A plant does not need to share sensitive formulations for this purpose—coded product families and state changes can be enough.

The first review should distinguish electricity cost from thermal fuel, steam and ETP cost. A batch process may have a high energy problem that does not appear in the MSEDCL invoice, or a large electricity bill dominated by cooling, pumping and compressed air. Stamped’s immediate proof is bill-linked, therefore the team should identify what is both economically material and visible in the electricity data. If the best opportunity is a boiler firing or thermic-fluid optimisation outside that boundary, record it as a referral/discovery item rather than promise it as an electricity-bill saving.

6.5 Safe action library and M&V rules

Potential action classes require process and EHS approval. They may include scheduling flexible utility starts so they do not coincide with reactor/centrifuge/pump demand; identifying cooling-tower, chilled-water or compressed-air base load during validated idle windows; checking compressor control bands and leak-driven runtime; investigating PF deterioration against the actual invoice; and reviewing whether noncritical transfer/packing work can occur in a lower-cost time window. They do not include changing a reaction recipe, shortening a mandatory hold, reducing agitation necessary for quality or safety, changing solvent handling, or bypassing an emissions/ETP process.

For maximum demand, compare like days with similar production/batch state and log all material starts at the peak. For compressed air and cooling, compare approved idle periods while controlling for ambient conditions and mandatory safety ventilation. For PF, isolate the bill adjustment, check instrument integrity and establish whether capacitor-bank maintenance or operating loads explain the variance. For tariff timing, only shift work that the production owner says is flexible. Every prescription should identify the responsible role, expected ₹ range, operational guardrail, execution evidence and whether the next invoice supports the result.

Before calling a reduction “verified,” finance and operations should agree on a counterfactual: same grade, comparable ambient/season, comparable batch volume, no major outage, no rate/tariff revision and no new-capacity commissioning. If such a comparison is impossible, state the outcome as an observed operational improvement rather than a verified bill saving. This is especially important around the Dombivli pilot plant or a new Patalganga/SEZ capacity event, where production mix and commissioning can distort a monthly trend.

6.6 Buying process, commercial framing and disqualifiers

The initial message should request a 20-minute site-selection call, not a full group rollout. A corporate executive can sponsor an introduction, but the technical discovery should include a plant manager, utilities/electrical owner, process representative and finance reviewer. Ask who owns MSEDCL demand charges, who receives utility alarms, which recommendations currently stall, and whether the plant can approve a read-only 90-day operating proof without a long group procurement cycle.

The right commercial frame is a bounded Bill Verification Program: one site, a defined data set, two or three action categories, process/EHS guardrails and a shared calculation method. The commercial decision comes after the bill gate, not before. Do not cite a 12–20% benchmark as a promise; public evidence does not establish Fine Organic’s avoidable portion after existing controls. A credible first promise is to identify or reject one bill-linked operational lever.

Defer if the selected account is below ₹30L/month, the bill is entirely controlled through non-operational procurement terms, all material loads are safety/quality fixed, plant leadership cannot assign an owner, or data cannot be shared even at aggregate/bill level. These stop conditions are a quality filter, not a reason to pressure a site into an unsuitable pilot.

6.7 Plant walk-through agenda and data minimisation

The first site walk-through should be no more invasive than necessary. Start at the incomer/control room to establish meters, bill ownership and interval-data availability; then map utilities before entering process areas: cooling water, chilled water, compressed air, vacuum, electrical rooms, pumping/transfer and packing. Follow that with a process-owner discussion of batch timing, mandatory holds and changeovers. This order keeps Stamped from presenting a process theory before the plant supplies the operational facts.

Ask for a block diagram rather than confidential P&IDs or formulations. Mark which utility loads serve one process, which are shared, which run on standby and which cannot be interrupted. A practical output is a “three feeder / three event” shortlist: one demand-coincidence candidate, one idle/base-load candidate and one PF/tariff question. The plant can then decide whether the economics merit a deeper data connection.

Data minimisation is especially useful for a specialty-additive producer. Stamped can request time-stamped operating states and coded grade families, not customer names, ingredient recipes, proprietary quality results or export contracts. An agreed data-retention, read-only access and role-based-review plan should be set before data is transferred. This addresses valid listed-company and IP concerns without reducing the project to a dashboard exercise.

6.8 Specific pilot review cadence

Run an initial bill/data review in week one; validate the utility and batch map in weeks two and three; issue only approved prescriptions thereafter. A weekly plant review should discuss actions completed, exceptions, production changes, upcoming campaign changes and whether the expected bill mechanism remains valid. At month end, operations and finance reconcile observed data and list confounders; do not wait until day 90 to discover that an output or tariff change invalidated the comparison.

At day 90, the decision should be explicit: expand to a second site, maintain the current operational queue, redesign scope around a different utility/system, or exit. A multi-site company can benefit from a common operating taxonomy, but only after the initial site establishes a valid MSEDCL-linked proof. Copying a reactor schedule or cooling setpoint between Ambernath and Patalganga without local process confirmation would be unsound.

The proposed cadence gives the company an audit trail: every candidate has an operational owner, safety/process approval, estimated value, execution date, measured outcome and stated caveat. That evidence is more useful to finance and internal sustainability reporting than a dashboard trend alone.

Any cross-site expansion must repeat bill and safety qualification. Similar products do not guarantee identical utilities, tariff exposure, process routes or local decision rights.

Before scale-up, finance should confirm that plant-level invoice improvements reconcile to the group’s management accounts. This protects against mistaking allocation or accounting treatment for a realised operating saving.