312. Offers, objections and honest risk

The page is persuasive until the reader reaches the button. Then the questions arrive all at once. Is the license per computer? Will my old files open? What happens when the trial ends? Can I get my money back? The page has answers to most of them, somewhere below the footer, in a section called “FAQ” that nobody reached.

An offer is not only a price. It is the whole set of terms a reader weighs at the moment of decision: what they get, what it costs, who qualifies, how long it lasts, what they risk and how they can leave. Objections are the questions that stop them. This chapter puts both where the decision happens.

The offer card

Before writing offer copy, fill a short card. Use this fictional packet throughout the chapter:

Field	Supplied detail
Product	A font editor, version 5
What the buyer gets	A version 5 license and its updates
New license	EUR 199
Upgrade from version 4	EUR 49 until 30 November 2026, 23:59 CET; EUR 69 afterwards
Reason for the introductory price	Version 5 has just been released
Trial	30 days, every feature, exports carry a watermark
Refund	Within 14 days of purchase
Unknown	Tax treatment, device allowance

These are invented terms for a writing exercise. The unknowns must be resolved before a real offer is published.

Now apply the one-sentence test. Can you say who qualifies, what they get, the price and the date in a sentence or two?

Owners of version 4 can upgrade to version 5 for EUR 49 until 30 November 2026, 23:59 CET; after that the upgrade costs EUR 69.

If the sentence will not come, the offer is not ready, and better copy will not fix it. Ask for the missing term.

Give every offer a true reason

A discount without a reason reads as a tactic. A discount with a stated, true reason reads as a decision someone made. In the packet, version 5 has just been released, and that is the stated reason for the introductory upgrade price. An education price, a crossgrade from another editor or an upgrade price can each state its reason in a sentence; if the reason is not supplied, ask for it. Discounts tied to eligibility are honest when their reason is stated.

Never invent the occasion. A “birthday sale” for a company whose founding date is elsewhere, a “last chance” that returns next month, a “special price for you” sent to everyone: each is a small lie that makes the next true offer harder to believe.

The terms block beside the button

Put the exit terms in the same block as the price, where they read as part of the offer rather than a defense against a complaint:

Upgrade from version 4: EUR 49 until 30 November 2026, 23:59 CET (EUR 69 afterwards). New license: EUR 199.

The 30-day trial has every feature; exports carry a watermark. Refunds within 14 days of purchase.

Upgrade now

Trial length, what the trial limits, what happens when it ends, the refund window and how to cancel a renewal all belong here when they apply. So does what the buyer keeps if they stop: whether the version they bought keeps working, whether files stay in an open format. These facts reverse risk more honestly than any guarantee language.

Name the kind of promise exactly. “Refunds within 14 days of purchase” is a term. “Risk-free” is a mood. A guarantee about outcomes (“twice as fast or your money back”) is a promise the company cannot keep for every reader and will not appear in our copy.

Let the price stand

Apologetic: It costs EUR 199, which is honestly less than a couple of coffees a month if you think about it.

Plain: A version 5 license and its updates: EUR 199.

What the price buys belongs before or beside the number, in the reader's terms. After the number, the reader needs the conditions and the button. An apology or a minimizing comparison after a price sounds as if the writer does not believe it either. Answering a reader's price question with what the price covers is not an apology; it is the answer.

Avoid “only” before a price, invented reference prices (“normally EUR 299”), charm framing and per-day arithmetic that hides the total. If the reader can pay monthly or once, print both totals so they can compare without a calculator.

When the price is the objection

Ask “Compared with what?” first, and name the alternative the reader is weighing (another tool, an older version, doing the work by hand) before stating the value.

The honest answer to “too expensive” is rarely an unexplained cut on the same thing, which suggests the first price was not real. More often it is a different package at its own price, clearly described. [Hypothetical edition]

If you do not use scripting, the Studio edition costs EUR 119 and includes everything on this page except the scripting panel.

Or it is a narrower recommendation. A good advisor does not hand over a menu; they ask what the reader is making and recommend one option with the reason. “If you only convert fonts between formats, TransType is the tool; you do not need a full editor for that.” The reader who hears that will remember who said it.

Every claim needs its evidence before it appears

A factual claim is safe to print only when the evidence is already on file, for every reasonable reading of it. “Opens every format a type designer meets” promises a complete list; “saves hours” promises a measurement; “the only converter” promises a survey of the market. Keep one row per claim: the claim, its readings, the evidence, the version tested, the date and who tested it. Pages and emails draw only on sentences that have a row. When the evidence is missing, describe the mechanism instead.

Quotations follow the same rule, because a customer's sentence that we publish is our claim. Show the date, the product version and the source beside it. Disclose any connection: employment, a partnership, a free license, a pre-release build. Retire a quotation about a version the speaker has not used.

“Free” carries its condition everywhere it appears: the subject line, the preheader, the post, the notification and the translation. “TransType 5 is free for you” sent to a mixed list fails; “Free if you bought TransType 4 in 2026” passes. An earlier or later price named in copy is a price that was or will actually be charged.

Real deadlines

Deadlines are allowed when they are true. Check each one:

1. Is it real and specific: a date, a time, a time zone?
2. Is there a true reason for it?
3. Does something actually change when it passes?
4. Is it stated the same way everywhere the offer appears?
5. Will we keep it?

The fifth question is the one that matters over years. A company that extends every “final” deadline teaches readers to wait. A company that keeps them makes the next deadline credible without raising its voice.

No resetting timers, no “only 50 licenses left” for a digital product, no “offer ends tonight” that does not.

Early access, described as it is

A beta or early-access offer is attractive precisely because it is unfinished. Say what works today, what does not, what the reader gives in return and how their feedback is handled:

