Green
5:00
The problem, customer, and reason to care are clear. Move into proof or the demo.
Free timer · no account · works offline
Rehearse a concise pitch, demo, and next-step ask
Space start / pauseF fullscreenM muteR reset
Buyer-centered pitch rehearsal
A strong pitch makes one customer problem feel concrete, proves the change, and earns a clear next step. Use the timer above to rehearse that sequence, trim feature drift, and arrive at the ask before the clock forces it.
Make the clock useful
The preset turns color changes into editing decisions. Green asks whether the buyer can name the problem, yellow asks whether you are still adding material, and red asks whether the next step is already clear.
Green
5:00
The problem, customer, and reason to care are clear. Move into proof or the demo.
Yellow
6:00
Stop adding features. Make the value concrete and prepare the next-step ask.
Red
7:00
Land the close. A pitch that keeps explaining after the red signal loses its decision window.
Practice marker
7:30
A configurable guardrail for rehearsal, not a universal sales or event rule.
A useful starting shape
This arc is a rehearsal aid, not a script. Move the turns earlier or later when the buyer’s context demands it, but keep the connection between problem, proof, value, and next step visible.
Open with the costly, frustrating, or time-sensitive situation your audience recognizes. Replace a company biography with a reason this conversation matters now.
Define who has the problem, what they do today, and what changes when the problem remains unsolved. Keep the context specific enough to make the demo meaningful.
Show the smallest workflow or product moment that proves the promise. Narrate the user outcome, not every menu, setting, or technical detail.
Use one credible result, comparison, customer example, or implementation detail. Explain why the evidence matters to this buyer instead of listing unrelated features.
Summarize the change, answer the most likely objection, and make one specific request: a trial, technical review, follow-up, or decision meeting.
Delivery decisions
Return to the buyer’s situation before each proof point. If the demo becomes a tour of features, the audience loses the reason to change.
After showing a workflow, say what becomes faster, safer, clearer, or possible. A click without an outcome is not yet a selling point.
Protect the final minute for a specific next step. “Any questions?” can follow the ask; it should not replace it.
Before the next run
When the pitch runs long, cut in this order: company background, the least decisive feature, and repeated proof. Keep the buyer problem, the strongest demonstration, the evidence that matters, and the next-step ask. Then run it again with the actual screen and expected handoff.
Choose a matching workflow
Answers for pitch practice
There is no universal sales-pitch length. A discovery call, product demo, investor conversation, and conference pitch each have a different brief. This page starts with a generic five-to-seven-minute rehearsal window; edit the four thresholds to match the organizer or buyer.
Green at 5:00 is a minimum practice target, yellow at 6:00 is a cue to stop expanding the story, and red at 7:00 is the rehearsal maximum. The 7:30 marker is only a guardrail and does not make a pitch compliant with any external rule.
Yes. Rehearse the demo as part of the pitch rather than timing the spoken introduction separately. Include loading, clicks, handoffs, and the sentence that connects each proof point to the buyer’s outcome.
Choose one customer problem and one decisive workflow. If a feature does not change the buyer’s decision, move it to a follow-up resource. Use yellow as the point where you stop opening new threads.
Yes. Start the timer, select fullscreen, and share the browser tab or window. The color cues remain useful even when you mute the optional sound alerts.
No. The timer measures the run in your browser and does not ask for your script, recording, customer name, company, or meeting details.