memwiki

Project: memwiki

Self-reported basis: Author's own description, submitted to the OpenAI 2026 hackathon on Devpost. No independent verification.

Commercial due-diligence read: The project is a self-described AI-powered second brain for mobile, built by one person (Vansh Khosla), inspired by LLM-wiki by Karpathy. It targets non-technical users who primarily use smartphones. There is no evidence of product-market fit, revenue, customers or traction. The description contains no commercial data, pricing, or business model details. The author states the project is not yet viable and has not achieved PMF. This is a very early-stage idea with no demonstrated commercial viability.

The description states that memwiki is “an AI based second brain for mobile with easy UI.” It is intended for “non-technical users who are not really active on laptop but use smart phone as the primary source of information.”

• Inferred: The product appears to be a mobile application.
• Not evidenced: No details about functionality, features, or how it works beyond being AI-powered and mobile-first.

The author states that memwiki is inspired by “LLM-wiki by Karpathy.” This suggests an intent to build a knowledge management or personal wiki tool using large language models.

• Inferred: The positioning is to offer a simplified, AI-driven personal knowledge base for mobile users.
• Not evidenced: No claims about competitive differentiation, market positioning, or user value proposition beyond the inspiration from Karpathy’s work.

The description states that memwiki targets “non-technical users who are not really active on laptop but use smart phone as the primary source of information.”

• Inferred: The target is mobile-first, non-technical individuals.
• Not evidenced: No segmentation or customer persona details, no evidence of user research or validation.

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

• Not evidenced: No commercial data, pricing structure, or revenue model described.

The project was built using: codex, expo.io, openaisdk, python, react-native, typescript.

• Evidenced: The tech stack is self-reported and includes mobile development tools and AI SDKs.
• Inferred: It is a mobile application built with React Native and integrated with OpenAI’s SDK.
• Not evidenced: No information on architecture, scalability, or delivery timeline beyond the author’s statement that it may be launched in less than two weeks.

The author states:

• “I haven’t achieved PMF (product market fit) and it’s PMF or die.”
• “If the product doesn't make it then there is no purpose of thinking about the challenges.”
• “In the future after fixing some design and system design inaccuracies will try to launch it in less than two weeks.”
• Not evidenced: No evidence of user adoption, customer feedback, or traction.
• Inferred: The project is at a very early stage, possibly pre-product-market fit.

The author references “LLM-wiki by Karpathy” as inspiration.

• Inferred: The space may include AI-powered knowledge tools or wikis.
• Not evidenced: No mention of competitors, market size, or competitive landscape.

• No product-market fit achieved — the author explicitly states this.
• Single founder — only one person is involved in building the project.
• No revenue or traction — no evidence of customers, usage, or monetization.
• Unverified claims — all statements are self-reported and unverified.
• Unclear delivery timeline — the author says it may be launched in less than two weeks but has not yet achieved PMF.

1. What specific problem does memwiki solve for users, and how did you validate that?
2. How do you plan to achieve product-market fit if you haven’t yet?
3. What is your go-to-market strategy for reaching non-technical mobile users?
4. Are there any existing tools in this space, and how does memwiki differ from them?
5. What are the key technical challenges you've faced, and how do you plan to overcome them?
6. How do you intend to monetize or generate revenue from this product?