Solanasis Docs

solanasis-claude-in-chrome-gtm-playbook

16 min read

Solanasis Playbook: Using Claude in Chrome for GTM, Prospect Research, and Browser-Assisted Execution

Purpose

This playbook is meant to help Solanasis make practical use of Claude in Chrome as a browser-side operator for research, prospecting support, enrichment, outreach drafting, and workflow handoff.

The core idea is simple: use it to handle the repetitive browser work that slows us down, while we stay in control of judgment, positioning, and any final action that matters.

Executive Summary

Claude in Chrome is best understood as a supervised browser copilot, not a magic autonomous sales rep.

It is strong at reading live pages, opening tabs, extracting signals, comparing accounts, drafting messages, turning browser context into structured notes, and handing research off into docs or code workflows. It is weaker on brittle, fully autonomous social-site behavior, especially where dynamic UI, friction prompts, or high-volume repetitive actions are involved.

For Solanasis, the highest-leverage use cases are:

  • Prospect triage from LinkedIn, X, Google, directories, and company sites
  • Account research briefs for SMBs, nonprofits, startups, and operationally messy orgs
  • Outreach drafting in a founder-led voice that does not feel pitchy
  • Competitor and market research across other firms, consultants, MSSPs, and AI/security providers
  • Content mining from posts, comments, and market chatter
  • Browser-to-CRM handoff where research becomes structured notes and next steps

The right operating model is:

  1. Let Claude do the research and browser labor
  2. Let Claude draft the first pass of messages and notes
  3. Keep all important sending, posting, and judgment with a human
  4. Turn the best flows into reusable prompts and recorded workflows

What Claude in Chrome Is Good At

1) Browsing with context

It can look at the live page you are on, read visible content, reason about it, and help navigate from there.

That matters because GTM work is rarely about one static document; it is usually about bouncing between profiles, company sites, posts, search results, and internal notes.

2) Multi-tab research

It can help compare tabs and synthesize what it is seeing across multiple open pages.

That makes it useful for account research, competitor comparisons, and deciding which prospects are actually worth your time.

3) Structured extraction

It is good at taking messy browser context and turning it into clean outputs, such as:

  • prospect shortlists
  • account briefs
  • talking points
  • first-message drafts
  • objection notes
  • content ideas
  • CRM-ready summaries

4) Workflow recording and repeatability

Once you identify a browser task that repeats often, you can start making it more systematic with saved prompts and recorded workflows.

This is where the real leverage begins, because the win is not one clever prompt; the win is building a repeatable GTM system.

5) Handoff into broader Claude workflows

The browser layer becomes more powerful when paired with Claude Code, Cowork, or other structured workflows.

In practice, this means Claude in Chrome can gather and organize the raw context, while another workflow turns that into a spreadsheet, CRM import, battlecard, or polished deliverable.

What It Is Bad At

1) Fragile autonomous social-site behavior

It is not wise to build your GTM engine around fully autonomous social-media execution.

LinkedIn and X are dynamic, modal-heavy, and prone to little layout or state changes that can break brittle browser flows.

2) Long unattended runs

The more steps a task requires, the more likely something drifts, stalls, misreads, or gets weird.

That is why the highest-ROI use is usually supervised operation rather than “set it loose and come back later.”

3) Final-action trust

Anything that can send, submit, post, or otherwise create consequences should be handled carefully.

For Solanasis, the right approach is to let Claude get everything ready, then keep final approval and send actions in human hands.

4) Hidden-state assumptions

If a site is relying on popups, invisible states, loading weirdness, or subtle UI logic, reliability drops.

Browser agents are strongest when the page state is clear, visible, and stable.

The Best Solanasis Use Cases

A. Prospect Triage

This is one of the cleanest first wins.

Use Claude in Chrome to review search results, LinkedIn results, X profiles, directories, local business sites, nonprofit directories, startup databases, chamber listings, or partner pages, then build a shortlist of which accounts look like good fits for Solanasis.

What to score for

  • likely operational complexity
  • obvious systems sprawl
  • signs of growth without mature operations
  • regulated or risk-sensitive environment
  • outdated site or credibility gaps
  • security/compliance language gaps
  • messy vendor stack clues
  • nonprofit or SMB fit
  • evidence they may need fractional operational resilience help

Output format

Have Claude output:

  • company
  • person
  • title
  • why they fit
  • likely pains
  • relevant Solanasis offer
  • warmth score
  • next action

