The Copy Scout System Behind 25K Projects

Deploy market intelligence scouts that never sleep

Handle 12 Clients Like You're Handling One

Mark Masters here.

Six weeks ago, I watched a competitor lose a $25,000 VSL project to one of my students.

The competitor had more experience. Better portfolio. Lower rates.

But here's what happened in the pitch meeting:

My student referenced the exact customer language from 47 support tickets. Identified the emotional trigger the client's competitors were all missing. Showed data from review mining that revealed an entirely untapped positioning angle.

The competitor talked about "proven frameworks" and "15 years of experience."

One copywriter had scouts in the field. The other was guessing.

The client increased the project scope on the spot. Added email sequences. Monthly retainer. Full funnel rewrite.

$25K became $63K.

Your clients aren't hiring you to only write. They're also hiring you to figure out things their competitors don't.

Today, I'm giving you the exact system my top students use. What I call The Research Command Center™, a Claude Projects setup that deploys specialized scouts to gather market intelligence 24/7.

While your competition writes from assumptions, you'll write from intelligence your scouts gathered this morning.

Let me show you how to deploy your scout network.

The Problem With How You Handle Research

Let's talk about your current "system."

You've got customer interviews in Google Docs. Survey results in Excel. Competitor analysis in Notion. Sales call notes in Apple Notes. Review screenshots in a folder called "Research_FINAL_v2_ACTUALLY_USE_THIS."

Every time you write, you're hunting through digital debris. Trying to remember that perfect customer quote. Searching for that competitor weakness you spotted three weeks ago.

You're not using research. You're hoarding it.

Meanwhile, opportunities are hiding in plain sight:

  • Customer language that would triple your CTR

  • Competitor blind spots worth six figures

  • Emotional triggers no one's addressing

  • Market gaps your clients don't know exist

You need scouts. And they need a command center.

The Research Command Center™: Your Scout Headquarters

Here's what we're building today:

A dedicated Claude Project that transforms scattered research into active intelligence.

What Goes In Your Project Knowledge Base:

  • Customer interview transcripts (word-for-word)

  • Survey results with raw response data

  • Competitor campaign teardowns

  • Sales call recordings (transcribed)

  • Review mining results (Amazon, G2, Trustpilot)

  • Support ticket patterns

  • Lost deal analysis reports

  • Industry trend reports

  • Swipe file of campaigns that actually converted

  • Customer success stories with transformation language

The Custom Instructions That Activate Your Scouts:

You have access to comprehensive market research for copywriting projects. You are a scout gathering intelligence. 

ALWAYS:
- Extract exact customer language from transcripts (verbatim quotes)
- Scout for patterns across multiple data sources
- Reference specific data points with numbers when making claims
- Address real objections using actual words from sales calls
- Use proven hooks from the swipe file with performance data
- Scout competitor territories for gaps and opportunities
- Ground all copy in actual field intelligence, not assumptions
- Identify emotional triggers competitors are missing
- Spot emerging trends before they become obvious
- Report opportunities with specific evidence and examples
- Connect disparate data points to reveal hidden insights
- Prioritize recent data but note historical patterns
- Flag conflicting intelligence for human review

WHEN ANALYZING:
- Look for what's NOT being said as much as what is
- Track frequency of mentions to gauge importance
- Note emotional intensity, not just content
- Identify transformation language for stories
- Find unique mechanisms no one else claims
- Spot new problems entering the market

WHEN REPORTING:
- Lead with most actionable intelligence
- Provide exact quotes, not paraphrases
- Include context (source, date, frequency)
- Highlight contrarian insights
- Suggest specific applications for findings
- Connect insights to revenue opportunities

Your mission: Transform raw research into tactical advantages.

The Project stores your intelligence. The Skills deploy your scouts.

The Three Scouts You Need

