Copywriting Research Process: From Evidence to Message Strategy

11 min read

Reviewed by

Daily Intel Research Team

Evidence base

VSLs, ads, funnels, UTMs, transcripts, and market pattern review

Coverage

14+ languages · blackhat, greyhat, and whitehat patterns

8,000+

Videos & Ads

+50-100

Fresh Daily

$29.90

Per Month

Full Access

12+ TB database · 70+ niches · cancel anytime

Quick answer

Copywriting research becomes useful when it supports a decision.

Interviews, reviews, competitor pages and product documents may all contain useful material. Yet a folder full of sources does not show what the copy should emphasize. You need a process that connects evidence to a specific sales question.

This copywriting research process produces five working outputs:

  1. Prioritized prospect concerns
  2. Documented connections between those concerns and the product
  3. Clear limits around the available evidence
  4. Message and lead hypotheses
  5. A register of unresolved claims

A lead is the opening approach of a sales message. A message hypothesis is a provisional direction supported by available evidence. It is not a proven winner.

The central principle is to begin with prospect priorities rather than the feature the company most wants to promote. [1]

Sales question
      ↓
Separate source groups
      ↓
Context-rich source records
      ↓
Voice-of-customer coding
      ↓
Priority and capability mapping
      ↓
Message and lead hypotheses
      ↓
Working research brief

Example note: Relay, its customers, every quotation and all proposed copy below are hypothetical. None is a real campaign, historical quotation or observed result.

1. Define the sales question

Start with the decision the research must support. Record:

  • The intended audience
  • The offer
  • The action the audience is being asked to take
  • The uncertainty preventing confident drafting

Imagine a software product called Relay.

A broad prompt would be:

Research why operations teams need automation.

A decision-focused question would be:

For operations managers evaluating workflow tools, which coordination problem should organize Relay’s landing page, and which documented capability can address it?

The second question directs the research without assuming that automation is the audience’s main concern.

Separate facts from assumptions

KnownAssumedUnresolved
Relay displays task ownersBuyers want fewer status meetingsWhich coordination failure creates the most concern?
Relay stores selected workflow changesSetup time may be an objectionWhat setup claims can the product support?
Relay offers a free trialVisibility matters more than flexibilityDoes prospect evidence support this priority?

This table stops an internal belief from quietly becoming a research conclusion.

2. Keep source groups separate

Collect material in four groups:

  • Prospect evidence: interviews, surveys, reviews, support conversations and sales calls
  • Product documentation: capabilities, limitations, demonstrations and technical records
  • Competitive messaging: positioning, offers and common category language
  • Proof sources: primary documents, tests and other evidence used to support claims

These sources have different roles. A customer anecdote can document one person’s experience. A product specification can document a capability. Neither automatically establishes a broad outcome.

A proclamation-style lead opens with a bold central assertion. That assertion should emerge from supporting research, rather than being invented first and justified afterward. [2]

Record four evidence layers

Assign a stable ID to each useful item.

IDLayerHypothetical entry
SRC-01Observation“I spend Monday morning asking who owns each task.”
INT-01InterpretationUnclear ownership may create repetitive coordination work.
CLM-01Proposed copy“See task ownership without chasing updates.”
GAP-01Missing supportConfirm recurrence and document exactly what Relay displays.

Customer language is evidence of what someone said or perceived. It is not automatically true, representative or suitable for an unqualified claim.

Keep product facts separate from prospect priorities as well. “Relay displays task ownership” is a documented capability. It does not establish that ownership is the audience’s most important concern.

3. Collect voice-of-customer language with context

Voice of customer, or VOC, is the language prospects and customers use to describe their situations, priorities and doubts.

Save the context around every excerpt:

  • Who said it and where
  • What situation prompted it
  • Which product or alternative was under discussion
  • Whether the person fits the intended audience
  • Whether the statement describes a perception, behavior or checkable fact

A Relay source log might begin as follows:

IDExact language or factContext
SRC-01“I spend Monday morning asking who owns each task.”Operations-manager interview about weekly handoffs
SRC-02“I can build the workflow. I just can’t tell who changed it later.”Interview after an internal process audit
SRC-03“Another tool means another rollout I have to defend.”Sales call with a manager comparing vendors
PD-01Relay displays the current task ownerProduct documentation; display conditions need confirmation
PD-02Relay records selected workflow changesProduct documentation; scope and retention limits unresolved

