Mohit
54f76456ab
Signature features that turn breadth (174 skills) into a differentiated product: - Workflow recipes: 5 cross-profession chains (workflows.json) that pass each output forward — slash commands (/ship-a-feature etc.), WORKFLOWS.md generated by scripts/build-workflows.mjs, README + MCP (list_workflows/get_workflow) wired - Eval-backed quality: real per-skill scores from evals/results.json surfaced as badges in the playground and an honest README section (6 scored skills) - One-click MCP: 'claude mcp add' install + workflow tools, works in any MCP client - Playground: 'which skill?' recommender, with/without compare toggle, shareable ?skill= deep-links with prefilled inputs - Sample-output gallery: hand-written examples for the hero five + generator (scripts/build-samples.mjs) + web/examples.html - Skill-of-the-week: scheduled workflow + script that composes X/LinkedIn posts and posts to an optional webhook Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
42 lines
1.9 KiB
Markdown
42 lines
1.9 KiB
Markdown
---
|
||
skill: competitor-teardown
|
||
title: Competitor Teardown
|
||
input: "We're a lightweight team wiki for small startups. Compare us against Notion and Coda. We're cheaper and faster to set up but have fewer integrations."
|
||
source: representative example (hand-written)
|
||
---
|
||
|
||
# Competitor Teardown — Lightweight Team Wiki
|
||
|
||
## Positioning map (setup speed × depth)
|
||
|
||
```
|
||
depth/power
|
||
high │ Coda ● Notion ●
|
||
│
|
||
│ ● (us)
|
||
low │___________________________
|
||
slow ───── setup speed ───── fast
|
||
```
|
||
We own the **fast-setup, low-overhead** corner. Notion and Coda compete on depth and power, at the cost of setup time and learning curve.
|
||
|
||
## Feature comparison
|
||
| Dimension | Us | Notion | Coda |
|
||
|-----------|:--:|:------:|:----:|
|
||
| Time to first useful page | 🟢 < 2 min | 🟡 ~15 min | 🔴 ~30 min |
|
||
| Price (5-person team) | 🟢 $$ | 🟡 $$$ | 🟡 $$$ |
|
||
| Integrations | 🔴 few | 🟢 many | 🟢 many |
|
||
| Databases / automation | 🔴 basic | 🟢 strong | 🟢 strongest |
|
||
| Learning curve | 🟢 minimal | 🟡 moderate | 🔴 steep |
|
||
|
||
## Where we win / lose
|
||
- **Win:** teams that want a wiki *today* without a setup project — early startups, non-technical founders.
|
||
- **Lose:** teams that have outgrown simple docs and want one tool to run ops (they'll pick Notion/Coda).
|
||
|
||
## Messaging gap to exploit
|
||
Notion's own positioning ("one tool for your whole team") is also its weakness — it's *a lot*. Lean into **"a team wiki you'll actually finish setting up."** Speed and simplicity, not feature parity.
|
||
|
||
## Strategic recommendations
|
||
1. **Don't chase integration parity** — it's their moat, not your battlefield. Add only the 3–4 integrations startups ask for most (Slack, GitHub, Google Drive).
|
||
2. **Make migration off us painless** — removing lock-in fear lowers the bar to try.
|
||
3. **Target the "Notion is too much" segment** directly in messaging and SEO.
|