ECOMMERCE

Buying guide from your own range

Use when you want a buying guide that leads to your products rather than a generic explainer.

buying-guide-from-product-range.md

Download .md

Write a buying guide titled "{{GUIDE_TITLE}}" for {{SITE_NAME}}.

Range available:
{{PRODUCT_LIST_WITH_KEY_SPECS_AND_PRICES}}

Reader: {{READER_DESCRIPTION}}. They are choosing between options and do not know the jargon.

Structure:
1. The decision in one paragraph - what the real trade-off is.
2. "Start here" - 3 to 5 questions the reader should answer about themselves, each with what their answer implies.
3. A specification glossary table: Term | What it means | Why it matters | What number to look for.
4. Three named picks from the range only: best for {{USE_CASE_A}}, best for {{USE_CASE_B}}, best on a budget. For each: why it wins, who should not buy it.
5. Common mistakes - 4 bullets.

Rules:
- Only recommend products from the list. If nothing in the range fits a pick, say "no good option in range" and say what is missing.
- Every spec figure must come from the list. Do not estimate, average or round unlabeled numbers.
- Include one honest reason a reader might buy nothing at all.
- 900 to 1200 words. No em dashes. No closing summary that restates the intro.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{GUIDE_TITLE}}
{{SITE_NAME}}
{{PRODUCT_LIST_WITH_KEY_SPECS_AND_PRICES}}
{{READER_DESCRIPTION}}
{{USE_CASE_A}}
{{USE_CASE_B}}

Getting a better result

Include prices in the input - guides without price context give picks that make no sense against each other.
The "who should not buy it" line is what makes the guide trusted. Do not let it get cut in edit.
Run it again with a different reader description to get a second guide that does not cannibalise the first.

Questions about this prompt

When is this better than a general explainer article?

When you want the guide to end in a decision about your range rather than being an explainer that could sit on any site in the category. If you stock one product per use case there is nothing to guide between, and a comparison page or a stronger product page will do more for the same effort.

What do I need before writing the guide?

The range with key specs and prices, a reader description, and the two use cases the picks are built around. Prices are not optional, as the tips say. Without them the best on a budget pick has nothing to anchor against and the three recommendations stop making sense next to each other.

What comes back, and which part does the work?

The trade-off in a paragraph, self-assessment questions, a specification glossary, three named picks and four common mistakes. The glossary table earns its place because of the what number to look for column, and the who should not buy it line under each pick is what makes the rest of the guide believable.

What gets cut in edit that should not be?

Letting an editor delete the who should not buy it lines and the honest reason to buy nothing at all. They read as lost sales and they are the reason the guide is trusted. Check every spec figure against your input as well, since an estimated or rounded number here repeats through the whole piece.