Deep Research

Spreadsheet. That is where many impressive AI research reports quietly go to die. A model can browse twenty web pages, produce a polished executive memo, cite three market reports, and still fail at the boring part: comparing numbers, checking whether a table supports a claim, generating the right chart, and then explaining what the chart actually means. The output looks like research. The mechanism underneath is closer to literary confidence with a browser tab. ...

A spreadsheet is a cruel test of artificial intelligence. Not the toy spreadsheet used in demos, with six rows, three columns, and a suspiciously cooperative universe. I mean the kind of table a real analyst asks for: every qualifying supplier in a region, every product SKU released over a decade, every regulatory filing matching a narrow condition, every competitor with exact addresses, dates, sources, and no missing cells because apparently human suffering needs columns. ...

Search is easy to admire because it looks busy. The agent opens pages. It follows links. It finds PDFs. It writes Python. It returns a neat JSON object, ideally with the confidence of someone who has just discovered government statistics. This is the part of AI demos that makes executives lean forward: the machine appears to have become an analyst. ...

Research agents have a bad habit that will feel familiar to anyone who has watched a junior analyst “verify one more source” for three hours. They search. They visit. They re-search. They validate the thing they already validated. Then, because the context window is now full of debris, they occasionally forget the actual question. A triumph of diligence, perhaps. A triumph of intelligence, less obviously. ...

Deals are not usually lost because nobody wrote a beautiful market summary. They are lost because the right asset sat in a regional announcement, under a local-language alias, attached to a company page, trial registry, conference PDF, or corporate filing that nobody searched properly. Then, six months later, the same asset appears in a large-pharma partnership press release, and everyone acts surprised. The surprise is often very well-formatted. That does not make it useful. ...

A research request usually begins with a deceptively harmless sentence: “Can you give me the full picture?” Then comes the usual enterprise ritual. Someone breaks the topic into pieces. One person checks competitors. Another checks regulation. Another reads technical reports. Another searches recent news. Everyone works quickly. Everyone returns with fragments. Then one unlucky analyst stitches the fragments into a report and pretends the seams are a design choice. ...

Workflow is the unglamorous part of agentic AI. Which is precisely why it matters. A research agent can have a strong language model, a decent search tool, and an impressive ability to produce paragraphs that sound like a McKinsey intern who drank too much espresso. Yet when the task becomes long, ambiguous, and evidence-heavy, the same agent often fails for a boring reason: it does the right actions in the wrong order, repeats the same weak search, summarizes too early, forgets to verify a source, or changes its own instructions so enthusiastically that it becomes a different employee halfway through the job. ...

A research agent enters a company budget meeting. That sounds like the beginning of a bad consulting joke, but it is exactly where “deep research” systems are heading. The first generation of excitement was about capability: can an AI agent search, plan, decompose, synthesize, and write a report that feels less like a chatbot answer and more like an analyst memo? Fine. The next question is less glamorous and far more operational: can the company control how much research the agent performs before the invoice becomes a small weather event? ...

A research workflow usually starts clean. The first search is sensible. The first source is relevant. The first reasoning step looks promising. Then the agent opens five webpages, follows a few tangents, remembers an early mistake too faithfully, and keeps dragging the whole mess forward like a consultant who refuses to delete old slides. By the time the problem actually becomes difficult, the model is no longer short of information. It is drowning in it. ...

The Missing Metric: Measuring Agentic Potential Before It’s Too Late Procurement teams love a leaderboard. It is tidy, numeric, comparable, and therefore dangerously comforting. A model scores well on MMLU, looks respectable on GSM8K, passes a coding benchmark, and suddenly someone in a meeting says it is “agent-ready.” Lovely. By that logic, a person who passes a written driving test should be handed the keys to a forklift in a crowded warehouse. ...