MerchantCore AI

The description states that MerchantCore AI is:

• An agentic operations SaaS platform for ecommerce merchants
• A platform with a searchable catalog of ready-to-run AI agents
• A personal workspace where teams can configure and launch controlled missions
• Built around a "mission" concept that includes preview, test, and production modes
• Designed to work with PrestaShop through a legacy webservice adapter
• Capable of producing PDF reports and CSV exports from agent operations

The platform is described as having three initial AI agents: Catalog Quality, Category Structure, and Product Image. It includes features like mission monitoring, detailed results and logs, immutable execution history, and customer-specific agent publication.

The description states that the company's guiding principle was "simple and sober on the surface, extremely powerful underneath." It positions itself as:

• An operating layer around commerce automation rather than another isolated utility
• A platform that allows merchants to find capabilities, configure missions, preview them, and understand results without needing developer knowledge
• A system that keeps important boundaries visible through explicit Preview, Test, and Production modes

The positioning appears to have evolved from a hackathon prototype to a vision of an open-ended catalog of commerce workflows that can grow beyond the initial three agents.

The description states:

• The target customer is "commerce merchants"
• The platform works with PrestaShop stores
• It's designed for teams that handle operational work like finding inconsistent product identifiers, repairing category structures, improving images, maintaining translations, and monitoring changes across live stores
• The platform includes features like multilingual support (TEN/CEN/country-locale architecture) suggesting it targets international merchants

The description does not provide evidence of specific customer segments beyond "commerce merchants" or detailed ICP criteria.

Not evidenced. The description contains no information about pricing, revenue models, or commercial arrangements beyond the fact that it's a SaaS platform.

The description states:

• Built with React, TypeScript, Django, Celery, RabbitMQ, Playwright, OpenAI Codex
• Uses a "persistent Django Job" to own mission lifecycle while Celery workers execute
• Has a connector boundary isolating commerce-platform communication from agent logic
• Implements a "core runtime rule" where browser creates mission once and becomes observer
• Includes features like immutable execution history, audit records, and durable application state
• Uses a "shared source of truth" for summaries, counters, findings, reports, exports, and archived history
• Has a multilingual architecture with Technical English, Custom English, and country-specific locales

Not evidenced. The description contains no information about:

• Customer adoption or retention
• Revenue generation
• User engagement metrics
• Product usage data
• Market traction beyond the hackathon submission

The project is described as a "working catalog" with three agents, but there's no evidence of commercial deployment or user base.

Not evidenced. The description does not mention competitors, market positioning relative to existing solutions, or competitive advantages.

• Solo developer team: Only one team member (Janos Kozma) is mentioned, which raises questions about scalability and operational capacity
• Hackathon prototype: The project was submitted to a hackathon, suggesting it's an early-stage demonstration rather than a mature product
• No commercial evidence: No revenue, customers, or traction data provided beyond the self-reported description
• Limited connector support: Currently only supports PrestaShop with plans for Shopify and other platforms
• Unverified claims: All statements are self-reported without independent verification

1. What is the actual commercial traction beyond the hackathon submission?
2. How does the platform handle data security and privacy compliance?
3. What is the timeline for expanding to additional commerce platforms beyond PrestaShop?
4. How do you plan to monetize this platform given it's currently a prototype?
5. What are the specific technical challenges that remain before production deployment?
6. How will you scale from a solo developer to a sustainable business model?