CreatorZone

The description states that CreatorZone is a creator-discovery app for Indian influencer workflows. It syncs data from Notion into a database and makes it searchable through a web UI.

• Frontend: Built with Next.js (App Router), TypeScript, Tailwind, TanStack Query, backed by Supabase Postgres.
• Backend: FastAPI with Celery for background jobs.
• Ingestion: Notion sync module that respects rate limits and maps Notion properties to schema.
• Search infrastructure: Meilisearch for keyword search; Qdrant wired in for semantic search (not yet implemented).
• Deployment: Local Docker Compose setup with mocked APIs for CI.

Evidence The author's own write-up describes the architecture and components. No evidence of actual product usage or customer adoption.

The description states that CreatorZone aims to turn influencer discovery from a manual grind into a searchable, data-backed workflow — starting in India's creator economy, built to scale.

• The app positions itself as an enhancement to existing Notion-based workflows.
• It claims to respect how teams already work (using Notion) while adding search capabilities.
• The author notes that most internal creator databases live in Notion but lack discovery features.

Evidence Self-reported claims about workflow and positioning. No evidence of market validation or competitive differentiation beyond the stated intent.

The description states that CreatorZone targets:

• Startup founders
• Small agencies
• Solo brand managers

These users are said to currently find creators by scrolling Instagram, screenshotting profiles into spreadsheets, and DM'ing people cold — indicating a pain point in manual discovery workflows.

Evidence Self-reported user personas. No evidence of actual customers or usage data.

The description does not provide any information about pricing models, monetization strategies, or business model details.

Evidence Not evidenced.

• Built with Next.js (App Router), TypeScript, Tailwind, TanStack Query
• Backend built with FastAPI and Celery
• Ingestion respects Notion API rate limits with retry logic
• Uses Meilisearch for keyword search; Qdrant for semantic search (not yet implemented)
• Designed to run on free-tier infrastructure (Supabase, Docker, mocked APIs)
• CI runs against mocked API responses
• PII is encrypted or stripped before reaching indexes

Evidence Author's own technical write-up. No evidence of production deployment or performance metrics.

The project was built for a hackathon and submitted to the OpenAI 2026 hackathon on Devpost.

• Team size: 4
• Built in a short timeframe (weekend)
• Uses free-tier infrastructure
• No evidence of revenue, customers, or user adoption

Evidence Self-reported project timeline and constraints. No traction data.

The description does not mention any competitors or competitive landscape.

Evidence Not evidenced.

• Product-Market Fit Uncertainty: The app is built as a hackathon prototype with no evidence of real adoption or user feedback.
• Scalability Concerns: Built on free-tier infrastructure, which may not support growth.
• Technical Debt Risk: The architecture was designed around constraints (e.g., rate limits) rather than scalability.
• Lack of Monetization Strategy: No mention of pricing or revenue model.
• Limited Scope: Semantic search is configured but not yet implemented; many features are described as "next steps."

Evidence Self-reported limitations and design decisions. No independent validation.

1. What specific problems do you observe in current influencer discovery workflows?
2. Have you validated your assumptions with actual users or potential customers?
3. How do you plan to monetize this product?
4. What is the timeline for implementing semantic search and other next steps?
5. Are there any existing partnerships or integrations with Notion or Instagram that could help accelerate adoption?
6. How will you handle data privacy and compliance as you scale?