B. Account Brief Creation

This is where Solanasis can stand out.

Instead of generic prospecting, use Claude to gather enough context to produce a fast, grounded account brief that makes outreach feel sharp and relevant.

What to pull

  • who they serve
  • their scale clues
  • their likely operational burden
  • security/compliance hints
  • signs of fragmented tools or processes
  • signs of growth strain
  • whether AI adoption seems opportunistic or thoughtful
  • any public proof of outages, data risk, or operational drag

Why this matters

A short, well-framed account brief is the bridge between random lead lists and founder-led outreach that actually lands.

C. Founder-Led Outreach Drafting

Claude should not be treated as the one who “does outreach.” It should be treated as the one who helps prepare thoughtful, customized drafts much faster.

Best outputs

  • 3 short connection-note options
  • 2 medium follow-up messages
  • 1 warm referral ask draft
  • 1 “saw this and thought of you” draft
  • 1 concise reason-this-matters line

Style guidance for Solanasis

Keep it:

  • warm
  • sharp
  • grounded
  • not overly polished
  • not corporate
  • not hypey
  • not generic
  • not long

The message should feel like a real person who understands messy operations, risk, and behind-the-scenes breakdowns, not like a growth-hack robot.

D. Competitor and Positioning Research

This is an underrated use case.

Have Claude review competitors and adjacent firms so it can help you sharpen Solanasis messaging, offers, objections, price framing, and differentiation.

Review these categories

  • fractional CIO firms
  • fractional CISO firms
  • managed service providers
  • cybersecurity consultancies
  • DR / BCP providers
  • systems integration consultants
  • AI implementation consultants
  • nonprofit tech consultants

Ask Claude to extract

  • what they lead with
  • what they hide in the fine print
  • how they price or package
  • who they seem to target
  • what language feels stale or generic
  • what gaps Solanasis can own more credibly

E. Content Mining

This is one of the best ways to turn market noise into useful content.

Use Claude to review posts, comments, and conversations from SMB founders, nonprofit leaders, IT people, operations folks, and startup operators, then summarize recurring pain points and language patterns.

Useful outputs

  • top recurring frustrations
  • phrases people use to describe chaos
  • objections to hiring help
  • misconceptions about cybersecurity or resilience
  • pain points around AI use inside real orgs
  • content topic ideas
  • hooks for posts and blog articles

F. Browser-to-CRM or Browser-to-Doc Handoff

This is where browser work becomes operationally valuable.

Claude in Chrome is most useful when it can turn what it sees into clean notes that can be dropped into your CRM, spreadsheet, markdown file, or internal system.

Good output structure

  • date
  • account name
  • contact name
  • source URL/page type
  • fit summary
  • likely pains
  • recommended service line
  • message draft
  • next action
  • notes

The Right GTM Workflow Architecture

Use this as the default Solanasis model.

Layer 1: Discovery

Find targets via:

  • LinkedIn search
  • X profiles and conversations
  • Google search
  • chamber/member directories
  • nonprofit directories
  • startup directories
  • partner ecosystems
  • local business groups

Layer 2: Enrichment

Open company sites and social context, then gather:

  • market
  • scale clues
  • maturity clues
  • pain clues
  • public language
  • trust signals
  • likely operational weaknesses

Layer 3: Qualification

Score whether the account is:

  • strong fit
  • possible fit
  • weak fit
  • wrong fit

Layer 4: Message Prep

Draft:

  • short opener
  • relevance line
  • softer CTA
  • stronger CTA
  • referral version if applicable

Layer 5: Human Review

You decide what gets:

  • sent
  • commented
  • saved
  • skipped
  • revisited later

Layer 6: Logging

Turn the work into structured notes so nothing gets lost.

What Not to Build Around

Do not make your first serious workflow any of these:

  • mass connection sending
  • mass DM sending
  • auto-commenting at scale
  • unattended long-run social outreach
  • complex flows that depend on precise UI layouts staying constant
  • any workflow that assumes stealth, bypass, or “human mimicry” is dependable

Even when something is technically possible in a narrow sense, it can still be a lousy operating foundation.

The better move is to use Claude where it is already strong, then let your human judgment do the final few percent.

1) Prospect Triage Prompt

Review the visible results on this page and identify which companies or people appear to fit Solanasis’s ICP.
 
Our core fit is smaller organizations, nonprofits, startups, or operationally messy teams that may need help with cybersecurity, operational resilience, disaster recovery verification, systems integration, data migrations, or responsible AI implementation.
 
