6. Fundability
6.1 Would I invest at pre-seed or seed?
Pre-seed: No. It's a single Marketplace app in a crowded category, with a realistic ceiling in the tens of thousands of dollars of MRR. That's a good small business, but it can't return a venture fund. I'd look again only if all of these were true:
- a founder who has run change-control evidence for audits (a GRC, security or IT-audit background);
- a plan to become a multi-app audit-evidence vendor across the Atlassian stack (Jira, JSM, Confluence, Bitbucket), not one app;
- 30+ paying sites with month-3 retention of 80% or more.
Seed: No. Nothing here needs seed money. The build is small, infrastructure is almost free, and Atlassian collects the revenue.
6.2 What a skeptical investor says in the first five minutes
- "I searched 'time in status' on the Marketplace and got a free app with 10,000 installs. Why would anyone find you?"
- "SaaSJet already sells Issue History with HIPAA and FDA Part 11 language and the Runs on Atlassian badge. What stops them adding your exceptions report next quarter?"
- "Isn't this a once-a-year purchase? What's your month-3 retention after the audit?"
- "Atlassian controls your ranking, your rate limits, your platform pricing and your payouts. What happens when they change one?"
- "How big can one Jira app get? Show me any single new app that reached $1M ARR in three years."
- "Do Vanta and Drata already pull this from Jira?"
- "Your rate-limit pool is shared across every customer. What happens at 500 installs?"
- "Why 'StatusLens' for audit evidence? The name says reports."
- "Who on the team has sat through a SOC 2 audit?"
- "What's the exit? Who buys a $10k MRR Jira app?"
If you can't answer 1, 3 and 6 crisply, the rest doesn't matter.
6.3 Three proof points that would change the answer
| # | Proof point | Threshold | Why it matters |
|---|---|---|---|
| 1 | Paid retention through an audit cycle | ≥50 paying sites, with ≥80% still paying 3 months after their audit | Proves this is a year-round product, not an audit-week purchase. |
| 2 | Measured time saved per audit | Median ≥2 engineer-days saved per audit, or zero change-control findings for customers who used the pack (self-reported, with permission to quote) | Turns "nice report" into "pays for itself in a day". That's the listing copy and the sales pitch. |
| 3 | Discovery you control | ≥40% of trials from your own content and referrals, not Marketplace search alone | Proves the business survives a ranking change. |
A fourth, for a bigger story: a second app on the same evidence engine (for example JSM or Confluence) reaching $2k MRR within 6 months of launch. That's the start of a portfolio.
6.4 Bootstrap or raise?
Bootstrap. Don't raise.
- The build is small. A Forge app with event capture, a few reports and an export is 8–10 weeks of focused work for one experienced developer.
- Costs are near zero. 0% revenue share up to $1M lifetime, Forge free allowances, no servers of your own, no payment handling.
- Revenue arrives through Atlassian from the first paying site, paid monthly once you pass $500 accrued.
- Raising would push the wrong way. Investors would want the broad suite and fast growth, which is exactly the crowded path.
- The exit that exists is a sale, not an IPO. Large Marketplace vendors such as Appfire (which lists JXL, Time to SLA and Dashboard Hub Pro) and Tempo are known to grow partly by acquiring apps. That acquisition history, and app acquisition prices and multiples, were not verified in this run. A clean, profitable, Forge-only app with good reviews is the kind of asset they buy.
Honest bottom line: the version described isn't fundable, and it doesn't need to be. The narrow version is a low-overhead, profitable app with a sale as the realistic exit. Build it that way.