Polynus

The company appears to be a solo-built, self-reported AI productivity tool for managing scattered context across professional, academic, and personal life modes. The project is described as an MVP built during a hackathon, with no evidence of revenue, customers or traction. The core commercial question is whether this concept can scale beyond a prototype and gain user adoption.

The description states that Polynus is:

• A "daily command center" for people balancing three life modes
• A tool that organizes AI-work context into Professional, Academic, and Personal categories
• A dashboard that surfaces pending tasks, makes AI time visible, removes repeated task noise, and recommends next moves
• Built as a full-stack Next.js application using React, TypeScript, Supabase, Google OAuth, and OpenAI Codex

Inference The product appears to be a UI layer that aggregates and categorizes user-generated AI content into structured tasks across three life modes.

The description states:

• Polynus addresses the problem of scattered attention from AI tools
• It positions itself as an alternative to "giant task lists" that force everything into one pile
• It claims to help users identify a "focused next move"
• It emphasizes "calm, mode-aware" operation over "scattered" AI-work context

Inference The positioning appears to be a productivity tool for people who use multiple AI tools across different life contexts, rather than a general-purpose task manager.

The description states:

• The target is "people balancing three modes of life"
• These modes are Professional, Academic, and Personal
• The tool is designed for users who already use AI tools but struggle with scattered context

Inference The ICP appears to be individuals managing multiple life contexts using AI tools, likely professionals, students, or creators.

The description states:

• No pricing information is provided
• The MVP uses "approved/imported or demo AI-work context"
• Future phases will include opt-in integrations with Gmail, Outlook, Calendar, Drive
• Users control what Polynus can access

Inference The business model appears to be based on user-controlled data access and future paid integrations, but no pricing evidence exists.

The description states:

• Built with Next.js, React, TypeScript
• Authentication via Supabase and Google OAuth
• Deployment on Vercel
• AI-assisted development using OpenAI Codex
• Dark, calm command-center UI with three distinct mode colors
• MVP includes secure sign-in, AI context import, task categorization, daily command center dashboard

Inference The technical stack suggests a modern web application with authentication and data management capabilities.

The description states:

• This is an MVP built during a hackathon (OpenAI 2026)
• No revenue, customer or traction data is provided
• The product has a polished landing page explaining value, trust principles, and roadmap
• The team size is one person (Omkar Sanjay Pawar)

Inference There is no evidence of user adoption, revenue, or market traction beyond the prototype stage.

The description states:

• Most productivity tools force everything into one giant task list
• Polynus aims to be different by organizing context into distinct life modes
• It does not claim to scrape private conversation histories from AI platforms

Inference The competitive landscape includes general-purpose productivity tools, but Polynus positions itself as addressing a specific gap in mode-aware organization.

The description states:

• No evidence of revenue, customers or traction
• Only one team member (Omkar Sanjay Pawar)
• MVP uses demo or imported context, not real user data
• Privacy-respecting approach may limit functionality
• No pricing model or monetization strategy described

Inference Key risks include lack of market validation, limited team capacity, and unclear path to monetization.

1. What specific user problems are you solving that existing tools don't address?
2. How do you plan to acquire users beyond the hackathon community?
3. What is your timeline for moving from MVP to a paid product?
4. How will you ensure user privacy while building integrations with email/calendar services?
5. What metrics will indicate product-market fit?