11 Best Design Inspiration Websites for SaaS Founders and Product Teams

SaaS founders, product managers, and small teams often need to make interface decisions before there is time for a full design study. Questions about onboarding, pricing, dashboards, account settings, trial conversion, and lifecycle messaging usually need concrete references. The websites below cover different parts of that work, from complete product journeys to marketing pages and emails.

1. Page Flows

Teams that need to see how an interaction unfolds can visit Page Flows and review recorded journeys from real digital products. The library includes web, iOS, Android, screens, UI elements, and emails, with flows covering onboarding, checkout, settings, upgrades, invitations, search, and payments. This format is useful when the sequence matters as much as the individual screens.

Baremetrics provides a clear example. Its Page Flows references move through signup, integrations, phone verification, company details, team invitations, and the dashboard. The same product also has references for account settings and goal creation. A founder reviewing onboarding can therefore examine where setup ends and regular product use begins.

2. SaaSFrame

SaaSFrame focuses on SaaS websites, interfaces, flows, and emails. Its library currently contains more than 5,000 UX and UI examples, including dashboards, pricing pages, account setup, landing pages, and editing experiences.

A useful example is FullEnrich, whose references cover account creation, onboarding, dashboards, and data enrichment actions. This gives teams a way to inspect how a B2B SaaS product moves from initial setup into everyday use.

SaaSFrame is also relevant when marketing and product design are discussed together. The same library can be used for landing pages, in product screens, and email communication rather than treating each area as a separate research task.

3. Nicelydone

Nicelydone is centered on SaaS interface examples and currently indexes more than 201,500 screens, 12,600 user flows, and 30,700 UI components from more than 500 products. Content can be filtered by product, page type, pattern, or text appearing inside screenshots.

Its onboarding section includes references from Linear, Mailchimp, Maze, Dovetail, Voiceflow, and other SaaS products. Dedicated pricing and account setup collections make it easier to examine one part of the customer journey without moving through unrelated examples.

4. Refero

Refero organizes product references around screens, flows, page types, UX patterns, and interface elements. Categories include dashboards, subscriptions, profiles, billing, payment methods, onboarding, password resets, and account deletion. A product manager can start with the task under discussion rather than searching for a particular company.

Pricing work is a good example. Plan comparison pages, billing dashboards, trials, and subscription flows are separated into distinct areas. That makes it easier to break a broad monetization problem into smaller interface decisions.

Refero covers both web and iOS products. That can matter when the same account, subscription, or profile system appears across several devices.

5. SaaS Interface

SaaS Interface is organized around common SaaS screen types, including dashboards, checkout, pricing, billing, settings, onboarding, forms, search, filters, profiles, and empty states. Its dashboard gallery contains products including Ahrefs, Mixpanel, Grafana, and Similarweb, while settings references include ClickUp and Clerk. Checkout examples include Supabase and Postman. For a team reviewing one screen category, these named examples provide a direct route into the problem.

6. Growth.Design

Growth.Design approaches product inspiration through case studies rather than galleries. Its library examines onboarding, retention, revenue, referrals, and other behavioral questions through recognizable products. Current examples include Trello onboarding, Zapier upgrade UX, Blinkist trial conversion, and Typeform cancellation.

The Typeform case is especially relevant to SaaS teams working on churn. Instead of stopping at the cancellation screen, the case examines the broader offboarding journey and the decisions around retention.

That type of analysis can be more valuable than another collection of attractive screens when the real question is why a flow exists in its current form.

7. GoodUI

GoodUI combines interface patterns with A/B test results. Its library currently reports 141 patterns based on hundreds of experiments, with categories covering signup, pricing, checkout, landing pages, and product screens.

The important distinction is that GoodUI also shows losing tests. A familiar design choice is therefore not presented as automatically effective. For SaaS teams responsible for conversion metrics, that makes the site useful when deciding which ideas deserve testing rather than immediate implementation.

8. SaaS Landing Page

SaaS Landing Page is focused on acquisition pages rather than the in product experience. Its collection includes hundreds of examples divided into pricing, features, testimonials, FAQs, contact pages, and other marketing sections.

This narrower focus is useful when a team is reworking positioning or conversion before signup.

A pricing page, for example, can be evaluated separately from the homepage. That matters because the visitor reaching pricing usually has different questions from someone seeing the product for the first time.

The site also identifies fonts and technology stacks for many references. That extra context can be useful when implementation considerations are part of the discussion.

9. Saaspo

Saaspo offers a SaaS focused gallery with filters for page purpose, industry, visual style, and technology stack. Its collections include pricing, product, integration, customer, enterprise, and demo pages.

The resource works particularly well for targeted redesigns. A team replacing a pricing page can stay inside one page category instead of browsing entire websites. Its product page collection serves the same purpose for feature presentation and product explanation.

10. One Page Love

One Page Love has a dedicated SaaS collection alongside its broader app and SaaS categories. The SaaS section currently contains 150 curated references, with reviews that point out notable elements of each site.

It is best suited to early marketing site work, especially when a small team needs to review how other companies explain the product, expose the interface, and position the main call to action.

Unlike product flow libraries, it stays focused on the public facing website. That makes it a better fit for homepage and landing page discussions than for account settings or dashboard behavior.

11. Email Love

Email Love covers the communication that happens outside the product. Its dedicated SaaS collection currently lists 158 curated emails from 75 brands, including onboarding messages, product updates, usage reminders, feature announcements, and trial conversion emails.

The onboarding collection includes real sequences and subject lines from companies including Intercom. A SaaS team can use these references when deciding what information belongs in the interface and what can be handled later by email.

This becomes especially relevant when onboarding continues after the first session.

A new user may leave before completing setup, ignore an invitation, or forget about a trial. Email then becomes part of the product journey rather than a separate marketing task.

Conclusion

Different design resources answer different product questions. Page Flows, SaaSFrame, Nicelydone, and Refero are strongest when teams need to understand flows and interface structure. SaaS Interface works well for individual screen categories, while Growth.Design and GoodUI add analysis and experiment results. SaaS Landing Page, Saaspo, and One Page Love concentrate more heavily on acquisition, and Email Love covers communication after signup.

The useful habit is to choose the reference source based on the decision being made. A dashboard problem, a pricing problem, and a trial conversion problem should not start with the same research set. For founders and PMs without formal design training, this keeps discussions tied to observable product behavior instead of personal preference.