Teams don't have an operating system for thinking together when AI agents are in the loop. One person prompts, one person reviews, everyone else is a spectator. Kettel puts strategy, creative, and technology in the same room — and gives the agent all three perspectives to build from.
Strategic intent gets lost in translation across perspectives. Someone defines what matters. Someone else interprets that into direction. A third translates both into prompts. By the time code ships, there are multiple layers of telephone game.
People who span strategy, creative, and technology are rare and don't scale. Every tool on the market is built for this person. Kettel is built for the team that replaces them.
Research, customer context, creative references, technical spikes. Upload anything — auto-converted to linked markdown.
Strategy writes Intent. Creative writes Direction. Technology writes Approach. The agent synthesizes all three into implementation steps.
Architecture decisions, standards, conventions. Promoted from plans. Persists across features. Grows with the project.
Open-core. Plan file, notebook, locking, annotations, agent modes, and GitHub integration are open source. Enterprise tier (SSO, audit trails, access controls, hosted version) is paid.
The shared artifact is the viral loop. Every person who receives a plan link becomes a user.
v0.1 — Web application. The room, in the browser.
v0.2 — MCP server. Technology accesses Kettel from the IDE.
v0.3 — CLI. Power users and CI/CD pipelines.
v0.4 — API. Third-party integrations.
Craft doesn't scale through faster execution. It scales through better thinking. The more powerful the agent, the more the plan matters. Kettel owns the plan.