Context prevents a vivid quotation from being stretched beyond what its source supports.

4. Code the evidence with a VOC sheet

Coding makes records comparable while preserving the original language.

Evidentiary strength means what a source can legitimately support, along with what it cannot establish.

Voice-of-customer coding sheet

FieldWhat to record
Record IDStable reference used in later decisions
Exact languageUnedited excerpt
Source and contextSource type, situation and audience fit
Pain or frictionDifficulty being described
Desired outcomeWhat the person wants instead
ObjectionReason for hesitation
Awareness signalFamiliarity, skepticism or readiness
Emotional importanceWhy the issue appears consequential
Product connectionRelevant documented capability
Evidentiary strengthWhat the record can and cannot support
InterpretationResearcher’s provisional reading
Open questionMissing context, contradiction or proof

Completed hypothetical record

FieldEntry
Record IDSRC-02
Exact language“I can build the workflow. I just can’t tell who changed it later.”
Source and contextOperations-manager interview after an audit
Pain or frictionUnclear change history
Desired outcomeTraceable changes
ObjectionNot stated
Awareness signalFamiliar with workflow tools
Emotional importanceThe audit affected confidence in the process
Product connectionPD-02, selected workflow-change history
Evidentiary strengthOne relevant account; not representative alone
InterpretationTraceability may matter more than workflow creation
Open questionWhich changes does PD-02 record, and how often does this concern recur?

Do not invent scoring formulas, frequency thresholds or sample-size rules without a defensible measurement method.

Treat awareness as a conditional signal

Broadly, a familiar and ready audience may permit a more direct opening. A skeptical or less familiar audience may require more explanation or a gentler bridge. [3]

Use tentative coding notes:

  • Familiar with the category but skeptical about switching
  • Recognizes the problem, but knowledge of available approaches is unclear
  • Readiness cannot be inferred because the source was not discussing a purchase

These notes are planning inputs. They are not definitive awareness-stage assignments or rules for choosing a lead.

5. Find recurring priorities

Group related pains, desires and objections without erasing differences between sources.

ClusterRecordsProvisional findingLimitation
CL-01SRC-01, SRC-02Visibility across handoffs and changes may be a shared concernTwo accounts do not establish market-wide priority
CL-02SRC-03Rollout burden may be a purchase objectionOne record requires further investigation

Frequency shows recurrence within the material collected. It does not prove effectiveness or market-wide importance. Emotional intensity is also insufficient by itself.

A problem-solution direction should reflect a prospect concern and introduce relevant hope without dwelling needlessly on distress. [4]

Next, map the clusters to documented capabilities:

Prospect clusterProduct connectionStatus
Unclear ownershipPD-01: current task owner is visibleSupported at capability level
Unclear changesPD-02: selected change historyPartial; limits need documentation
Rollout burdenNo verified setup evidenceUnresolved
Elimination of meetingsNo direct supportDo not claim

Remove themes that cannot connect credibly to the product. The opening, claims, benefits and offer should remain organized around one unifying idea. [5]

6. Create a message hypothesis

Each message hypothesis should retain its evidence trail.

FieldHypothetical MH-01
Central problemImportant workflow context becomes unclear during handoffs
Desired resultSee current ownership and relevant changes
Provisional promiseMake workflow responsibility easier to inspect
Primary objectionAnother tool may create rollout work
Product explanationPD-01 and PD-02 display selected ownership and change information
Available evidenceSRC-01, SRC-02, PD-01 and PD-02
Unifying ideaWorkflows need visible responsibility, not only documented steps
Missing supportProduct limits, recurrence and any outcome claim

A mechanism is the proposed explanation connecting a capability to a result.

For example:

Visible ownership → fewer ambiguous handoffs → less manual reconstruction of responsibility

This is a hypothesis, not a validated performance claim. Each arrow needs support. If one link is missing, record it as an open question rather than writing it as fact.

7. Develop lead hypotheses

Practitioner frameworks describe recurring openings such as Offer, Promise, Problem-Solution, Big Secret, Proclamation and Story. Use these as overlapping labels for exploration, not rigid or mutually exclusive categories. [6] [7]

Possible leads for MH-01 include:

  • Direct: “See current task owners and recorded workflow changes in one place.”
  • Problem-solution: “When ownership disappears between handoffs, the next meeting becomes an investigation.”
  • Story: “On Monday, Maya’s workflow looked complete. By Thursday, nobody could explain who changed the approval step.”

