Seven SaaS ideas worth validating before you build

Executive overview

Most SaaS idea lists start with the builder, not the buyer. These seven came from founders and operators who said "I wish this existed" — a better filter than "what could I build?"

No idea here has been validated. The right first step is identifying which fits your skills, then talking to potential customers before writing a line of code.

The best source of ideas is people describing a problem they'd pay to solve.

The seven ideas

1. NPS tool for recruitment ATS — integrates with Job Adder (open API); existing tool costs $800/month, leaving room for a lower-priced entrant targeting small recruitment firms.
2. Hotness Hosting — Markdown-based site hosting that auto-updates to the latest web framework so sites never look dated; question is whether you need to own the hosting layer or just build a plugin.
3. Waterfell — waterfall project management SaaS narrowly focused on medical device development; compliance requirements (requirements tracking, change control, V&V) may lock out generic tools.
4. OAuth integrations as a service — drop-in JavaScript snippet for OAuth-based integrations; a maintained commercial version of the open-source Pirsley project.
5. Airport hotel parking — lets independently owned airport hotels rent unused spots to travelers; low-code start possible; key unknowns are market size and hotel willingness.
6. Dialysis care management — software supporting at-home dialysis patients; potential licensing play with providers like Fresenius; may require a two-sided marketplace model.
7. Affordable contract redlining — existing tools are expensive per seat; entering as a 20–40% undercut while building trust in a risk-averse legal market is the challenge.

Bonus: GDPR-compliant alternatives as a category

• Fathom and Plausible proved privacy-first analytics can win market share.
• The same lens applies across Martech: split testing, marketing automation, personalization, advertising.
• Most Martech relies on third-party cookies and tracking — GDPR-compliant versions are largely unbuilt.
• Question: does the whole product need to be GDPR-first, or can it be a compliant tier — similar to how HIPAA is often an enterprise add-on?

How to approach any of these

• Ask "what do you wish existed?" not "what's a good idea?" — the framing surfaces real pain.
• Validate market size early; some niches (independent airport hotels) may be too small.
• Build as little as possible to test demand — no-code or manual pilots before a full app.
• In trust-sensitive verticals (legal, medical), early logos and influencer partnerships matter more than features.