Membership 2 Pro models its core objects as custom post types in wp_posts. Memberships are ms_membership, member-to-membership relationships are ms_relationship, invoices are ms_invoice, and protection rules are stored as serialised data in wp_postmeta against membership posts. Subscriber state (active, expired, trial, cancelled) lives in postmeta on the relationship record along with start, end, and trial dates.

The default Membership 2 Pro admin gives separate screens for Memberships, Members, Add-ons, Settings, and Billing. Joining a member to their invoices and current relationship state needs the Reports screen or navigating between three sections. The Members screen lists subscribers but doesn't expose invoice status or lifetime spend as columns, so the operational view (who's active, who paid recently, who's about to expire) requires multiple drilldowns.

SleekView reads wp_posts for ms_relationship and ms_invoice, joins them by member ID, and shows subscribers as a single sortable view with membership level, status, lifetime spend, last invoice outcome, and renewal date as proper columns. The expiry-this-week cohort becomes a saved filter.

Membership 2 Pro is well-architected because every operational object is a custom post type with its relationships modelled in postmeta. That makes the data easy to query and easy to extend. The default admin then walks that structure with a screen per CPT, which is fine for editing one record at a time but slow for row-level operational work.

Almost every retention question is cross-CPT: who's expiring this week, whose last invoice failed, who's still on trial past day fourteen, which membership level has the worst churn. The data is all there; the workspace is not. SleekView builds that workspace by joining ms_relationship to ms_invoice by member, exposing membership level and lifetime spend as columns, and treating subscriber state as a top-level filter.

Finance teams reconcile monthly close in one view; membership admins triage expiry and trial conversion at the table level; support staff see full context on every ticket. Each persona was already doing these workflows manually across three screens. SleekView turns that work into a saved view per role and an inline edit per row.