Your Revenue Dashboard Now Alerts You Before Problems Become Crises

Release v1.0.38 — Intelligence Update

A revenue chart turning red is only useful if someone is watching. Until now, the SaaS Factory Revenue Dashboard would display a negative month-over-month MRR figure in red — and stop there. No alert. No notification. No escalation. If MRR dropped 25% and nobody happened to open the dashboard, the platform stayed silent.

That changes with v1.0.38.

---

The Problem with Passive Dashboards

Dashboards are historical records. They tell you what happened. But in an autonomous platform, waiting to be checked is a design flaw. If the system knows MoM growth has dropped below -10%, it should act — not wait.

The gap was concrete:

• The Revenue Dashboard had no concept of a threshold.
• The notification system had no revenue_drop event type.
• The billing cron ran daily but never evaluated revenue health.
• The Revenue Discovery Agent had no automated trigger.

Every piece existed. They just weren't wired together.

---

What v1.0.38 Does

A New Threshold: -10% MoM MRR

When month-over-month MRR growth drops below -10%, the platform now automatically:

1. Surfaces a warning banner on the Revenue tab — persistent until growth recovers.
2. Sends a revenue_drop notification via the existing notifications infrastructure (in-app, email, Slack — wherever you're connected).
3. Optionally triggers the Revenue Discovery Agent to begin finding monetization improvements.

New Notification Event Types

Two new events join the NotificationEvent type:

• revenue_drop — fires when MoM MRR crosses the -10% floor.
• churn_spike — fires when churn rate breaches its configured threshold.

These aren't one-off additions. They're the beginning of a richer event vocabulary for revenue intelligence.

The Billing Cron Gets Smarter

The daily billing-crons.ts run now does more than process billing records. It computes the current MoM MRR delta and, if the threshold is breached, fires sendNotification. The entire alerting chain runs on the same schedule that was already running — no new infrastructure, no new maintenance burden.

---

Detection to Action

The most important design decision in this release isn't the banner or the notification. It's the optional escalation to the Revenue Discovery Agent.

Most alerting systems stop at detection: something is wrong, go fix it. SaaS Factory can close the loop. A revenue_drop event doesn't just inform — it can initiate. The Revenue Discovery Agent begins surfacing monetization improvements autonomously, without waiting for a human to read the alert and decide what to do next.

This is what intelligence in operations actually looks like: the system detects a problem, notifies the right parties, and starts working on the solution — simultaneously.

---

Summary

Before v1.0.38	After v1.0.38
Negative MoM shown in red	Warning banner on Revenue tab
No notification sent	revenue_drop notification fired
Billing cron: billing only	Billing cron: billing + revenue health check
No Revenue Discovery trigger	Optional agent escalation on drop
revenue_drop not a valid event type	revenue_drop + churn_spike in NotificationEvent

---

v1.0.38 is available now. See the changelog and feature documentation for full details.