How to Write a One-Sentence Pitch for Your Indie SaaS (2026)

If you cannot say what your product does in one sentence, you cannot validate it. The pitch is the test before the test. Most indie SaaS launches go to crickets because the pitch was vague, and a vague pitch produces a vague waitlist signup, and a vague signup converts to nothing. This is the format I use, the examples that work, and the four mistakes that kill the pitch before it gets a chance.

I have shipped 7 indie apps over 8 years and ended up building two tools for myself along the way: Spaceport, a SwiftUI starter that gets a paid iOS app live in days, and Lighthouse, the launch toolkit this post is mostly about. The pitch format below is the one both products lead with on their landing pages.

Table of contents

• Why one sentence is the test
• The format that works
• Examples worth stealing
• Anti-examples: what does not work
• Four mistakes that kill the pitch
• How to test your pitch in a day
• Frequently asked questions

Why one sentence is the test

The one-sentence pitch is doing three jobs at once. It is the headline on the waitlist landing page, the first line of the launch tweet, and the answer you give a stranger at a meetup when they ask what you are working on. If those three lines are different, the product does not have a pitch yet; it has three half-pitches.

More importantly, the sentence is what visitors mentally sign off on before they sign up. A waitlist signup is them agreeing that the sentence describes a problem they have. If the sentence is fuzzy, they will not sign up; if the sentence is clear but does not match their problem, they will not sign up; if the sentence is clear AND matches, they will. That is the validation signal the pitch produces.

The format that works

The format that consistently lands for indie SaaS:

[Solution category] for [specific audience] who[specific pain].

Three slots, all specific. The category tells the visitor what kind of tool this is. The audience tells them whether the tool is for them. The pain tells them whether the tool solves something they actually feel. All three are required; drop any one and the sentence stops doing its job.

Examples worth stealing

Real pitches that work, broken down by slot:

• “A training plan for runners who hate generic plans.” Category: training plan. Audience: runners. Pain: generic plans not built for them.
• “A styling app for women 5'4" and under who cannot find clothes that fit.” Category: styling app. Audience: women 5'4" and under. Pain: clothes never fit.
• “A waitlist toolkit for indie founders who want survey answers, not just emails.” Category: waitlist toolkit. Audience: indie founders. Pain: email-only waitlists don't validate anything.
• “A SwiftUI starter for indie iOS developers who do not want to rebuild the same plumbing every project.” Category: SwiftUI starter. Audience: indie iOS developers. Pain: rebuilding plumbing every project.

Notice what is shared: each one is short enough to fit on a single line on a phone, each one names a real audience (not “professionals”), and each one names a pain the audience would nod at without explanation.

Anti-examples: what does not work

The same product, in pitches that do not land:

• “The future of personalized training.” No category (vague), no audience, no pain. Reads like venture capital copy. Indie audiences smell it and bounce.
• “An AI-powered platform that uses machine learning to deliver value at scale.” Every word is a buzzword. The reader cannot tell whether this is for them, what it does, or what it costs.
• “Lighthouse helps you grow.” Specific verb (helps) but everything else is vague. Grow what? For whom? From what problem?
• “Runwell.” Just the product name. Some indie founders treat their product name as the pitch. The name is a label, not a sentence. Labels do not validate.

Four mistakes that kill the pitch

1. Naming the technology, not the job

“A GraphQL API for...” or “A SwiftUI framework for...” The visitor does not care about the tech; they care whether the product solves their problem. Lead with the job, mention the tech later (or in the FAQ).

2. Saying “everyone” or “anyone”

“A tool for anyone who builds online.” If the audience is everyone, no one will recognise themselves. Pick a narrower audience even if it feels like leaving money on the table. You can broaden after you find product-market fit; you cannot find PMF if the pitch does not let any specific person self-identify.

3. Naming a feature, not a pain

“A waitlist with survey questions on the signup form.” That is a feature, not a pain. The pain version is “a waitlist toolkit for indie founders who want survey answers, not just emails.” The feature shows up in the body of the page; the pain belongs in the pitch.

4. Hedging the audience or the pain

“A planning tool for busy professionals who could maybe use some help organising their week.” The hedge (“maybe,” “some,” “could”) kills the recognition signal. Specific pitches feel risky to write because they exclude some readers, and that is exactly why they work for the readers they include.

How to test your pitch in a day

You do not need a focus group. You need three conversations and one landing page:

• Say it out loud to three strangers. A coffee shop, a meetup, a Discord call. Watch their face. If they nod and say “ohhh, that's actually useful for X, right?” the pitch landed. If they say “cool, what does it do?” the pitch did not land.
• Put it on a landing page as the H1. Use the full pitch as the headline, exactly as you would say it out loud. Run paid or organic traffic for a day. See what to put on your waitlist landing page for the supporting layout.
• Read the survey answers from your first ten signups. The ones that mention the exact pain you named are the validation. The ones that talk about a completely different pain are the signal that the audience self-selected for something else and the pitch needs work. See why answers beat emails for the survey questions that surface this.

Iterate. The first pitch is rarely the right one. Most products go through three to five pitch revisions before the signups start converting.

Frequently asked questions

What if my product has multiple audiences?

Pick the one you are starting with. Multi-audience pitches consistently underperform single-audience pitches at the indie stage because the reader cannot self-identify quickly enough. Land with one audience first; expand the pitch later as the product earns the right to broaden.

How long is one sentence allowed to be?

Eight to twenty words is the sweet spot. Long enough to fit the three slots, short enough to read on a phone without wrapping awkwardly. Anything longer than twenty words is usually two pitches stitched together.

Should the pitch mention the price?

No. The pitch is for recognition (“this is for me, this solves a thing I have”). Price is a separate decision that happens after recognition. Putting the price in the pitch crowds out the audience and the pain.

What about the founder raising capital?

The same pitch format works for investor decks, with a small tweak: append the market size or unit-economics hook after the audience-pain sentence. For the broader fundraising stack, dedicated platforms like Funding Banker, a curated investor directory with pitch and outreach tracking, are where the raise itself runs. The pitch belongs on the cover slide either way.

Where does this pitch sit in the launch checklist?

Step 1 of the pre-launch checklist. The pitch is the foundation everything else (the waitlist, the signups, the launch email, the post-launch loop) builds on. Get the pitch wrong and every downstream step gets harder.

One sentence. Three slots: category, audience, pain. The pitch is the smallest piece of content you will write for your product, and the one that does the most work. Indie founders who get the pitch right early ship faster, validate cheaper, and stop second-guessing whether anyone wants the thing.

Lighthouse gives you the waitlist landing page where your one-sentence pitch becomes the H1, the survey questions that validate whether the pitch matches the audience's real pain, and the launch email that converts the validated list. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.