For agency research, use a sourced-answer tool such as Perplexity to find and rank references, then a general assistant such as ChatGPT or Claude to work through the documents you collect. Whatever you use, add a source-check step: every statistic, quote and product claim is opened at its source before it enters a client draft.
The workflow matters more than the tool. Two writers using the same assistant will produce research of very different reliability depending on whether they record where each claim came from. The sections below give a brief template, a tool comparison by job and a check you can run in 20 minutes.
What an agency needs from research that a solo blogger does not
A solo writer who publishes a wrong figure corrects it and moves on. An agency has a client's name on the page, a contract, and usually a reviewer who did not do the research. That changes three requirements.
- Traceability. Anyone on the team can see where each claim came from, weeks later, without asking the writer.
- Repeatability. A new writer given the same brief reaches the same sources.
- Handover quality. The research is a document the editor and client contact can read, not a chat history.
Generic advice on AI research tools rarely covers these three. The workflow below is built around them.
The research brief that goes before any prompt
Before a writer opens a tool, fill in a one-page research brief. It stops the assistant wandering and gives the source check something to measure against.
| Field | Filled-in example (illustrative) |
|---|---|
| Piece and reader | 1,800-word guide for a coworking operator's prospects: "how to choose a flexible office" |
| Question the piece must answer | What should a 10-person team compare before signing a flexible workspace agreement? |
| Claims we expect to make | Typical notice periods, what deposits cover, what is usually included in a membership |
| Source rules | Primary first: operator terms, regulator or standards-body pages, published reports with named authors. No anonymous listicles. |
| Freshness | Anything with a price, date or rule must be checked on its own page this week |
| Off-limits | Competitor claims we cannot verify; the client's confidential pricing |
| Output wanted | Claims table: claim, source link, exact supporting sentence, date checked |
The last row is the key one. Asking every tool for a claims table in the same shape means the output of any assistant drops straight into the check step.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowFour tools compared on the agency job
Prices and plan limits change, so verify on the vendor's page before you commit a team budget. The figures below were checked on the vendors' own pages as of November 2026.
| Tool | Best used for | Cost to know | Watch out for |
|---|---|---|---|
| Perplexity | Finding sources fast, comparing what several pages say, a first map of a topic | Pro shows as $17 a month billed annually on its pricing page (check the monthly rate there); Enterprise Pro starts at $40 a seat a month or $400 a seat a year | Its summary can read more certain than the sources are; on Free, Pro and Max the AI Data Retention setting is on by default, so switch it off under Preferences |
| ChatGPT | Working across several uploaded documents, restructuring notes into a brief | Business seats $25 a month, or $20 on annual billing, with a two-seat minimum | Web answers without sources should be treated as unsourced; ask for links every time |
| Claude | Reading long documents closely, such as a client's 300-page report or a standard | Team seats $25 a month, or $20 on annual billing, from two seats; PDFs up to 1,000 pages, but charts and images are read only in PDFs of 100 pages or fewer | Without browsing, it only knows what you give it and its training; do not ask it for live facts |
| Gemini Notebook (formerly NotebookLM) | Question-answering strictly over a set of sources you add, with answers tied to them | The free Standard tier allows 100 notebooks of up to 50 sources each; chat limits vary by plan, so check Google's usage-limits page | It cannot find sources for you; the quality of the notebook is the quality of what you load |
A reasonable small-agency setup is one search-first tool for discovery and one document-first tool for analysis. If budget allows only one, pick by the job your writers do most. A team that spends its days finding statistics benefits most from the search tool. A team that writes from client-supplied material benefits most from the document tool. For a deeper two-way comparison, see Perplexity versus ChatGPT for business research.
When each tool wins, with a sample task
Task one: a writer needs three reputable sources on typical notice periods in flexible workspace agreements. A sourced-answer tool wins, because the writer wants the links first and the summary second.
Task two: the client sends a 120-page internal operations manual and wants a FAQ drawn from it. A document-first tool wins. Load the file, ask for questions a prospect would ask, and require that each answer quotes the manual's section number.
Task three: a writer has 14 saved pages and wants a gap analysis against the client's draft outline. A source-bound notebook tool wins, because answers must stay inside those 14 pages.
A search prompt that returns checkable output
Loose questions produce fluent answers with no audit trail. Use a prompt that demands a table and tells the tool what to do when it cannot find support.
Research question: What notice period and deposit terms are typical for flexible office agreements for teams of 5-15 people?
Return a table with columns: claim, source URL, the exact sentence on that page that supports it, publisher type (operator, regulator, trade body, news, other), date on the page.
Rules:
- Use only pages you can open now. Do not cite a page you have not read.
- If you cannot find support for a claim, write "no support found" instead of guessing.
- Prefer primary sources (operator terms and conditions, official guidance) over summaries.
- Give 8-12 rows, and list any disagreement between sources.
A realistic sample of what comes back (illustrative): nine rows, five from operator terms pages, two from a trade body, two from news sites. One row reads "Deposits are usually two months' fees", with a source that actually says "deposit equal to one month". That mismatch is exactly what the check step is for, and it is why the "exact sentence" column exists. A claim without a quoted sentence is a claim you cannot verify quickly.
The source-check step, in order
Run this on every brief's claims table before drafting starts, and again on the draft before it goes to the editor. It takes roughly 15 to 25 minutes for a piece with about twelve claims.
- Open every link. Do not rely on the tool's summary of it. A dead link, a login wall or a different page than described fails the row.
- Find the supporting sentence. Search the page for the key number or phrase. If you cannot find it, fail the row.
- Check the date. For prices, rules and product features, the page must have been updated recently. Otherwise find the current vendor page.
- Check the publisher type. A claim about a product comes from that product's own page. A claim about a rule comes from the body that made it. Aggregators and listicles are leads only.
- Look for a second source on any number that carries the argument. If two independent pages disagree, either resolve it or write the claim with the range.
- Mark the row. Verified, adjusted (what changed), or removed. Initial and date it.
Our five-minute routine in fact-checking AI output is a shorter version of this for general text. The agency version adds the claims table and the sign-off column.
What the filled-in claims table looks like
| Claim | Source | Supporting sentence found? | Date checked | Status |
|---|---|---|---|---|
| Typical deposit is one month's fees | Operator terms page | Yes, "deposit equal to one month's membership fee" | Today | Adjusted: the tool said two months |
| Notice period 30 days | Second operator terms page | Yes | Today | Verified |
| "Most teams save 40% on rent" | Listicle, no named author | No underlying study | Today | Removed |
| Fixed-term contracts may auto-renew | Consumer-guidance page | Yes, with the conditions | Today | Verified, with the condition added |
Notice the third row. Statistics that sound plausible and cannot be traced turn up again and again in AI-assisted drafts. Remove them. Replace them with a general statement or a figure you can source.
Three failure patterns to look for
These appear again and again in agency drafts built on AI research, so train editors to hunt for them.
The real source, the wrong claim. The citation exists and is respectable, but the page says something narrower. A report finds an effect in one group and the summary states it as general. Fix by reading the sentence around the number, not only the number.
The stale fact. A product's price or limit was correct two years ago. Search tools often surface older pages because they have more links. Fix by going to the vendor's current page and noting the date you checked.
The confident invention. No source at all. A named study, a quote with a person's name, a statistic with a decimal point. If a claims table row has no URL, or a URL that returns an error, the claim is gone until a human finds real support. Never invent a quote, an expert or a client story to fill a gap.
Turning verified research into a brief the writer can use
Once the claims table passes, ask an assistant to assemble the brief from it. Feed only the verified rows. That way the assistant cannot add claims of its own.
Using ONLY the verified claims in the table below, write a content brief for a 1,800-word guide.
Include: working title, reader and intent, an outline of 6-8 sections with the claims to use in each (by row number), questions the piece must answer, and a list of things the writer must not claim because we have no verified source.
Do not add any fact that is not in the table.
The "must not claim" list is surprisingly useful. It tells the writer where the gaps are before they hit them, and it stops the draft filling gaps with fluent guesswork. A brief built this way travels well: the editor can check any sentence in the draft against the row number.
If the research started from an audit of the client's existing pieces, see how to audit a client's article library, which produces the gap list that feeds these briefs.
Handling client confidentiality in research tools
Research for a client often means pasting parts of their documents into a tool. Set rules before the first project.
- Use a business plan where the vendor states that workspace content is not used for training by default. ChatGPT Business and Claude Team both require at least two seats, which a very small agency should factor into the budget.
- On individual plans, switch off the setting that allows chats to be used for model training, and know that the setting labels differ by vendor and change.
- Do not load unpublished client strategy, personal data or contracts into a search-first tool, because its queries may be retained. Perplexity's help centre says its AI Data Retention setting is on by default for Free, Pro and Max users, while Enterprise data is never used for training.
- Keep client material in a project folder per client, and remove it when the work ends.
Put a line in the statement of work saying which tools handle client material. It costs nothing and heads off awkward questions later.
A worked pass: one brief, start to finish
Say a translation agency asks for a guide, "How to brief a translator", for its own website, which the content agency is writing. Illustrative timings follow.
- Brief (15 minutes). The writer fills the research brief. Claims expected: what a translator needs from a client, typical turnaround ranges, what a glossary is for. Source rules: the agency's own process pages first, professional-body guidance second.
- Discovery (25 minutes). Using a search-first tool and the prompt above, the writer gets 11 rows. Four come from the client's own process documents, which the writer had loaded separately into a document-first tool.
- Check (20 minutes). Nine rows verify. One turnaround figure came from an aggregator and is replaced by the client's own stated range. One row, a claim that machine translation cuts cost "by half", has no traceable source and is removed.
- Assemble (10 minutes). The verified table becomes the brief. The "must not claim" list includes cost comparisons with machine translation.
- Draft and re-check (60 minutes plus 15). After drafting, the editor spot-checks six sentences against row numbers. One sentence drifted from the source wording and is corrected.
Total research and verification: roughly 85 minutes, for a draft that previously would have gone to the editor unchecked. Those minutes buy a draft in which no sentence is a guess, which is what the client is paying the agency for.
Checking a finished draft against its claims table
The research check protects the brief. A second, shorter check protects the draft, because writers paraphrase and paraphrasing is where numbers drift. Give an assistant the verified table and the draft and ask it to act as a checker, not an author.
Below are (1) a verified claims table and (2) a draft. Do not rewrite the draft.
List every sentence in the draft that states a fact, number, date, price or quote. For each, say which table row supports it, or "NO ROW" if none does.
Then list any sentence whose wording is stronger than its row (for example "always" where the source says "usually").
Return two tables: Supported sentences, and Problems.
Illustrative output for a 1,800-word draft: 17 factual sentences found, 14 matched to rows, two with "NO ROW", one flagged as stronger than its source ("deposits are one month's fees" where the row says "usually one month"). The two unmatched sentences are the interesting ones. One was a general statement the writer could soften. The other was a figure the writer remembered from a previous project, which had no source in this one. That sentence goes, or gets a source.
The assistant can miss sentences, so the editor still reads the draft. Think of the assistant as a second pair of eyes that is good at matching and bad at judgement. The editor supplies the judgement, such as whether a softened claim still serves the client.
Quotes, experts and anything with a name attached
Quotes need stricter rules than statistics, because an invented or altered quote misrepresents a real person. Set these house rules and print them on the brief:
- A quote enters the draft only if the writer has opened the original page, video or document and copied the words from it.
- The attribution names the publisher and date, and the link goes to the original, not to a tool's summary.
- An assistant may suggest where to look for a view on a topic, never what a named person said.
- For client spokespeople, quotes come from the client in writing, approved by them.
A realistic mistake: a writer asks an assistant for "a quote from a hospitality expert about event costs" and receives a fluent line attributed to a plausible-sounding person. There is nothing to link to. The editor's rule that every quote has an original link catches it in seconds, which is the whole point of the rule.
Before and after: the same paragraph
Before, from an unchecked draft for an event venue: "Studies show that 70% of corporate events run over budget, so booking early saves thousands." There is no study, the figure has no source, and the saving is an invention.
After the check: "Costs can climb late in planning, when catering numbers and equipment hire are confirmed. Our venue holds a fixed hire rate for bookings made 90 days ahead; ask us for the current terms." The second version makes only claims the client can stand behind, and the first claim is general enough to be true without a statistic.
Keeping a research library the team reuses
Verified rows are an asset. Store them in a shared spreadsheet by client and topic with the date checked and a "re-check by" date, usually 90 days for prices and features and 12 months for stable facts. When a new piece covers the same topic, writers start from the library and only re-verify what has expired. After a few months, a repeat topic starts from a page of checked rows instead of a blank search.
It also helps new hires. A writer joining the team can see how a claim is documented and imitate it. For the wider flow from brief through approved draft, see the AI content workflow for agencies.
Choosing between tools when budgets are tight
If you must pay for one tool this quarter, run a two-week trial across the same three real briefs. Score each on four things: how many rows verified on first check, how many links were dead or off-topic, how long discovery took, and whether the output pasted cleanly into your claims table. The tool that wins on first-pass verified rows is cheaper in practice even if its subscription costs more, because failed rows cost writer time.
That test also settles arguments in the team. Opinions on which assistant is best vary by the person asking, but a table of verified rows per brief does not.
Questions writers ask about AI research
Can I trust the citations an AI research tool gives me?
Treat a citation as a lead, not proof. Open the link, find the sentence the claim rests on, and check that the page actually says it. Tools sometimes attach a real source to a claim it does not support, so the click-through is the verification step.
Is Perplexity better than ChatGPT for research?
Perplexity is built around sourced answers, so it suits finding and ranking references quickly. ChatGPT and Claude suit working through documents you already hold and drafting from them. Many agency teams use one of each and pay for whichever gets used daily.
How much should a source-check step add to a brief?
Budget 15 to 25 minutes per brief for a 1,500-word piece with about a dozen factual claims. That is far cheaper than a client finding one wrong statistic after publication, and the time shrinks as writers learn the routine.
Should the client see which tools we used for research?
Say so in your process note. Clients value knowing that a person verified every claim, and some contracts require disclosure of AI use. Never paste a client's confidential brief into a free consumer tool with training switched on.
Further reads
- ChatGPT for SEO: A Quality Gate for Keyword Clusters and Briefs — Quality gates for the keyword side of a brief.
- Jasper vs ChatGPT for Content Agencies: Which Is Worth Paying For? — Per-seat prices, a six-person agency priced for a month, a same-brief test with a stopwatch and the editing minutes Jasper must save to be worth it.
- AI Agents for Content Creation and Publishing: A Client Approval Flow — How a content agency can let AI agents draft and schedule client content while a person approves every stage, with the exact approved version published.
- Best AI for Copywriting Ads: Variants, Testing and Client Sign-Off — A small-agency workflow for ad copy: variants by angle, platform character limits, an approval log the client signs, and a testing plan that reads cleanly.
- Content Refresh With AI: Update Old Articles and Track Rankings — A client-by-client method for choosing old articles, refreshing them with AI, and measuring the ranking change against pages you left alone.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Perplexity pricing page and help centre (plan comparison, Data Collection at Perplexity), OpenAI ChatGPT Business pricing page, Claude pricing page and Claude help centre (uploading files), Google help pages for Gemini Notebook (usage limits).