forMika

What the company appears to be: forMika is a self-reported project that claims to turn group chats into shared planning tools for events, focusing on guests, food, dietary needs and costs. It uses AI (specifically OpenAI APIs) to suggest next best actions.

What changed: This is a hackathon submission with no evidence of prior development or traction. The project was submitted to the OpenAI 2026 hackathon, indicating it's in early-stage experimentation or prototype form.

Single most important open question: Is there any evidence of user adoption, revenue, or customer feedback beyond the self-reported tagline and technology stack?

The description states that forMika is a project built for the OpenAI 2026 hackathon. It is not evidenced to have any commercial traction, customers, or revenue. The team size is stated as two people (Lorenzo Castiglione, Irene Fiesoli). No evidence of funding, partnerships, or product-market fit exists in the provided description.

The description states that forMika turns scattered group chats into one shared plan for guests, food, dietary needs and costs. It uses AI to suggest the next best action. The author also states that it was built with a specific tech stack including Next.js, React, Supabase, OpenAI APIs, and others.

Evidence:

• Tagline: "forMika turns scattered group chats into one shared plan for guests, food, dietary needs and costs with Mika suggesting the next best action."
• Technology stack includes: codex, css, eslint, geoapify, github, gpt-5.6, lucide-react, next.js, node.js, openai-api, openai-responses-api, openai-sdk, pnpm, postgresql, react, row-level-security, supabase, supabase-auth, tailwind, typescript, vercel, vitest, zod

Inference: The product appears to be an event planning tool that integrates AI for decision-making in group settings. However, no functional demonstration or user interface is described.

The description states that forMika aims to reduce the burden of organizing events by centralizing planning and suggesting actions based on input from group members.

Evidence:

• Tagline: "forMika turns scattered group chats into one shared plan for guests, food, dietary needs and costs with Mika suggesting the next best action."

Inference: The positioning is to simplify event coordination through AI assistance. There's no evidence of prior positioning or evolution in claims beyond this single statement.

The description does not state specific target customers or ideal customer profiles (ICP). It implies a general use case for group planning but lacks specificity.

Evidence:

• Tagline: "forMika turns scattered group chats into one shared plan for guests, food, dietary needs and costs"

Inference: The product seems aimed at groups organizing events, such as families, friends, or colleagues. No evidence of segmentation or targeting beyond this general idea.

There is no evidence in the description regarding business model or pricing structures.

Evidence:

• No mention of monetization, subscriptions, or pricing

Inference: The product appears to be a prototype or hackathon submission with no commercial model described. It's not evidenced to have any revenue streams.

The project is built using modern web technologies including Next.js, React, Supabase, and OpenAI APIs. It was submitted to the OpenAI 2026 hackathon.

Evidence:

• Built with: codex, css, eslint, geoapify, github, gpt-5.6, lucide-react, next.js, node.js, openai-api, openai-responses-api, openai-sdk, pnpm, postgresql, react, row-level-security, supabase, supabase-auth, tailwind, typescript, vercel, vitest, zod
• Submitted to OpenAI 2026 hackathon

Inference: The technical stack suggests a modern full-stack web application with AI integration. However, there is no evidence of production deployment or delivery mechanisms beyond the hackathon submission.

There is no evidence of traction, adoption, or maturity. It was submitted to a hackathon and has no stated users, customers, or revenue.

Evidence:

• Submitted to OpenAI 2026 hackathon
• No mention of users, customers, or revenue

Inference: The project appears to be in early development stage with no demonstrated traction or market validation.

The description does not provide information about competitors or competitive positioning.

Evidence:

• No mention of competitors or market analysis

Inference: Without any evidence of market research or competitor comparison, it's impossible to assess the competitive landscape. The product may be in a crowded space such as group planning tools or AI-assisted collaboration platforms.

Key risks include lack of traction, unclear business model, and limited team size for execution. No evidence of user feedback or market validation exists.

Evidence:

• Team size: 2
• Submitted to hackathon
• No revenue, customers, or adoption

Inference: The small team size may limit execution capability. The lack of commercial traction raises questions about product-market fit and scalability.

1. What specific problems are you solving in event planning?
2. How do you plan to monetize this tool?
3. Have you tested it with real users or groups?
4. What is your go-to-market strategy?
5. How does this differ from existing solutions?