PROJECT SCREENSInside the design
Auto-scrolling — hover any screen to pause & pan
UI/UX design for a modern SaaS subscription module — plans, billing and upgrades designed to feel effortless.
A subscription module is where a SaaS product earns its money — and where users feel the most friction. This concept redesigns plan selection, billing and upgrades into a clear, confident flow.
Pricing pages and billing settings are often dense, jargon-heavy and anxiety-inducing. Users need to compare plans, understand what changes, and trust the transaction.
End-to-end design of the module: flows, wireframes, high-fidelity UI and interaction states for plan comparison, checkout and account billing.
Feature-by-feature comparison without a wall of checkmarks.
Change of plan previewed with prorated cost before confirming.
Clear billing summary, no surprise renewals or hidden fees.
Invoices, payment methods and cancellation without support tickets.
Discovery focused on the jobs users hire the product for: what decision does this screen serve, what action follows, what can wait behind a click. Auditing comparable SaaS tools showed the same trap everywhere — dashboards that display everything and prioritise nothing.
Users open the product to do something. The landing view must answer “what needs me today?” before showing anything else.
Dense tables are fine — undifferentiated dense tables are not. Summary first, detail on demand.
In daily-use tools, users get fast by building muscle memory; consistent patterns are a performance feature.
Lives in the product, values speed and keyboard-friendly flows, and notices every inconsistency. Needs dense-but-ordered screens that reward familiarity.
Drops in weekly for status and numbers. Needs summaries, trends and export — without relearning the interface each visit.
A restrained interface where colour means something: neutrals for structure, one accent for primary actions, and semantic colour reserved for status. Tables use progressive disclosure, cards summarise before they detail, and every component comes from a documented library so new screens ship consistent by default.
Prototypes were tested against realistic data volumes — hundreds of rows, awkward edge cases, long names — because SaaS designs that demo well often collapse under real data. Iterations tightened empty states, loading states and error states, the three screens teams usually forget.
Auto-scrolling — hover any screen to pause & pan
A calm, conversion-minded subscription experience — explore every screen in the full Behance case study.
View full project on Behance