For each good-fit lead, output:
- company
- person
- title
- why they fit
- likely pain points
- relevant Solanasis service line
- confidence score from 1-10
- suggested next step
 
Do not click send, submit, or post anything.

2) Account Brief Prompt

Open the company site and any relevant tabs, then create a concise account brief.
 
I want:
- what this organization appears to do
- who they likely serve
- what operational or security pain may be present
- signs of fragmented systems or process strain
- whether they look like a likely fit for Solanasis
- the best outreach angle
- one strong sentence on why now
 
Keep it practical, specific, and brief.

3) Founder-Led Outreach Draft Prompt

Based on the context you just reviewed, draft 3 short outreach options in my voice.
 
Voice guidance:
- warm
- sharp
- not salesy
- not over-polished
- grounded in real observation
- concise
 
Each draft should feel like a thoughtful note from someone who understands messy operations and wants to be useful.
 
Do not send anything.

4) Content Mining Prompt

Review the visible posts, comments, and profiles in this niche and summarize the top recurring pain points, emotional language patterns, and misconceptions.
 
Then turn that into:
- 10 content angles for Solanasis
- 5 strong hooks
- 5 contrarian but grounded points
- 3 calls to action that do not feel pitchy

5) Competitor Review Prompt

Review these competitor sites and extract:
- who they target
- what they lead with
- how they frame the pain
- how they package services
- what feels generic or stale
- what Solanasis can say more honestly or more sharply
 
Then summarize our best differentiation points.

6) Browser-to-CRM Prompt

Convert the context from the open tabs into CRM-ready notes.
 
Use this structure:
- company
- contact
- role
- source
- why they may fit
- likely pain points
- relevant service line
- outreach draft
- next step
- notes
 
Keep it clean and concise.

Suggested Solanasis ICP Guidance Block

Paste this into prompts as needed.

Solanasis helps smaller organizations, nonprofits, and startups get their technology, security, and operations dialed in.
 
Strong fits often have:
- visible operational mess or systems sprawl
- growth strain
- compliance or data sensitivity
- no clear security or resilience owner
- brittle processes behind the scenes
- disconnected tools
- AI interest but no real governance or operational rigor
 
Our offers include:
- cybersecurity assessments
- disaster recovery verification
- responsible AI implementation
- systems integration / automation
- data migrations
- broader operational resilience support
 
We are especially interested in organizations where the pain is real but the team is too busy to fix the basics well.

Suggested Message Style Block

This is designed to keep outputs closer to your natural voice.

Write in a way that feels warm, thoughtful, grounded, and human.
 
Keep paragraphs short. Avoid corporate jargon, hype, and generic sales language. Do not sound like an SDR or a polished agency. Sound like someone who has seen behind the scenes of messy systems and understands what actually breaks.
 
Be concise, but specific. Make it feel like a real note, not a template.

Day-by-Day Rollout Plan

Day 1: Set the operating lane

Goal: make the extension useful without making it brittle.

Actions:

  • install and verify Claude in Chrome works cleanly in your normal browser session
  • decide what browser profile you want to use for GTM work
  • gather 3-5 repeatable prospect research tasks
  • save your ICP block and style block in a reusable notes file
  • use only supervised mode for now

Success looks like this:

  • Claude can see your browser context
  • it can summarize visible results accurately
  • it can produce useful structured notes

Day 2: Build your first real workflow

Goal: turn browsing into a repeatable prospect triage flow.

Actions:

  • run a LinkedIn or Google-based prospect search
  • have Claude shortlist 10-20 prospects
  • have it enrich the top 5 with company-site context
  • have it draft outreach notes for the top 3
  • refine the prompts until the outputs feel sharp

Success looks like this:

  • you have one repeatable research workflow that saves real time

Day 3: Add account-brief capability

Goal: upgrade from “lead list” to “context-rich shortlist.”

Actions:

  • choose 5 companies that seem like realistic targets
  • have Claude produce short account briefs for each
  • compare the briefs against your own judgment
  • tighten the qualification rubric
  • save the best-performing prompt version

Success looks like this:

  • you can go from profile/site to useful brief in minutes

Day 4: Build founder-led outreach drafts

Goal: improve speed without losing your voice.

Actions:

  • feed Claude the briefs from Day 3
  • generate multiple message variants for each account
  • edit them manually until they feel right
  • note what it keeps getting wrong
  • update your style block and constraints

