How to write a product pitch that converts (the indie-SaaS structure)

A press release announces. A product pitch sells. The press release answers 'what did you ship, and when.' A product pitch answers 'why should I care, what's in it for me, and what does it cost.' If you ship a press release as your product pitch, you have built a page that journalists might write about and buyers will skip.

'We have 47 features' is a feature list. A product pitch names the single outcome the customer gets, names the one thing that makes the outcome possible, and asks for the next step. The feature list is the appendix; the pitch is the headline. Your product pitch is the page a customer reads. The feature list is the page a customer sends to a friend who already asked.

A pitch deck walks a buyer through a story in a room. A product pitch lives at a URL. The deck format fights you in cold outreach; the page format compounds over time. A product pitch on a permanent page is the asset you send in every follow-up, in every ad, in every reply.

Same six parts as every other pitch: problem, agitate, solution, proof, offer, close. For a product pitch, the 'solution' section is the demo (a video, a screenshot, a 30-second walkthrough). The 'proof' section is the customer quote + the HonestScore (the audience's call on the pitch itself). The 'offer' section is the price, the trial, the guarantee, the date. The 'close' is the one button: Start trial, Buy, Book a 15-minute demo, Join the waitlist.

A launch tweet reaches your existing followers for 24 hours, then it is gone. A product pitch on a permanent page is sent in every cold email next month, in every follow-up next quarter, in every reply next year. The same URL, the same HP code, the same HonestScore compounding. The work you put into the page compounds. The work you put into the tweet does not.