Research Analyst

You are about to make a decision, and you need to know what is true. The internet is full of confident claims. Many are copied from each other, and few of them link back to the original. Checking each one by hand takes hours, and it is easy to trust the wrong source.

The Research Analyst does that checking for you. It turns your question into a research plan, goes to the original papers, filings, documentation or data, and compares what they say. Think of it as a good librarian. It does not just hand you a summary of a book. It takes you to the right shelf, opens the book and marks the exact page.

It keeps a clear line between what is confirmed and what is only inferred. When sources disagree, it tells you so, and it says how confident it is when the evidence is thin. Every report ends with its sources, with links and dates, so you can check the work yourself in a few minutes.

Like a fact-checker at a newspaper, it reads the original before it repeats anything. A claim that appears only in a summary is marked as second-hand. A claim that appears in the source itself is marked as confirmed. That habit lets you act on the answer without redoing the search.

• Turn your question into a research plan, then run the searches, in parallel where that helps, so the answer comes back sooner.
• Read web pages and the files in your folders as evidence, and note which is which.
• Write a cited report with the answer first and the evidence after. You can open, mark up and share it in the document panel.
• Separate what is confirmed from what is inferred, and say when sources disagree with each other. It also says how confident you can be when the evidence is thin.
• Follow a topic over time when you ask, such as two main competitors, and report only what has changed since last time.
• Remember the sources you trust and the depth you like, so future reports match your taste.
• Use your Google Drive, Google Docs and Notion pages as sources, and save finished reports there, once you connect your account.
• Open the pages it reads in the Browser panel, so you can see exactly what it looked at.

Everyday research needs no special skill. You ask a question, and the analyst plans the work. For example: "Summarise the data protection rules that apply to a small online shop in India."

The analyst has one skill of its own, clone-reviews. It reads what real users say about an existing app in public places, such as app stores, review sites, Reddit and Hacker News, and the app's own feature-request board. It ranks what users hate, what is missing and what nobody has solved yet. Then it turns that into a fix plan for a competing product, and a positioning angle you can sell. Every quote it uses is real, word for word, and linked to its source. Use it when you are building a competing app and want to know what the original's users dislike before you start.

Like a building inspector, it checks the wiring rather than the brochure. It reads what people actually wrote, not what the company says about itself. It asks before it shares or publishes a report, and before it writes into a shared Drive folder or Notion page, because both are hard to take back.

Here is the question people bring most often: what do the studies really say about a big idea before they decide.

1. You ask: "What do recent studies say about four-day work weeks?"
2. The analyst turns the question into a plan. It decides what kinds of study to look for, how recent they should be, and which sources come first. It puts original research ahead of summaries.
3. It runs the searches and opens the original studies in the Browser panel. It reads the methods and the numbers themselves, not only the headlines.
4. It notes where the studies disagree, and marks any claim it could not confirm from the original.
5. It writes the report: the answer first, then the strongest evidence, then the details.
6. Every claim has a link and a date. Anything it infers is labelled as inference, with a note on how confident it is.
7. It saves the report as a document you can open, mark up and share. It does not share the report for you.
8. You read the answer, open two of the links and check one number yourself. If something looks wrong, you ask a follow-up question.
9. If you want to follow the topic over time, you ask it to keep track. It will report only what has changed.

Like a careful librarian who hands you the book and the page number, the analyst gives you the source, not just the verdict. You check the work, and it stays honest about what it could not confirm.

What you get at the end is a cited report with the answer first, every source linked and dated, a clear split between what is confirmed and what is inferred, and a list of anything it could not confirm. You decide what to do with it.