Sales Message Examples for Fans: 10 Annotated Cases
Ten sales messages you could send as written, each with the reason it holds or fails, including three counter-examples built on the faults we measured.
Published 28 July 2026
Most collections of sales messages are a list of lines with nothing attached, and it teaches you nothing. A line that lands in one thread fails two messages earlier in another, and the list never says which is which.
What follows is ten messages that could be sent as written, each with the reason it holds or
fails. Seven are built to be copied; three are built to be recognised and deleted. Prices
appear as [price], which you fill in from your own list.
What makes a sales message work?
It names one object, names the price, and says what happens next. Then it stops.
- One object. Two offers in one message turns it into a comparison, and comparisons stall.
- The price stated flatly. A number surrounded by hedges reads as negotiable, because that is plainly how the person who wrote it treats it. Holding it when the fan pushes back is its own move.
- A next step you own. “I’ll send it through” ends the message with your move. “Let me know” ends it with theirs.
- Placement past the sixth message. Our data puts an early pitch at roughly a third of conversion lost, with the optimum after about ten exchanges. When you pitch moves the number more than how you pitch.
- Three prohibitions at the close, demonstrated in the last section.
What does a clean first offer look like?
One object, one number, one statement of what happens next.
Example 1: the plain offer.
I shot something this afternoon that’s more your thing than what I usually post. It’s [price]. I’ll send it over now and you can tell me what you make of it.
Why it holds: object, price, next step, in that order. The last line is a statement, not a request for permission. The reason given for the offer is about the content, not about the fan’s biography.
Example 2: personalisation, placed upstream.
You said you’d rather have one long thing than a stack of short ones. That stuck with me.
So: the long version, one file, [price]. Going out in a minute.
Why it holds: the personal line and the offer are two messages, not one clause. The offer sentence carries no history about the fan. This is the same edit as the callback mistake, applied before it becomes a mistake.
How do you offer a bundle or a custom piece?
As one deliverable with one number, so the fan decides once.
Example 3: the bundle.
There’s the set from the shoot, plus the clips that didn’t make the cut. [price] for the lot, which is less than they come to separately. It goes out as one file.
Why it holds: the bundle is described as a single thing to receive, so the fan is deciding once rather than picking. The saving is arithmetic the fan can check, not a claim about value.
Example 4: the custom request.
I can do that one. Give me until tomorrow evening and it’s yours. It’s [price] because it’s made for you and it doesn’t go anywhere else. I’ll start on it as soon as it’s through.
Why it holds: the clause that carries the price is about the object. A custom is one-off by definition, and saying so names what the fan is buying rather than what he once told you. Describing the piece as made for one person is not a personal callback; recalling the fan’s week is, which is counter-example 10. Delivery time is stated before the price, so the number arrives attached to something.
How do you offer to a fan who already knows what they want?
A repeat buyer and a fan who asked need no build-up.
Example 5: the second offer to a fan who has bought before.
The other half of that shoot is edited. It’s longer than the first one and it’s [price]. Going out to you now.
Why it holds: nothing is re-explained, because a fan who has bought already knows the format and what he is getting. The only thing referred to backwards is the previous file, named as an object rather than produced as a favour being recalled.
Example 6: the answer to a direct question.
Yes, there’s a version of that with sound. It’s the long one, [price]. I’ll send it across now.
Why it holds: the fan asked, so the offer is an answer rather than an interruption, and the request already carries the interest the rest of a sales message has to build. Nothing is added to sell it. The price sits in the same breath as the detail that answered the question.
What does an offer inside a mass message look like?
The same shape, with nothing borrowed from a thread.
Example 7: the broadcast.
The set I said I was saving is finished. [price] for the whole thing, one file, going out tonight.
Why it holds: a mass message has no thread behind it, so it borrows nothing and pretends nothing. The same closing rules apply, and with less context to recover from a weak last line, the ending matters at least as much.
Which sales messages lose the sale, and why?
These three, each built on one of the closing faults our data measured.
Counter-example 8: the ellipsis.
I’ve got something new and I really think you’d like it… it’s [price] if you want it…
Why it fails: ending a sales message with an ellipsis is the worst-performing closer in our corpus. It reads as hesitation about your own offer. “If you want it” compounds it by making the sale conditional on enthusiasm the fan has not yet expressed.
Counter-example 9: the closed question.
The full set is ready, [price] for everything. Do you want it?
Why it fails: a closed question at the moment of closing costs several points of conversion. Yes-or-no hands the fan a one-word exit they would not otherwise have typed. How to end a sales message rewrites this ending, and four others, line by line.
Counter-example 10: the callback at the pitch.
I remembered you saying your week had been brutal and you needed to switch off, so I made this with you in mind, [price].
Why it fails: a personal callback placed at the exact moment of the pitch costs points, and it is the most counter-intuitive result in our corpus. The recalled detail acquires an obvious purpose, and the fan gets it in the same breath as the number. Split it into two messages, as in example 2.
What separates the two groups?
| Element | Working examples | Counter-examples |
|---|---|---|
| Last line | States your next move | Trails off, or asks a yes-or-no |
| Personal detail | In the message before | Inside the offer sentence |
| Price | Stated, then silence | Stated, then softened, questioned or fused to a callback |
| Where placement sits | Past the sixth message | Wherever the shift got to |
What do you change tomorrow morning?
- Read the last line of every offer sent in one shift. Count the trailing dots and the yes-or-no questions. That count is the cheapest thing on the page you can fix.
- Split every fused pitch in two. Personal line first, offer second.
- Put the three prohibitions in the script as prohibitions, not preferences.
- Rewrite these ten in the creator’s voice and keep them as worked examples, never as a message bank.
Frequently asked questions
Can I copy these messages straight into my inbox?
You can send them as written, but they will read as somebody else's voice inside a week. Use them the way a chatter uses a worked example: keep the shape, the order of the parts and the prohibitions, and rewrite the words in the creator's register. Two fans comparing identical text is a worse problem than a clumsy sentence.
Why is there no price in any of the examples?
Because a number printed on a guide becomes an anchor, and we have measured nothing about price levels. The placeholder is there so you fill it from your own price list. What the examples do show is where the price goes in the sentence and what tone the line after it sets.
How long should a sales message be?
Short enough that the object, the price and the next step are all visible without scrolling. Length is not the real variable, though: the failure mode is not word count but extra clauses about the fan, which dilute a sentence that should be about the thing being sold.
Do these examples work for a mass message as well as a one-to-one thread?
One of them is written as a mass message and is marked as such. The difference is that a broadcast has no thread behind it, so it cannot borrow context and it must not pretend to. The closing rules apply identically; a mass message has less to recover with if the last line is weak.
What do I do if the fan replies that it costs too much?
You hold the price and keep the conversation, which is a separate skill with its own moves.
Are these examples measured, or written?
Written. The messages are illustrations. What is measured is the set of rules they obey: the timing of the pitch, and the three closing faults the counter-examples were built to demonstrate. The rules are the finding; these sentences are only one way of obeying them.
See what it looks like in practice
The justonedash chatbot holds the conversations, keeps each creator’s voice and works around the clock.