Version 5 is in beta. Masters and kerning work; scripting is not finished. Beta access is free. In return we ask for one short report of anything that breaks; we read reports on Tuesdays and Fridays. [hypothetical terms]

A limit on places is acceptable when it is real and has a reason (“so each report gets read”). A limit invented to create a rush is not.

Collect objections before writing

Objections are evidence, and they can be collected. Read support mail, forum threads, reviews of our products and of the tools readers compare us with, and the questions people ask before buying. List the reasons someone does not buy, in their words. Rank them by how often they appear.

For a font editor, the list might include: my old files may not open; the license may not cover my second computer; my scripts may break; learning a new tool will take weeks; I may not be able to undo the decision. Some of these are about the product. Others are about the reader's confidence in themselves: “I have never made a font”, “I cannot draw”. Those deserve their own answers, usually a demonstration of the first useful task rather than a claim that everything is easy.

Answer each objection where it arises

An objection answered in an FAQ at the bottom of the page arrives after the reader has left. Put the answer next to the decision it blocks:

• “Will my files open?” beside the upgrade price.
• “Is the license per computer?” beside the license options.
• “Can I try it first?” beside the buy button.

A useful order for each answer is objection, claim, proof, benefit:

Objection: Moving to a new editor means relearning shortcuts.

Claim: You can choose the shortcut layout you already know. [CONFIRM LABEL]

Proof: The shortcut preference, shown with the layouts listed.

Benefit: The first evening is spent on letters, not keys.

If the claim is not true, the honest answer is still an answer: “Shortcuts differ; the cheat sheet lists the 20 you will use first.” [CONFIRM: cheat sheet exists]

Answer the strongest real objection directly, including the honest limit. Expert readers distrust a page that never admits a weakness; naming one and answering it with facts makes the rest believable. An answer can raise a second question, so keep a follow-up column in the objection list and answer that one too.

Name the objection in its own words

An answer to an objection the copy refuses to name sounds evasive. Write the reader's worry as they would say it (“Will my version 4 files and settings come across?”), then the fact or the literal term that answers it. Naming a real limit plainly is also one of the few things that raises belief in the claims around it.

Objections the corpus keeps meeting

• “It looks hard.” Count what a first result actually needs: the tools, the steps, the time on a stated example. A number answers difficulty better than “easy”.
• “I can find this free.” Say what the free route costs in time or limits, without disparaging it, and name when the free route is enough.
• “Not in the budget.” Budget is not value. State the price plainly and, where it exists, a smaller package at its own price.
• Running costs. When a feature runs on the buyer's own account with a third party (an AI provider, a cloud service), give a measured cost for a typical run, or say that the cost is the provider's and how to see it.
• Ratings. Quote a rating with its base and, where available, the distribution: “4.6 from 212 ratings”, not “highly rated”.

Close with the choice

End a notice to owners on the last fact, and let that fact be the choice: “Version 4 keeps working. Upgrade when the master view matters to you.” People agree more readily when they are told, sincerely, that they are free to decline. The sentence must be true: if the old version stops working on a date, say the date instead.

Fit statements

Sometimes the most useful sentence on a page tells some readers to go elsewhere. When the evidence supports it, say who the product is for, what they need before starting, and when another tool will serve them better:

You will need outlines to start: a font, a drawing or a scan you can trace. If you are looking for fonts to use rather than to make, a font library is the better place to begin.

Write fit as a requirement, never as a judgment. “For serious designers” grades the reader; “You will need outlines to start” informs them. A fit statement is not compulsory on every page, and it should not invent exclusions to sharpen a headline. Where the product genuinely serves many readers, routes serve better than a refusal.

Answer the reasons people give for not buying

When surveys, replies and support questions show why people did not buy, group those stated reasons: price, fit, quality, timing. Answer each with matching evidence: a plain cost statement, a named permissioned user, a sample file, the trial. Send reminders only to people who asked for mail, address the reason they gave rather than one you guessed, and limit how often anyone sees them.

Practice: one offer, one objection

Use this fictional packet (its prices and terms are invented):

• A line-art app costs EUR 79 for a perpetual license.
• The free demo opens and edits files but cannot save them.
• Version 3 adds a new fill type; owners of version 2 upgrade free.
• No trial, refund or tax terms are supplied.

Write the offer sentence for a newcomer, then the terms block beside the download button, using [CONFIRM OFFER: refund terms] where a term is missing. Then take the objection “I cannot draw, so line art is not for me” and write an answer in four parts. The proof must be something the app can show: a photograph turned into line artwork, with the settings visible.

Read the result as the doubtful reader. Is anything they need to decide missing from the block? Does any sentence apologize for the price or invent a reason to hurry?

Checklist

• The offer passes the one-sentence test before any copy is written.
• Every promotion has a true, stated reason.
• Price, eligibility, term and exit terms sit together beside the action.
• The price stands without “only”, an invented reference price, an apology or a minimizing comparison.
• Risk reversal is expressed as literal terms; no outcome guarantees.
• A real deadline has date, time and time zone, appears everywhere and is kept.
• Price resistance is met with a clearly described package or a narrower recommendation; eligibility discounts state their reason.
• Early access says what works, what does not and what the reader gives.
• Objections come from evidence, are ranked and are answered where they arise.
• The strongest real objection is answered directly, with its honest limit.
• Fit statements are requirements, not judgments, and appear where evidence supports them.
• Every factual claim has its evidence on file for each reasonable reading; quotations show date, version, source and any connection.
• “Free” and every earlier or later price carry their condition in the same unit, in every format and language.
• The strongest objection is named in the reader's words before it is answered.
• A notice to owners ends on the last fact, which may be the reader's free choice, stated truthfully.