Tutorial — Maintaining Usage Drivers

What This Tool Is For

How to keep the operational quantities (users, traffic, transactions) flowing — the denominators of every per-unit metric.

Step-by-Step Walkthrough

Step 1 — Know your drivers: the handful of quantities your economics divide by — active users, data delivered, transactions processed. They arrive automatically where a source exists, manually where one doesn't.

Step 2 — For manual drivers, set a cadence (weekly or monthly) and an owner. An unowned manual driver decays into staleness within two cycles, and every per-unit metric built on it quietly rots.

Step 3 — Enter values with their date and origin ("analytics dashboard, read July 1"), exactly like any other data point.

Step 4 — Sanity-check the curve after entry: a driver that doubles or halves in a month is either big news or a typo — both deserve a second look before the dashboards drink it.

Real-World Example

Scenario: Cost-per-active-user has been flat for three months — suspiciously flat, since costs rose. Check the driver: monthly active users was last manually updated in March; the denominator froze. The owner enters the missed months (April 17,400; May 18,000; June 18,600 from the analytics tool), the metric recomputes — and shows per-user cost actually FELL. The business was scaling more efficiently the whole time; only the bookkeeping of the denominator had stalled.

Tips & Common Mistakes

• Per-unit metrics fail silently when denominators go stale — staleness, not error, is the enemy.
• Automate any driver you find yourself typing more than three times.
• When a driver's definition changes (what counts as "active"?), note the date of the change; otherwise the trend break will be misread forever.

---

Everything described in this tutorial is a working feature of TupicFinance, the financial management platform of the Tupic ecosystem. The screens, workflows, and guardrails above behave exactly as written there — this guide doubles as the platform's user manual for this tool.