Voice of Customer Shell: A Copyable Coding Sheet

Quick answer

A voice of customer shell is a blank coding sheet for raw prospect language. It keeps three things in separate columns:

“Voice of customer shell” is a practical label here, not a universally accepted term or method. The sheet helps you capture and code evidence. It does not conduct interviews, establish what an entire market believes, complete the analysis, or generate finished copy.

• The customer’s exact words and source
• Your provisional interpretation
• Possible uses or questions for later work

What a Voice of Customer Shell Is—and Is Not

This shell covers the first two parts of a larger workflow:

**Source material → evidence capture → preliminary coding → analysis → copy development**

An evidence unit is one coherent idea that you want to code, such as a stated problem, desired change, or objection. One interview answer can contain several units, but splitting it does not create several independent source occurrences.

The shell starts with prospect priorities rather than the product feature you want to promote. That prospect-first approach is consistent with the practitioner guidance in *Great Leads*. **[1]**

Use this page to build one coding sheet. Repository structure, full voice-of-customer analysis, and copy execution belong in separate workflows.

Copy the Voice-of-Customer Coding Shell

The block below is tab-separated. Copy it into a spreadsheet or table tool. The first line contains the column headers; the second is a blank starter row.

```text Record ID Source type Source reference Collection date Participant or author label Product or category Niche Context Exact quote Explicit situation Explicit concern Explicit desired change Explicit objection Inferred situation Inferred job Inferred pain Inferred outcome Inferred emotion Awareness or directness clue Interpretation evidence reference Confidence note Possible message use Solution bridge Possible opening tags Substantiation status Next research question [add] [add] [add] [add] [add] [add] [add] [add] [add] [leave blank if unstated] [leave blank if unstated] [leave blank if unstated] [leave blank if unstated] [optional] [optional] [optional] [optional] [optional] [optional] [quote words or source location] [add] [optional] [optional] [optional] [add] [optional] ```

Treat this field set as an editorial starting point, not an industry standard. Change it when the project requires different context or fewer interpretations.

Source and Traceability Fields

A quote should remain traceable to its original context. Note details that could change its meaning, such as whether it came before purchase, after a refund request, or in response to a leading question.

Current privacy, recording, retention, and platform requirements need separate review using appropriate primary sources.

Verbatim Customer-Evidence Fields

These are explicit-only fields. Leave one blank if the source does not state it. Do not fill gaps with assumptions.

For example, if someone says, “I keep opening the app, but I never know what to do first,” you can record the uncertainty about where to begin. You cannot record “wants an automated daily plan” as an explicit desire. That would be an interpretation.

Keep the exact wording untouched. If you shorten a long quotation, mark the omission rather than silently joining separate fragments.

Researcher-Interpretation Fields

An inferred job is not a fact merely because it sounds plausible. The same rule applies to pains, emotions, and desired outcomes. Connect every interpretation to supporting language and keep alternative readings visible.

An awareness or directness clue is also a working hypothesis. The retrieved practitioner material associates greater audience awareness with more direct openings and lower awareness or greater skepticism with less direct approaches, but treats that relationship as a tendency rather than a fixed rule. **[2]**

Optional Downstream Fields

These columns contain possibilities, not conclusions or finished copy. If you apply an opening tag, allow more than one when appropriate. The lead categories described in *Great Leads* are recurring patterns rather than perfectly separate boxes. **[3]**

“Substantiation status” means the current evidence position of a possible claim. Research may suggest a bold assertion, but supporting material must be checked before that assertion is used. **[4]**

How to Set Up the Shell

Start with a small, useful label set. Let actual source material reveal where definitions need to change.

• **Choose one product or category and one niche.** Label material from meaningfully different audiences instead of mixing it.
• **Create the three main groups.** Visually separate source evidence, researcher interpretation, and optional downstream use.
• **Define your labels.** Write a short definition for every source type, status, and recurring code.
• **Choose a source-reference format.** Every row should lead back to the original material.
• **Preserve the raw source.** Keep an untouched copy so someone can audit the coding later.

How to Code One Evidence Unit

Use the same order for every row:

