How to write a decision explainer a buyer can send to a teammate
The shape of a product explainer that answers one question, shows the tradeoff, and still makes sense when someone forwards the URL.
What is a decision explainer?
A page that answers one buyer question about a product: who it is for, what they give up, and when it is the wrong call. A teammate who opens the URL without the original conversation should still be able to decide whether to take the next step.
One question, written as a question
“Is Fieldnote worth it for a support lead who already has a help desk?” is a question a page can finish. “Everything about Fieldnote” is a brochure. Put the question in the title or in the first line so the rest of the piece has a job.
If you discover a second question while drafting — pricing for enterprises, or a migration from a different tool — it is a second piece. A forwarded URL that answers two questions usually answers neither, because the reader does not know which one they were sent.
Write for the person who was not in the meeting
The teammate did not hear your pitch. They have the link and a minute. The first section should restate the product, the person, and the question without “as we discussed.” Context that lives only in the sender’s head dies in the forward.
Name the constraint that makes this a decision: team size, an existing help desk, a deadline before next standup. Constraints are why a smart product can still be the wrong yes.
Show the tradeoff in sentences, not a slogan
Every useful product refuses something. Fieldnote might refuse to be the system of record and only brief what the help desk already knows. Write that refusal next to the benefit. A page of benefits with no refusal reads as an ad, and teammates skip ads.
Use the product’s actual boundary. Invented tradeoffs (“it might be too powerful”) insult the reader. If you do not know the boundary, you are not ready to explain the decision.
A section for “not this”
Give the wrong fit its own short section. Who should keep the shared inbox. Who needs an admin the product does not replace. This is the paragraph a skeptical teammate looks for, and it is the paragraph that makes the yes believable.
Do not hide the “not this” under a FAQ at the bottom if it changes the decision. Promote it until it sits near the tradeoff. People forward the part they trust. They trust a page that can say no.
End on the next step, not a crescendo
The last section should say what the reader can do with the answer: try the brief on last week’s tickets, or stop and stay with the current queue. A crescendo (“the future of support”) throws away the decision you just earned.
One link to the product is enough, in a sentence that matches the answer. If the answer was “not for you,” the link can still be there for the person it is for. Do not beg.
Read it as the recipient
Open the draft in a clean window, without the outline beside it. Ask whether you know the question, the person, the tradeoff, and the no. If any of the four is missing, the piece is not forwardable yet.
Piece Press is built for that read. A longer page is not a padded page. It is a page with room for the no. If you cannot fill that room with the decision, write a shorter story on another desk.
Questions
How long should a decision explainer be?
Long enough to hold the question, the fit, the tradeoff, and the no — often somewhere past 800 words and rarely useful past 2,000 if it starts repeating. Length without a no is just a sales page.
Can it include a story from a customer?
Yes, if the story answers the same question. A customer anecdote that changes the subject belongs in a different piece.
Should I mention competitors?
When the decision is “this or the tool they already have.” Name the alternative and the criterion that separates them. A drive-by list of logos is a different form.
What if the product changes?
Update the page and keep the URL. A forwarded link should land on the current decision, not on a new post that orphans the old one.