Critical Understanding: Projects vs. Skills

  • Projects = Your intelligence storage (where research lives)

  • Skills = Your scout training (how to analyze that research)

  • Projects work only in that Project. Skills work everywhere in Claude.

  • You need BOTH: Projects hold the data, Skills extract the intelligence.

Think of it like this: Your Project is the command center full of maps and reports. Your Skills are the trained scouts who know how to read those maps and find opportunities.

Now let's set up your three scouts.

Scout #1: The VOC (Voice of Customer) Scout

This scout infiltrates customer conversations and brings back the exact language that converts.

Create a Skill folder called voc-scout with this SKILL.md:

---
name: voc-scout
description: Scout customer conversations to extract powerful language and emotional triggers for copy
---

# VOC Scout - Customer Language Extractor

## Your Mission
Scout all customer research to extract language that converts.

## Extraction Protocol

### Phase 1: Emotional Language Scan
- Identify words that carry emotional weight
- Mark phrases repeated 3+ times
- Capture transformation moments
- Note specific pain descriptions

### Phase 2: Pattern Recognition
- Group similar complaints
- Identify desire patterns
- Map objection themes
- Track satisfaction triggers

### Phase 3: Hook Extraction
- Pull quotable phrases
- Identify story beginnings
- Extract comparison language
- Capture "aha" moments

## Output Format
- **Power Phrases**: [exact quotes with emotional weight]
- **Repeat Patterns**: [phrases appearing multiple times]
- **Transformation Language**: [before/after descriptions]
- **Objection Patterns**: [common concerns]
- **Hook Candidates**: [attention-grabbing statements]

Scout #2: The Competitive Intelligence Scout

This scout maps competitor territory and finds the gaps they're not defending.

Create a Skill folder called competitive-scout with this SKILL.md:

---
name: competitive-scout
description: Scout competitor positioning to identify gaps and opportunities for market differentiation
---

# Competitive Scout - Market Gap Identifier

## Your Mission
Scout competitor campaigns to identify undefended market positions.

## Reconnaissance Protocol

### Phase 1: Territory Mapping
- Document all competitor claims
- Map their emotional territories
- Identify their core angles
- Track their proof elements

### Phase 2: Gap Analysis
- Find emotions they don't address
- Identify audiences they ignore
- Spot mechanisms they don't claim
- Locate proof they can't provide

### Phase 3: Opportunity Identification
- Undefended value propositions
- Emotional territories available
- Unique mechanism opportunities
- Counter-positioning angles

