3. Feature-by-Feature Scrutiny (The Idea as Stated)
Categories:
- Table stakes (TS): customers expect it. It earns nothing, but its absence costs you.
- Differentiator (D): a real reason to choose you over the alternatives.
- Distraction (X): built but unlikely to move revenue or retention.
- Liability (L): creates support, compliance, legal or trust risk.
The idea arrived as a concept from the catalog, not a feature list. Its 8 stated elements are classified below. Some sit in two buckets; the primary bucket comes first.
3.1 Classification table
| # | Stated element | Category | Reasoning |
|---|---|---|---|
| 1 | "Single-purpose" app | D | Right. A single job makes the listing, the search term and the pitch clear. Abot and Anonymous Bot both do one thing. The risk is picking the wrong one thing. |
| 2 | "One narrow team ritual", chosen later | L (as stated) | Leaving the ritual open is the biggest weakness. Four of the five examples are native, free or owned by a bigger tool (02 §2.1). Choose anonymous questions now. |
| 3 | Standups as the ritual | X | Geekbot is free for up to 10 people and $2.50–3 per participant after that. DailyBot and Standuply have free plans. Slack AI recaps are in every paid Slack plan since June 2025. |
| 4 | Kudos as the ritual | X on Teams, TS on Slack | Teams has Praise built in for every licensed user. On Slack, Karma, HeyTaco, Bonusly and Matter lead. Karma's revenue came from a team selling goals and performance, not kudos alone. |
| 5 | Birthdays as the ritual | X | Once a year per person, low willingness to pay, and many free bots. It's a feature inside engagement apps, not a product. |
| 6 | Anonymous feedback as the ritual | D | Not native in Slack or Teams channels. Paid use proven since 2018 (Abot). Best on Teams, where the direct competitors are survey tools. |
| 7 | On-call handoffs as the ritual | X / L | The buyer already pays PagerDuty, incident.io, Rootly or Jira Service Management, which post shift changes to chat. Getting a handoff wrong during an incident is a real liability. Opsgenie's end of life (5 Apr 2027) moves its users into Jira Service Management, not into a standalone bot. |
| 8 | Slack first, Teams "possibly" | X (Slack first) / D (Teams first) | For this ritual, Slack is crowded and, since 29 May 2025, slower to enter (Marketplace-only commercial distribution, 10-install minimum, review up to 10 weeks). Teams is less crowded and has far more users. Reverse the order. |
| 9 | Sold per workspace | TS | Correct and expected: Abot, Anonymous Bot, Anony Botter and OpenSay all price per workspace. On Teams, price per tenant (organisation) in flat headcount tiers. |
| 10 | Growth from app-directory placement | TS / risk | Abot's growth came from Slack App Directory placement and one Hacker News spike. SEO and Product Hunt did nothing. A directory is a channel you don't control. Pair it with exact-match search content and Microsoft Q&A answers. |
| 11 | Low maintenance (~5 hrs/month, ~$50/mo hosting) | D (as a business trait) | True for Abot after 5 years. Not true in year 1, and less true on Teams, where IT admins ask security questions. Budget 10–15 hours a week for the first 6 months. |
(The 8 stated elements expand to 11 rows because the "narrow ritual" element carried 5 example rituals.)
3.2 Scoreboard
| Category | Count | Elements |
|---|---|---|
| Table stakes | 2 | Per-workspace pricing, directory placement |
| Differentiator | 3 | Single purpose, anonymous questions, Teams first (plus low maintenance as a business trait, later) |
| Distraction | 4 | Standups, kudos on Teams, birthdays, Slack first |
| Liability | 2 | Choosing the ritual later, on-call handoffs |
About a third of what was described is a reason to buy. The rest is either already served or points at the wrong platform.
3.3 "Building to avoid selling": explicit call-outs
- A bot per ritual, or a ritual "platform". Building five small bots feels productive. It spreads a few hours a week across five listings, none of which ranks.
- Both Slack and Teams at launch. Two SDKs, two review processes, two sets of admin questions. One platform until the month-12 gate.
- AI summaries and sentiment dashboards. Impressive in a demo, but they don't answer "will leaders pay for anonymous questions?". On Slack they also carry the no-LLM-training rule and disclosure duties.
- Enterprise features before enterprise customers: SSO settings pages, data residency options, Microsoft 365 Certification. Do publisher attestation early. Do full certification only when a paying buyer asks for it.
3.4 What a disciplined v1 looks like
Keep: anonymous post and reply in a Teams channel, a moderation queue, upvotes, the all-hands question window with a ranked host view, an answer posted back to the channel, and billing (Microsoft SaaS offer plus Stripe). Defer: anonymous polls, multi-channel admin, answer archive tab, CSV export, the Slack port. Cut: identity reveal, whistleblowing flows, AI sentiment, standups, kudos, birthdays, on-call.