Prompt Library

How to do market research with AI

Not a summary of what's on page one of Google. Sai works a market the way an analyst does — sizing it, mapping the players, finding the buyers' actual complaints, and telling you where the evidence runs out.

The PROMPTS
Copy prompt
Research [topic / market] for me and come back with a structured brief I can act on, with every claim sourced. Tell me first if you need me to narrow anything. Otherwise, cover: 1. What this market is and how it's currently defined — including where sources disagree 2. Size and growth: [TAM / SAM, recent growth rate, the numbers people actually cite] 3. The main players, what differentiates each, and where the gaps are 4. Who the buyers are, what they're actually trying to solve, and what they complain about 5. What's changed in the last [12 months] — funding, entrants, regulation, shifts in demand 6. The counter-case: what would make this market less attractive than it looks For each section, cite your sources inline and flag anything where the evidence is thin or the sources contradict each other. Don't smooth over gaps — tell me what you couldn't find. Put it in a [Google Doc], structured with headers so I can drop sections straight into a deck, and send me the link with a three-line summary of what surprised you.
Run this TaskView Demo

Platforms this prompt works across

The problem was never access to information

Market research used to be gated by data. It is now gated by synthesis. Everything you need for a first-pass view of most markets is public — analyst summaries, funding announcements, review sites, job postings, earnings commentary, forum threads where the actual buyers complain in specific detail. The work is not finding it. The work is reading enough of it to know which parts are load-bearing and which are one consultancy's projection being quoted back and forth until it sounds like consensus.

That is the job worth handing to an agent, and it is also where most AI research falls down. Ask a model to research a market and you typically get a fluent, confident document that reads well and cannot be checked. The fluency is the problem: an unsourced claim and a well-evidenced one look identical on the page.

What a defensible research pass looks like

The difference between output you can put in front of a partner and output you cannot comes down to a few habits, all of which the prompt enforces:

  • Every claim carries its source. Inline, not a link dump at the end. If a number cannot be attributed, it is marked as unattributed rather than stated.
  • Disagreement is preserved, not averaged. When two credible sources size a market differently, both figures appear with their methodology. Splitting the difference invents a number nobody published.
  • Gaps are named. What could not be found is as informative as what could — an absence of buyer complaints in a category usually means you are looking in the wrong place, and knowing that early saves a week.
  • The counter-case is written down. A brief that only argues one direction is advocacy. Asking explicitly for what would make the market less attractive surfaces the risks that get discovered later and more expensively.

The six things to cover

A market research brief that is actually useful tends to answer the same six questions, in roughly this order:

Definition. What is in this market and what is not. Sounds trivial, and it is where most disagreement about market size actually originates — two analysts sizing "AI infrastructure" differently are usually not disagreeing about numbers, they are drawing the boundary in different places.

Size and growth. TAM and the serviceable slice, the growth rate, and critically the provenance of each figure. Track the number back to who produced it and how.

Competitive map. Who is operating here, what each one actually does differently, and where the coverage is thin. Positioning claims from company websites are the least reliable input available; what a company hires for and what its customers say in reviews are far better signals.

The buyer. Who holds the budget, what they are trying to accomplish, and what they complain about. Review sites, support forums and community threads outperform any report for this, because they are the only place buyers describe the problem in their own words.

Recent change. What moved in the last twelve months — funding, new entrants, regulation, a shift in how buyers are procuring. Markets are usually described in a static way and behave dynamically.

The counter-case. What a skeptic would say. Structural headwinds, incumbents who could close the gap trivially, demand that looks real but is a temporary effect of something else.

How this differs from a search summary

Point a chatbot at a market and it will produce something resembling the above. The gap is in the sourcing discipline and the breadth of what gets read. Sai works across sources rather than summarizing the first page of results, cross-references figures that appear in multiple places to see whether they are independent or all tracing back to one original, and produces a document with the citations attached — so anyone reviewing it can check the claim that matters to them without redoing the research.

The output lands as a structured document with proper headers, which matters more than it sounds. Research that has to be reformatted before it can be used tends not to get used.

Stop doing repetitive tasks. Let Sai handle them for you.

Sai is your AI computer use agent — it operates your apps, automates your workflows, and gets work done while you focus on what matters.

Try Sai