This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 6 · Lesson 6.4 · 11 min

Browser and Web Research

Use the agent for market and competitor research on the web and in your own browser, with sources you can check.

Module 6
Connecting Your Tools

Give your AI department safe access to where your business lives

Bruno Ashford
Bruno Ashford · Module 601 / 13
The problem
If you copy data into the chat and paste answers back out, you are the slowest part of your own AI.
Bruno Ashford
Bruno Ashford · Module 602 / 13
6.1 Plain English

MCP is a standard plug

Each tool publishes a panel of buttons. Claude can only press those.

  • Server: the tool's panel of actions
  • Tools: read, search, draft, update, send
  • You decide which buttons need approval
  • Nothing happens outside the panel
Bruno Ashford · Module 603 / 13
Two routes in

How a connection arrives

  1. 1claude.ai connectorsAdd in account settings, appear in Claude Code
  2. 2claude mcp addTerminal command with the vendor's URL
  3. 3/mcpCheck status, sign in, see tools
Bruno Ashford · Module 604 / 13
Scope

Who gets the connection

ScopeWhoUse it for
localYou, this projectDefault, testing, client data
projectTeam via .mcp.jsonApproved shared tools
userYou, all projectsPersonal utilities
Bruno Ashford · Module 605 / 13
6.2 Email, calendar, docs

Read, draft, then you send

The rule for the whole module.

  • Stage 1: read-only triage
  • Stage 2: drafts in your email client
  • Sending stays human
  • Deny rule on send tools
Bruno Ashford · Module 606 / 13
6.3 CRM and spreadsheets

Preview, approve, write

Every change appears as a table before it is saved.

  • Health report first, read-only
  • Record, field, old, new, reason
  • Approve by row number
  • Log every change
Bruno Ashford · Module 607 / 13
Roofing CRM cleanup (illustrative case)

What a read-only report found

1,140open deals before
612inactive 60+ days
318open deals after
Bruno Ashford · Module 608 / 13
6.4 Web research

Research you can repeat monthly

Public web for facts, your browser for signed-in work.

  • Link on every fact
  • claude --chrome for signed-in sites
  • Save to dated files
  • Spot-check three sources
Bruno Ashford · Module 609 / 13
6.5 The uncomfortable part
Connecting a tool hands a stranger's software a key to part of your business. Check the key first.
Bruno Ashford
Bruno Ashford · Module 610 / 13
Risk check

Five questions before any connector

  1. 1Who built it?Vendor, known project or anonymous
  2. 2What data?Clients, money, health, legal
  3. 3Can it write?Send, change, delete
  4. 4Where are secrets?Env variables, never shared files
  5. 5How do we exit?Remove and revoke
Bruno Ashford · Module 611 / 13
Project

Two systems, one workflow

CRM leads become email drafts. Nothing sends itself.

  • Score both connectors
  • Connect at local scope
  • Block send and delete
  • Measure minutes before and after
Bruno Ashford · Module 612 / 13
Recap
Connect what earns its place, read before you write, and keep the send button in human hands.
Bruno Ashford
Bruno Ashford · Module 613 / 13
01 / 13

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1Use web search for public research

For public information such as competitor websites, pricing pages, news and reviews, you do not need any extra setup. Claude Code can search the web and fetch pages. Ask it to cite every source with a link.

Prompt for Claude
Research the five main competitors of my business in my city (see CLAUDE.md for what we sell and where). For each, find: services, published prices or price ranges, main promise on their homepage, review rating and count, and one weakness customers mention in reviews. Cite a link for every fact. Put it in a table, then give me three positioning gaps we could own.
2Connect your browser for signed-in work

Some research lives behind a login: your ad accounts, a review platform dashboard, an industry portal. Install the Claude in Chrome extension and start Claude Code with the Chrome flag. Claude opens its own tabs, uses your existing sign-ins, and pauses when it hits a login page or a CAPTCHA so you handle it yourself.

Terminal
claude --chrome
3Control which sites it may touch

Site permissions come from the Chrome extension settings. Allow only the sites you need for the task, and approve browser actions when asked. Run /chrome to check the connection or reconnect if it drops during a long session.

4Save the output as a file, not just a chat

Ask Claude to save each research run to a dated file in your project, for example research/competitors-2026-10.md. Next month you run the same prompt and ask for a comparison. Now you have a trend, not a snapshot.

Prompt for Claude
Save this competitor table to research/competitors-[today's date].md. If an earlier file exists in that folder, add a section called 'What changed since last time' comparing prices, promises and review counts.
5Verify before you act

Web pages change and agents can misread them. Spot-check three facts per report by clicking the cited links. If a number drives a decision, like cutting your price, verify it yourself.

A law firm partner told me she paid a junior associate two full days to compare the websites, pricing pages and reviews of eight competing firms. The report was good. It was also out of date the week it was delivered.

Claude Code can search the web, read pages, and, with the Claude in Chrome extension, work inside your own browser where you are already signed in. That turns competitor research from a two-day project into a repeatable 20-minute routine you can run every month.

Key points

  • Public web research needs no setup: ask for links on every fact.
  • The Claude in Chrome extension lets the agent work in your signed-in browser.
  • You control sites through extension permissions and approve actions.
  • Dated files turn one-off research into a monthly trend.

Avoid

  • Accepting a research table without clicking any of the sources.
  • Leaving browser access enabled on every site when the task needs two.
  • Asking for 'research' with no list of fields, and getting an essay instead of a table.
Real-world example: a marketing agency

A 12-person marketing agency runs this routine on the first Monday of each month for each retainer client. Claude researches the client's top competitors, saves a dated file, and highlights what changed. Account managers open the file, verify the highlights, and bring one insight to the monthly client call. What used to be an occasional 'competitor audit' sold as an extra is now a standard part of every report.

Bruno Ashford Subscribe