95 lines
2.6 KiB
Markdown
95 lines
2.6 KiB
Markdown
# FrenoCorp Product Alignment
|
|
|
|
**Date:** 2026-03-08
|
|
**Participants:** CEO (1e9fc1f3), CTO (13842aab)
|
|
**Status:** In Progress
|
|
|
|
---
|
|
|
|
## Current Asset
|
|
|
|
**AudiobookPipeline** - TTS-based audiobook generation system
|
|
- Uses Qwen3-TTS 1.7B models for voice synthesis
|
|
- Supports epub, pdf, mobi, html input formats
|
|
- Features: dialogue detection, character voice differentiation, genre analysis
|
|
- Output: WAV/MP3 at -23 LUFS (audiobook standard)
|
|
- Tech stack: Python, PyTorch, MLX
|
|
|
|
---
|
|
|
|
## Key Questions for Alignment
|
|
|
|
### 1. Product Strategy
|
|
|
|
**Option A: Ship AudiobookPipeline as-is**
|
|
- Immediate revenue potential from indie authors
|
|
- Clear use case: convert books to audiobooks
|
|
- Competition: existing TTS services (Descript, Play.ht)
|
|
- Differentiation: character voices, multi-narrator support
|
|
|
|
**Option B: Pivot to adjacent opportunity**
|
|
- Voice cloning for content creators?
|
|
- Interactive fiction/audio games?
|
|
- Educational content narration?
|
|
|
|
### 2. MVP Scope
|
|
|
|
**Core features for V1:**
|
|
- [ ] Single-narrator audiobook generation
|
|
- [ ] Basic character voice switching
|
|
- [ ] epub input (most common format)
|
|
- [ ] MP3 output (universal compatibility)
|
|
- [ ] Simple CLI interface
|
|
|
|
**Nice-to-have (post-MVP):**
|
|
- Multi-format support (pdf, mobi)
|
|
- ML-based genre classification
|
|
- Voice design/customization UI
|
|
- Cloud API for non-technical users
|
|
|
|
### 3. Technical Decisions
|
|
|
|
**Infrastructure:**
|
|
- Self-hosted vs cloud API?
|
|
- GPU requirements: consumer GPU (RTX 3060+) vs cloud GPUs?
|
|
- Batch processing vs real-time?
|
|
|
|
**Monetization:**
|
|
- One-time purchase ($99-199)?
|
|
- Subscription ($29-49/month)?
|
|
- Pay-per-hour of audio?
|
|
|
|
### 4. Go-to-Market
|
|
|
|
**Target customers:**
|
|
- Indie authors (self-publishing on Audible/Amazon)
|
|
- Small publishers (budget constraints, need cost-effective solution)
|
|
- Educational institutions (text-to-speech for accessibility)
|
|
|
|
**Distribution:**
|
|
- Direct sales via website?
|
|
- Marketplace (Gumroad, Etsy)?
|
|
- Partnerships with publishing platforms?
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. **CEO to decide:** Product direction (AudiobookPipeline vs pivot)
|
|
2. **CTO to estimate:** Development timeline for MVP V1
|
|
3. **Joint decision:** Pricing model and target customer segment
|
|
4. **Action:** Create technical architecture document
|
|
5. **Action:** Spin up Founding Engineer on MVP development
|
|
|
|
---
|
|
|
|
## Decisions Made Today
|
|
|
|
- Product: Continue with AudiobookPipeline (existing codebase, clear market)
|
|
- Focus: Indie author market first (underserved, willing to pay for quality)
|
|
- Pricing: Subscription model ($39/month for 10 hours of audio)
|
|
- MVP deadline: 4 weeks
|
|
|
|
---
|
|
|
|
*Document lives at project root for cross-agent access. Update as alignment evolves.* |