How to Turn Customer Research Into Copy

It's Thursday afternoon, and Hester owes the designer a page argument by Friday. Eighty interview excerpts sit beside a trial page still headed "Work smarter." The excerpt she keeps scrolling past is I09, from a shop owner who says the old spreadsheet works fine.

Hester is invented, and so is Pollenharbor, the inventory tool for independent craft shops she's writing for. Every interview line, record ID and draft sentence here is hypothetical.

The page is for owners who already track stock in spreadsheets and are thinking about a change before a busy market weekend. The designer needs to know what to show them, and why.

Freeze the brief before sorting the quotes

Before Hester sorts anything, she writes down the decision the page supports: should a shop owner try a stock-count workspace before the next market? Pollenharbor records quantities and flags low-stock items. It doesn't forecast sales or place supplier orders.

Writing that limit down early takes several tempting promises off the table. Beside it she adds a research question: when do owners stop trusting their current count, and what would make a replacement worth trying?

A quote about long-term expansion might be interesting and still have nothing to do with this page. Save it for another assignment.

Copyhackers' research overview connects research with message selection and hierarchy. I'd start there, then make the selection visible so someone else can see why you chose what you chose. The broader copywriting research lesson covers collecting the product facts this handoff also needs.

Reduce excerpts to findings without losing the source

Hester reads every record in a theme, exceptions included. Then she writes a short finding with the record IDs attached, and marks which excerpts came from the same person.

Keep observation and interpretation apart. I03 reports counting display stock again because the sheet is behind. "This owner recounts before the Saturday order" preserves the behavior; "owners need confidence" jumps to a broader explanation.

I07 wants a count to rely on when ordering. That supports the importance of the task, while leaving their current checking routine unknown.

Nielsen Norman Group's guidance on thematic analysis describes coding qualitative material and developing themes from it. Your drafting handoff starts after that work. One theme may need a single sentence on the page, so don't let the number of tags decide the structure.

Pollenharbor evidence bundle

Situation: interview I03

Before I order for Saturday, I count the display stock again because the sheet is usually behind.

Desired outcome: interview I07

I want one count I can use when I make the supplier order.

Objection: support S02

Will I have to enter every item before I can see how it works?

Exception: interview I09

Our sheet works fine because only one person changes it.

Keep the task and the exception visible in the handoff.

That last card is the one Hester kept skipping. Read again, it raises a question she hadn't written down: does the number of people changing the stock decide whether a spreadsheet stops working?

One owner can't settle that. So she keeps I09 in the brief and adds a comparison of single-editor and shared-editing shops to the next research round.

Build a message-and-proof table

For each candidate message, Hester separates customer evidence from product evidence. She records a drafting decision next to them so the designer can see which promises still need checking.

When a promise has no product evidence yet, she marks it pending and names who will check it. Asking the designer to make it look convincing in the meantime would hide the gap.

Give the product reviewer a concrete check. Start with a known physical quantity and enter it in Pollenharbor. Record a stock change, then compare the displayed quantity with the stock you can count.

Next, remove an item without recording the change. Compare the display with the physical count again and document the discrepancy.

Enter the missed change and check whether the counts agree. Save the steps and the conditions with the candidate claim.

That record supports wording about the workflow checked. A claim about accuracy across other stock situations would need evidence covering those situations too.

The FTC's U.S. advertising-substantiation policy calls for support for objective claims before publication. It weighs factors including the consequences of a false claim, so match the check to what the page promises.

Which message should open the page?

Hester picks a provisional opening about preparing the next supplier order. I03's recount and I07's desired outcome make that task relevant. She keeps the wording about recorded stock beside the check that supports it.

A common theme deserves a look, and its frequency still can't pick the headline on its own. One unresolved condition that stops a suitable buyer from trying the offer can matter more than a minor complaint repeated in twenty records.

She keeps the condition in sight: people have to record stock changes. If the page promises a current count and hides that work, owners will find out after signing up, and the support inbox will hear about it.

Use the desired-outcome lesson to sharpen the scene and the customer-objection lesson to find what a doubtful reader needs next. Write one sentence saying why this message goes first and what evidence would make you reconsider.

Order the page around the reader's next question

The designer needs to know what follows the opening. Hester puts the stock view next to its manual-update requirements, then shows how an owner can try the workspace.

Pollenharbor page argument

Prepare the next supplier order with a clearer view of your recorded stock.

See what needs attention

Understand how counts stay accurate

Try a limited setup first

See what needs attention

• Show a realistic low-stock list and explain how thresholds are set.

Understand how counts stay accurate

• Demonstrate recording a sale, receipt or correction. State that unrecorded changes are not included.

Try a limited setup first

• Show the sample workspace and explain the confirmed options for adding a few items.

Review the page sequence as plain text before layout. Check that the manual-update condition sits beside the stock-view promise. The messaging-hierarchy lesson builds out the wider strategy document.

Write a rough page with evidence placeholders

Say the product checks confirm manual updates, low-stock thresholds and an optional sample workspace. Hester keeps the evidence IDs in her working file as she drafts the page.

Before you place the next supplier order, see what needs restocking.

Keep recorded quantities and low-stock items together. Enter stock changes as they happen, then review the list before ordering.

Set a low-stock level for each item. When its recorded quantity falls below that level, the item appears on your low-stock list.

Try the sample workspace first. Add a few of your own items when you're ready to explore your setup.

Explore the sample workspace.

The product reviewer gets the threshold claim with a demonstration showing when an item enters the low-stock list. The onboarding owner gets the partial-setup line with the confirmed signup steps. Each can review a specific promise against the experience it describes.

The owners' words helped her decide where the page begins, and none of them has become a testimonial. A real customer quotation would need its exact wording checked and the right permission to publish it.

Keep the reader's explanation beside the relevant draft sentence.

Check the draft against a missed update

Show the designer where the manual-entry requirement belongs: beside the stock display. Ask a new reader to explain what happens to the displayed count when someone removes an item without recording it.

Review the leaps, then review the language

Do a claim pass before a style pass. Hester underlines every factual assertion, implied outcome and condition. Then she asks what a reasonable reader would expect from each line.

"See what needs restocking" sounds harmless. A new reader might still assume the tool notices a sold mug on its own, so she keeps the manual-entry sentence right alongside it and flags the question for testing.

GOV.UK's research-analysis guidance separates observations from findings and actions. Keep those stages in your handoff so a reviewer can challenge the reasoning without digging through transcripts.

A practical handoff review

Do

• Trace each main message to source IDs and each factual promise to product evidence.
• Keep conditions and contradictory accounts in the working brief.
• Mark the direction as a candidate for evaluation.

Avoid

• Count several excerpts from one person as several independent customers.
• Blend different people's sentences into a single invented quote.
• Call a research-informed draft a proven conversion winner.

Then edit for language owners would recognize. Swap internal labels like "inventory visibility" for the task as they describe it. Keep the conditions that matter even when they make a line less elegant.

Make the next evaluation answer a question

Hester will use the missed-update scenario above to check whether suitable readers understand manual entry. Then she'll ask what they expect after clicking the sample invitation. Those answers will guide revisions to the update explanation and the transition into setup.

A misunderstanding gives her something to fix in the copy or the offer. Small sessions like these show how people understood this draft. A conversion gain would need a controlled comparison with its outcome and decision rule set in advance.

Keep the evidence next to the draft

At six on Thursday the handoff is ready: a page argument the designer can follow, and claims the product owner can check line by line. The open audience question goes to the next round of Research.

Before she sends the file, Hester moves I09 to the top of the brief and opens the next interview plan. Beneath the owner's words, she types, "Compare shops with one stock editor against shops with several."