Learning copywriting

How copywriting differs from writing

Copywriting is writing text that asks the reader for one specific action. The definition is simple and it has a hard consequence: the measure of quality comes from outside the text, not from inside it. A beautiful sentence after which nobody does anything is a bad sentence in this craft, however fond of it you are.

So the question changes. In a teaching piece we ask whether the reader learned something. In copy we ask whether the reader understood what to do next and why now. Every small decision in the text, from sentence length to paragraph order, is an answer to that second question.

There is another difference that gets less airtime: in copy, cutting takes longer than writing. The first draft is always longer than what is needed, and the second pass is almost always the shortening pass. If your text got longer after an hour of work, you probably moved in the wrong direction.

How a headline actually gets written

The headline is the only part everyone reads, and it has exactly one job: get the reader to the next line. Not to sell, not to summarise the whole page. That is all.

Three things burn a headline. First, being generic: "a comprehensive solution for your business" is about nobody, so nobody claims it for themselves. Second, cleverness: a headline that has to be read twice to be understood does not get read once. Third, promising something the rest of the page does not deliver; that one earns the click and burns the trust, and burnt trust is not recovered by the next headline.

The practical method is plain and needs no taste. Instead of hunting for one good headline, write seven, each making a different promise rather than seven wordings of one promise. Then ask each one a question: after reading this, what exactly can the reader do? Any headline whose answer is "know more" gets deleted. Usually two of the seven survive, and choosing between two is not hard.

Feature or benefit: which one goes in

A feature is something the product has. A benefit is what changes for the buyer because of that feature. "A six stage filter" is a feature; "the water tastes different and the kettle stops scaling" is a benefit.

The common rule says write benefits, not features, and it stops halfway. A benefit with no feature behind it is an unsupported claim, and a buyer who is comparing goes looking for exactly that feature so they can put two options side by side. The order that works is: benefit first, the feature immediately behind it, and any number you have right there, so the claim can be checked.

One thing we keep noticing in technical sales: the more expert the buyer, the heavier the feature side gets. For someone who sets up servers themselves, writing "fast" says close to nothing and writing a model and a number says something. So the audience sets that balance, not a general rule repeated in every course.

A real rewrite: before and after

The example is a laptop repair shop, because it is simple and nobody in that trade is making grand claims. The original, the kind of text you see everywhere:

"Provision of specialist laptop repair services drawing on an experienced team and quality parts, together with a valid warranty. Your satisfaction is our pride."

And the rewrite:

"Laptop will not turn on? Diagnosis is free, and by six the same day we tell you what is wrong and what it costs. If it cannot be repaired, you pay nothing."

Four things changed and none of them is about being prettier. First, the opening line names the reader situation instead of introducing the company; the person reading this has a laptop that will not start right now. Second, adjectives gave way to a checkable commitment: "experienced" and "quality" cannot be disputed, "by six the same day" can. Third, a clear financial condition arrived, which moves the risk off the buyer. Fourth, "your satisfaction is our pride" is gone, because it is about the writer rather than the reader.

And now the condition that teaching material usually leaves out: the second version is only better if every sentence in it is true. If you cannot answer by six every time, do not write it. A specific promise that goes unmet does more damage than a vague sentence, because the buyer knows exactly where you lied.

Why plainness pays off more in Persian

Our position is plain: clarity sells more than cleverness, and in Persian the gap is wider than in English. The reason is not cultural, it is a writing habit. Formal Persian has been written for years with heavy verbs and bureaucratic constructions, and that register carried over into advertising copy. A Persian reader recognises the tone and has learned, without thinking about it, that there is usually nothing behind it.

The practical consequence is short. Use plain verbs. Then take out the adjectives that measure nothing, such as "professional", "high quality", "leading" and "the best", and see what the sentence lost. Usually nothing, which is the proof that they were saying nothing to begin with.

For us this is not personal taste, it is a written rule. The site publishing this lesson keeps a content rules file that explicitly bans twenty two Persian phrases, and no text goes out without being checked against that list. The editorial policy is the public version of the same rules. The reason for the strictness is simple: those phrases are not merely useless, they signal to the reader that the writer had nothing to say and is filling space.