Pochade — Visual Research Studio for Public-Domain Art

The description states that Pochade is a browser-based visual research studio for public-domain art. It operates as a local-first engine, meaning it runs entirely in the browser without backend dependencies.

Key features include:

• A working Agent Studio interface
• Support for uploading an image or selecting from a verified public-domain corpus (12 works from the Art Institute of Chicago)
• The ability to choose between Generate or Transform modes
• Rendering of three visual studies on screen
• Export of both a JPG and a Creative DNA JSON manifest
• No account, API key, or token cost required for basic use

The tool uses:

• React, TypeScript, Vite
• A deterministic browser Canvas engine
• Local image normalization
• Codex and GPT-5.6 during development (not part of the runtime)

Inference The product is a proof-of-concept prototype built for a hackathon, not yet validated in production or with real users.

The author states that Pochade aims to address creative block, which they describe as “looking like productivity” — collecting references and building moodboards without deciding what to change. The tool is positioned to give a designer or art student one defensible next move while keeping source material accountable.

Initial versions were gallery-first and form-heavy, but evolved into a simpler model:

• One working image
• One visual intention
• Three visible results
• One exportable decision

This pivot was driven by user feedback during Build Week, where the team found earlier versions felt difficult to use.

Inference The positioning reflects an attempt to simplify creative workflows, but there is no evidence of market validation or user adoption beyond the hackathon context.

The description states that Pochade targets designers and art students, who are described as being in a state of “creative block” — collecting references without making decisions.

It also mentions:

• Art students
• Designers
• Users who want to make a decision smaller, not larger

There is no evidence of segmentation beyond this broad category. No specific personas or use cases beyond the hackathon demo are described.

Inference The ICP is likely early-stage creative professionals, but there is no data on whether these users actually exist in sufficient numbers or have been engaged with the tool.

The description states that Pochade works without an account, API key, or token cost, and that it uses a local-first engine. There is no mention of any monetization strategy, pricing tiers, or paid features.

The product is described as:

• Browser-based
• No platform-funded inference or silent fallback
• Future upgrades include local-model and Cloud BYOK connectors

There is no evidence of revenue streams, subscriptions, or paid access beyond the MVP.

Inference The business model remains undefined. It appears to be a prototype with no clear path to monetization.

The tool is built using:

• React
• TypeScript
• Vite
• Canvas engine for deterministic rendering
• Local image normalization and processing
• Browser storage for state persistence

It supports:

• Upload of images
• Generate or Transform modes
• Before/After comparison
• Export of JPG + JSON manifest

The seed corpus includes 12 public-domain works from the Art Institute of Chicago, each verified through API checks.

Codex and GPT-5.6 were used during development to turn the thesis into an MVP and test the experience.

Inference The technical stack is functional for a prototype but lacks evidence of scalability or production-grade infrastructure.

The project was submitted to the OpenAI 2026 hackathon, indicating it is a demo-level product. There is no evidence of:

• Revenue
• Customers
• User adoption
• Product-market fit
• Real-world usage beyond the hackathon context

The team size is listed as 1 person, and the tool is described as an MVP.

Inference No traction or maturity signals are evident. The product is in a very early stage, likely post-hackathon but pre-commercial.

There is no mention of competitors in the description. The author does not reference existing tools for visual research or creative inspiration.

The tool’s positioning as a local-first, no-account, no-key solution may differentiate it from some AI-assisted design tools that require cloud-based access or API keys.

However, there is no evidence of:

• Market analysis
• Competitive landscape
• Prior art or similar products

Inference No competitive context is provided. The tool’s uniqueness is not validated against existing solutions.

• No revenue or monetization strategy: The product has no clear path to generating income.
• Single-person team: Limited capacity for scaling or iterating.
• Prototype-only status: No evidence of real-world usage, user feedback, or product-market fit.
• Unproven commercial viability: The tool is described as a hackathon demo with no traction or adoption metrics.
• No clear ICP validation: The target customer segment (designers/art students) is not confirmed to be large or engaged.
• Limited technical depth: The use of a deterministic canvas engine may limit scalability or advanced features.

Inference The product is at a very early stage with no commercial viability or traction evidence. Risks are high due to lack of validation and scalability.

1. What specific user feedback did you receive during Build Week that led to the pivot?
2. How do you plan to validate demand from your target customer segment (designers/art students)?
3. Are there any plans for monetization or revenue models beyond the MVP?
4. What are the technical limitations of the local-first engine, and how would you scale it?
5. Have you tested the tool with real users outside of the hackathon context?
6. How do you plan to expand the public-domain corpus beyond the 12 works from the Art Institute of Chicago?
7. What is your roadmap for moving from MVP to a product that could attract paying customers?