Two complete scripts for a product presentation, each for a different stage: one customer launch and one internal briefing for the sales team. The companies are fictional, the mechanics are real. After each text, you will see why it works. The framework behind it is explained on the product launch presentation page.
Example 1: The customer launch presentation
Situation: Launch event at a software company, 35 guests in the room, existing customers and prospects from e-commerce, 20 minutes of speaking time plus questions.
Before I show you anything, one number from your daily work: a mid-sized online shop processes each return by hand for an average of 11 minutes. Open the parcel, check the condition, book it in the system, take a photo, trigger the refund, inform the customer. With 300 returns a month, that is 55 staff hours. And on Mondays, after the weekend, boxes still pile up by the loading bay. A full-time role that sells nothing, buys nothing, and makes no customer happier.
Over the past two years, we have taken that exact workflow apart with 20 shops, step by step. The result is what I am introducing today. It is called Retoura, and it turns one photo of a return into the complete process. To build it, we photographed, labelled, and analysed 14,000 returns, from trainers to coffee machines.
I will show you three moments live. First: goods in. I am uploading the photo of this returned jacket now. Watch the right-hand column. Condition recognised, category: resellable, storage location assigned, refund prepared. Four seconds. Your team member is still holding the parcel and the job is already done.
Second: your customer. The moment the photo is processed, the email goes out: your return has arrived, your refund is on the way. You can see the email here in the test inbox, seven seconds after upload. Your support team sees the same status in the same system, without opening a second window. Our pilot shops reduced where-is-my-money queries by 40 percent.
Third, and this saves the most over time: analysis. Retoura shows you why each item comes back. This trainer has a return rate of 38 percent, and 6 out of 10 returns name size as the reason. One sentence on the product page, comes up small, order one size larger, and the rate drops. One of our pilot shops prevented 1,900 returns in three months before they ever happened.
What does it cost? 490 a month, all features, no setup fee, cancel monthly. For comparison: those 55 hours of manual work currently cost you around 2,200 every month. Retoura pays for itself in the first week. For shops with more than 1,000 returns a month, there is tiered pricing, which I can show you at the stand afterwards.
And so you do not have to trust a stage: the trial version is available from this evening. Thirty days, full feature set, your real returns. Anyone who sets up access today gets the first analysis reviewed personally with our team. The QR code is by the exit. Now I am looking forward to your questions.
Why this works: The presentation begins with the problem in numbers before the product has a name; anyone handling 300 returns a month recognises themselves in the first paragraph. The demo is choreographed: three announced moments, each answers a question, each ends with a number. The price appears once, directly after the strongest proof, and sits next to the current 2,200 cost. That makes 490 sound manageable. The ending turns attention into a next step: trial version, deadline today, and a personal review as the reward for quick action.
Example 2: The internal product briefing for the sales team
Situation: Monday meeting at a trade software company, 12 people from sales, 15 minutes to introduce a new module, followed by role-play.
From Monday, you have a new argument in your bag: the Quote Assistant. In fifteen minutes, you will know what it does, who it is built for, and how to sell it.
First, the problem our customers can remove. A roofing company writes an average of 14 quotes a week, and each one takes 45 minutes: typing up measurements, finding line items, checking prices. Four of the 14 become jobs. The other ten are pure cost, more than seven hours of unpaid admin every week.
The assistant turns 45 minutes into ten. I will show it briefly with the roofing demo project: upload measurement photos, the line items appear automatically, the prices come from the company’s own calculations. The owner checks, adds two items, clicks send. Done. It all runs in the same login as the rest of our software, with no new window and no new training.
Who is it for? Companies with five or more employees that currently quote in Word or Excel. That is 60 percent of our existing customer base. You are not convincing anyone of us as a company; you are calling people who already trust us and lose seven hours every week. Ask in the first conversation how many quotes they write per week. From ten, the module always pays.
Pricing logic: 79 a month in addition to the main licence. Your discount limit is 10 percent; anything above that comes through me. The calculation for the customer is simple: ten unsuccessful quotes times 35 minutes saved is almost six hours a week, worth more than 1,100 a month at skilled-worker rates. In the pilot quarter, 9 of 12 test companies subscribed after 30 days.
Now the three objections that will definitely come. First: my pricing is too specific. Answer: the assistant only uses the company’s own prices; we bring none of our own. Second: another subscription. Answer: use the 1,100 calculation, then stop talking and wait. Third: I want to see it first. That is why every one of you gets demo access today with the roofing sample data on your laptop.
Our target by the end of the quarter: 80 existing customers on the module. The list of the 200 most likely candidates is in the CRM from Monday, sorted by quote volume. Questions now, then we will role-play the three objections once.
Why this works: Internally, the team needs ammunition. The briefing gives them everything for the sales conversation: a problem calculation the customer can follow, a clearly defined target group within the existing base, price and discount boundary, and three objections with ready answers. The demo takes one minute because the team already knows the product; the time goes into arguments. The ending sets a measurable goal with the tool to reach it: 80 subscriptions, 200 names in the CRM, role-play immediately after.
The pattern behind both scripts
Both follow the same foundation: problem in numbers, product in one sentence, short demo moments with signposting, a price moment with a comparison figure, and a next step with a deadline. What changes is the weighting: customers get drama and proof, while the internal team gets objections and targets. The product launch presentation page shows how to transfer this foundation to your product, and eloqole writes both variants from the same information.