Igotchu - ease you through your day

The company appears to be a solo-project, self-reported, unverified product built by one individual (Bizarro delbuort) for personal use during a hackathon. It is described as an AI-powered assistant that integrates Gmail and Google Calendar into a spoken conversation format, aiming to ease users through their day rather than overwhelm them with inboxes.

What changed: The author states they are building this tool while contracting at a pharma company and managing a family. They describe a shift from trying productivity tools that add more inboxes to creating one that uses conversation as the interface.

The single most important open question: Is there any evidence of actual user adoption, revenue, or traction beyond the author's own use case?

Note: This analysis is based entirely on the self-reported, unverified description provided by the author. No external verification or historical data exists for this project.

• The description states that Igotchu is not another inbox.
• It turns mail and Calendar into a spoken conversation.
• It briefs users in the morning using real Gmail and Google Calendar data.
• It drafts replies into Gmail Drafts folder, never sending without approval.
• Meetings can be booked after confirmation.
• It supports "Jog mode" for hands-free voice interaction during activities like running or making coffee.

Inference: The product appears to be an AI agent that uses APIs from Gmail and Google Calendar to create a conversational interface. However, the exact technical architecture is not detailed beyond what was declared in the tags (e.g., codex, GPT-5.6, javascript, node.js).

• The author claims Igotchu “eases you through your day” and avoids traditional inbox mechanics.
• It positions itself as an alternative to existing productivity tools that merely manage email.
• The product is described as solving the problem of morning dread caused by triple-bookings, missed compliance trainings, and deadlines.
• It evolved from a simple idea into a more structured approach involving AGENTS.md, golden paths, and non-negotiable principles.

Claim: The author states that Igotchu was built to solve their own personal productivity issues. This is a self-reported claim about intent and positioning, not proof of traction or adoption.

• Not evidenced.
• The description does not name specific customer segments or personas.
• It implies a general user base with busy schedules, but no clear definition of who that includes.

Absence of evidence: No explicit identification of target customers or ideal customer profile (ICP) is provided.

• Not evidenced.
• There is no mention of pricing models, monetization strategies, or business model assumptions.
• The author mentions “work accounts” and potential enterprise approval but does not elaborate on how this might be monetized.

Absence of evidence: No indication of how the product would generate revenue or whether it has a defined business model.

• Built with Codex, GPT-5.6, Gmail API, Google Calendar API, OpenAI Realtime API, OAuth2, JavaScript, Node.js.
• The author describes using an AGENTS.md file to define goals and principles for the AI agent.
• The system includes automated tests (26), API read-back verification, and audit trails via git commits.
• It supports deep-linking into Gmail and restricts GPT output to presentation fields.

Inference: The technical stack suggests a modern AI-powered integration tool built using LLMs and APIs. However, no evidence of scalability or production deployment is provided.

• Not evidenced.
• No mention of users, customers, or usage metrics.
• The project was submitted to a hackathon (OpenAI 2026), suggesting early-stage development.
• The author describes the tool as being in a “warm dawn” redesign phase.

Absence of evidence: No data on traction, adoption, or maturity beyond the initial prototype and personal use case.

• Not evidenced.
• No mention of competitors or competitive landscape.
• The author does not reference similar products or services in the market.

Absence of evidence: No information about existing alternatives or competitive positioning is available.

• The project is described as a solo effort by one person (Bizarro delbuort).
• It was built during a hackathon, indicating early-stage development.
• The author admits to being “not a developer” and relies heavily on AI tools like Codex.
• There are no external validations or third-party integrations beyond Google APIs.
• The product uses GPT-5.6, which may not be publicly available or stable.

Inference: Risk of limited scalability, lack of robustness, and dependency on a single individual for continued development.

1. What is the actual user base beyond yourself?
2. How do you plan to scale beyond a single developer’s involvement?
3. Are there any plans for monetization or revenue generation?
4. What are the key assumptions behind the product vision, and how have they been validated?
5. Have you considered potential security or privacy risks in handling sensitive data like emails and calendars?
6. How do you intend to handle API limitations or changes from Google?