This order makes it harder to reshape a quote around a feature or angle chosen in advance.

Preserve the Quote Before Interpreting It

**Original hypothetical example**

Customer statement:

> “By the time I decide what to work on, my uninterrupted hour is half gone.”

Weak, product-first summary:

> Customer wants an AI scheduling feature.

Prospect-first coding:

The improved version preserves what is known and exposes what still needs investigation.

• Add the record ID and source reference.
• Paste the exact quote.
• Record only the situation, concern, desire, or objection stated explicitly.
• Add provisional interpretations in their separate columns.
• Point each interpretation to the words supporting it.
• Record uncertainty and alternative readings.
• Add possible downstream uses last.
• **Explicit situation:** Has an uninterrupted hour available
• **Explicit concern:** Much of that hour is lost deciding what to do
• **Inferred job:** Establish a useful starting priority
• **Interpretation evidence:** “By the time I decide what to work on”
• **Possible solution bridge:** Explore whether guided prioritization is relevant
• **Next question:** Does the person want automation, a simpler process, or fewer choices?

Hypothetical Filled Example

Everything below is fictional and created only to demonstrate the shell.

> “I download meal plans every Sunday, but by Wednesday I’m improvising again because the recipes take longer than I expected.”

From Evidence to One Message Hypothesis

The sampled Daily Intel corpus contains cold opens that name a daily frustration before introducing a product. This is a pattern in that limited sample, not evidence of conversion performance or the wider market. **[5]**

**Original hypothetical adaptation:**

> “Your meal plan works beautifully—until the week actually begins.”

This line is copywriter invention based on the fictional concern. It is not a customer quotation or a documented winner. The shell should retain that distinction even when an idea sounds close to the original language.

For full copy development, move the evidence into a separate workflow instead of expanding the shell into a drafting system.

Mark Uncertainty and Avoid False Recurrence

Useful status labels include:

One source statement cannot establish recurrence. You may code several distinct ideas from it, but they still come from the same source occurrence. Repetition can justify further investigation; it does not by itself establish prevalence, importance, causation, or commercial value.

• Observed once
• Observed again in another source occurrence
• Possible pattern
• Interpretation unresolved
• Conflicting evidence

Quality-Control Checklist

Before moving into analysis, confirm that:

**Original hypothetical quality-control failure**

> Exact quote: Customer struggles with complicated meal planning. > Source: Online somewhere. > Pattern: Everyone wants faster recipes.

**Corrected version**

> Exact quote: “I download meal plans every Sunday, but by Wednesday I’m improvising again because the recipes take longer than I expected.” > Source: Fictional instructional record H-01. > Interpretation: Time requirements may contribute to abandoning the plan. > Evidence reference: “The recipes take longer than I expected.” > Pattern status: One fictional source occurrence; no broader inference.

• Every quote has a recoverable source.
• Verbatim language has not been silently rewritten.
• The surrounding context is recorded.
• Explicit evidence and inferred meaning occupy different fields.
• Unstated evidence fields remain blank.
• Each inference points to supporting words.
• Uncertainty and conflicting interpretations remain visible.
• Several codes from one statement are not counted as several source occurrences.
• Possible patterns are not presented as market-wide facts.
• Message ideas are not presented as customer quotations.
• Possible claims have a substantiation status.
• Downstream ideas connect logically to the underlying evidence.

What to Do After the Shell Is Populated

Move completed rows into a separate analysis process. There you can compare sources, investigate contradictions, refine codes, and decide which hypotheses need more evidence.

For broader context, see Research and Voice of Customer. For one downstream application, see VSL copy research. Repository governance, synthesis, prioritization, and finished copy remain outside this capture shell.

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. 64.
• **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. 102.
• **Daily Intel transcript corpus.** Convenience sample (n=0); 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, Copywriting Headline Swipe File: A Practical Working Framework, Storytelling Copywriting Course: An Evidence-Led Buyer’s Guide, The Storytelling Copywriting Formula: From Narrative Tension to Product Bridge, VSL Ad Script: An Evidence-Led Structure and Editing Guide, 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.