Your paywall is losing money.
Voltaire tracks exactly why.
Run /voltaire. Voltaire connects your Stripe, reads your codebase, installs its own SDK, and proposes a targeted fix. One command.
Claude Code plugin
curl -fsSL https://mcp.hivoltaire.com/install | bash
Then run /voltaire
It gets smarter every week
Not a one-time fix. A loop that compounds.
Run /voltaire
Voltaire connects your Stripe, reads your codebase, installs its own SDK, and wires 6 behavioral events automatically. No manual setup. First fix in the same session.
Data accumulates
Sessions, feature usage, paywall events flow in. Voltaire emails you when anomalies spike or when you hit a new milestone. The more data, the sharper the next analysis.
Full context. Sharper fix.
Run /voltaire anytime. It reads everything that happened since the last run, knows what the first fix moved, and goes straight to what matters next.
Three agents. Every /voltaire.
- Timing: when your paywall fires vs the optimal moment, with confidence rating based on data volume.
- Cohort: what differentiates users who paid vs users who left. The one feature that predicts conversion.
- Churn: MRR health, monthly churn rate, median days before cancel, top cancellation reasons from Stripe.
Not just revenue data. Behavior data.
- Sessions, features used, paywall drop-off. 6 events wired directly into your codebase by Voltaire.
- Stripe revenue is always current. Benchmarked against your SaaS category, not generic averages.
- Voltaire reads the patterns, explains the why, and writes the fix with file and line number.
The data is already there. Start reading it.
One command. First fix today.
curl -fsSL https://mcp.hivoltaire.com/install | bash
Then run /voltaire in Claude Code