Vū Studio Insights

Software Support Tickets Submitted per Month

Software Support (most recent first)

All paying software customers (HubSpot Software pipeline, closed-won deals) ranked by total Mixpanel actions in the last 30 days (excl. @vustudio.com). 🟢 >20 actions  ·  🔴 ≤20 actions or no activity.

Issue Types Resolved

Open Jira items ranked by number of labels (most → least). Each label captures a distinct request/requester on the item.

Paid cohort = the 33 paying software customers' accounts. Activated paying users engage far harder than the blended average, which is diluted by trial sign-ups with little activity: paid customers are only — of active users but drive — of all interactive usage.

Sign Up → Purchase Conversion

Monthly Sign Ups — Last 6 Months

Ranked by how many distinct customers touched the feature, not by raw event volume — a feature with 5,000 events from one account is not a loved feature. Events per user shows depth: high reach + high intensity is a habit; high reach + low intensity is a feature people try once. Excludes @vustudio.com accounts, the 11 passive machine events, and sign-up/login/profile lifecycle events.

📋 Inactive User Notes

Who is NOT using the software: Mixpanel tracks only users who fire at least one event. To identify inactive users, compare the total registered user count (from your auth system or HubSpot) against the — unique users active in the last 30 days. Users who signed up but haven't fired an event in 30+ days are your at-risk cohort.

Daily users: The DAU chart above shows that peak weekday usage reaches ~180–207 unique users/day, while the 30-day unique total is ~1,789. This implies most users are occasional, not daily. A stickiness ratio below 10% suggests the majority of monthly users do not return daily.

Power users vs. casual:

Total Interactions vs Human Interactions (30d)

External users generated — total interactions, of which — were human actions (—). Paying customers: — human of — total. The remainder is passive machine telemetry from players and kiosks — real usage, but not engagement. Excluded events:

Every user who fired Sign Up in the last 30 days, ranked by total actions performed since (excludes @vustudio.com; matched on the email user property). Because all signed up inside the window, this is effectively their post-sign-up activity. 🟢 >20 actions · 🟡 6–20 · 🔴 ≤5 (activation gap).

Everything above excludes internal users. This section is the inverse — it shows only the traffic the exclusion removes, so we can see what our own team exercises. Internal = email contains vustudio.com OR is_internal = true (the "Vū Internal Users" cohort definition).

🔝 Top 20 Features Used by Internal Users

Raw event counts, same basis as the external Feature Usage lists above.

📈 Staff Weekly Usage — Last 26 Weeks (Target: 20 Active Staff / Weekday)

Bars: average daily active staff per week (distinct @vustudio.com users with ≥1 Page View, Mon–Fri average; test rigs stage1@/stage3@ and lobby@ excluded). Line: 4-week rolling average. Dashed line: target of 20 active staff per weekday (~67% of 30 staff).

Weekly active staff = distinct staff with any Page View that week. Human actions exclude the 11 passive machine events. Target = 20 of 30 staff active each weekday (stretch 24); grow ~+10% month over month until reached, then hold ≥20 (flag a month below 18). Holiday weeks dip.

📅 Daily Active Staff — Month over Month

Distinct @vustudio.com staff with ≥1 Page View per day, overlaid by day of month (weekdays only — weekends hidden; test rigs stage1@/stage3@ and lobby@ excluded). Current month is solid; prior months are dashed; green dashed line = target (20). Growth phase: +10% month over month until the target; then maintain ≥20 (flag below 18).

Requests explicitly raised by external customers in the last 30 days, sorted by number of distinct accounts.