Paid Member Subscriptions (Cozmoslabs) handles its own member-and-payment layer separately from wp_users. Subscription plans live in a plans table, member assignments in a members-to-plans table with status (active, expired, cancelled, pending), start and expiry timestamps, and the linked WordPress user, and payments in a payments table with gateway transaction IDs linking renewals to their parent subscriptions. WooCommerce-restricted products and Stripe recurring charges all flow through the same payments table.

The default Paid Member Subscriptions admin gives Members and Payments separate screens with their own filters. Joining a member to their last payment, current plan, and lifetime spend means jumping between screens and matching by user ID. The members screen shows status but doesn't show last-payment outcome, plan name, or expiry alongside it. Per-plan cohort retention, dunning queues for failed Stripe charges, and lifetime-spend rankings all sit somewhere between the default screens and the export tool.

SleekView reads the plugin's tables directly, joins members to plans and payments on the user ID, and produces a member-centric roster with plan name, status, last payment, lifetime spend, and expiry as columns. The dunning queue becomes a filter on payment status; the renewal-risk list becomes a sort on expiry.

Paid Member Subscriptions sits in a sweet spot for sites that have outgrown the simplest membership plugins but don't need the breadth of MemberPress or Paid Memberships Pro. It does its core job well — plan capture, content restriction, recurring billing — and stays out of the way otherwise. The cost of that simplicity shows up on the operational side, where members and payments are two separate admin screens.

Every retention question, every dunning workflow, and every cohort analysis needs both tables read together. Did this member's last payment fail? Are they still listed as active despite that? How much have they paid since signup? When does their plan expire? PMS stores the data, but reaching it from the default admin means screen-jumping and exports. SleekView's joined view collapses that into one workspace where the row-level question is one filter away — finance running monthly close, support handling chat, and growth running cohort retention all benefit from the same simplification.