A language model is a research assistant, never an oracle. That one sentence saves more money than any prompt technique, because almost every disappointment people report with AI in markets comes from asking it to be the second thing. The tool is not broken when it fails at prediction. It was never built to do prediction, and no amount of clever phrasing moves that boundary.
There is a line running through everything you might ask it to do. On one side sit tasks where the machine is genuinely, usefully strong — compressing long documents into structured summaries, holding one consistent checklist across many names so your screening does not drift when you are tired, and drafting a first version that you then verify. On the other side sit tasks it will attempt with equal confidence and fail at: predicting price, knowing anything outside what it was given, and telling you when it is unsure.
This article walks both sides of that line in detail, because knowing that the line exists is not the same as being able to locate it at nine in the morning with a filing open and a position to review. Then it gives you the one test that works when you are not sure which side you are standing on — a single question, borrowed from how you would treat a capable but unproven junior analyst.
The one thing to remember
AI is strong at compression, consistency and first drafts, and weak at prediction, anything it was not given, and knowing what it does not know — and one question tells you which side of that line you are on.
Where the Line Sits
The line is not really about difficulty. People assume the model must be better at easy questions and worse at hard ones, but that is not how it divides. It is excellent at a genuinely hard job — reading forty pages of dense management commentary and returning the six claims that matter — and useless at a question a child can phrase, which is what a stock does tomorrow.
The line is about whether the answer already exists in front of it. Compression, restructuring, comparison and drafting all work on material you supplied. The information is present; the job is transformation, and transformation is exactly what a text-completion machine does well. Prediction, recall of recent events and self-assessment all require something the model does not have in the room with it.
This is why the same tool can feel brilliant on Monday and reckless on Tuesday. Nothing changed about the tool. What changed was whether you handed it the material it needed. Once you start noticing that, the variability disappears and the machine becomes predictable — which for a research process matters far more than being impressive.
The map below is the whole article in one view. It is worth reading the third column first, because that column is where the work actually lives. Nothing on the strong side is trust-free; it is simply the side where your verification is cheap and quick rather than impossible.
The capability line
The line is not about difficulty. It is about whether the answer is already in the room.
| What you are asking for | Side of the line | What you must still do |
|---|---|---|
| Summarise this pasted annual report section | Strong — transformation of supplied text | Spot-check every figure against the page it cites |
| Apply the same eight checks to these twelve names | Strong — consistency across repetition | Confirm the checklist itself is the right one |
| Draft a comparison table from these two filings | Strong — structuring what is present | Edit it; treat it as a first pass, never a finished note |
| Where will this stock trade next week? | Weak — nothing supports an answer | Do not ask; the honest answer does not exist |
| What did the company announce recently? | Weak — outside what it was given | Paste the filing yourself, or do not ask |
| How confident are you in that number? | Weak — no internal confidence measure | Verify by category, not by how sure it sounds |
Strength One — Compression
The most valuable thing a language model does for a working trader is turn something long into something structured. A three-hundred-page annual report, a ninety-minute concall transcript, a twenty-page scheme document — these contain perhaps a dozen facts you actually need, buried in language designed to be thorough rather than readable. Extracting those dozen facts is real work, and the machine does it in seconds.
This works because nothing is being invented. You supplied the text. The model is rearranging material that is already in front of it, which is the operation it is genuinely built for. Ask for the same six headings every time — demand drivers, cost commentary, capital expenditure, debt, related-party items, anything management declined to answer — and you get a scannable brief where you previously had a wall.
What it buys you is not accuracy. It is coverage. Most retail research fails not because a number was wrong but because a document was never opened. Compression makes it realistic to actually read the filings for a watchlist of twenty names in an evening, which is a different quality of process from reading three of them properly and skimming headlines for the rest.
The discipline that makes it safe is a page reference beside every claim. Once the model must name where something came from, two useful things happen: your verification takes seconds instead of minutes, and a claim with no locatable source becomes visibly suspect rather than blending into the rest of the summary.
Work only from the document text I paste below. Do not use any prior knowledge of this company. Document: [name the filing and the section] Text: [paste the section here] Return exactly these six headings, in this order: 1. Demand and volume commentary 2. Cost and margin commentary 3. Capital expenditure and capacity 4. Debt, interest and cash flow 5. Related-party or one-off items 6. Not stated in this section Under headings 1 to 5, give at most three bullets each. Every bullet must end with the page or paragraph reference it came from, and must be traceable to a sentence in the text I pasted. Anything you expected to find but could not, list under heading 6. Do not estimate any number. Do not carry a figure forward from memory.
When to use — The first pass over any long document — annual report section, concall transcript, offer document — before you decide whether it deserves a full read.
A good answer — Short bullets, every one carrying a reference you can jump to, and a genuinely populated heading 6. A brief where every heading is full and nothing is missing usually means gaps were filled rather than reported.
Strength Two — A Checklist That Does Not Drift
Human screening degrades under repetition, and it degrades invisibly. By the twelfth name in an evening you are not applying the same eight checks you applied to the first. You are skipping the two that are tedious, weighting the one you find interesting, and quietly forming a view before the checks are done. Everyone does this. It is not a discipline failure; it is what attention does.
A model does not get tired and does not get bored. Give it the same eight questions against twelve different documents and it will ask all eight, twelve times, in the same order, with the same phrasing. That consistency is worth more than most people credit, because the value of a checklist comes entirely from its being applied uniformly. A checklist applied selectively is just a list of things you already believed.
This is also where the model complements rather than replaces you. Judgement about which eight checks matter is entirely yours — it depends on the sector, the setup, your own process and what you have been burnt by before. The machine contributes no view on that. What it contributes is the guarantee that check number seven gets asked at eleven at night with the same care as at eight in the evening.
The practical shape is one document per run, the same prompt each time, and output in a fixed format you can stack side by side. Twelve briefs with identical headings can be compared in one screen. Twelve briefs with different structures cannot be compared at all, which quietly defeats the purpose.
You will apply the same fixed checklist to one company at a time. Do not compare companies. Do not rank anything. Work only from the document I paste in this message. Company: [name] Document: [filing and period] Text: [paste here] For each of the checks below, answer in one sentence, then give the source sentence in quotes. If the document does not address a check, write exactly: NOT ADDRESSED IN THIS DOCUMENT. 1. What did management say about demand direction? 2. What did they say about input costs or pricing? 3. Was any capacity addition or capital expenditure mentioned? 4. What was said about debt levels or refinancing? 5. Were there related-party transactions or one-off items? 6. Was there any change in accounting treatment or segment definition? 7. Which analyst question was answered least directly? 8. What is stated here that would not appear in a headline summary? Do not add a conclusion, a rating, or a view on the stock.
When to use — Working through a watchlist. Run it once per name, in its own fresh thread, and keep the outputs side by side.
A good answer — Eight answers in the same order every single time, several of them reading NOT ADDRESSED IN THIS DOCUMENT, and no summary opinion at the end. If the structure varies between names, the outputs are no longer comparable and the exercise has lost its point.
Strength Three — The First Draft
A blank page is expensive. Getting a comparison table started, roughing out the structure of a thesis, listing the ways an idea could be wrong, converting your own scattered notes into something with headings — these are all jobs where getting to a bad first version quickly is worth more than getting to a good version slowly. Editing is faster than originating, for almost everyone.
The model is well suited to this precisely because a draft carries no authority. Nobody acts on a draft. Its errors are supposed to be found and fixed, which means the technology’s central weakness — confident wrongness — is contained by the format itself. You were always going to rewrite it.
The most useful drafting job in market work is the inversion. You have formed a view; ask the model to construct the strongest case against it using only the document you supplied. It has no ego and no position, so it will do this cleanly. You keep the argument, discard the rest, and you have stress-tested a thesis in two minutes rather than waiting for the market to do it for you.
The failure mode here is subtle and worth naming. A fluent draft is persuasive by construction, and after two edits it starts to feel like yours. Keep drafts visibly separate from verified notes — a different file, a different colour, a header that says DRAFT. Anything that quietly graduates from draft to research without a verification step in between is a problem waiting for a bad quarter.
Watch out — A draft that has been lightly edited feels like your own work within about ten minutes. Keep AI output in a separate file from verified notes until every figure in it has been checked against its source.
Weakness One — Price Prediction
Nothing on this planet can tell you where NIFTY closes tomorrow, and a language model is further from being able to than most things, because it has no market data, no model of price and no forecasting mechanism of any kind. Ask it anyway and you will get an answer, because producing an answer is what it does. The answer is a plausible-sounding sentence, and that is all it is.
It is worth being precise about why, since the reason is not merely that markets are hard. A language model has learned the patterns of how people write about markets. So when you ask where a stock goes next, the machine reproduces the shape of market commentary — a level, a condition, a hedge, a target. It is a very good imitation of an analyst’s sentence, generated with no information about the stock at all.
This also covers the questions that are price prediction in disguise, which is most of the ones people actually type. Is this a good entry. Should I hold this through results. Will this breakout hold. Each of those requires knowledge of the future, and each will receive a confident reply. The reply tells you what market commentary usually sounds like. It tells you nothing about your position.
The reframe that works is to convert every prediction question into a fact question. Not "will this breakout hold" but "list every statement in this filing about order book and capacity, with references". Not "should I hold through results" but "what did management guide to last quarter, in their own words". The model can genuinely help with the second version of each. The decision stays where it belongs, which is with you.
Asking a model to compress a forty-page report is using the tool. Asking it whether a stock will go up is using the tool as a mirror for what you already hoped.
Weakness Two — Anything It Was Not Given
The model knows what it learned up to its training cutoff, plus whatever you paste into the conversation. That is the complete list. It has no live feed, no access to the exchange website, no view of your holdings, and no knowledge of the filing that came out this morning unless you put it there yourself.
The failure is not the ignorance. Ignorance is fine and expected. The failure is that the machine cannot perceive its own boundary. There is no internal signal that says this question lands outside what I have. So a question about last week’s board meeting outcome gets the same fluent treatment as a question about a document sitting in the prompt, and the two answers look identical on the page.
This is also true within a document. If you paste chapter four and ask about something discussed in chapter nine, the model will not say that chapter nine is missing. It will answer from general knowledge of how such things usually read, which is exactly the situation where a plausible fabrication is most likely and hardest to catch, because the answer is in the right register and about the right company.
The habit that solves it is unfashionably simple. For anything time-sensitive or document-specific, supply the material. Then ask, in the same prompt, for the source sentence behind each claim. A model working over pasted text with a citation requirement is a substantially different tool from a model asked to recall — same machine, completely different reliability.
Pro tip — Before asking anything about a company event, ask yourself one question: have I given it the document, or am I asking it to remember? If it is remembering, the answer is decoration. Go and paste the filing.
Weakness Three — It Cannot Flag Its Own Doubt
You are used to reading confidence as information. A colleague who is sure of a figure says it flatly; one who is guessing hedges, slows down, or offers to check. That signal is genuinely useful with people and completely absent here. The model has no internal measure of whether a statement corresponds to anything real, so it has nothing to hedge with.
What you get is a uniform surface. A correctly extracted figure and an invented one are written with the same assurance, the same supporting detail, the same willingness to elaborate if you ask a follow-up. Ask it directly how confident it is and you get another generated sentence — the text that plausibly follows a question about confidence, not a reading from any gauge.
The consequence is more practical than it first appears. You cannot triage. With a human analyst you check the claims they seemed shaky on and take the rest on reasonable trust, which is what makes working with people efficient. Here there is no shakiness to detect, so triage by feel is not merely unreliable — it is actively misleading, because the fabricated claims are often the most fluent ones.
So verification has to be organised by category rather than by impression. Every number that will touch a position gets checked. Every citation gets opened. Every claim about anything after the cutoff gets sourced or deleted. That sounds heavy until you notice it applies to a handful of lines in a page-long brief, and that the alternative is trusting a signal that does not exist.
The One Test — The Junior Analyst Question
When you are unsure which side of the line a task sits on, ask yourself one question: would I accept this from a junior analyst without checking their sources? Not a bad analyst — a capable, hard-working one who has been with you a few weeks and whose judgement you have not yet had a chance to calibrate.
If the answer is yes, the model has almost certainly done its job. A structured summary, a first-pass comparison, a consistently applied checklist, a rough draft — you would take all of these from a new junior and work with them, precisely because their errors are the kind you would catch while working. That is the strong side of the line.
If the answer is no — if it is a specific figure, a claim about a specific filing, or anything that will move a real position — then the model’s job is finished and yours begins. You would not let a new junior’s number go into a decision unchecked, and you have far more reason to check this one, because at least the junior would have told you they were unsure.
There is a shorter version for when even that feels like too much thought. Ask: if this is wrong, how would I know? If you have a concrete answer — page eighty-two of the annual report, the filing on the exchange website, the transcript you have open — proceed. If you have no way to find out, you are not looking at research yet. You are looking at a well-written suggestion of what research might say.
Would I accept this from a junior analyst without checking their sources? Yes means the tool did its job. No means the tool is finished and you have started.
Standing on the right side of the line
Do
- Hand it long documents and ask for structure, headings and references — the work it is genuinely built for.
- Reuse one fixed checklist across every name so your screening stays uniform when you are tired.
- Ask it to argue against a view you already hold, using only the document you supplied.
- Rewrite every prediction question as a fact question about material you have pasted.
- Check every figure that will touch a position, regardless of how assured the text sounds.
Don't
- Do not ask where a stock or index will trade — the honest answer does not exist and you will still get one.
- Do not ask about recent events without pasting the source document into the prompt.
- Do not use confidence, detail or fluency to decide which claims deserve checking.
- Do not let a draft become a research note without a verification pass in between.
- Do not ask it to decide anything; the decision is the part that is legally and practically yours.
Before an AI output enters your research notes
Five questions. On a page-long brief this takes a couple of minutes, and it is the difference between a research process and a well-formatted guess.
- Was the source material supplied by me, or is this the model working from memory?
- Does every figure carry a page, paragraph or sentence reference I can actually open?
- Is anything here dated after the model’s training cutoff and not backed by something I pasted?
- Have I opened the primary document for the one number this decision actually rests on?
- If this claim turns out to be wrong, do I have a concrete way of finding that out?
Common questions
No. A language model holds no market data, no price model and no forecasting mechanism — it produces the text that plausibly follows a market question. What comes back imitates the shape of analyst commentary. Predictive machine-learning models are a different technology entirely, and even those express statistical tilts rather than forecasts of a level.
Knowledge Check
You paste a concall transcript and ask for the six main points with source sentences. Which side of the capability line is this?
Written By
Rohit Singh
Mr. Chartist
With 14+ years of experience in Indian financial markets, Rohit Singh (Mr. Chartist) is a SEBI Registered Research Analyst, Amazon #1 bestselling author, and the founder of Investology — a premium trading ecosystem trusted by a 1.5 Lakh+ strong community across India.
Keep reading
What AI Actually Is in a Trading Context
Four different technologies wear the same label. Knowing which one you are holding decides what it is safe to use it for.
Research CraftHallucination and the Audit Trail — Verify Everything That Moves Money
A wrong answer and a right answer arrive in identical tone. Tone is not a reliability signal, so the defence has to be procedural.
Governance & PracticeGuardrails, SEBI and the Human in the Loop — Where AI Ends and Advice Begins
Advice is a regulated activity with a named, accountable person behind it. A model has none of that, and cannot acquire it.
