Skip to content
Idea Atlas
Sign in

StatusLens

As described:StopNarrowed:Narrow

No as a general Jira reporting suite. Go, small, as an audit-evidence app.

audited software teams · ~$80 a month per paying Jira site · last reviewed (next review by 29 Dec 2026) · 27 cited sources

Save
Share

← All research

One-Page Brief

Verdict

As described, StatusLens is a Jira reporting suite: time-in-status and SLA reports, cross-project roll-ups of estimates and progress, and audit exports. It has roughly a 6% chance of $10k MRR by month 24 and a 3% chance of $20k (judgment estimates). Each of its four parts is already a crowded Marketplace category with an established leader, and one of them has a free app with 10.5k installs. It is not fundable, and it doesn't need to be.

Cut to one job, change-control evidence for audited Jira teams, and the odds rise to ~15% ($10k) and ~7% ($20k) at ~15 hrs/week, or ~26% and ~14% full-time. $1k–3k MRR is a realistic outcome (55–70% for $1k). See 01 and WHAT-TO-DO-AND-AVOID.md.

The five things that matter

  1. The economics are the best in this portfolio. The market is the most crowded. Forge apps keep 100% of Marketplace revenue up to $1M lifetime Forge revenue (since 1 Jan 2026 for standard Forge apps). A $20k MRR app runs at ~98% gross margin. But a buyer searching "time in status" sees SaaSJet (5,322 installs, 207 reviews), OBSS Timepiece (4,442 installs, 270 reviews), Bloompeak's free app (10.5k installs) and a dozen others before you.
  2. The 0% fee is a margin edge, not a customer edge. Customers don't see it. It helps you survive on few customers. It doesn't win you any.
  3. "Runs on Atlassian" is table stakes, not a moat. SaaSJet's Time in Status and Issue History already carry the badge. You need it to be considered, not to win.
  4. The one opening is a job, not a report. Incumbents sell reports: time in status, raw history exports. Nobody verified in this run sells audit evidence: "every production change was approved by someone else, here are the exceptions, here's the pack for your auditor." That buyer has a deadline, a budget and a reason to pay per user. It's still a thin edge. SaaSJet already markets Issue History for HIPAA and FDA 21 CFR Part 11, and could copy the framing in a quarter.
  5. The platform sets hard limits. Jira Cloud's points-based rate limit (enforced since 2 Mar 2026) gives each app one 65,000-point hourly pool shared across all its installs by default. A reporting app that rescans history will throttle itself as it grows. Capture changes from events, and backfill slowly.

Feature sort (headline)

  • Table stakes: time-in-status reports, business-hours calendars, CSV/XLSX export, dashboard gadgets, Forge-only build, the "Runs on Atlassian" badge.
  • Differentiator candidates: change-approval evidence with self-approval and skipped-step exceptions, period sampling for auditors, a tamper-evident export, and a monthly control check.
  • Distractions: cross-project roll-ups, PMO portfolio dashboards, the Confluence version, a Data Center version, AI "ask your Jira" features.
  • Liabilities: "SOC 2 compliant" style claims, egress integrations that break the badge, and full-history rescans that break the rate limit.

Most likely cause of death

Nobody finds it. It's listed on the Marketplace, sits on page two for every search term that matters, and gets 3–5 trials a month. Early warning: fewer than 20 trials a month by month 6. See 05.

Next 90 days

Do: sell 3–5 hand-made evidence packs to audited Jira teams, build a Forge-only v1 around that one job, and list it by week 10–12. See plans/08. Stop: planning a time-in-status clone, roll-ups, or a Confluence app.