ARMember Pro keeps its operational data in dedicated arm_* tables: arm_subscription_plans for plan definitions, arm_member_payments for every transaction with status, amount, and gateway, arm_subscription_logs for state changes across the subscription lifecycle, and member records linking everything by user_id. Clean schema for the plugin, opaque for cross-cutting questions like MRR-by-plan or churn-by-month.

SleekView Charts reads the same tables and exposes them as a chart canvas you assemble yourself. A Number card sums monthly recurring revenue from arm_member_payments.amount for active recurring plans. A Pie card splits active members by plan from arm_subscription_plans.plan_id. A Bar card ranks gateways by payment volume. An Area card plots daily payments to surface campaign-driven spikes.

Because every card runs against the live arm_* tables, the dashboard reflects right-now state, not a nightly snapshot. Finance opens the MRR view before billing, admins watch plan mix and churn, and support gates a member-context dashboard, all from the same source as the ARMember admin screens.

MRR is the single number every membership business needs in front of them every morning. ARMember Pro records every recurring payment in arm_member_payments, every plan change in arm_subscription_logs, every cancellation as a status row. The default admin shows totals and tables, but no real chart canvas.

Finance teams either build a custom dashboard or export the payments table to a spreadsheet, and the spreadsheet drifts out of sync the moment the next subscription renews. SleekView Charts runs against the same arm_* tables the admin screens read, so the MRR card matches the payments table and the plan-mix Pie matches the active-subscription count. Finance, admins, and support work from one source of truth, configured from WP Admin without writing SQL.