AUDITMAY 2026

Monitoring, Analytics & Operations System Audit

Complete inventory of what exists — no new builds

QuiPlans already has a significant analytics and reporting infrastructure. The problem is not that nothing exists — it's that too much exists, it's fragmented across 15+ admin pages, and no single operator can answer all 9 key business questions from one place.

What Exists (Confirmed by Code Audit)

CapabilityStatusWhere
Revenue tracking (today/7d/30d/YTD)✅ ExistsAdminDashboard, RevenueControlCenter, KPIDashboard, DailyPerformanceDashboard
Funnel visualization (lead → purchase)✅ Exists (in 3 places)AdminDashboard, RevenueControlCenter, KPIDashboard
Sales mix by package type✅ Exists (in 2 places)RevenueControlCenter → Overview, KPIDashboard → Sales Mix tab
State revenue breakdown✅ ExistsKPIDashboard → Segments tab, AnalyticsCommandCenter
Attribution (UTM source)✅ ExistsRevenueControlCenter → Attribution section, AdminOrders
Email sequence tracking⚠️ Partial — open/click rates only if EmailLog populatedKPIDashboard → Email tab
Checkout abandonment rate✅ Exists (CheckoutAttempt entity)DailyPerformanceDashboard
Engineering pipeline✅ ExistsKPIDashboard → Ops tab, RevenueControlCenter → Engineering
Quig economy analytics✅ ExistsKPIDashboard → Quig Economy tab, RevenueControlCenter → Builder & Quigs
Annual run rate / goal tracking✅ Exists (in 2 places)RevenueControlCenter, KPIDashboard → Goals tab
Builder pipeline✅ ExistsKPIDashboard → Builder tab, AdminBuilderPipeline
CTA performance tracking⚠️ Entity exists (CTARegistry, EmailCTARegistry) — no live reporting UIFunnelCtaDashboard (exists but not verified functional)
Meta ad CAPI events⚠️ metaCapi function exists — not verified firingmetaCapi backend function
GA4 events⚠️ gtag initialized in Layout — purchase event not verifiedlayout.jsx, lib/analytics.js
Revenue forecasting✅ Exists (7d + 30d projections)RevenueControlCenter → Forecast section
Margin tracking✅ Exists (configurable)RevenueControlCenter → Margin tab

The Core Problem: 3-Level Fragmentation

🚨Level 1 — Duplicate data: Revenue, funnel, and sales mix are computed 3 separate times (AdminDashboard, RevenueControlCenter, KPIDashboard) from the same source entities. Each page re-queries Order + AduLead independently. This is inefficient and causes display inconsistencies when date ranges differ.
⚠️Level 2 — Split purpose: The "daily operations" dashboard (AdminDashboard) and the "strategic KPI" dashboard (KPIDashboard) have 70% overlapping content. A new operator has no clear instruction on which one to use for what.
⚠️Level 3 — Broken data chains: Email analytics in KPIDashboard requires EmailLog entity to be populated with opened/clicked fields — but the current email sending functions (SendGrid via sendEmail) do NOT appear to log back to EmailLog entity automatically. This tab likely shows 0 data.
base44
Edit with Base44