HelpDeck (originally "a help center or forms layer on top of Notion")
Idea status: Idea stage · Target: an MRR ladder ($1k → $50k) instead of one fixed number · Verdict: No as described. Weak Go only as a Forge help-center app for Confluence Cloud, and only as a second Forge app. · Last updated: 30 Sept 2026
Origin: this idea came from the 30 Sept 2026 micro-SaaS idea catalog, row C4 ("Help center or forms layer on top of Notion"). See ../_research/2026-09-30-micro-saas-idea-catalog.md.
Name: "HelpDeck" is a working name. It sits very close to the generic term "help desk", so it will be hard to own. Check trademark and domain before using it publicly.
Start here → WHAT-TO-DO-AND-AVOID.md for:
- odds at each MRR level, with the conditions met ($1k ~35–48%, $5k ~11–18%, $10k ~5–9%, $20k ~2–4%);
- customer math, the churn check, 12 do's, 14 avoids and checkpoints.
The short version. The two Notion layers in the catalog are both worse bets in 2026 than when they made money:
- Forms on Notion are finished as a business for a newcomer. Notion Forms is free on every Notion plan. Tally gives unlimited forms with a free Notion integration and claims 500,000+ teams. NotionForms itself was renamed NoteForms, and its founder built OpnForm, a form builder without Notion, to reduce platform risk.
- A Notion help center is a crowded, solved niche. HelpKit leads, claims 1,000+ customers, and took about 3.5 years to reach its reported $10k+ MRR as the first mover. At least six other Notion site or help-center builders compete, and Notion Sites is free.
Five versions were scored (see analysis/01): Notion forms, Notion help center, Confluence help center, Google Docs help center, and a vertical help center. A Confluence Cloud help-center app on Forge scored highest, and it's still weak. It ranks last in this portfolio. StatusLens and DocPress beat it at every rung.
Research was run on 30 Sept 2026, with a confidence level on each claim. See research/10-verified-research.md.
Folder layout
helpdeck/
├── 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, customer math, profit and churn checks, 12 do's, 14 avoids, checkpoints |
| 00 | analysis/00-one-page-brief.md | The whole assessment on one page |
| 01 | analysis/01-verdict.md | Five versions scored, the MRR ladder for each, Tier A/B, fundable yes/no |
| 02 | analysis/02-market-reality-check.md | Buyer segments, pain scores, native tools, Notion layers, Confluence apps, standalone help centers, market size |
| 03 | analysis/03-feature-scrutiny.md | The stated idea and its typical features, classified |
| 04 | analysis/04-expanded-feature-catalog.md | About 40 features, classified and prioritised for the wedge |
| 05 | analysis/05-pre-mortem.md | Top 3 causes of death, warning signs, whether each is fixable |
| 06 | analysis/06-fundability.md | Invest?, the skeptic's questions, proof points, bootstrap vs raise |
| 07 | analysis/07-gaps.md | Gaps to paid, renewed and referred customers, pricing, compliance |
| 08 | plans/08-90-day-plan.md | First 90 days, week by week, with a day-45 kill test |
| 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, and what's still unverified |
| 11 | plans/11-24-month-gated-roadmap.md | Phases, gates, revenue path for each time commitment, budget guardrails |
Caveat
Team, hours per week, Forge experience, geography and budget were not provided. The assumptions are in analysis/09.
No verified base rate exists for bootstrapped B2B add-ons reaching MRR levels. All odds are judgment estimates. Three items could change the verdict and are still unverified: whether Atlassian itself now ships a public-pages feature for Confluence, how fast Confluence publishing apps churn, and whether a public site can be served cleanly from a Forge app. See research/10.