Success looks like this:

  • Claude produces drafts that are directionally strong, even if you still polish them

Day 5: Create browser-to-CRM handoff

Goal: make the work operationally reusable.

Actions:

  • define the exact fields you want for CRM or markdown logging
  • run a workflow where Claude researches 5 leads and outputs clean note blocks
  • copy those notes into your actual system
  • identify what fields are missing or redundant

Success looks like this:

  • browser work no longer dies in tabs or memory

Day 6: Add content mining

Goal: turn market chatter into positioning leverage.

Actions:

  • review a set of relevant LinkedIn or X posts in your niche
  • have Claude summarize recurring pains and language patterns
  • turn that into 10-20 post ideas or blog angles
  • note which pain language feels most alive

Success looks like this:

  • you are no longer guessing what content to write about

Day 7: Decide what gets standardized

Goal: turn experiments into process.

Actions:

  • list the 3 workflows that saved the most time
  • save your best prompt blocks
  • decide which parts remain supervised forever
  • decide which low-risk steps can become more automated
  • write a one-page SOP for each repeated workflow

Success looks like this:

  • you now have a real GTM operating layer, not just scattered experiments

Simple SOP Templates

SOP 1: Prospect Research Sweep

Objective

Create a shortlist of realistic-fit leads from browser-based sources.

Inputs

  • search results page
  • ICP block
  • prompt block

Steps

  1. Open a search results page or lead source
  2. Run the prospect triage prompt
  3. Shortlist the top leads
  4. Open company sites for the top leads
  5. Generate concise notes
  6. Save outputs to CRM or markdown

Output

A ranked shortlist with fit reasons and next steps.

SOP 2: Account Brief Prep

Objective

Create a useful brief before outreach.

Steps

  1. Open the profile and company site
  2. Run the account brief prompt
  3. Review for accuracy
  4. Ask for one outreach angle and one why-now line
  5. Save into the prospect record

Output

A concise account brief and message direction.

SOP 3: Content Mining Sweep

Objective

Extract pain language and content angles from live conversations.

Steps

  1. Open relevant posts or search results
  2. Ask Claude to summarize recurring pains and phrases
  3. Turn that into hooks and post ideas
  4. Save the best angles into your content backlog

Output

A list of grounded content ideas pulled from live market language.

Metrics to Track

This part matters, because otherwise the tool feels useful without proving useful.

Track:

  • time saved per research session
  • number of useful prospect briefs created
  • number of good outreach drafts created
  • hit rate of “Claude shortlist” vs your own judgment
  • number of content ideas worth actually using
  • number of browser research sessions that produced CRM-ready output
  • failure modes and breakpoints

You do not need complex analytics at first; you just need enough evidence to know whether the workflow is paying for itself.

Failure Modes to Watch

  • it overgeneralizes based on thin context
  • it sounds too polished or too generic
  • it misses subtle but important fit clues
  • it pulls the wrong lesson from a page
  • it gets lost in tab sprawl
  • it behaves well on simple sites but poorly on dynamic ones
  • it creates too much output instead of the right output

The answer is usually not “abandon the tool.” The answer is to narrow the workflow and tighten the prompt.

  • keep final judgment with a human
  • keep sending/posting actions supervised
  • start narrow and repeatable
  • standardize what actually works
  • save prompt blocks that perform well
  • treat dynamic social flows as fragile
  • use the tool for leverage, not fantasy

Practical Recommendation for Solanasis

If I were deploying this for Solanasis right now, I would make these the first three workflows:

Workflow 1

Prospect shortlist builder from LinkedIn, Google, directories, and company sites

Workflow 2

Account brief builder for your best-fit prospects

Workflow 3

Founder-led outreach draft generator using real context gathered from the browser

Once those are stable, I would add:

  • browser-to-CRM logging
  • competitor sweeps
  • content mining sweeps

That sequence gives you practical GTM leverage without relying on the most brittle parts of browser automation.

Notes for Further Iteration

Use this section to refine the playbook after live testing.

What worked best

What felt brittle

What prompts performed best

What should become a recorded workflow

What must always stay human-reviewed

Final Framing

The real opportunity here is not to turn Claude in Chrome into a fake human prospector.

The opportunity is to use it as a fast, context-aware browser operator that helps Solanasis move from scattered tabs and half-finished research into sharper briefs, better messages, cleaner notes, and a more repeatable GTM motion.

Graph View