Why this matters
Pricing and login need to land together because access should map cleanly to each Stripe plan before real usage starts. If the billing model is vague, the product can still launch, but every future usage limit, upgrade path, and support answer becomes harder to reason about.
The first version does not need a complicated pricing system. It needs a clear boundary between free testing, paid usage, and future team access.
Implementation notes
The Stripe setup should start with a small number of plans and a single source of truth for entitlement checks. Authentication can then attach each user or workspace to the correct plan without spreading billing logic through the app.
- Create Stripe products and prices
- Add login before gated features
- Store the active plan on the account record
- Keep limits readable inside the product UI
Open questions
The main decision is whether the first paid version should charge by document volume, seats, or a simple monthly plan. For now, a simple monthly plan is easier to explain and easier to support while usage patterns are still forming.