For-whom, not-for-whom, why-hard
How to position an indie SaaS by category.
One positioning guide per crowded SaaS category. Each names the market context, the buyer you can win, the buyer to give up on, the single biggest positioning trap, and templated one-liner examples. Brunson Hook overlay; April-Dunford-style polarity.
How to position a payments SaaS
Category: Payments and creator monetization
Payments is the most over-positioned indie SaaS category because Stripe dominates the default. The trap is competing head-on; the win is naming a specific buyer Stripe under-serves and a specific job-to-be-done where the buyer pays for category-specific behavior, not for raw payment plumbing.
How to position a forms SaaS
Category: Forms and surveys
Forms is a category where Typeform set the design ceiling and Tally undercut on price. New entrants get squeezed unless they pick a specific buyer or specific form-job-to-be-done that neither of the leaders optimizes for.
How to position an analytics SaaS
Category: Privacy analytics
Analytics is split into three sub-categories with different rules: web analytics (Plausible, Fathom), product analytics (PostHog, Mixpanel), and BI / data warehousing. Pre-revenue indie SaaS analytics tools usually fall into the first two; positioning has to pick a sub-category cleanly and win it.
How to position a newsletter SaaS
Category: Newsletter and creator email
Newsletter SaaS is in its second major positioning phase: Substack built brand around creators-and-community; Beehiiv won on monetization tooling; Ghost on open-source. New entrants have to pick a third axis — niche-vertical, deliverability, or a specific monetization shape — to win.
How to position a scheduling SaaS
Category: Scheduling
Scheduling SaaS has consolidated around Calendly (commercial default) and Cal.com (open-source challenger). Pre-revenue indie tools have to either pick a vertical (medical, legal, coaching) or pick a specific scheduling-job-to-be-done (interview scheduling, large-group coordination) — generic positioning loses.
How to position an email API SaaS
Category: Email APIs and transactional email
The email API market is split between enterprise-incumbent (SendGrid, Mailgun) and developer-first new entrants (Resend, Postmark, Loops). Pre-revenue tools either pick a developer-experience wedge or a deliverability-niche wedge — volume positioning loses without enterprise infrastructure.
How to position a developer-docs SaaS
Category: Developer documentation
Developer-docs SaaS sits between open-source (Docusaurus, MkDocs) and full-product (GitBook, Mintlify). Pre-revenue indie tools have to pick a specific docs-job-to-be-done — API docs, internal docs, customer-facing knowledge base — and win there. Generic 'better than Docusaurus' loses to free.
How to position a testimonials SaaS
Category: Testimonial collection
Testimonials SaaS in 2026 has split: simple collection (Senja, Testimonial.to) versus full social-proof workflow (Wall of Love, integrated marketing). Pre-revenue indie tools have to pick which side and own one specific testimonial-job-to-be-done — generic 'collect testimonials' positioning loses to Google Forms + a copy-paste workflow.
Position is right, page is broken?
The free 90-second Launch Diagnostic takes your live page and tells you whether the positioning is making it to the visitor — Wrong Person, Weak Offer, or Weak Belief.