Structure a product demo around the prospect's stated problems — their workflow first, features only as answers, and checkpoints that keep them talking.
Structure my demo for {{prospect}} (what I learned in discovery: {{discovery_notes}}). Build: the 2-minute recap of THEIR problem to open (confirms I listened, frames everything after), the demo path — their highest-pain workflow first, not our menu order; per feature shown: the problem it kills, the show, and the checkpoint question ('is this how your team would use it?'), the wow moment placed early (attention decays), what NOT to show (features that invite objections or confuse), and the close: next step proposed with a date. Time-boxed for {{duration}}.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekWrite a short, personalised cold email that gets replies.
Generate a 4-touch follow-up sequence after no reply.
Prepare sharp discovery questions for a sales call.
Respond to a sales objection three ways — reframe, clarify, prove — with the diagnosis of what the o...
Draft a clear one-page proposal from your deal notes.
Write the objection-handling FAQ for a sales page: the real hesitations, answered honestly, ordered...