Make It Pop

What the company appears to be: Make It Pop is a self-reported tool for designers to manage feedback, revisions, and approvals from clients in a structured way. The author states it focuses on the design review process rather than replacing tools like Figma or Google Drive.

What changed: This is a solo developer project submitted to an AI hackathon. No prior version or commercial history is evidenced.

Single most important open question: Is there evidence of real-world usage, customer feedback, or traction from freelance designers who would use this tool?

The description is self-reported and unverified. It does not contain any evidence of revenue, customers, adoption, or market validation beyond the author's own account. The project appears to be a proof-of-concept built in a short timeframe with no external validation.

The description states that Make It Pop:

• Gives designers one place to share work, collect feedback, manage revisions, and receive final decisions
• Allows designers to create projects, upload previews, and send private review links to clients
• Enables clients to comment, request changes, or approve designs without creating an account
• Saves each new upload as a separate version to avoid mixing old and new feedback
• Uses AI to summarize long feedback threads into revision checklists
• Is not meant to replace Figma, Google Drive, or local design files
• Focuses specifically on the feedback, revisions, and decisions around those files

The author describes it as an application built with FastAPI (backend), SQLAlchemy (database), Jinja templates (frontend), HTMX, Alpine.js, Tailwind CSS, and OpenAI APIs.

The description states:

• The tool is positioned specifically for the designer-client review process
• It was inspired by the author's own experience working remotely as a graphic designer
• The name "Make It Pop" came from the common phrase used in design feedback
• It is not trying to be a general project management tool but a focused solution for design reviews

The claim evolution appears to be:

1. Problem: Scattered design feedback across multiple platforms
2. Solution: Centralized review process with version control and AI summarization
3. Positioning: Focused tool for designers, not replacement for existing tools

The description states:

• The primary users are graphic designers working remotely
• Clients who review designs (without needing accounts)
• Freelance designers specifically mentioned as the target audience for beta testing
• The tool is designed for the designer-client review workflow

No specific customer segments, personas or market size data are provided.

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

The description states:

• Built with FastAPI (backend), SQLAlchemy (database), Alembic (migrations)
• Frontend: Jinja templates, HTMX, Alpine.js, Tailwind CSS
• Uses OpenAI APIs for AI features
• Containerized with Docker and deployed on Railway
• Authentication using JWT, bcrypt, Passlib
• Database: SQLite
• AI features include summarization and revision checklist generation
• Includes output limits, timeouts, retries, rate limits, fallback behavior
• Handles network failures, repeated submissions, duplicate comments via idempotency keys and database constraints

Not evidenced. The description contains no information about:

• Revenue or monetization
• Customers or user base
• Adoption metrics
• Product usage data
• Market traction
• Any form of customer feedback beyond the author's own experience

The description states:

• It is not trying to replace Figma, Google Drive, Dropbox, or local design files
• The focus is on feedback, revisions, and decisions around those files
• No specific competitors are named

No competitive analysis or positioning against existing tools is provided.

Inferences based on the description:

1. Single-person development: Only one team member (the author) is mentioned, which raises questions about scalability and long-term maintenance
2. No commercial traction: No evidence of revenue, customers, or market adoption
3. Limited validation: The project appears to be a hackathon submission with no external validation or user testing beyond the author's own experience
4. AI dependency: Reliance on OpenAI APIs for core features may create operational risks and cost concerns
5. Unproven market fit: No evidence that freelance designers actually struggle with the described problems or would pay for this solution

1. What specific pain points do freelance designers experience in their current review workflows?
2. Have you conducted any user interviews or surveys with actual designers?
3. How many freelance designers have you shown this to, and what was their feedback?
4. What is your plan for customer acquisition and retention?
5. How do you intend to monetize this tool?
6. What are the technical limitations of the current implementation that would prevent scaling?
7. Have you considered how to handle multiple reviewers or stakeholders in a single project?
8. What metrics would indicate success for this product?