StatusLens (working name)
Idea status: Idea stage · Target: an MRR ladder ($1k → $50k) instead of one fixed number · Verdict: No as a general Jira reporting suite. Go, small, as a change-control evidence app for audited Jira teams, built on Forge · Last updated: 30 Sept 2026
Start here → WHAT-TO-DO-AND-AVOID.md: odds at each MRR level (with conditions: $1k ~55–70%, $5k ~28–42%, $10k ~15–26%, $20k ~7–14%), 12 do's, 14 avoids, checkpoints.
Where this came from. This idea came out of the 30 Sept 2026 micro-SaaS research run, as one of several ideas assessed in the same batch. It was not a feature list supplied by a founder, so there's no stated team, price or traction. See analysis/09.
Name. "StatusLens" is a working name. Check trademark, domain and existing Marketplace listing names before using it publicly. Several Marketplace apps already use "Status" and "Time in Status" in their names.
The idea in one line: a paid Forge app for Jira (Confluence later), sold on the Atlassian Marketplace, that covers enterprise reporting and audit gaps: time-in-status and SLA reports, cross-project roll-ups, and "who changed what and when" exports. Buyers are Jira admins and PMOs at companies that pay per user.
Research was run on 30 Sept 2026, with a confidence level on each claim. See research/10-verified-research.md.
Folder layout
statuslens/
├── WHAT-TO-DO-AND-AVOID.md ← final analysis and decision (read first)
├── README.md ← this index
├── analysis/ ← the investor-style assessment
│ ├── 00-one-page-brief.md
│ ├── 01-verdict.md
│ ├── 02-market-reality-check.md
│ ├── 03-feature-scrutiny.md
│ ├── 04-expanded-feature-catalog.md
│ ├── 05-pre-mortem.md
│ ├── 06-fundability.md
│ ├── 07-gaps.md
│ └── 09-assumptions-and-open-inputs.md
├── plans/ ← execution plans
│ ├── 08-90-day-plan.md
│ └── 11-24-month-gated-roadmap.md
└── research/ ← cited evidence
└── 10-verified-research.md
File numbers match the other ideas in this portfolio, so cross-references like "doc 08" work the same way.
Documents
| # | Document | What it answers |
|---|---|---|
| — | WHAT-TO-DO-AND-AVOID.md | Final decision: MRR ladder with odds, customer math, 12 do's, 14 avoids, checkpoints |
| 00 | analysis/00-one-page-brief.md | The whole assessment on one page |
| 01 | analysis/01-verdict.md | MRR ladder for 5 versions of the idea and 2 time commitments, Tier A/B, fundable yes/no |
| 02 | analysis/02-market-reality-check.md | Buyer segments, pain scores, Marketplace competitors with install counts, native Jira, market size |
| 03 | analysis/03-feature-scrutiny.md | The 9 stated elements of the idea, classified |
| 04 | analysis/04-expanded-feature-catalog.md | About 40 features Jira admins, PMOs and auditors ask for, classified and prioritised |
| 05 | analysis/05-pre-mortem.md | Top 3 causes of death, warning signs, fixable? |
| 06 | analysis/06-fundability.md | Invest?, the skeptic's questions, proof points, bootstrap vs raise |
| 07 | analysis/07-gaps.md | Gaps to pay, renew and refer, plus Forge platform limits and compliance |
| 08 | plans/08-90-day-plan.md | First 90 days, week by week |
| 09 | analysis/09-assumptions-and-open-inputs.md | Assumptions made, and the inputs that would change the verdict |
| 10 | research/10-verified-research.md | Cited research with confidence levels, refuted items, and what's still unverified |
| 11 | plans/11-24-month-gated-roadmap.md | Month 0–24 phases, gates, revenue path, budget guardrails |
Caveat
Team, hours per week available, geography, price and traction were never provided. The assumptions are in analysis/09. Competitor per-user prices, Marketplace trial-to-paid rates, app churn rates and any recent solo Forge revenue case are still unverified (see research/10). There is no verified base rate for new Marketplace apps reaching a given MRR.