When a Customer Asks Whether You Can Do Something
August 28, 2026
A prospect or customer asks whether your product can do a specific thing. This is the highest-intent message you will receive all week — somebody has a real requirement and is checking you against it.
The standard reply is "yes, we support that", possibly with a documentation link, and it converts far worse than it should.
Why "yes" underperforms
- Everybody says yes. The word carries no information at this point in an evaluation.
- It does not show the shape. Two products can both support something and differ enormously in how.
- Documentation is a task, and they asked a question rather than requesting homework.
- It cannot be forwarded to whoever actually raised the requirement.
Send the thing happening
A short walkthrough of that specific feature, recorded once, answers the question in a way that cannot be doubted and takes them thirty seconds.
It also answers the question they did not ask, which is how much work it will be — visible immediately from the number of steps.
These accumulate into something valuable
The questions repeat. After a few months of this you have a small library covering the things prospects actually care about, built entirely from real demand rather than guesses about what to demo.
That library is more useful than any feature page, because every item in it exists because somebody asked.
When the answer is no
Say no clearly and quickly. A prospect who finds out during a trial that the answer was really "not quite" is a refund and a bad review rather than a saved deal.
If there is a workaround, show the workaround honestly and let them judge whether it is enough. That is a much better position than a yes that unravels.
Frequently asked questions
- How should I answer "can your product do X?"
- With a short walkthrough of that specific thing rather than "yes, we support that". Everybody says yes, so the word carries no information -- and a recording also shows how much work it takes, which is the question underneath the question.
- Is a documentation link a good reply?
- Weak on its own. They asked a question and a docs link returns homework. It also cannot be forwarded meaningfully to whoever raised the requirement, which is usually somebody other than the person messaging you.
- What if my product cannot do it?
- Say so clearly and quickly, and show the workaround honestly if there is one. A prospect who discovers during a trial that the answer was really "not quite" becomes a refund and a bad review rather than a saved deal.
Keep reading
This is what Demorta does
Click through it — the same kind of demo you can record of your own product.
Try it on your own product
Record your first interactive demo free.
Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.
Start free →