MVP Documentation

I'm building an MVP and need help documenting my product vision and strategy. 

**IMPORTANT**: Before we start, please:

1. **Check the README.md file** in this codebase to understand my current tech stack

2. **Perform real-time web research** on current pricing, features, and capabilities of my tech stack components

3. **Read the existing Project Documentation → Idea page** (content/docs/product-docs/idea.mdx) to understand what's already documented

4. **Note**: I should have already completed the Target Market & ICP deep dive from the [Idea Validation guide](/docs/company-building/idea-validation). This documentation will expand and formalize that analysis.

**My Product Idea**: [Describe your product idea in 2-3 sentences]

**Current Understanding**: [What you know about your target market, competitors, etc.]

Please help me create documentation for the "Idea" page in my Project Documentation. I want to document:

1. **Problem Statement** - What problem am I solving?

2. **Solution Overview** - How does my product solve it?

3. **Target Audience & ICP Deep Dive** - Deeply identify and understand your target market:

   - **Demographics** - Age, location, occupation, income level, education

   - **Psychographics** - Behaviors, motivations, pain points, goals, fears

   - **Behavioral Patterns** - How they currently solve this problem, what tools they use, daily routines

   - **Pain Intensity** - How urgent is this problem? How much time/money does it cost them?

   - **Willingness to Pay** - Have they paid for similar solutions? What's their budget?

   - **Platform Identification** - Where do your target users spend most of their time online? (LinkedIn, X/Twitter, Instagram, TikTok, Reddit, Discord/Slack, Facebook Groups, YouTube, industry-specific forums, etc.)

   - **Distribution Strategy** - Based on platform identification, how will you reach your first 10-100 users? What's your clear plan for finding and engaging with them?

   - **Validation Evidence** - Have you spoken to potential customers? Did someone say "I will pay for this" or show clear payment intent? Document your validation conversations and commitments.

   - **Competitor Analysis** (if cloning an existing app) - Analyze competitor ad strategies, distribution channels, content strategies, and community presence using tools like Rival Sonar (https://www.rival-sonar.com/blog/exploit-gaps-in-competitor-ad-strategy)

4. **B2C vs B2B Classification** - Determine if this should be a B2C (Business-to-Consumer) or B2B (Business-to-Business) app:

   - Analyze the target audience, use case, and product characteristics

   - Consider factors like: individual vs team usage, pricing models, sales cycles, support requirements

   - Recommend the appropriate model and justify the decision

   - **Stack Requirements**: If B2B, identify what needs to be enabled/configured in the current stack:

     - Organization/team management features

     - Multi-tenant architecture considerations

     - Admin/dashboard capabilities for team management

     - SSO (Single Sign-On) or enterprise authentication options

     - Billing/subscription management for teams vs individuals

     - Any additional Convex schema, BetterAuth configurations, or Polar.sh features needed

   - **Cost Implications**: Research and document:

     - Additional costs for B2B features (e.g., SSO pricing in BetterAuth, team management costs)

     - Scaling costs as teams/organizations grow

     - Any premium tier requirements for B2B functionality

     - Comparison of B2C vs B2B pricing tiers for all relevant services

5. **Core Features** - What features do I need for MVP?

6. **Competitive Analysis** - How am I different?

7. **Expected Scale** - How many users do I expect to have?

8. **3rd-party libraries/providers/APIs** - What external libraries/providers/APIs do I need to use (other than what my current tech stack provides)?

9. **Pricing Model Decision** - Subscription vs One-time vs Hybrid (justify with web research and product type)

10. **Implementation Planning** - Development phases, timeline estimation, resource requirements, risk assessment, success metrics, launch strategy

Use this decision framework when selecting the pricing model:

- Recurring Subscriptions

  - Use when you provide ongoing value

  - Examples: SaaS tools used regularly, monitoring services, continuous access platforms

  - Benefits: Predictable revenue, higher LTV, easier to scale

- One-Time Payments

  - Use when value is delivered once

  - Examples: Digital downloads, one-off transformations, limited-time access

  - Benefits: Simpler to manage, no recurring obligations, clear value proposition

- Hybrid Models

  - Combine both payment types

  - Examples: Setup fee + monthly access, one-time purchase + optional subscription support

  - Benefits: Maximizes revenue opportunities, caters to preferences, flexible strategy

- Product Type Considerations

  - Transformation Products → bias to one-time (e.g., fitness apps, course platforms)

  - Utility Products → bias to subscription (e.g., budget trackers, productivity tools)

- Currency & Pricing Psychology

  - Align currencies with target demographics

  - Use psychological pricing (e.g., $29 vs $30)

**Output**: A clear recommendation with rationale and sources. Also note downstream impacts on database schema, pricing page UX, and payments provider configuration.

Make sure to include the following sections in Project Documentation → Idea (content/docs/product-docs/idea.mdx):

**Target Audience & ICP Deep Dive**

- Demographics: [Detailed breakdown]

- Psychographics: [Behaviors, motivations, pain points]

- Behavioral Patterns: [How they currently solve the problem]

- Pain Intensity: [Urgency and cost of the problem]

- Willingness to Pay: [Payment history and budget]

- Platform Identification: [Where they spend time online - specific platforms]

- Distribution Strategy: [How to reach first 10-100 users on identified platforms]

- Validation Evidence: [Customer conversations and payment commitments]

- Competitor Analysis: [If cloning, competitor ad/distribution/content analysis]

**B2C vs B2B Classification**

- Classification: [B2C | B2B | Hybrid]

- Rationale: [2-4 bullets explaining why this classification fits the product]

- Stack Requirements: [What needs to be enabled/configured in the current stack, if B2B]

- Cost Implications: [Additional costs, premium tiers, scaling costs for B2B features]

- Schema Impact: [Notes on how this affects database design - organizations/teams tables, user-organization relationships, etc.]

**Pricing Model Decision**

- Decision: [Subscription | One-time | Hybrid]

- Rationale: [2-4 bullets citing product type and web research]

- Product Type: [Transformation | Utility | Mixed]

- Currency & Pricing: [Primary currency and psychological price points]

- Database Impact: [Keep/remove: subscriptions tables, one-time payments tables, and invoice fields?]

- Provider/Webhooks: [Which flows are needed and why]

These sections must be present in content/docs/product-docs/idea.mdx so downstream docs (architecture, database, payments) can reference them.

**CRITICAL**: When we're done, I need you to **replace the entire content** of the Project Documentation → Idea page (content/docs/product-docs/idea.mdx) with our final documentation, not just provide text to copy.

Before you do that, please ask me clarifying questions and help me think through each area thoroughly. Use real-time web research to ensure accuracy of current market conditions, competitor pricing, and tech stack capabilities.

I'm building this product idea. Please review it as if you're Alex Hormozi and provide:

1. **Gap Analysis** - What's missing from this idea? What questions haven't been answered?

2. **Marketing Strategy** - Based on this specific product and target audience, what marketing strategies would work best?

3. **Offer Refinement** - How can I make the offer more compelling?

4. **Positioning** - How should this product be positioned in the market?

5. **Go-to-Market** - What's the best way to launch and scale this?

Ask me clarifying questions and help me think through my specific product/company thoroughly.

Be specific and actionable with your advice. Reference frameworks from your books and playbooks where relevant, and explain why they're relevant to my specific product/company.

Based on my product idea (See the 'Idea' page in my Project Documentation - content/docs/product-docs/idea.mdx) and Hormozi's feedback from NotebookLM, I need help documenting a marketing strategy.

**IMPORTANT**: Before we start, please:

1. **Check the README.md file** in this codebase to understand my current tech stack

2. **Read the existing Project Documentation → Idea page** (content/docs/product-docs/idea.mdx) to understand the product vision, target audience, pricing model, and B2C/B2B classification

3. **I'll paste Hormozi's NotebookLM response below** - use it as expert guidance for marketing strategies

**Hormozi's NotebookLM Response**:

[Paste the full response from NotebookLM here]

Please help me create marketing strategy documentation. I want to document:

1. **Positioning Strategy** - How to position this product in the market based on Hormozi's feedback

2. **Target Audience Refinement** - Any adjustments to target audience based on gaps identified

3. **Marketing Channels** - Which channels would work best for this specific product (content marketing, paid ads, partnerships, etc.)

4. **Content Strategy** - What content should be created and where it should be distributed

5. **Go-to-Market Plan** - Step-by-step launch strategy

6. **Offer Refinement** - How to make the offer more compelling based on Hormozi's recommendations

7. **Pricing Strategy** - Refine pricing based on positioning and offer improvements

8. **Conversion Funnel** - How to move prospects through awareness → interest → decision → action

9. **Marketing Metrics** - What KPIs to track for marketing success

10. **Scaling Strategy** - How to scale marketing efforts as the product grows

**CRITICAL**: When we're done, I need you to **create a new file** at `content/docs/product-docs/marketing-strategy.mdx` with our final marketing strategy documentation, not just provide text to copy.

Based on my product idea and vision (See the 'Idea' page in my Project Documentation - content/docs/product-docs/idea.mdx), I now need help designing and documenting the technical architecture.

**IMPORTANT**: Before we start, please:

1. **Check the README.md file** in this codebase to understand my current tech stack

2. **Read the existing Project Documentation → Idea page** (content/docs/product-docs/idea.mdx) to understand the product vision and pricing model decision

3. **Perform real-time web research** on current pricing, features, and capabilities of my tech stack components

4. **Research current best practices** for my specific tech stack combination

Please help me design a technical architecture, using mermaid diagrams. I want to document:

1. **System Overview** - High-level architecture diagram

2. **Tech Stack Decisions** - Frontend, backend, database, etc. (based on my current stack - see this codebase's README.md file for more details)

3. **Tech Stack Specific Features (see this codebase's README.md file for more details)** - Serverless functions, cron jobs, real-time features, etc.

4. **Payments Architecture** - Based on the chosen pricing model (subscription vs one-time vs hybrid), outline provider flows, webhooks, and data sync responsibilities

   - **Free Trials**: Ask the developer if they need free trials for their product (Polar.sh supports trial periods if needed)

5. **Data Flow** - How data moves through the system

6. **API Design** - Key endpoints and data structures

7. **Security Considerations** - Authentication, authorization, data protection

8. **Performance & Scalability** - How to handle growth

9. **Infrastructure** - Hosting, deployment, monitoring

**CRITICAL**: When we're done, I need you to **replace the entire content** of the Project Documentation → Architecture page (content/docs/product-docs/architecture.mdx) with our final documentation, not just provide text to copy.

Before you do that, please ask me clarifying questions and help me think through each area thoroughly. Use real-time web research to ensure accuracy of current tech stack capabilities, security considerations, and performance & scalability best practices.

Use real-time web research (if you need to) to ensure accuracy of current tech stack capabilities, pricing models, and architectural best practices. Ask clarifying questions about my technical requirements and constraints.

Based on my product idea and technical architecture (See the 'Idea' and 'Architecture' pages in my Project Documentation), I now need help calculating operational costs and revenue projections.

**IMPORTANT**: Before we start, please:

1. **Check the README.md file** in this codebase to understand my current tech stack

2. **Read the existing Project Documentation → Idea page** (content/docs/product-docs/idea.mdx) to understand the product vision, pricing model, and expected scale

3. **Read the existing Project Documentation → Architecture page** (content/docs/product-docs/architecture.mdx) to understand the technical stack and infrastructure choices

5. **Perform real-time web research** on current pricing for ALL components of my tech stack

Please help me create cost estimation documentation. I want to document:

1. **Tech Stack Operational Costs** - Monthly costs for hosting, databases, APIs, third-party services

2. **Revenue Projections** - Based on pricing model and expected user growth

3. **Profit Margins** - At different user scales:

   - 10 monthly active users

   - 100 monthly active users  

   - 1,000 monthly active users

   - 10,000 monthly active users

4. **Break-even Analysis** - When the product becomes profitable

5. **Scaling Costs** - How costs increase with user growth

6. **Cost Optimization Strategies** - Ways to reduce operational costs

**My Product**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for the product description

**Tech Stack**: See the existing Project Documentation → Architecture page (content/docs/product-docs/architecture.mdx) for tech stack details

**Pricing Model**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for pricing model decision

**CRITICAL**: When we're done, I need you to **replace the entire content** of the Project Documentation → Cost Estimation page (content/docs/product-docs/cost-estimation.mdx) with our final documentation, not just provide text to copy.

Before you do that, please ask me clarifying questions and help me think through each area thoroughly. Use real-time web research to ensure accuracy of current pricing for all tech stack components, hosting costs, third-party service fees, and market rates.

I've defined my product vision and architecture. Now I need help designing the database schema and data models.

**IMPORTANT**: Before we start, please:

1. **Check the README.md file** in this codebase to understand my current tech stack

2. **Read the existing Project Documentation → Idea page** (content/docs/product-docs/idea.mdx) to understand the product vision, core features, B2C/B2B classification, and pricing model decision

3. **Read the existing Project Documentation → Architecture page** (content/docs/product-docs/architecture.mdx) to understand the technical context and database choice

4. **Read the existing Project Documentation → User Flows page** (content/docs/product-docs/user-flows.mdx) to understand user interactions and data requirements

6. **Perform real-time web research** on current pricing, features, and capabilities of my database technology

7. **Research current best practices** for my specific database technology

**My Product**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for the product description

**B2C/B2B Classification**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for B2C vs B2B classification and schema impact notes

**Core Features**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for core features list

**User Flows**: See the existing Project Documentation → User Flows page (content/docs/product-docs/user-flows.mdx) for user interactions

**Tech Stack**: See the existing Project Documentation → Architecture page (content/docs/product-docs/architecture.mdx) for database choice

Please help me create database documentation. I want to document:

1. **Data Models** - Core entities and their properties

2. **Relationships** - How entities connect to each other

3. **Schema Design** - Tables, fields, types, constraints

4. **B2C/B2B Schema Considerations** - Based on the B2C/B2B classification from the Idea page:

   - If B2B: Include organization/team tables, user-organization relationships, role-based access control structures

   - If B2C: Focus on individual user data models and personal account structures

   - If Hybrid: Design flexible schema that supports both individual and team usage

   - Reference the "Schema Impact" notes from the B2C/B2B Classification section

5. **Data Flow** - How data is created, updated, deleted

6. **Indexing Strategy** - Performance optimization

7. **Data Validation** - Input validation and business rules

8. **Migration Strategy** - How to evolve the schema over time

9. **Backup & Recovery** - Data protection strategies

10. **Payments Schema Plan** - Reflect the chosen pricing model:

   - If one-time only → remove subscription tables and `subscription_id` from invoices

   - If subscription only → remove one-time payment tables and fields

   - If hybrid → keep both sets and define clear relations and invariants

   - **Free Trials**: Ask the developer if they need free trials (Polar.sh helps with this if needed)

**CRITICAL**: When we're done, I need you to **replace the entire content** of the Project Documentation → Database Design page (content/docs/product-docs/database-design.mdx) with our final documentation, not just provide text to copy.

Use real-time web research to ensure accuracy of current database capabilities, pricing models, and performance best practices. Ask clarifying questions about data requirements, relationships, and performance needs.

Before you do that, please ask me clarifying questions and help me think through what data models, relationships, and schema are needed for my product.

I've defined my product vision and technical architecture. Now I need help designing the user experience and interaction flows.

**IMPORTANT**: Before we start, please:

1. **Check the README.md file** in this codebase to understand my current tech stack

2. **Read the existing Project Documentation → Idea page** (content/docs/product-docs/idea.mdx) to understand the product vision, target audience, and core features

3. **Read the existing Project Documentation → Architecture page** (content/docs/product-docs/architecture.mdx) to understand the technical context and payments architecture

5. **Research current UX best practices** for my specific tech stack and industry

6. **Research intuitive UI components** that would be perfect for my specific product type and use case

7. **Study dashboard design patterns** for similar products in my industry

**My Product**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for the product description

**Target Users**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for target audience details

**Core Features**: See the existing Project Documentation → Idea page (content/docs/product-docs/idea.mdx) for core features list

**Technical Stack**: See the existing Project Documentation → Architecture page (content/docs/product-docs/architecture.mdx) for technical stack details

Please help me create user flow documentation. I want to document:

1. **Primary User Flows** - Main user journeys (onboarding, core feature usage)

2. **Secondary Flows** - Supporting interactions (settings, notifications, etc.)

3. **Error & Edge Cases** - What happens when things go wrong

4. **Mobile vs Desktop** - Responsive behavior differences

5. **Conversion Funnel** - Where users might drop off

6. **User Personas & Flows** - Different user types and their paths

7. **Accessibility Considerations** - Ensuring inclusive design

8. **Intuitive UI Components** - Specific components that would make the app feel super intuitive

9. **Dashboard Design** - Core logic pages and dashboard layout for maximum usability

10. **Wireframes** - Visual mockups of key screens and user flows

11. **Onboarding Flow** - Whether onboarding is needed and how to make it seamless and intuitive

**SPECIFIC REQUIREMENTS**:

- **Research and recommend** specific UI components (tables, charts, forms, navigation, etc.) that would be perfect for my product type

- **Design wireframes** using ASCII art or text-based layouts for key screens

- **Focus on dashboard design** - how should the main dashboard be organized for maximum intuitiveness?

- **Component recommendations** - what specific components would make my core features feel natural and easy to use?

- **Interaction patterns** - what interaction patterns work best for my type of product?

- **Onboarding assessment** - determine if onboarding is needed based on product complexity and user familiarity

- **Onboarding flow design** - if needed, design a seamless onboarding experience that guides users to their first success

- **Onboarding optimizations** - suggest specific optimizations and strategies for onboarding that best suit this product idea to really lower friction. Consider:

  - Progressive disclosure (what to show vs. hide initially)

  - Default states and smart defaults

  - Quick wins and time-to-value

  - Guided tours vs. contextual help

  - Social proof and examples

  - Skip options for experienced users

  - Mobile-first vs. desktop-first onboarding patterns

  - Product-specific friction points and how to eliminate them

**CRITICAL**: When we're done, I need you to **replace the entire content** of the Project Documentation → User Flows page (content/docs/product-docs/user-flows.mdx) with our final documentation, not just provide text to copy.

Create Mermaid diagrams for key flows, wireframes for important screens, and ask clarifying questions about user behavior patterns. Use real-time web research to find the most intuitive components and design patterns for my specific product type.

Before you do that, please ask me clarifying questions and help me think through each area thoroughly. Use real-time web research to ensure accuracy of current UX best practices, product type, and user behavior patterns.