Direct-Response Copywriting

A sales page can be polished and still miss the reason someone is reading it. The gap usually opens before drafting. The writer has a loose idea of the audience but no clear account of the reader’s situation, decision or next step. Research replaces those guesses with evidence. In this chapter you define a specific reader and the progress they want. You gather their words from interviews, reviews and enquiries. Then you turn the findings into a short brief. Along the way you keep what you know separate from what you infer. By the end you can open any copy assignment with a defined reader, a clear action, evidence about their decision and a list of assumptions still to check.

“Small business owners” describes a large audience. It does not tell you what any of them is trying to decide. Useful research narrows the reader by situation: what prompted them to look, what they already know, what they are comparing and what could stop them acting. A founder choosing a payment service before opening a shop faces a different decision from one replacing a provider after a failed transaction.

Jobs-to-Be-Done gives you a lens for that situation. In Harvard Business Review, Clayton M. Christensen, Taddy Hall, Karen Dillon and David S. Duncan argue that the circumstances a person is in explain their choices better than their characteristics do [1]. They add that a job is never only functional. It has social and emotional sides too. Here “job” means the progress a person wants, not their job title. Use the lens to shape your questions, not to answer them.

A desired action must be observable. “Feel interested” is not something you can count. “Book a product demonstration”, “request a quote” or “start an application” is. Choose the action the copy should prompt and name where it happens.

Suppose Emma, a marketing specialist in Hyderabad, is writing a landing page for a regional accounting software provider. The page is for independent consultants comparing ways to organise invoices before tax season. The action is to book a demonstration. That framing hands Emma clear questions. What triggers the search? What is hard to manage now? What would make a demonstration worth the time? Which concerns could stop a booking?

Before drafting, finish four sentences: “This copy is for…”, “They are considering this because…”, “They need to decide…” and “After reading, they should…”. Check that the action fits the situation. A reader still comparing options may need a conversation before a commitment. And do not mistake a persona for evidence. Invented details about age or personality do not establish a buying need.

You rarely need a large formal study to start. Useful material often sits in customer interviews, product reviews, support tickets, enquiry forms, sales-call notes, feedback portals and customer relationship management records. UserVoice’s guide describes collecting feedback from sources like these, bringing it into one view, then finding patterns and acting on them [2].

Copywriter Joanna Wiebe of Copyhackers explained in a 2017 Wistia interview that this work is manual [4]. Her team reads survey answers, interviews and public reviews line by line, then highlights and tags phrases that repeat or surprise. She gives an example: a team might stress ease of use when customers actually say the product makes them faster. The next step is to gather those “fast” phrases and test them in copy.

Each source has limits. A review comes from someone who chose to write one. A support enquiry reflects one question in one context. A sales-call note may carry the seller’s summary. Treat each item as evidence of what one person said, not proof of what every reader believes.

Record exact wording in quotation marks when you have it, and keep your explanation in a separate field. Suppose a buyer writes, “I need to know whether this will work with our current booking system.” The observation is a question about compatibility. Your interpretation might be that switching systems feels risky. That may be fair, but it stays an inference until other evidence supports it.

Suppose Daniel, a customer-support lead in Rotterdam, is helping a logistics firm write copy for a delivery service aimed at small retailers. He pulls relevant questions from enquiry emails, feedback forms and recorded interviews. For each item he notes the source, the reader’s situation, the exact wording and any interpretation he wants to test. He removes personal details the task does not need and follows his organisation’s rules on customer data.

Two mistakes are common. One is treating a memorable comment as the audience’s shared view. The other is polishing a reader’s words into marketing language before you record them, which erases the concrete concern you need to answer. Frequency alone tells you little. Check who asked, at what point and what proof might help them decide.

A research brief is not a transcript or a pile of every comment. It is a short working document that tells the writer who the copy addresses, what that reader is trying to do, what evidence supports the message and what action to prompt. It helps someone choose which concern to answer first, what proof to include and what the call to action should ask. The structure below is a practical one used in this course, not an industry standard.

Do not give every note equal space. A finding belongs in the brief when it changes how the writer understands the reader or shapes the message. Interesting details that change nothing stay in the research record.

Suppose Leo, a communications specialist in Lagos, is preparing an email for a regional bank that offers a business account to independent caterers. The email should prompt an enquiry about opening an account. Enquiry notes ask about separating business and personal spending, which documents an application needs and how long the process takes. Leo records the exact questions and their sources. The idea that readers fear rejection is his interpretation, so he marks it for checking rather than making it the central claim.

Leo’s brief might read: “For independent caterers considering a separate business account now that they take regular customer payments. Prompt an enquiry about opening an account. Enquiries ask how to separate spending and what an application requires. Explain the enquiry route and give verified application details. Check whether fear of rejection appears in further reader evidence.” It guides a draft without pretending the research answered everything.

Read the brief as if you had missed the research. Can you name the reader and situation? Is the action observable? Can you trace key reader language to a source? Are interpretations labelled? Does each message implication follow from the evidence? If a writer would have to guess, revise the brief or state the open question.

Common problems include pasting a whole interview into the brief, reporting a team opinion as a customer finding and leaving out the action. Keep claims about the offer separate from reader evidence, and confirm product details with the right internal source before you use them.

Suppose Sara, a marketing coordinator in Melbourne, must prepare a landing page for a subscription meal service aimed at shift workers. The page should prompt a trial order. Customer enquiries ask whether delivery can fit changing work hours. Reviews mention convenience but do not say which delivery arrangements readers need. A colleague says the audience mainly wants cheaper meals. Your task is to turn this into a sound brief without treating that view as a finding.

You can name a specific reader in a real situation, state the action the copy should prompt and back your message choices with reader evidence. You keep exact language and its source, separate observation from interpretation and mark open questions instead of filling them with confident guesses. Your brief gives another writer enough direction to draft and makes your reasoning easy to check.