All three are original, hypothetical lines.

Indirect leads can use emotion or curiosity, but they may become slow or disconnected from the product. [8]

Record the bridge for each indirect opening:

Unexplained change → cost of reconstructing events → need for visibility → PD-02

Remove the lead if it cannot make that transition clearly.

Curiosity gaps around an overlooked component or process appeared in six examples within one stratified convenience sample. The repeated structure revealed the point before explaining it. This is only a sampled pattern, not evidence of effectiveness or a market-wide norm. [9]

A restrained hypothetical adaptation might be:

The workflow was not failing where the team expected. The missing information appeared between two approvals.

The copy must then explain the issue plainly. Curiosity does not permit a fabricated secret, hidden cause or unsupported claim.

8. Assemble the working brief

The final brief should make drafting decisions and evidence gaps visible.

Brief fieldHypothetical entry
Sales questionWhich coordination problem should organize the page?
AudienceOperations managers evaluating workflow tools
Priority clusterCL-01: unclear ownership and changes
Product connectionPD-01 supported; PD-02 partially documented
Message hypothesisMH-01: visible responsibility
Lead alternativesDirect, problem-solution and story
Main objectionCL-02: rollout burden
Open issuesProduct limits, recurrence and setup evidence
Claim statusNo performance or meeting-reduction claim supported

Maintain an unresolved-claims register:

StatusMeaning
SupportedAppropriate evidence is recorded
QualifiedUsable only with stated limits
ContradictedMaterial evidence conflicts with the claim
Verification requiredScientific, legal, market, platform or performance support is missing

This process produces organized evidence and traceable hypotheses. It does not prove that participants represent the market, establish that a message will convert or replace legal and specialist review.

For broader research context, see /copywriting/research-voc/. Use the separate research checklist for execution tasks and the research template for a reusable document.

Sources and Method Notes

Books support theory and history; corpus notes are observational, not performance evidence.

  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 65.
  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 102.
  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 64.
  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 65.
  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 41.
  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 42.
  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 41.
  • Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 40.
  • Daily Intel transcript corpus. Convenience sample (n=12); observational, not conversion evidence.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For external context, readers should compare advertising and research decisions against authoritative primary references such as Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel adds the proprietary direct-response layer: blackhat, greyhat, and whitehat campaign pattern comparison across VSL-heavy niches and 14+ language markets.

For deeper evaluation, continue through Copywriting research library, VSL Ad Script: An Evidence-Led Structure and Editing Guide, VSL Copywriting Meaning: What a Video Sales Letter Is and How It Works, How to Build a Video Sales Letter Landing Page With a Timestamped Beat Map, VSL Landing Page Examples: Message Hierarchies to Study and Adapt, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.

Founding rate — locked forever

Access curated VSL intelligence for $29.90/mo

  • 50–100 manually validated VSLs every day at 11PM EST
  • major niches niches, 14+ languages, blackhat-to-whitehat pattern coverage
  • live catalog VSL/ad catalog, transcripts, UTMs, full funnel maps
  • Cancel anytime — founding rate stays yours forever

Daily Intel Service delivers manually curated research around active-scaling VSLs, Meta creatives, UTMs, funnels, and nutra market movement.

$29.90/mo

$299/mo

Coupon LIFETIME-269-OFF auto-applied

Claim the rate

Secure checkout · Stripe

Frequently asked questions

  • How is a process different from a checklist?

    A checklist records tasks. A process explains how evidence moves from collection to a message decision.
  • How should original customer wording be preserved?

    Save the exact excerpt with its source, situation, audience fit and surrounding context.
  • How do you separate an observation from a claim?

    Record the source material first, your interpretation second and the proposed copy claim third.
  • Which customer problems deserve priority?

    Consider recurrence, audience fit, contradictions, emotional importance and connection to a documented capability. No single factor is conclusive.
  • When is the research ready for drafting?

    Draft when the main hypotheses have traceable evidence, the product bridge is clear and every material gap appears in the unresolved-claims register.

Continue the research path

Related pages

Next in copywritingCopywriting Research Template: Turn Evidence Into Message HypothesesA useful copywriting research template does more than collect quotes. It preserves the path from source evidence to interpretation, then from

Lock $29.90/mo forever

Coupon LIFETIME-269-OFF · Cancel anytime

Get Access