## Output Format
- **Competitor Claims Map**: [what they're saying]
- **Undefended Territories**: [what they're NOT saying]
- **Positioning Opportunities**: [how to differentiate]
- **Counter-Narratives**: [how to reframe]
- **Proof Advantages**: [evidence they can't match]

Scout #3: The Pattern Recognition Scout

This scout connects dots across all intelligence to spot opportunities before they're obvious.

Create a Skill folder called pattern-scout with this SKILL.md:

---
name: pattern-scout
description: Scout across market research data to identify recurring themes and emerging opportunities
---

# Pattern Scout - Opportunity Spotter

## Your Mission
Identify patterns across all intelligence sources that reveal hidden opportunities.

## Analysis Protocol

### Phase 1: Cross-Reference Intelligence
- Connect customer complaints to competitor gaps
- Link objections to missing proof elements
- Match desires to unaddressed emotions
- Correlate success stories to patterns

### Phase 2: Trend Identification
- Spot increasing mention frequency
- Identify emerging concerns
- Track shifting priorities
- Monitor new comparison points

### Phase 3: Opportunity Prediction
- Hidden desires becoming visible
- Problems growing in urgency
- Gaps widening in market
- Angles becoming available

## Output Format
- **Emerging Patterns**: [trends gaining momentum]
- **Hidden Connections**: [non-obvious relationships]
- **Opportunity Windows**: [time-sensitive angles]
- **Predictive Insights**: [where market is heading]
- **Strategic Advantages**: [patterns competitors miss]

How Your Scouts Work Together (Real Example)

Let me show you exactly what happens when you deploy all three scouts on a real project.

Scenario: New Email Sequence for SaaS Client

Step 1: Open your Research Command Center Project

  • All your intelligence loads instantly

  • Custom instructions activate

  • Your scouts are ready

Step 2: Deploy your VOC Scout

You type: "VOC Scout: Extract the exact language customers use when describing their problem"

Scout returns:

POWER PHRASES EXTRACTED:
- "drowning in spreadsheets" (mentioned 14 times)
- "can't see the forest for the trees" (8 times)
- "flying blind with our data" (6 times)
- "finally seeing the full picture" (in success stories)
- "everything just clicked" (transformation moment)

EMOTIONAL PATTERN: Overwhelm → Confusion → Desperation → Clarity

Step 3: Deploy your Competitive Scout

You type: "Competitive Scout: What angle are all competitors missing?"

Scout returns:

COMPETITOR BLIND SPOTS:
- All focus on features (dashboards, integrations, speed)
- None address emotional journey from chaos to clarity
- Missing: The relief feeling when everything connects
- Opportunity: Position around emotional transformation, not technical capability
- Unique angle available: "From overwhelming to obvious"

Step 4: Deploy your Pattern Scout

You type: "Pattern Scout: Find the connection between frustration and conversion"

Scout returns:

PATTERN DISCOVERED:
- 82% of converters mention "overwhelm" before "clarity"
- Conversion happens 3-5 days after peak frustration
- Trigger phrase: "I can't keep doing this"
- Success stories always include "moment of realization"
- Hook opportunity: Mirror their journey in your sequence

Step 5: Write with Intelligence

Now you write:

  • Email 1 Subject: "Still drowning in spreadsheets at 9pm?"

  • Email 2 Subject: "When flying blind becomes too expensive"

  • Email 3 Subject: "The moment everything finally clicks"

Body copy uses exact VOC language. Positioning leverages competitor blind spots. Emotional sequence follows a proven pattern.

Result: 67% open rate. 34% click rate. 12% conversion.

Not because you're a better writer. Because you had better intelligence.

The Weekly Scout Protocol

Here's how my $10K/month copywriters run their scout operations:

Day

Scout Mission

Scout Deployed

Intelligence Output

Monday

Sales call transcripts

VOC Scout

Objection-handling language

Tuesday

Competitor campaigns

Competitive Scout

Positioning opportunities

Wednesday

Customer reviews

Pattern Scout

Emerging desire patterns

Thursday

Support tickets

VOC Scout

Problem/solution language

Friday

All data sources

All three scouts

Complete market intelligence report

Building Your Scout Network: 60-Minute Deployment

But first, let me be clear about something.

If you don't have research files, you're building a command center with no intelligence to command.

Where to Gather Intelligence Fast:

Customer Language Sources (Get These Today):

  • Reviews: Amazon reviews for books in your client's space (copy/paste 50+ reviews)

  • Reddit: Search "[industry] + problem" - goldmine of unfiltered language

  • YouTube Comments: Find popular videos in the niche, mine the comments

  • Facebook Groups: Join, observe for a week, export discussions

  • Trustpilot/G2: B2B software reviews are intelligence gold

Competitor Intelligence (30 Minutes):

  • Facebook Ad Library: See every ad they're running (free)

  • Email Lists: Sign up with a burner email, screenshot everything

  • Sales Pages: Use Wayback Machine to track positioning changes

  • YouTube Ads: Use YouTube Ad Finder extension to capture their VSLs

Quick Customer Research (If You Have None):

  • Send a 3-question survey to any email list

  • DM 10 customers on social media with one question

  • Call 5 customers for 10-minute interviews

  • Export your client's support tickets (last 90 days)

Minimum Viable Intelligence:

  • 20 customer reviews/comments

  • 5 competitor campaigns

  • 10 support tickets or complaints

  • 1 customer survey with 20+ responses

Now let's build your command center.

Step 1: Establish Scout Base

  1. Prepare Your Intelligence Files:

    • Create a folder called "Research Intelligence"

    • Organize your files by type:

      • customer-interviews/ (save as .txt or .docx)

      • survey-results/ (export as .csv from Google Forms/Typeform)

      • competitor-analysis/ (PDFs or documents)

      • sales-calls/ (transcribe using Otter.ai or Rev.com)

      • reviews/ (copy/paste into .txt files)

      • support-tickets/ (export from Zendesk/Intercom as .csv)

  2. File Preparation Tips:

    • Interviews: One file per interview, named "Interview_CustomerName_Date.txt"

    • Surveys: Keep raw data with all responses, not summaries

    • Competitor Ads: Screenshot + copy text into documents

    • Sales Calls: Include objections verbatim, not paraphrased

    • Reviews: Include 1-star to 5-star for full picture

  3. Create Your Research Command Center:

    • Go to claude.ai/projects

    • Click "New Project" button

    • Name it exactly: "Research Command Center"

    • Add description: "Market intelligence and customer research hub"

  4. Upload Your Intelligence:

    • Click "Project Knowledge" in left sidebar

    • Click "Upload" button

    • Select up to 5 files at a time

    • Start with your most recent/relevant research

    • Wait for "Processing" to complete (usually 10-30 seconds per file)

    • Continue until all research is uploaded

    • Note: You can have up to 100 files per Project

  5. Add Scout Instructions:

    • Click "Project Instructions" in left sidebar

    • Copy and paste this exact configuration:

Your intelligence base is now operational.

Step 2: Train Your Scouts

  1. Enable Skills First:

    • Go to Claude.ai Settings → Labs

    • Toggle ON "Use custom skills"

    • Toggle ON "Code execution" (required for Skills to work)

  2. Get the Skills Template:

  3. Create Your Scout Skills:

    • Create a new folder called scout-skills on your desktop

    • Inside, create three separate folders:

      • voc-scout

      • competitive-scout

      • pattern-scout

  4. Build Each Skill:

    • In the voc-scout folder, create a new text file

    • Name it exactly SKILL.md (capitals matter)

    • Copy the VOC Scout configuration from above

    • Save the file

    • Repeat for other two scouts

  5. ZIP Each Skill Correctly:

    • Mac: Right-click the voc-scout folder → "Compress"

    • Windows: Right-click the folder → "Send to" → "Compressed folder"

    • Critical: ZIP the folder itself, not the files inside

    • Repeat for all three scout folders

  6. Deploy Your Scouts:

    • Go back to Claude.ai

    • Click your avatar → Settings → Skills

    • Click "Create skill" button

    • Upload voc-scout.zip

    • Wait for "Skill created successfully"

    • Repeat for other two ZIP files

  7. Verify Deployment:

    • You should see all three scouts listed

    • Each shows status: "Active"

    • If any show errors, check your YAML formatting

Your scouts are now trained and ready.

Step 3: Test Your Scout Network

  1. Open Your Research Command Center:

    • Go to Claude.ai/projects

    • Click on "Research Command Center"

    • Start a new chat within the Project

  2. Test Each Scout Individually, VOC Scout Test:

    • Type: "Deploy VOC scout to extract the top 5 customer pain points with exact quotes"

    • Expected output: Numbered list with verbatim customer language

    • Success indicator: You see phrases you forgot were in your research

  3. Competitive Scout Test:

    • Type: "Deploy competitive scout to identify what emotions our competitors aren't addressing"

    • Expected output: Gap analysis with specific opportunities

    • Success indicator: You spot at least 3 positioning angles

  4. Pattern Scout Test:

    • Type: "Deploy pattern scout to find connections between customer complaints and purchase triggers"

    • Expected output: Correlation insights with evidence

    • Success indicator: You see a pattern you hadn't noticed

  5. Test Integrated Scout Operations:

    • Type: "Deploy all scouts to analyze our market position and identify our biggest opportunity"

    • Watch all three Skills activate automatically

    • Expected output: Comprehensive intelligence report

    • Success indicator: Actionable insight you can use today

  6. Advanced Scout Commands to Try:

    • "VOC scout: Find transformation language from our happiest customers"

    • "Competitive scout: What proof elements are competitors using that we could counter?"

    • "Pattern scout: What's the emotional journey from problem awareness to purchase?"

    • "All scouts: Build a campaign angle based on current intelligence"

  7. Troubleshooting:

    • Scouts not activating? Check code execution is enabled in Labs

    • Generic responses? Your Project instructions might not have saved

    • Surface-level insights? Upload more specific research (transcripts, not summaries)

    • Skills not showing? Verify YAML frontmatter formatting (name: and description: must be exact)

If scouts aren't finding intelligence that makes you rethink your entire approach—you need better research files.

Common Scout Deployment Issues (And How to Fix Them)

"My Skills aren't showing up"

  • Check: Settings → Labs → "Use custom skills" is ON

  • Check: Code execution is also ON

  • Fix: Re-ZIP the folder (not the files inside)

  • Fix: Ensure SKILL.md is capitalized exactly

"Scouts aren't activating automatically"

  • Check: Your description in YAML is under 200 characters

  • Check: Description clearly states what the Skill does

  • Fix: Make description more specific to trigger activation

  • Example: Change "Analyzes text" to "Scout customer conversations to extract powerful language"

"I'm getting generic responses, not intelligence"

  • Check: Project instructions saved properly (refresh and verify)

  • Check: You're in the Project, not a regular chat

  • Fix: Upload actual transcripts, not summaries

  • Fix: Include raw data, not cleaned reports

"The insights aren't actionable"

  • Check: Research files have specific examples, not general points

  • Fix: Upload customer language verbatim

  • Fix: Include dates and context in your files

  • Fix: Add more recent research (last 90 days)

"It's not finding patterns"

  • Check: You have enough data (minimum 20+ data points)

  • Fix: Upload research from multiple sources

  • Fix: Include both positive and negative feedback

  • Fix: Add time-based data to spot trends

The Intelligence Gap Is Permanent

Let me be perfectly clear about what happens next.

Every day you operate without scouts, your competition gathers intelligence you'll never recover.

They're discovering customer language you won't hear. 

Spotting patterns you won't see.

Finding opportunities you won't know existed.

This is about operating blind while others have perfect vision.

In the next 60 minutes, you could have:

  • Your Research Command Center operational

  • Three Scout Skills deployed

  • Your first intelligence reports generating

  • Patterns emerging from your existing research

Or you could bookmark this email. Add it to your "implement later" folder. Watch another YouTube video about "AI prompts for copywriters."

While someone else (maybe your direct competitor) builds their scout network today.

The Masters Method Reality

I told you about my student who turned $50K into $120K.

Want to know the real story?

Three months earlier, they were charging $2K for VSLs. Competing on price. Losing pitches to cheaper writers.

Then they built their Research Command Center. Deployed their scouts. Started showing up to pitches with intelligence instead of opinions.

  • Their close rate went from 20% to 70%.

  • Their average project value increased 5x.

  • Their client retention hit 100%.

Not because they became better writers. Because they built better infrastructure.

The Master’s Memo

The scout system is right here. Every technical detail. Every Skill configuration. Every custom instruction.

  • This isn't hidden behind a $5,000 course.

  • It's not gatekept in a private mastermind.

  • It's not "coming soon in my new program."

It's in this email. Right now. Free.

The only thing between you and market intelligence superiority is execution.

Build it today: Join the 5% who turn knowledge into infrastructure.

Build it someday: Join the 95% who collect interesting emails.

Your choice. But your competitors already chose.

Stop reading. Start deploying.

More clicks, cash, and clients,
Mark Masters