Wizzo

The description states that Wizzo is an AI-native planning and execution workspace. It allows users to:

• Turn broad goals into structured quests, trials, tasks, and subtasks
• Define dependencies so work happens in the correct order
• Track progress, status, evidence, and completion history
• Create reusable templates for recurring workflows
• Compare performance and activity across projects
• Receive contextual recommendations about what to do next
• Review AI suggestions before they affect the underlying plan

It is built as a full-stack web application using Next.js, React, TypeScript, Neon/PostgreSQL, Vercel, serverless infrastructure, LLM APIs, retrieval-augmented generation (RAG), and structured analytics.

The system separates generative output from deterministic behavior. Model responses are validated and translated into structured application state rather than being trusted as unrestricted instructions.

Inference The product is described as a tool for managing personal or individual-level workflows with AI assistance, not enterprise-scale project management.

The author claims Wizzo explores a different model of productivity tools, one that helps people move from intention to action while keeping the user in control. It contrasts itself with:

• Tools that record work after decisions are made
• Chat-based AI tools that lose context or produce disconnected suggestions

Key positioning elements include:

• Human-in-the-loop decision policy
• Structured workflows and dependencies
• Contextual recommendations tied to structured product state
• Shadow mode for evaluating AI behavior before allowing it to influence production

Inference Wizzo positions itself as a human-centered AI planning tool, not a general-purpose AI assistant or task manager.

The description does not explicitly name target customers or define an ideal customer profile (ICP). However, it implies:

• Users who manage personal goals and projects
• Individuals seeking structured workflows with AI support
• People who value control over AI-generated actions

It is built for individuals, not teams or organizations.

Inference The ICP likely includes solo founders, freelancers, or knowledge workers managing complex, long-running tasks.

There is no evidence of a business model or pricing structure in the description. The author states that Wizzo was built as a solo founder project, with no mention of monetization, subscriptions, or paid features.

Inference No commercial model is evident beyond personal development and experimentation.

Wizzo is built using:

• Frontend: Next.js, React, TypeScript
• Backend: PostgreSQL (with Neon), serverless functions, REST API
• AI Stack: LLM APIs, RAG, retrieval-augmented generation
• Infrastructure: Vercel, feature flags, versioned SQL migrations
• Analytics & Audit: Structured analytics, audit records, lifecycle events

Key technical features include:

• Separation of generative output from deterministic behavior
• Shadow mode for AI decision evaluation
• Stable identifiers, fallback paths, and audit records
• Use of structured state to maintain context across long-running work
• Fallback mechanisms for infrastructure failures

Inference The architecture shows a deliberate focus on safety, control, and operational robustness, especially around AI integration.

The description states that Wizzo was built by a single founder (Michael Chaves) and submitted to the OpenAI 2026 hackathon. No evidence of revenue, customers, or adoption is provided.

It includes accomplishments such as:

• Shipping analytics and dashboards
• Implementing shadow evaluation before automated execution
• Replacing fragile dependencies with serverless fallbacks

However, these are described as development milestones, not signs of product-market fit or traction.

Inference No evidence of traction or maturity beyond a solo developer’s prototype.

The author does not name competitors. However, Wizzo appears to be positioned in the space of:

• AI-powered productivity tools
• Workflow and task management platforms
• Human-in-the-loop AI systems

It contrasts with tools that are:

• Chatbot-first
• Contextually disconnected
• Unstructured or opaque in their AI decision-making

Inference Wizzo is likely competing against general-purpose AI assistants (e.g., ChatGPT, Claude) and task managers (e.g., Notion, Todoist), but without specific competitive positioning.

• No revenue or customer data: The product is described as a solo founder project with no evidence of monetization or adoption.
• Unproven market demand: No indication that users are actively using the tool beyond its creator.
• Limited scalability: Built by one person; unclear if it can scale beyond prototype-level functionality.
• Unclear commercial viability: No pricing, business model, or go-to-market strategy is evident.
• Self-reported only: All claims are unverified and based on a single author’s account.

Inference The project lacks evidence of commercial traction or market validation.

1. What specific user problems does Wizzo solve, and how do you know?
2. Have you tested the product with any users beyond yourself?
3. What is your plan for monetization or scaling beyond a solo developer?
4. How do you intend to validate the effectiveness of the decision-policy architecture?
5. What are the key assumptions in your product design that you’re testing?
6. Is there any data on how often users accept, reject, or modify AI recommendations?