Write a Listing That Converts: Titles, Demos, Proof

A buyer landing on your listing is asking one quiet question: "If I trust this, will I regret it?" Your job is to answer that faster than they can click away. This guide shows you how to write titles, demos, proof, and objection-handling that turn browsers into subscribers.

The real job of a listing: reduce risk, prove value fast

Buyers on AgentDukaan aren't reading for pleasure. They're scanning to rule things out. Every claim you make adds a small risk in their head ("what if it doesn't work for my use case?"), and every piece of proof removes one. A converting listing is just a stack where proof outweighs risk before the buyer runs out of patience.

So write to two questions, in this order:

1. What does this do for me, and how fast? (value)
2. Why should I believe you, and what if it breaks? (risk)

If your listing only answers #1, you'll get traffic and no conversions. Most weak listings on any marketplace are all features, no risk reduction.

Titles and the first screen that earn the click

Your title and first screen (the part visible before scrolling) do 80% of the work. Treat the first screen as a complete pitch on its own.

Write the title as a promise, not a label

A label says what it is. A promise says what changes for the buyer. Buyers buy the change.

A useful title formula: [outcome] for [who] via [channel], without [pain]. Example: "Answer customer FAQs on WhatsApp 24x7, without hiring night staff."

Nail the first screen

Above the fold, a buyer should learn five things in under ten seconds:

• Outcome — the one job this does, in plain Hinglish-friendly English.
• Channel — WhatsApp, Telegram, in-app chat, or email. Buyers filter hard on this.
• Buying mode — subscribe to hosted, buy source code, or done-for-you setup. Don't make them guess.
• Price anchor — a clear starting price in rupees (mention "+18% GST" so there's no checkout surprise).
• One proof signal — a number, a named integration, or a short outcome line.

Lead with a one-line summary, then a 3-bullet "what you get." Skip the autobiography of your dev journey.

Showing a believable demo

Buyers don't trust descriptions; they trust seeing the thing run. A demo that feels real is your single highest-leverage asset.

What makes a demo believable:

• Show the actual channel. A screenshot of a real WhatsApp thread beats a polished marketing graphic. Buyers recognise the green bubbles and trust them.
• Use a realistic conversation, including a messy input. Show a customer typing "kitne ka hai bhai" and the agent handling it gracefully. Perfect inputs look staged.
• Show the boring middle, not just the win. Include the clarifying question, the error it caught, the "let me confirm" step. Real systems aren't magic.
• Caption every frame with what just happened, so a skimmer following only the captions still gets the story.
• Keep video under 60 seconds, start on the result, and don't make sound mandatory — many buyers watch muted.

Mask real customer names and numbers in screenshots. Under the DPDP Act, don't publish identifiable personal data from real conversations; use clearly fake sample data.

If you want a quick demo script, use this prompt:

You are helping me script a 45-second product demo for an AI agent I sell on a marketplace.

Agent does: [one-line job]
Channel: [WhatsApp / Telegram / in-app chat / email]
Buyer: [who they are, e.g. a 2-person D2C brand owner]
Their biggest doubt: [e.g. "will it handle Hinglish and rude customers?"]

Write a turn-by-turn demo conversation (customer message -> agent reply)
that:
- opens on a realistic, slightly messy customer message
- shows ONE clarifying step and ONE edge case handled well
- ends on the concrete outcome the buyer cares about
For each turn, add a 6-word caption explaining what just happened.
Keep all names and numbers obviously fake.

For building the agent behind a convincing demo, see Build Your First AI Agent: Idea to Live in a Weekend.

Proof: outcomes, before/after, guarantees

Proof is what lets a stranger believe you. Use the strongest proof you actually have — never invent it. Fake numbers get found out and kill trust permanently.

Order proof from strongest to weakest, and use what's true:

1. Measured outcomes — "Cut first-response time from 3 hours to under 1 minute in our own store." Only if you measured it.
2. Before/after — show the manual workflow vs. the agent's. This works even with zero customers because the "before" is the buyer's current pain.
3. Concrete capability proof — "Handles GST-compliant invoices," "works with Razorpay payment links," "replies in Hindi, English, and Hinglish." Specifics read as competence.
4. Guarantees — a refund window or a free test run removes the "what if I waste money" fear. On AgentDukaan you can offer a non-billable test run so buyers verify before they commit.

A clean before/after table does a lot of quiet persuasion:

If you have no buyers yet, run the agent in your own business for two weeks and report your numbers honestly as "our results." That's real proof, clearly framed.

Handling objections in the description

The description's real purpose is to remove the four or five reasons a ready buyer hesitates. Write the objection, then answer it — don't pretend it doesn't exist.

Common Indian-buyer objections and how to defuse them:

• "Will it work for my business?" — State who it's for and who it's not for. Disqualifying buyers builds trust and cuts refund requests.
• "Is setup painful?" — Give a one-line setup time and link to done-for-you if you offer it.
• "What about my data?" — One honest line on what data it touches and that it follows DPDP-aligned handling. Don't overclaim.
• "What if I get stuck?" — State your support channel and response time.
• "Why this price?" — Anchor against the cost of the manual work or a part-time hire. See How to Price Your AI Agent.

Address the buying-mode confusion explicitly: who should subscribe, who should buy source, who should take done-for-you setup. A confused buyer doesn't buy; they leave.

A listing self-review checklist

Read your own listing as a skeptical buyer in a hurry. Then run this:

• Title states an outcome and a channel, not just a category
• First screen shows outcome, channel, buying mode, price (+GST), and one proof point
• Price is in rupees with GST treatment made clear
• At least one real-looking demo of the actual channel, with fake/masked data
• Demo shows a messy input and one edge case handled
• A before/after or measured outcome — true, not invented
• A guarantee or free test run is offered and visible
• "Who this is NOT for" appears somewhere
• The top 4 objections are each named and answered
• Support channel and response time are stated
• No claim you couldn't defend to a buyer's face
• A first-time visitor can grasp it in under 10 seconds

If any box is empty, that's your highest-value edit.

Next steps

1. Rewrite your title today using the [outcome] for [who] via [channel], without [pain] formula.
2. Capture one real (masked) demo conversation showing a messy input handled well.
3. Add one true before/after row and one guarantee or free test run.
4. Run the self-review checklist before you publish.

When it's ready, list it on AgentDukaan — or browse strong examples on AgentDukaan to see how top sellers frame their first screen. For sharper words throughout, Prompt Engineering for Real Business Tasks pairs well with this guide.