Kollab vs Stet

The primitive here is a shared prompt-and-context registry with a workflow runner bolted on — which is a real problem, but the DX bet is squarely on the no-code crowd, not engineers who'd actually compose this into something. The Skills layer sounds like saved prompts with parameters, and there's no public API, no SDK, no repo to audit — so the 'full participant' positioning is marketing until I can call an agent from my own code. The moment of truth is building your first Skill, and if that's a form with dropdowns rather than a function signature, I'm out.

Open-source, BYOK, and local-first listening? This is how voice input should work. The Groq integration makes transcription near-instant. I've been using it for commit messages and code comments — genuinely faster than typing for longer explanations.

The direct competitors here are Notion AI with its database integrations, and more pointedly, Microsoft Copilot Pages — both of which already sit inside workflows teams actually use daily, backed by companies that own the productivity stack. The specific scenario where Kollab breaks is at the organizational scale: persistent memory across sessions sounds great until you have 200 employees, conflicting contexts, and no audit trail for what the agent 'remembered.' What kills this in 12 months isn't a competitor — it's that Slack and Notion each ship a native Skills-equivalent, and the integration layer Kollab's Bots occupy evaporates overnight.

Apple's built-in dictation has gotten surprisingly good, and it's free with no BYOK setup. The 'preserves your voice' pitch is compelling but subjective — I'd want a side-by-side blind test. Solo indie developer + $7/mo hosted tier raises long-term sustainability questions.