Esta página aún no está traducida, así que se muestra en inglés.

SaaS pack

The SaaS pack sets Rainbook up for subscription software: trials, plans and seats, renewals and expansion, and retention metrics.

Who it is for

Software companies selling subscriptions, from a first sales hire to a full revenue team. The SaaS pack is generally available and installs whole on every Rainbook edition, the free tier and Jira Free.

Trial stage and pipelines

The pack adds a Trial stage to your Deal workflow, between Discover and Propose, and three pipelines with stage probabilities that fit subscription sales:

Expansion is a Deal type, and Renewal is Rainbook's own work type, so you keep one place for every deal.

Fields

All of these are native Jira fields, searchable in JQL and readable after an uninstall.

Views, dashboards and metrics

Saved views: Renewals in the next 90 days, At-risk renewals, Open expansion, and Trials ending in 14 days.

The SaaS revenue dashboard shows net and gross revenue retention, renewals by health and pipeline coverage.

Metrics you can ask about and report on:

• ARR: the sum of ARR on customer accounts.
• Net revenue retention: start ARR plus expansion, minus contraction and churn, divided by start ARR, for the accounts that were customers when the period began.
• Gross revenue retention: the same, without expansion.
• Churned ARR and Expansion ARR.
• Pipeline coverage: open weighted pipeline closing in the period against your quarterly target.
• Seat utilisation: seats used against seats purchased.

Try: "What was NRR last quarter by plan?" or "Which open deals have a floor price over $50,000?"

Health signals

The pack tunes each account's Health score for subscription customers: support load, SLA breaches, open bugs, reply lag, sentiment, stage age and days to renewal, plus two SaaS signals. Seat utilisation scores low below 50% and full above 85%, and a plan downgrade in the last 90 days costs 15 points.

Rules

Each rule is on when you install the pack, and an admin can turn any of them off.

• MRR from ARR: when ARR changes, MRR follows, unless someone edited MRR in the last 30 days.
• Renewal lead time: renewals are created 120 days before the renewal date, instead of 90.
• Trial ending: the deal owner gets a reminder 3 days before Trial end.
• Churn save: when a renewal's Health drops below 40, Rainbook proposes a save play for its owner to approve.
• Expansion signal: when seats used pass 90% of seats purchased, Rainbook proposes a draft expansion deal for approval.

A Jira Automation template, "Support items → Follow-up for the account owner", is ready to download from Settings › Packs.

Rainbook's own AI, capture and background jobs are included in your subscription and use neither Rovo credits nor Automation steps. The Rainbook agent in Rovo, Rovo Studio agents that use Rainbook's tools, and Automation rules built from Rainbook's templates or actions use your Atlassian allowances: Rovo credits from 3 Dec 2026, and Automation steps from your first renewal on or after 3 Dec, shown per rule in your admin Usage tab.

AI that speaks SaaS

Summaries and next steps for accounts and renewals mention plan, seats, utilisation and renewal date, and for deals and renewals they include pricing terms, floor price and discount rationale. Health reasons name the top two signals with their numbers. Ask suggests SaaS metrics first, and drafted follow-ups have a renewal tone: value recap, usage and next step.

Get started

Install the pack from Settings › Packs and add the demo data to see a full SaaS pipeline in minutes. See Industry packs for how install, updates and removal work.