RitualBot (working name)
Idea status: Idea stage · Target: an MRR ladder ($1k → $50k) instead of one fixed number · Verdict: No as described. Go, small, as anonymous questions for Microsoft Teams. · Last updated: 30 Sept 2026
Start here → WHAT-TO-DO-AND-AVOID.md: odds at each MRR level (with conditions: $1k ~45–55%, $5k ~15–22%, $10k ~6–10%, $20k ~2–4%), 12 do's, 14 avoids, checkpoints.
Where this came from. This idea came from the 30 Sept 2026 micro-SaaS idea catalog, row C6 ("Paid Slack bot for one team ritual"), 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. "RitualBot" is a working name. Check trademark, domain, and Teams Store and Slack Marketplace listing names before using it publicly. Many chat apps already use "Bot" in their names, and a name that says "anonymous" or "ask" will sell the wedge better.
The idea in one line (as given): a paid single-purpose Slack app (and possibly Microsoft Teams) for one narrow team ritual, such as standups, kudos, birthdays, anonymous feedback or on-call handoffs, sold per workspace.
The idea in one line (after assessment): a Microsoft Teams app for anonymous questions: staff ask anonymously in a channel, a moderator approves, colleagues upvote, and leaders answer in the open, built around the all-hands cycle. Priced per organisation. Slack port only after the month-12 gate.
Research was run on 30 Sept 2026, with a confidence level on each claim. See research/10-verified-research.md.
Folder layout
ritualbot/
├── 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 6 versions of the idea and 2 time commitments, Tier A/B, fundable yes/no |
| 02 | analysis/02-market-reality-check.md | Ritual-by-ritual scoring, Slack vs Teams, competitors and prices, native features, market size |
| 03 | analysis/03-feature-scrutiny.md | The 8 stated elements of the idea, classified |
| 04 | analysis/04-expanded-feature-catalog.md | About 35 features buyers of anonymous-question tools 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 platform rules, privacy and moderation |
| 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, conflicts, 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. Teams Store install volumes for small apps, churn for anonymous-question apps, Teams Store validation times, and any revenue case for a solo Teams-first app are still unverified (see research/10). There is no verified base rate for new Slack or Teams apps reaching a given MRR.