TLDRocket
Sign in

Don't go all in on AI

LeanIX Engineering

A team tried to make a pharma AI agent do everything, and it broke. They had to swap in fixed tools for the parts that never change.

Based on reporting by LeanIX Engineering — read the original for the full story.

Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error

Agents are the hot thing right now, but this pharma project is a neat reminder that “more agentic” is not a strategy. The team behind it started with a system that tried to do everything through an LLM, from checking sales changes to figuring out why they happened. It sounded elegant. It also produced shaky reports, missed root causes, and recommendations that weren’t sharp enough for the client.

The use case itself was simple enough to describe: compare last month’s sales with the same month a year earlier, look for a meaningful change, and then investigate what caused it. If the decline was real, the system would propose how to reverse it; if the growth was real, it would suggest how to repeat it. But once the whole thing was left to the model, the process started wobbling. Sometimes steps were skipped. Sometimes the comparison took a different route. That sort of flexibility is useful when the problem is fuzzy. It’s a liability when the procedure is supposed to be the same every time.

So the team carved out the parts that were really fixed. The anomaly detection step now runs through a deterministic pipeline that checks sales data in Databricks, groups it by region, ranks regions by performance, compares the current month with the same month last year, and assigns a score from 1 to 10, with 5 meaning no change, 10 strong growth, and 1 decline. Only after that does the agent step in to reason over the result.

They made the same move in the investigation phase. Instead of letting the agent wander through the data however it liked, they set up deterministic tools for things like subscription counts, drug subsidies, and prescriptions per patient. The thinking is plain: there’s no prize for being creative about which data to fetch when the domain already tells you what matters. Once the facts are gathered, the agent can do the part that actually benefits from flexibility.

That’s the useful lesson here. Not “agents failed,” and not “deterministic systems win.” The real trick is knowing where the process needs judgment and where it just needs to stop improvising. A lot of AI projects are going to discover that the expensive part is not the model, but the humility to fence it in.

My take — AI-written commentary, not fact-checked reporting

This is the part of AI everyone keeps relearning: hype loves autonomy, but production loves guardrails. The smartest teams are not the ones that make everything agentic; they’re the ones that notice where the system is pretending to be clever. The rest is just a very expensive way to rediscover workflows.

Read more about this at: LeanIX Engineering

Related stories

The daily briefing

Every AI story that matters, in your inbox by 8am.

TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the day in two minutes. Follow companies and topics for alerts, or get the briefing in Slack. Free, no spam, unsubscribe anytime.