Kateto

Company: Kateto

Self-reported basis: The description is entirely from the author’s own submission to a hackathon — no external verification, no archived history, no third-party corroboration.

What it appears to be: A self-described AI-powered project management system built around a plugin architecture and “Voices” (agents) with defined roles like orchestrator, project manager, and scrum master. It is described as evolving and adapting to the user’s way of working.

What changed: The author states this is an ongoing project, with plans for more than 10 voices, and a system that is extensible and evolving.

Single most important open question: Is there any evidence of actual usage or traction beyond the author's own development and iteration?

The description states that Kateto is a system of plugins and events aimed at handling AI models represented as “Voices.” These agents have personalities, workflows, and skills. The system enforces deterministic pipelines with deliverables and evolves based on data.

• Plugin-based architecture: The system uses plugins to build and extend functionality.
• Voices as agents: There are currently three voices:
  • Jane (Orchestrator)
  • Doktor (Project Manager)
  • Conquest (SCRUM master)
• Workflow enforcement: Workflows are described as deterministic with deliverables.
• Extensibility: The author claims the system is extensible and plans to add more than 10 voices.

Inference: The system appears to be a developer-oriented tool, built using Python and Codex, and designed for lead developers managing multiple projects. It is not clear if it is a standalone product or an internal tool being developed for personal use or demonstration.

The author states that Kateto was born from an obsession with automating life, and currently automates the project management process. The positioning is self-described as:

• Automated project management: It handles documentation and organization for users who are too busy or lazy.
• Adaptive AI agents: The system evolves at every step and adapts to the user’s way of working.
• Developer-focused: The author identifies as a lead developer, suggesting it is aimed at developers or technical teams.

Inference: The positioning is aspirational — the product is described as evolving and improving with data, but there is no evidence of real-world adoption or feedback loops. It is positioned as a personal automation tool that may scale into something more.

The author states that Kateto was built to help lead developers who work on multiple projects at once. The system is described as being useful for managing risks, backlogs, events, and teams — roles typically associated with project managers or technical leads.

• Primary user: Lead developers managing multiple projects.
• Use case: Project management, risk handling, team coordination, and workflow enforcement.
• ICP (Ideal Customer Profile): Not explicitly defined. The description implies a niche audience of developers who want to automate their workflows.

Inference: The target customer is likely technical professionals or small teams. However, the lack of any stated customer base or user feedback makes it unclear if there is real demand beyond the author’s own use case.

The description does not contain any information about pricing, monetization, or business model.

• No pricing: Not evidenced.
• No revenue streams: Not evidenced.
• No commercial intent: The project is described as a personal automation tool and a hackathon submission.

Inference: There is no evidence of a business model or commercial viability. It appears to be a prototype or personal project, not a product with a monetization strategy.

The author states that the system was built using:

• Technology stack: Python and Codex.
• MVP delivery: The author mentions building an online MVP, fixes, and visual components for a presentation video.
• Plugin architecture: The system is described as plugin-based.
• Voice personalities: Agents with defined roles and workflows.

Inference: The technical approach is experimental and personal. It is not clear if the tool has been tested beyond the author’s own use or if it is scalable or stable for others.

The description does not contain any evidence of traction, adoption, or user feedback.

• No customers: Not evidenced.
• No revenue: Not evidenced.
• No usage metrics: Not evidenced.
• No user base: Not evidenced.
• No product-market fit signals: Not evidenced.

Inference: There is no indication that Kateto has moved beyond the prototype or personal development stage. It is described as an evolving system, but there is no evidence of real-world use or iteration with users.

The description does not mention any competitors or market context.

• No competitive analysis: Not evidenced.
• No market positioning: Not evidenced.
• No differentiation claims: Not evidenced.

Inference: The author does not provide any information about the competitive landscape, which makes it difficult to assess whether Kateto fills a gap or overlaps with existing tools in project management or AI automation.

• No traction or adoption: The system is described as personal and evolving — no evidence of real-world usage.
• No commercial viability: No pricing, revenue, or monetization strategy is evident.
• Unverified claims: All descriptions are self-reported and unverified.
• Developer-centric prototype: Likely not ready for broader use or market adoption.
• Lack of user feedback: No evidence of iteration based on user needs.

Inference: The project appears to be a personal experiment or hackathon submission, not a product with commercial intent or traction. It is at a very early stage and lacks any signals of maturity or scalability.

1. What specific problems are you trying to solve for developers, and how do you know these problems are real?
2. Have you tested the system with other users beyond yourself? If so, what feedback did you get?
3. How do you plan to monetize this product, if at all?
4. What is your roadmap for scaling beyond the current 3 voices and 10 planned voices?
5. What are the key assumptions underlying your approach to AI agents in project management?