Fdc Sales: Mis

But who? A rep desperate to meet target? A stockist colluding with a retailer? Or the MIS itself—not the software, but the people who controlled what data entered it.

Arjun clicked into the MIS module that tracked prescription audits . The software was expensive, licensed from a US vendor, and meticulously built. It aggregated data from 1,200 chemists across his zone. Every time a bill was generated for Nebuflam-D, the system recorded it. Every time a doctor’s prescription was scanned at a pharmacy loyalty program, the system knew. Fdc Sales Mis

And yet, week four of the launch, the MIS dashboard showed a flat green line where a hockey stick should have been. But who

“Rajesh gave me these,” she whispered. “He said, ‘Just enter them. The system will never know. The expiry dates are old anyway.’” Or the MIS itself—not the software, but the

Arjun did something unorthodox. He opened the raw SQL database behind the MIS—the tables the dashboards were built on. He wrote a query to join prescriber data with patient redemption data with stockist return data . Then he looked at the time stamps.

Arjun realized the MIS had no field for retailer anxiety . No column for patient self-medication . No variable for regulatory trauma .

The drug was called Nebuflam-D . A fixed-dose combination of an expectorant, a low-dose steroid, and a novel mucolytic. It was supposed to be a blockbuster for chronic bronchitis. The clinical trials were solid. The pricing was aggressive. The sales force was incentivized to the teeth.