Introduction

MVPurr is a comprehensive project studio designed to help founders move from idea to MVP efficiently. By leveraging AI, we automate the initial technical scaffolding and roadmap planning that typically takes weeks.

How it works

The process is simple:

1. Create a new project workspace.
2. Describe your idea to the AI assistant.
3. Review the generated roadmap and technical specs.
4. Start building with your auto-generated tasks.

Core Concepts

• Project: the top‑level workspace for a product or experiment.
• Chat: your AI partner. Prompts create artifacts (Tasks, Docs, Events, Assets).
• Tasks: the execution plan, tracked via Kanban (To do / In progress / Done).
• Documents: long‑form strategy (README, PRDs, briefs) saved to a permanent vault.
• Calendar: milestones, meetings and launch countdown (with reminders).
• Assets: domains, servers, and subscriptions; renewal reminders and burn tracking.

Architecture at a Glance

• Frontend: Next.js App Router + Tailwind, componentized per feature.
• API: Next.js routes (REST) backed by Drizzle ORM.
• Database: Postgres (Projects, Tasks, Docs, Assets, Calendar).
• AI Tools: Chat invokes tools (saveStartupDocument, generateTodos, saveAssets, saveCalendarEvent).

Data Model (Simplified)

Project(id, name, description, context)
TodoItem(id, projectId, title, status, priority, dueDate, type, typeData)
StartupDoc(id, projectId, title, type, content)
Asset(id, projectId, type, name, url, cost, renewalDate, status)
CalendarEvent(id, projectId, title, date, type)

Roles & Permissions

Role	Can Edit	Can View
Owner	Everything	Everything
Member	Tasks, Docs, Assets, Events	Everything
Public	—	Public Tasks (read‑only)

Limits & Best Practices

• Chat context: keep one goal per thread. Extract artifacts every 5–10 messages.
• Kanban hygiene: only 3 items “In progress” at once (WIP limit).
• Docs: save finalized copies to the vault; use README.md for handoffs.
• Calendar: every launch needs at least one prep review event.