# [Product name] — Product Plan

> A free template from PeterPlan (peterplan.co). Fill in what you can, in plain English, and
> delete anything that doesn't apply — but say so in a sentence ("No AI in this product",
> "No file uploads") rather than leaving it out. Replace everything in [square brackets].
> Upload the finished file as Markdown (.md) or paste it into a Word document.

## 1. The problem
- **Who it's for:** [the people who'll use it]
- **The problem:** [what's painful for them today, and what they do instead]
- **How you know it's real:** [interviews, a waitlist, people paying for a workaround, your own experience — and the numbers]

## 2. The first version
- **In the first version:** [the smallest list of features that proves the idea]
- **Not building yet:** [things you want eventually but are deliberately leaving out]
- **How you'll know it worked:** [a measurable target, e.g. "50 paying customers by June"]
- **What a user does, step by step:** [sign up → … → gets value]

## 3. Users and accounts
- **Who owns an account:** [one person each, or a shared team/household/company account]
- **Kinds of user:** [e.g. owner, staff, client — and what each can and can't do]
- **If accounts are shared:** [who manages them, who pays, who can invite people, what happens to someone's data when they leave]

## 4. Data
- **What you store:** [the main things, e.g. users, bookings, messages]
- **Personal or sensitive data:** [which items, and whether any are health, financial or about children]
- **Keeping and deleting:** [how long you keep it, and what happens when someone closes their account]

## 5. Outside services
- **Services you'll use:** [payments, email, AI, maps, other APIs — named or "to be chosen"]
- **Keeping them secure:** [e.g. "all calls are made from our server; keys are kept in the host's secret store"]

## 6. Build or buy
- **Stack:** [what you'll build with, and why]
- **Anything that already exists as a product:** [e.g. scheduling, e-signatures — and why you're building rather than buying]

## 7. AI (or "No AI in this product")
- **What it does:** [the job the AI does]
- **What it sees:** [the data sent to it, and whether the provider keeps or trains on it]
- **Checking its output:** [how you catch wrong or unsafe answers before they reach users]

## 8. Security
- **Logging in:** [how people sign in]
- **Keeping data separate:** [how the server checks each person only sees and changes their own data]
- **Secrets and admin:** [where keys are kept; how admin access is protected]
- **File uploads (or "No uploads"):** [allowed types and sizes; private storage; scanning anything others will open]

## 9. Speed and scale
- **Slow or heavy features:** [e.g. AI generation, video, imports — background or while the user waits?]
- **Busy periods:** [launch day, seasonal peaks, and how you'll cope]

## 10. Reliability
- **When a service is down:** [what users see, and what retries or fallbacks happen]
- **Backups:** [how often, and how you'd restore]
- **Knowing it's broken:** [error alerts, uptime monitoring]

## 11. Building and releasing
- **Who writes the code:** [you, a developer, AI coding tools]
- **Checks before users see a change:** [tests, code review, a test copy of the site]
- **Undoing a bad release:** [how]

## 12. Rules that apply
- **Where your users are:** [countries]
- **Rules you know about:** [e.g. UK GDPR; anything for health, money, children or employment data]

## 13. Pricing and costs
- **Prices:** [tiers and what each includes]
- **What each user costs you:** [AI, storage, SMS, paid APIs — and any caps]
- **Payments that fail, cancellations, refunds:** [what users keep, and for how long]

## 14. Abuse
- **What someone might game:** [free tiers, referrals, shared links, content others see]
- **Simple protections:** [one or two]

## 15. Launch
- **When:** [target date]
- **How many users:** [rough numbers for the first 3 and 12 months]
- **Support:** [who answers, how users reach you, how fast]